Thanks for the quick reply. But I want to come back first about the identical system a friend of my is using only with the xl driver for his public interface. But today he told me when pinging to a host like ping -s 4096 www.bart.nl and meanwhile enjoying the sound from the digitally imported shoutcast server, the 'no buffer space messages reappeared.
So he has the same problem only using the xl driver… But he was also complaining about that the problem never occurred in FreeBSD 4.4 or 4.3.. But some other info, we also had trouble with our connections. First of all we both used natd and ipfw also we connected our BSD boxes with GIF. When playing games natd always ended up using a lot of proctime like top indicated about 60 to 90%. The connection suffered from it and as result packet loss 100% and no recovery at all, I had to restart mpd and stuff. So ok, what’s wrong? With my experience I could not find any errors even when using natd in verbose mode. All I could see was lot’s of translations ;-) But trying ipnat what seemed to be more stable gave me more hope, but now I’m suffering from no buffer space available, so to problem persists and at the end we are still losing the connection and mass packet loss… I really want to make a point, is it third party software ‘mpd-3.7 Multi-link PPP daemon based on netgraph(4)’ that is causing this or is it something in the TCP/IP stack of BSD that is changed or the driver support. We had these problems in 4.3, 4.4 and still in 4.5. From using mpd 3.1 to 3.7 nothing changed about our problem. I think it’s an important notice why this is happening, because what if this is a real TCP/IP stack issue this would be very wrong and bad for FreeBSD. But I’m still no expert so I have to leave this open for the Pro BSD users/developers. Bye, Marcel To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-net" in the body of the message
