Date: Mon, 14 Dec 2009 11:52:47 -0800 From: Kurt Buff <kurt.buff@gmail.com> To: Jack Vogel <jfvogel@gmail.com> Cc: freebsd-net@freebsd.org Subject: Re: Not seeing data on an unnumbered interface... Message-ID: <a9f4a3860912141152l116f4e7aw38f4495adb0b5554@mail.gmail.com> In-Reply-To: <2a41acea0912141148y409453efj3cfc827723ec6fa8@mail.gmail.com> References: <a9f4a3860912141129v28af3f13x1f9e9ae725ff5170@mail.gmail.com> <2a41acea0912141135k35a4bd1fi8f727aaf19a188ec@mail.gmail.com> <a9f4a3860912141139p516a6345p56cf513462387e72@mail.gmail.com> <2a41acea0912141148y409453efj3cfc827723ec6fa8@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
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@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@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@gmail.com> wrote: >> > Not familiar with ntop, but I notice below that the em interface is no= t >> > UP, >> > what >> > if you `ifup em0` ? >> > >> > Jack >> > >> > >> > On Mon, Dec 14, 2009 at 11:29 AM, Kurt Buff <kurt.buff@gmail.com> wrot= e: >> >> >> >> 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'v= e >> >> 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@almeida.cse.buffalo.edu:/usr/obj/usr/src/sys/GENERIC =C2=A0i386 >> >> >> >> # cat /etc/rc.conf >> >> hostname=3D"zntop.mycompany.com" >> >> ifconfig_rl0=3D"DHCP" >> >> ntpdate_enable=3D"YES" >> >> ntpdate_flags=3D"-b 192.168.10.191" >> >> sshd_enable=3D"YES" >> >> ntop_enable=3D"YES" >> >> ntop_flags=3D"-d -u ntop -P /home/ntop/databases -K -L -t 6 -o -i em0= -W >> >> 0" >> >> >> >> zntop# ifconfig >> >> em0: flags=3D8902<BROADCAST,PROMISC,SIMPLEX,MULTICAST> metric 0 mtu 1= 500 >> >> =C2=A0 =C2=A0 =C2=A0 =C2=A0options=3D9b<RXCSUM,TXCSUM,VLAN_MTU,VLAN_H= WTAGGING,VLAN_HWCSUM> >> >> =C2=A0 =C2=A0 =C2=A0 =C2=A0ether 00:1b:21:04:2a:c5 >> >> =C2=A0 =C2=A0 =C2=A0 =C2=A0media: Ethernet autoselect (100baseTX <ful= l-duplex>) >> >> =C2=A0 =C2=A0 =C2=A0 =C2=A0status: active >> >> rl0: flags=3D8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mt= u >> >> 1500 >> >> =C2=A0 =C2=A0 =C2=A0 =C2=A0options=3D8<VLAN_MTU> >> >> =C2=A0 =C2=A0 =C2=A0 =C2=A0ether 00:0c:46:b3:43:53 >> >> =C2=A0 =C2=A0 =C2=A0 =C2=A0inet 192.168.24.51 netmask 0xffffff00 broa= dcast 192.168.24.255 >> >> =C2=A0 =C2=A0 =C2=A0 =C2=A0media: Ethernet autoselect (100baseTX <ful= l-duplex>) >> >> =C2=A0 =C2=A0 =C2=A0 =C2=A0status: active >> >> lo0: flags=3D8049<UP,LOOPBACK,RUNNING,MULTICAST> metric 0 mtu 16384 >> >> =C2=A0 =C2=A0 =C2=A0 =C2=A0options=3D3<RXCSUM,TXCSUM> >> >> =C2=A0 =C2=A0 =C2=A0 =C2=A0inet6 fe80::1%lo0 prefixlen 64 scopeid 0x3 >> >> =C2=A0 =C2=A0 =C2=A0 =C2=A0inet6 ::1 prefixlen 128 >> >> =C2=A0 =C2=A0 =C2=A0 =C2=A0inet 127.0.0.1 netmask 0xff000000 >> >> >> >> >> >> Kurt >> >> _______________________________________________ >> >> freebsd-net@freebsd.org mailing list >> >> http://lists.freebsd.org/mailman/listinfo/freebsd-net >> >> To unsubscribe, send any mail to "freebsd-net-unsubscribe@freebsd.org= " >> > >> > > >
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?a9f4a3860912141152l116f4e7aw38f4495adb0b5554>