User:TonyHoyle/Billion Trial: Difference between revisions
Content deleted Content added
No edit summary |
No edit summary |
||
| Line 37: | Line 37: | ||
* If you're using non-NAT the only way to allow LAN administration of the router is to enable 'Remote access control' and add your internal IP range as the list of allowed addresses. It should be able to say 'everything over br0' or something similar. |
* If you're using non-NAT the only way to allow LAN administration of the router is to enable 'Remote access control' and add your internal IP range as the list of allowed addresses. It should be able to say 'everything over br0' or something similar. |
||
* It would be nice if it contained the standard mss clamping line in the firewall that most routers do, so you don't have to enable TCPFix manually. |
* It would be nice if it contained the standard mss clamping line in the firewall that most routers do, so you don't have to enable TCPFix manually. |
||
* The router |
* The router negotiates the wrong MTU! |
||
BE Accept 0.0.0.0 77.89.165.67 tmhth0@a.1 b.gormless Via=BE BE MAC=0004EDDBA1CD Unknown circuit TCP-MRU-fix txrate=20257000bps*85% linerate=1000000000/1000000000 MTU=1500 |
BE Accept 0.0.0.0 77.89.165.67 tmhth0@a.1 b.gormless Via=BE BE MAC=0004EDDBA1CD Unknown circuit TCP-MRU-fix txrate=20257000bps*85% linerate=1000000000/1000000000 MTU=1500 |
||
This means TCPFix doesn't work, and anything that sends packets >1492 breaks. MTU of the ppp connection is clearly 1492 so no idea where it's getting 1500 from. |
This means TCPFix doesn't work, and anything that sends packets >1492 breaks. MTU of the ppp connection is clearly 1492 so no idea where it's getting 1500 from. |
||