If you like BoxMatrix then please contribute Supportdata, Supportdata2, Firmware and/or Hardware (get in touch).
My metamonk@yahoo.com is not reachable by me since years. Please use hippie2000@webnmail.de instead.

0
U

Property:lan0

From BoxMatrix
(Redirected from lan0)


BoxMatrix >> System >> lan0 @ BoxMatrix   -   IRC-Chat   -   Translate: de es fr it nl pl
News Selectors Models Accessories Components Environment Config Commands System Webif Software Develop Lexicon Community Project Media

Devices Filesystems Partitions Sockets Netlink Pipes Interfaces Bridges Ports Events Sources Sinks AVMIPC Processes Watchdogs Memory Slab Vmalloc ProcFS SysFS Research

Network-Interface

Goto:   Dependencies   -   Model-Matrix   -   Missing Supportdata   -   SMW-Browser

Details

lan0 is the internal ARM modem interface on Puma6 / Puma7 models.
It is the CMCI (Cable Modem to CPE Interface) ISP configuration interface, which is routed to a separate virtual connection.
It has the hardcoded IP 192.168.100.1 (defined by the DOCSIS specification) and uses the usb_rndis_mac MAC address.

It serves the ATOM Webinterface on Port-80-tcp and Port-443-tcp, which is proxied by pumaglued.
Optionally Port-8089-tcp could be forwarded for TR-069, also proxied by pumaglued.
Besides this snmp_agent_cm is also listening on this IP, on Port-161-udp and Port-162-udp.

Excerpt from showdsldstat of a DOCSIS connection with separate virtual connections for inet, voip and lan0:

2: name lan0 (attached)
2: sync_group: sync_lan0
2: iface lbr0 RBE/32/dsl e2:4b:a7:xx:xx:xx (local) stay online 1
2: IPv6: off
2: IPv4: native
2: IPv4: connected since 2022-05-11 13:49:39 (setup time 67 secs) (connect cnt 3)
2: IPv4: disconnect prevention disabled
2: IPv4: ip 192.168.100.2 mask 255.255.255.0 gw 0.0.0.0 mtu 1500
2: IPv4: masqaddr 192.168.100.2
2: route 192.168.100.0/24 protocol iface
2: RX bytes:0 pkt error:0 discard:0 filtered:0 dropped:0
2: RX pkts:0 unicast:0 multicast:0 broadcast:0
2: TX bytes:0 pkt error:0 discard:0 filtered:0 dropped:0
2: TX pkts:0 unicast:0 multicast:0 broadcast:0

RBE is routed bridge encapsulation, a Cisco implementation of bridged Ethernet over ATM with a separate broadcast domain
for every ATM circuit. It provides the multiplexing of the virtial connections.

Connections 0: (inet) and 1: (voip) use the sync_group sync_cable and both route to the erouter0 interface.
Connections 2: (lan0) uses the sync_group sync_lan0 and "routes" to the lbr0 interface, the lan0 bridge.

Dependencies

Daily updated index of all dependencies of this interface. Last update: GMT.
A * in the Mod column marks info from Supportdata-Probes, which will always stay incomplete.
A ** in the Mod column marks info from Supportdata2 probes, which by their nature will stay way more incomplete.
A - in the Mod column marks manual research, the Firmware then shows where the item occurs, not the Relation.

Relation Typ Object Mod Firmware Info Origin
0 dependencies for this interface

Model-Matrix

Daily updated index of the presence, path and size of this interface for each model. Last update: 2024-03-29 07:09 GMT.
Showing all models using this interface. Click any column header (click-wait-click) to sort the list by the respective data.
The (main/scrpn/boot/arm/prx/atom) label in the Model column shows which CPU is meant for models with multiple Linux instances.
Note that this list comes from Supportdata-Probes, which can have arbitrary settings and come from different firmware versions.
It doesn't say much if a model is not listed here. It may be a missing supportdata file or just a disabled feature.

Missing Supportdata

The data in this article is incomplete due to missing Supportdata-Probes for the models listed below.
If you own any of these models and would like to help then please get in touch.

SMW-Browser

Information is currently being retrieved from the backend.