Difference between revisions of "Billion 8800NL R2"

Jump to navigation Jump to search
2,352 bytes added ,  23:51, 17 August 2018
→‎PPP session ID cache bug 'packet accelerator': clean up, typos fixed: Broadcom based → Broadcom-based
(Created page with "We started testing out this router Feb 2017. Below are some notes. ==Default Settings== {|class="wikitable" !colspan="2"|Default/Factory Settings |- !Username: |admin |- !Pa...")
 
(→‎PPP session ID cache bug 'packet accelerator': clean up, typos fixed: Broadcom based → Broadcom-based)
 
(18 intermediate revisions by 3 users not shown)
We started testing out this router Febin February 2017. Below are some notes.
 
==Default Settings==
|192.168.1.254
|}
 
==Chipset==
Broadcom 63381
 
==Factory Reset==
With the router powered on, hold down the RESET button until the PWR light changes colour (RED), then release.
 
==Firmware==
Various releases of firmware can be found at the:
 
[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==
 
[[Category:AA Routers]]
 
==Support for Baby Jumbo frames (1508)==
This was a standard feature in the original BT supplied ECI and Huawei modems. This means that a PPP ethernet router which supports RFC 4638 can
run with an MTU of 1500.
 
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'==
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.
Ethernet frames containing IP packets with the same source and destination IP and port
combination that were used in the previous session are received with the
PPPoE Session-ID from the earlier session.
 
Our understanding of this, having talked to Huawei is that the problem
is with the 'packet accelerator' feature in the Broadcom chipset. It is
caching frame headers including the PPPoE Session-ID, but not checking
if the Session-ID is the same when searching for the entry in the cache
for subsequent packets. Unplugging the ethernet cable momentarily
resolves the problem - that action must trigger a cache flush in the
Broadcom chipset.
 
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)
608

edits

Navigation menu