Not seeing data on an unnumbered interface...

[Kurt Buff]

Heh.

Not a problem.

Kurt

On Mon, Dec 14, 2009 at 11:57, Jack Vogel <jfvogel at gmail.com> wrote:
> Hmmm, well there's a LOT of shared code changes between 7.1 and 8, and this
> sounds like something in the device init.  I don't really have time to look
> into the
> difference right now,  you'll just have to live with the difference, sorry
> :)
>
> Jack
>
>
> On Mon, Dec 14, 2009 at 11:52 AM, Kurt Buff <kurt.buff at gmail.com> wrote:
>>
>> Interesting.
>>
>> I'm doing nothing really very different on my 7.1R box, but don't have
>> this issue.
>>
>> Oh, well - just something to keep in mind, I suppose.
>>
>> Kurt
>>
>> On Mon, Dec 14, 2009 at 11:48, Jack Vogel <jfvogel at gmail.com> wrote:
>> > Usually assigning an address will bring it up, but you arent doing that,
>> > I
>> > am
>> > pretty sure using a pseudo device will always necessitating explicitly
>> > bringing
>> > it up, at least i know that is the case for VLANs also.
>> >
>> > Jack
>> >
>> >
>> > On Mon, Dec 14, 2009 at 11:39 AM, Kurt Buff <kurt.buff at gmail.com> wrote:
>> >>
>> >> Sigh. Yes, that works.
>> >>
>> >> So, to expose even more of my ignorance, any thoughts on why it isn't
>> >> up at boot?
>> >>
>> >> Kurt
>> >>
>> >> On Mon, Dec 14, 2009 at 11:35, Jack Vogel <jfvogel at gmail.com> wrote:
>> >> > Not familiar with ntop, but I notice below that the em interface is
>> >> > not
>> >> > UP,
>> >> > what
>> >> > if you `ifup em0` ?
>> >> >
>> >> > Jack
>> >> >
>> >> >
>> >> > On Mon, Dec 14, 2009 at 11:29 AM, Kurt Buff <kurt.buff at gmail.com>
>> >> > wrote:
>> >> >>
>> >> >> All,
>> >> >>
>> >> >> I'm having a very strange problem. I'm running ntop - the unnumbered
>> >> >> interface is not receiving any data.
>> >> >>
>> >> >> Running 'tcpdump -i em0' also gets no data. I am really baffled -
>> >> >> I've
>> >> >> tried it against a switch that I know has a correctly configured
>> >> >> mirror port, as I have ntop running on another machine and that
>> >> >> works
>> >> >> fine in the same port, but it's running 7.1-RELEASE.
>> >> >>
>> >> >> Anyone have thoughts on this?
>> >> >>
>> >> >>
>> >> >> # uname -a
>> >> >> FreeBSD zntop.mycompany.com 8.0-RELEASE FreeBSD 8.0-RELEASE #0: Sat
>> >> >> Nov 21 15:48:17 UTC 2009
>> >> >> root at almeida.cse.buffalo.edu:/usr/obj/usr/src/sys/GENERIC  i386
>> >> >>
>> >> >> # cat /etc/rc.conf
>> >> >> hostname="zntop.mycompany.com"
>> >> >> ifconfig_rl0="DHCP"
>> >> >> ntpdate_enable="YES"
>> >> >> ntpdate_flags="-b 192.168.10.191"
>> >> >> sshd_enable="YES"
>> >> >> ntop_enable="YES"
>> >> >> ntop_flags="-d -u ntop -P /home/ntop/databases -K -L -t 6 -o -i em0
>> >> >> -W
>> >> >> 0"
>> >> >>
>> >> >> zntop# ifconfig
>> >> >> em0: flags=8902<BROADCAST,PROMISC,SIMPLEX,MULTICAST> metric 0 mtu
>> >> >> 1500
>> >> >>        options=9b<RXCSUM,TXCSUM,VLAN_MTU,VLAN_HWTAGGING,VLAN_HWCSUM>
>> >> >>        ether 00:1b:21:04:2a:c5
>> >> >>        media: Ethernet autoselect (100baseTX <full-duplex>)
>> >> >>        status: active
>> >> >> rl0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu
>> >> >> 1500
>> >> >>        options=8<VLAN_MTU>
>> >> >>        ether 00:0c:46:b3:43:53
>> >> >>        inet 192.168.24.51 netmask 0xffffff00 broadcast
>> >> >> 192.168.24.255
>> >> >>        media: Ethernet autoselect (100baseTX <full-duplex>)
>> >> >>        status: active
>> >> >> lo0: flags=8049<UP,LOOPBACK,RUNNING,MULTICAST> metric 0 mtu 16384
>> >> >>        options=3<RXCSUM,TXCSUM>
>> >> >>        inet6 fe80::1%lo0 prefixlen 64 scopeid 0x3
>> >> >>        inet6 ::1 prefixlen 128
>> >> >>        inet 127.0.0.1 netmask 0xff000000
>> >> >>
>> >> >>
>> >> >> Kurt
>> >> >> _______________________________________________
>> >> >> freebsd-net at freebsd.org mailing list
>> >> >> http://lists.freebsd.org/mailman/listinfo/freebsd-net
>> >> >> To unsubscribe, send any mail to
>> >> >> "freebsd-net-unsubscribe at freebsd.org"
>> >> >
>> >> >
>> >
>> >
>
>