Hilko Meyer
2012-Apr-22 02:53 UTC
scanlogd doesnt start anymore after upgrade from 8.2 to 8.3 cause of USB
Hi, today I updated one server to 8.3. Now scanlod fails to start with some weird error message: root@falko:~> /usr/local/etc/rc.d/scanlogd start Starting scanlogd. pcap_compile: USB link-layer type filtering not implemented /usr/local/etc/rc.d/scanlogd: WARNING: failed to start scanlogd USB?!? Where does that come from? tcpdump seems affected too: root@falko:~> tcpdump tcpdump: WARNING: usbus0: no IPv4 address assigned tcpdump: unsupported data link type USB Any ideas about the reason? regards, Hilko
Claudius
2012-Apr-22 03:18 UTC
scanlogd doesnt start anymore after upgrade from 8.2 to 8.3 cause of USB
If you are using packet filter, echo hw.usb.no_pf=1 >>/boot/loader.conf http://lists.freebsd.org/pipermail/freebsd-stable/2012-January/065421.html Hope this helps. -- regards Claudius On 22/04/12 04:21, Hilko Meyer wrote:> Hi, > > today I updated one server to 8.3. Now scanlod fails to start with some > weird error message: > root@falko:~> /usr/local/etc/rc.d/scanlogd start > Starting scanlogd. > pcap_compile: USB link-layer type filtering not implemented > /usr/local/etc/rc.d/scanlogd: WARNING: failed to start scanlogd > > USB?!? Where does that come from? tcpdump seems affected too: > root@falko:~> tcpdump > tcpdump: WARNING: usbus0: no IPv4 address assigned > tcpdump: unsupported data link type USB > > Any ideas about the reason? > > regards, > Hilko > _______________________________________________ > freebsd-stable@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-stable > To unsubscribe, send any mail to "freebsd-stable-unsubscribe@freebsd.org"
Hilko Meyer
2012-Apr-22 15:47 UTC
scanlogd doesnt start anymore after upgrade from 8.2 to 8.3 cause of USB
Claudius wrote:>If you are using packet filter, >echo hw.usb.no_pf=1 >>/boot/loader.conf > >http://lists.freebsd.org/pipermail/freebsd-stable/2012-January/065421.html > >Hope this helps.Thanks! | echo hw.usb.no_pf=1 >>/boot/loader.conf did the trick. That helped. I'm a bit puzzled to see a disrupive change like this merged to a Stable-branch without a heads-up and without documentation how to disable it. regards, hilko PS: forgot to mention I'm not subsricbed to this list. Please keep me CCed.