Billion 8800NL R2: Difference between revisions
Appearance
Content deleted Content added
CrazyTeeka (talk | contribs) mNo edit summary |
→PPP session ID cache bug 'packet accelerator': clean up, typos fixed: Broadcom based → Broadcom-based |
||
| (12 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== |
|||
How to setup the 8800NL R2 as a Bridge: |
|||
*Configuration -> WAN -> WAN Service |
|||
**Edit ptm0.1 |
|||
**Type: Bridging |
|||
**Description: br_0_1_0.101 |
|||
**802.1P Priority: 0 |
|||
**802.1Q VLAN ID: 101 |
|||
**Click Apply |
|||
*Configuration -> LAN -> Interface Grouping |
|||
**Groups Isolation: Enable |
|||
**Click Apply |
|||
**Click Add |
|||
**Group Name: Bridge |
|||
**Grouped WAN Interfaces: ptm0.1 |
|||
**Grouped LAN Interfaces: P5/EWAN |
|||
**Click Apply |
|||
*Configuration -> Wireless -> Basic |
|||
**Wireless: Disable |
|||
**Click Apply |
|||
==WiFi Client Limit of 16== |
==WiFi Client Limit of 16== |
||
| Line 34: | Line 59: | ||
We're not yet sure if the 8800NL supports an MTU of 1508, but we have asked (February 2017) |
We're not yet sure if the 8800NL supports an MTU of 1508, but we have asked (February 2017) |
||
One of our customers reports that the 8800NL R2 doesn't support Baby Jumbo frames when tested in bridge mode using firmware 2.52.d1 (March 2017) |
|||
==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 |
||
| Line 51: | Line 78: | ||
We're not yet sure if the 8800NL has this 'feature' enabled, but we have asked (February 2017) |
We're not yet sure if the 8800NL has this 'feature' enabled, but we have asked (February 2017) |
||
One of our customers also reports that the 8800NL R2 doesn't appear to have this bug (March 2017) |
|||