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 !
Upgrade 1.0.8-1 only partially solves my "silicon bug&q
Hi David,
Currently we are fairly certain about why the traffic was dropped, but we are struggeling to reproduce your setup in order to actually verify that our solution works.
What was your setup when you got the MTU of 576 of you WAN port?
Bubba connected directly to your cable modem?
And if you connected your windows(?) PC directly did that get 1500 as MTU?
In other words bubba and your PC did not get the same MTU?
/PA
Currently we are fairly certain about why the traffic was dropped, but we are struggeling to reproduce your setup in order to actually verify that our solution works.
What was your setup when you got the MTU of 576 of you WAN port?
Bubba connected directly to your cable modem?
And if you connected your windows(?) PC directly did that get 1500 as MTU?
In other words bubba and your PC did not get the same MTU?
/PA
With my Bubba directly connected to my cable modem I got an MTU of 576 on the eth0 (WAN) side.pa wrote:Hi David,
Currently we are fairly certain about why the traffic was dropped, but we are struggeling to reproduce your setup in order to actually verify that our solution works.
What was your setup when you got the MTU of 576 of you WAN port?
Bubba connected directly to your cable modem?
And if you connected your windows(?) PC directly did that get 1500 as MTU?
In other words bubba and your PC did not get the same MTU?
/PA
With my PC directly connected the PC got a MTU of 1500.
If I connected the bubba via a router it got 1500 on the eth0 side.
Hi David,
When you connect your bubba directly to your and get the MTU of 576, could you try to run the commands (as root):
iptables -A INPUT -p icmp -m icmp --icmp-type 3/4 -j ACCEPT
iptables -A FORWARD -p icmp -m icmp --icmp-type 3/4 -j ACCEPT
This will open up the capabilites for bubba to talk to other routers for in order to fragment tcp packets.
The difference between Bubba and your PC could be that Bubba ask your router for which MTU to use, which is not always the case in all systems.
The router then provides the MTU of 576, but since it obviously can handle 1500, I would say that reporting this value is incorrect, but it should be handled in any case by Bubba.
However, since the larger MTU does work this is the preferable setting to use since larger packets most likely will give you a better performace on your internet connection.
I order to ignore the MTU reported by your modem (or more accurate, not ask for it), edit the file "/etc/dhcp3/dhclient.conf" and remove from the request "interface-mtu".
So there are two solutions for this, one is to allow the communications for regarding fragmentation, which would be the correct solution, the other one is for tweaking speeds. However this is not something that we feel comfortable with shipping, since this actually is a workaroung for limitations/bugs in other systems that we can not control.
/PA, Excito.
When you connect your bubba directly to your and get the MTU of 576, could you try to run the commands (as root):
iptables -A INPUT -p icmp -m icmp --icmp-type 3/4 -j ACCEPT
iptables -A FORWARD -p icmp -m icmp --icmp-type 3/4 -j ACCEPT
This will open up the capabilites for bubba to talk to other routers for in order to fragment tcp packets.
The difference between Bubba and your PC could be that Bubba ask your router for which MTU to use, which is not always the case in all systems.
The router then provides the MTU of 576, but since it obviously can handle 1500, I would say that reporting this value is incorrect, but it should be handled in any case by Bubba.
However, since the larger MTU does work this is the preferable setting to use since larger packets most likely will give you a better performace on your internet connection.
I order to ignore the MTU reported by your modem (or more accurate, not ask for it), edit the file "/etc/dhcp3/dhclient.conf" and remove from the request "interface-mtu".
So there are two solutions for this, one is to allow the communications for regarding fragmentation, which would be the correct solution, the other one is for tweaking speeds. However this is not something that we feel comfortable with shipping, since this actually is a workaroung for limitations/bugs in other systems that we can not control.
/PA, Excito.
Thanks for this. I will try it this evening and report back.pa wrote:Hi David,
When you connect your bubba directly to your and get the MTU of 576, could you try to run the commands (as root):
iptables -A INPUT -p icmp -m icmp --icmp-type 3/4 -j ACCEPT
iptables -A FORWARD -p icmp -m icmp --icmp-type 3/4 -j ACCEPT
This will open up the capabilites for bubba to talk to other routers for in order to fragment tcp packets.
/PA, Excito.
I presume that this must happen after each disconnect/reconnect on eth0 (e.g. an unplug or restart), just as the ifconfig workaround did.
I have tried, as an alternative, setting my eth1 to 576 and did experience the slow-down you referred to.
The following fix did not work, I'm sorry to say.
The following fix does work - after a reboot the MTU is 1500 and I can internet OK
By chance I had a power cut this afternoon, so my Bubba had rebooted on return of power into it's boot-up state. I ran the above 2 commands (by cut and paste) but could not access the internet from my PC.pa wrote: iptables -A INPUT -p icmp -m icmp --icmp-type 3/4 -j ACCEPT
iptables -A FORWARD -p icmp -m icmp --icmp-type 3/4 -j ACCEPT
The following fix does work - after a reboot the MTU is 1500 and I can internet OK
pa wrote:
In order to ignore the MTU reported by your modem (or more accurate, not ask for it), edit the file "/etc/dhcp3/dhclient.conf" and remove from the request "interface-mtu".