Billion 8800NL R2: Difference between revisions
Content deleted Content added
CrazyTeeka (talk | contribs) m Sync Rate Capping |
→PPP session ID cache bug 'packet accelerator': clean up, typos fixed: Broadcom based → Broadcom-based |
||
| (5 intermediate revisions by 2 users not shown) | |||
| Line 14: | Line 14: | ||
|192.168.1.254 |
|192.168.1.254 |
||
|} |
|} |
||
==Chipset== |
|||
Broadcom 63381 |
|||
==Factory Reset== |
==Factory Reset== |
||
| Line 19: | Line 22: | ||
==Firmware== |
==Firmware== |
||
Various releases of firmware can be found at the: |
|||
[http://www.billion.uk.com/esupport/index.php?/Knowledgebase/ |
[http://www.billion.uk.com/esupport/index.php?/Knowledgebase/List/Index/119 Bipac 8800NL R2 Support site] |
||
==Bridge Setup== |
==Bridge Setup== |
||
| Line 42: | Line 46: | ||
**Wireless: Disable |
**Wireless: Disable |
||
**Click Apply |
**Click Apply |
||
==Sync Rate Capping== |
|||
The 8800NL has a feature that allows you to cap the Sync Rate of the DSL line. In this example we use 40M down, 10M up, then the third number is the total of the first two numbers. |
|||
*telnet 192.168.1.254 |
|||
*admin |
|||
*admin |
|||
*adsl configure --maxDataRate 40000 10000 50000 |
|||
==WiFi Client Limit of 16== |
==WiFi Client Limit of 16== |
||
| Line 66: | Line 63: | ||
==PPP session ID cache bug 'packet accelerator'== |
==PPP session ID cache bug 'packet accelerator'== |
||
One problem we see with Broadcom |
One problem we see with Broadcom-based routers is that they have an |
||
internal feature which is a 'packet accelerator' which causes problems when a PPPoE session finishes and a new one starts. |
internal feature which is a 'packet accelerator' which causes problems when a PPPoE session finishes and a new one starts. |
||
Ethernet frames containing IP packets with the same source and destination IP and port |
Ethernet frames containing IP packets with the same source and destination IP and port |
||