User:TonyHoyle/Billion Trial: Difference between revisions

From AAISP Support Site
No edit summary
No edit summary
 
(One intermediate revision by the same user not shown)
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 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
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.

Latest revision as of 15:49, 28 Mayıs 2011

Billion trial notes

The Good

ipv6 worked perfectly out of the box!

The Bad

  • Quick start : no way to enter username or password? Not clear how to change from 0/38 from that screen - suggest a setup button.
  • Can't use pppoe on the first profile as something internal is trying to force 1500 MTU even though the MTU on the profile is set to 1492 (its default).
 Jan 01 00:02:07  daemon  pppd[624]: Couldn't increase MTU to 1500.
 Jan 01 00:02:07  daemon  pppd[624]: Couldn't increase MRU to 1500
 Jan 01 00:02:07  daemon  pppd[624]: Couldn't increase MRU to 1500

More detailed logs from the busybox command line (that alas I forgot to keep) show it warns about this a couple of times then aborts the entire login.

This makes the router unusable on Be without hacks...

A workaround is to leave the first profile as shipped and add a second profile for pppoe - this allows connect - *however* it fails to set the default route on login, leaving you with a nonfunctional connection. A side effect of this is each time the connection drops you must go in and manually re-add the default route.. which is problematic if you're accessing remotely (ipv6 may be a workaround in this case.. not had to try this yet).

  • The pppd shipped looks ancient and probably doesn't support mini jumbos - worth prodding them about this!
  • Setting static ipv6 routes, if gateway is link local you get the error 'Interface should be selected since gateway ipv6 address is link local' even if the interface is in fact already selected.
  • vlan config is very odd. Enabling vlan 4 on port 1 enables it on all ports except ewan and wlan. Enabling it on ewan locks out all access to the device requiring a factory reset. It should be possible to designate a port to vlan tag without affecting the other ports.
  • There is no way to give each vlan a separate IP address that I can see.. only config for the main IP and an 'alias' IP.
  • As above for ipv6.
  • Can't enable remote access filters for ipv6 - screen explicity says 'ipv4 only'.
  • Packet filter v6 configuration is insane - it expects ranges not netmasks!
  • The session time out is too fast.. several times it timed out on me as I was entering data.
  • The 'there is one user logged' error is bloody annoying. Suggest a button on to override (kicking the existing user off if necessary).
  • 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.
  • 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

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.