Please note the new address for this forum : forum.excito.org. The old address redirects here but I don't know for how long. Thanks !
New user's registration have been closed due to high spamming and low trafic on this forum. Please contact forum admins directly if you need an account. Thanks !
Eek wrote:hmm looks like DNS resolves,
but TCP connection fails
or NAT doesn't work
what is your setup?
internet connection direct into B2?
or internet -> router -> B2 ?
internet > wireless router
router > bubba LAN port
router > PC etc.
bubba configuration is for automatic IP assignment for both WAN and LAN.
Cable modems are sometimes using a bit "non-standard" but within specifications for the mtu setting. In the next upgrade there is a fix that hopefully will solve that problem.
Cable modems are sometimes using a bit "non-standard" but within specifications for the mtu setting. In the next upgrade there is a fix that hopefully will solve that problem.
/PA, Excito
Thanks for the suggestion. My ADSL modem is built in to the wireless router so I don't know if it's applicable. I tried these two commands anyway and it doesn't seem to help
I noted that you tried the workaround for the silicon bug, but can I ask you to run it once again (on LAN).
ethtool --offload eth1 rx off tx off
If you have rebooted bubba, this setting is not remembered. Usually this bug is not a problem on the LAN, but if your router does change the ports used in the communiation with bubba and the outside world, it is possible that this error can pass through the router.
/PA.
PS. If this solution works for you, update the software then edit the file /etc/init.d/disable-offload to disable offload on eth1 instead of eth0. This edit will make the workaround permanent.
I noted that you tried the workaround for the silicon bug, but can I ask you to run it once again (on LAN).
ethtool --offload eth1 rx off tx off
Thanks again for the help. I rebooted bubba and ran the command above as root but apt-get update and wget www.google.com still time out as before. I wonder if an
Flushing the iptables chains will actually render bubba inaccessible, so do not do that!
The default policy of the input chain is to drop all incoming packets, so withouthe rules all packets will be dropped!
I have send an email to you, please read this and come back to me.
Many thanks to PA for tracking this down. It appears to be a problem with tcp checksumming on certain routers. The solution for my bubba behind a speedtouch 716 router was to
connect to bubba over SSH (there's a free SSH program called 'putty' for windows)
become root with the command: 'su' and root password (excito by default)
Type the following command and press Enter (no output is printed to the screen):
I do think that this is a problem related to that the router does not handle tcp window scaling correctly. Disabling tcp checks in the router also made the system work, but altering the router configuration is not anything easyly done, finding this setting was quite tricky.
Also, note that for this workaround to take permanently this setting has to be added to /etc/sysctl.conf otherwise it will be lost at reboot.