This may seem impossible but I have been working for over three weeks on a FreeBSD machine setup as a gateway. Several times during the day, Internet access from the internal network just stops. No DNS, no pings, nothing. After a few minutes, it comes back.
I have tried ALTQ with priq, cbq and finally hfsc. I have tried kernels with and without device polling. Finally, today we got a good HFSC configuration and were in the middle of a test with some heavy Internet traffic when the problem came up again.
netstat -id showed no drop packets.
netstat -m looked ok.
I could ping yahoo.com from the gateway but not from the internal network. On the gateway, tcpdump showed the packets coming in on the internal interface but nothing going out on the external interface.
When I toogled packet forwarding (sysctl -w net.inet.ip.forwarding=0 / sysctl -w net.inet.ip.forwarding=1), the problem disappears.
I am running FreeBSD 7.2-p6 with a Marvel NIC (msk0) as the internal interface and a D-Link NIC (rl0) as the external one.
I am curious. Has anyone else seen this problem or has any idea where I can start looking for why packet forwarding is hanging?
I have tried ALTQ with priq, cbq and finally hfsc. I have tried kernels with and without device polling. Finally, today we got a good HFSC configuration and were in the middle of a test with some heavy Internet traffic when the problem came up again.
netstat -id showed no drop packets.
netstat -m looked ok.
I could ping yahoo.com from the gateway but not from the internal network. On the gateway, tcpdump showed the packets coming in on the internal interface but nothing going out on the external interface.
When I toogled packet forwarding (sysctl -w net.inet.ip.forwarding=0 / sysctl -w net.inet.ip.forwarding=1), the problem disappears.
I am running FreeBSD 7.2-p6 with a Marvel NIC (msk0) as the internal interface and a D-Link NIC (rl0) as the external one.
I am curious. Has anyone else seen this problem or has any idea where I can start looking for why packet forwarding is hanging?