On Mon, 21 Apr 2008, Jannik Sültz wrote: [snip] > DUMMYNET initialized (011031) > vr2: rx packet lost > usb0: 1 scheduling overruns > vr2: rx packet lost [snip] A probably unhelpful WAG, bit it seems like interrupts are being lost or packets not being worked off fast enough. Try a google for 'freebsd "rx packet lost"' (include the double quotes).
> arplookup 169.254.xxx.xxx failed: host is not on local network My least favorite address range, forever showing up in my ACL logs. Usually a Windows box that either has a second interface that is unused and needs to be disabled or failed to reach a DHCP server the last time its network interface bounced. Possibly the later if m0n0wall is serving your DHCP. > arp: 192.168.xxx.xxx moved from xx:xx:xx:xx:xx:xx to xx:xx:xx:xx:xx:xx > on vr0 > arp: 192.168.xxx.xxx moved from xx:xx:xx:xx:xx:xx to xx:xx:xx:xx:xx:xx > on vr0 This is a bit more interesting as it implies you have two NICs using the same IP address, or have a team/bond/aggregated link pair misconfigured. It could also indicate someone trying to do some ARP cache poisoning. Were you able to try 1.3 as suggested to you on the m0n0wall board? While you wouldn't think something would change in the software or hardware after a few months, if you live in the northern hemisphere and aren't running the Soekris in a data center with serious cooling, the Soekris' ambient temperature probably went up. This could lead to changed timing where a race condition no longer ends in your favor. -Jed _______________________________________________ Soekris-tech mailing list [email protected] http://lists.soekris.com/mailman/listinfo/soekris-tech
