7800DXL - Bridge mode & snmp / internet led

[Arkoth]

If I set the 7800DXL in bridge mode:
- snmp doesn't work
- internet led doesn't work but internet is ok on my router/lan

[billion_fan]

While the 7800DXL is set to “Bridging mode” , the Internet LED will not light up, as the device behind the 7800DXL (connecting via pppoe) is establishing the PPP connection not the 7800DXL. So this is normal

SNMP works while in router mode. If your router is set to “Bridging mode” , only a LAN PC with Static IP Address can use the SNMP features. (directly connected to the 7800DXL)

[Arkoth]

Ok for the internet led, "it's normal"... so...




On the 7800DXL (static lan ip 192.168.1.254) :
- ethernet port 1 : link to my router (ewan port - bridge mode)
- ethernet port 3 : link to my netgear switch

On the router asus rt-ac68u (static lan ip 192.168.1.1):
- ethernet port ewan: link to 7800DXL pppoe (wan ip auto by isp)
- port 1 : link to my netgear switch

On my computer (static lan ip 192.168.1.40):
- ethernet port: link to my netgear switch

On my computer, I can access to the router by his ip for the web interface, same for the 7800DXL...
but snmp don't work; yes it works when the 7800DXL is in "router mode" but why not in "bridge mode" ?

I buy a router because 7800DXL has wifi problems and crash the modem randomly and I don't want to wait a new firmware in hope it will be solve a day ( viewtopic.php?f=18&t=3471 ) because the problem exist since 2013; you've asked to me to try your beta firmware 2.32d.dr1 which don't solve the wifi / crash and break the snmp in "router mode" if you remember... so I flash with the old 2.32d_da1 to have snmp in "router mode"...
For information, I have no wifi problem with my new router for wifi now, amazing isn't it ?!... but now I loose the snmp for the 7800DXL because it's in bridge mode

Billion is a joke

[billion_fan]

Ok for the internet led, "it's normal"... so...




On the 7800DXL (static lan ip 192.168.1.254) :
- ethernet port 1 : link to my router (ewan port - bridge mode)
- ethernet port 3 : link to my netgear switch

On the router asus rt-ac68u (static lan ip 192.168.1.1):
- ethernet port ewan: link to 7800DXL pppoe (wan ip auto by isp)
- port 1 : link to my netgear switch

On my computer (static lan ip 192.168.1.40):
- ethernet port: link to my netgear switch

On my computer, I can access to the router by his ip for the web interface, same for the 7800DXL...
but snmp don't work; yes it works when the 7800DXL is in "router mode" but why not in "bridge mode" ?

I buy a router because 7800DXL has wifi problems and crash the modem randomly and I don't want to wait a new firmware in hope it will be solve a day ( viewtopic.php?f=18&t=3471 ) because the problem exist since 2013; you've asked to me to try your beta firmware 2.32d.dr1 which don't solve the wifi / crash and break the snmp in "router mode" if you remember... so I flash with the old 2.32d_da1 to have snmp in "router mode"...
For information, I have no wifi problem with my new router for wifi now, amazing isn't it ?!... but now I loose the snmp for the 7800DXL because it's in bridge mode

Billion is a joke

See attached screen shots, of SNMP feature working while in bridge mode (this test was performed off the latest firmware) also attached

dh52 has increased one to one NAT entries from 8 to 16

[Arkoth]

I flash 7800DXL with your firmware 2.32d.dh52:


in mode bridge:


snmp settings (like you):


the test... on the same OID like you:

on cacti: CMDPHP: Poller[0] Host[3] DS[30] WARNING: Result from SNMP not valid. Partial Result: U

I test with my router which have snmp too... and you know what ? it works on my router...


=> my lan/wan is ok, my settings too, 7800DXL don't work in snmp mode bridge here...
you're very lucky Billion if it works for you

[billion_fan]

I flash 7800DXL with your firmware 2.32d.dh52:


in mode bridge:


snmp settings (like you):


the test... on the same OID like you:

on cacti: CMDPHP: Poller[0] Host[3] DS[30] WARNING: Result from SNMP not valid. Partial Result: U

I test with my router which have snmp too... and you know what ? it works on my router...


=> my lan/wan is ok, my settings too, 7800DXL don't work in snmp mode bridge here...
you're very lucky Billion if it works for you

Anything funny listed within the system log once SNMP fails??

[Arkoth]

Jan 1 00:00:10 daemon warn kernel: Broadcom Forwarding Assist Processor (FAP) Char Driver v0.1 Feb 10 2015 21:26:35 Registered <241>
Jan 1 00:00:10 daemon warn kernel: Enabling SMISBUS PHYS_FAP_BASE[0] is 0x14001000
Jan 1 00:00:10 daemon warn kernel: FAP Soft Reset Done
Jan 1 00:00:10 daemon warn kernel: 4ke Reset Done
Jan 1 00:00:10 daemon warn kernel: FAP Debug values at 0xac89c810 0xac89c810
Jan 1 00:00:10 daemon warn kernel: Allocated FAP0 GSO Buffers (0xAC8AD898) : 1048576 bytes @ 0xAC900000
Jan 1 00:00:10 daemon warn kernel: Allocated FAP0 TM SDRAM Queue Storage (ac8ad89c) : 341376 bytes @ aca00000
Jan 1 00:00:10 daemon warn kernel: ^[[0;34m[NTC fapProto] fapReset : Reset FAP Protocol layer^[[0m
Jan 1 00:00:10 daemon warn kernel: [FAP0] DSPRAM : stack <0x80004000><1536>, global <0x80004600><3760>, free <2896>, total<8192>
Jan 1 00:00:10 daemon warn kernel: [FAP0] PSM : addr<0xE0010000>, used <24216>, free <8552>, total <32768>
Jan 1 00:00:10 daemon warn kernel: fapDrv_construct: FAP0: pManagedMemory=b1010650. wastage 8 bytes
Jan 1 00:00:10 daemon warn kernel: [FAP0] DQM : availableMemory 14652 bytes, nextByteAddress 0xE00045F8
Jan 1 00:00:10 daemon warn kernel: [FAP0] GSO Buffer set to 0xAC900000
Jan 1 00:00:10 daemon warn kernel: [FAP0] FAP BPM Initialized.
Jan 1 00:00:10 daemon warn kernel: bcmPktDma_bind: FAP Driver binding successfull
Jan 1 00:00:10 daemon warn kernel: [FAP0] FAP TM: ON
Jan 1 00:00:10 daemon warn kernel: bcmxtmcfg: bcmxtmcfg_init entry
Jan 1 00:00:10 daemon warn kernel: adsl: adsl_init entry
Jan 1 00:00:10 daemon warn kernel: Broadcom BCM6362B0 Ethernet Network Device v0.1 Feb 10 2015 21:27:07
Jan 1 00:00:10 daemon warn kernel: fapDrv_psmAlloc: fapIdx=0, size: 4800, offset=b1010650 bytes remaining 7000
Jan 1 00:00:10 daemon warn kernel: ETH Init: Ch:0 - 200 tx BDs at 0xb1010650
Jan 1 00:00:10 daemon warn kernel: fapDrv_psmAlloc: wastage 8 bytes
Jan 1 00:00:10 daemon warn kernel: fapDrv_psmAlloc: fapIdx=0, size: 4808, offset=b1011910 bytes remaining 2184
Jan 1 00:00:10 daemon warn kernel: ETH Init: Ch:0 - 600 rx BDs at 0xb1011910
Jan 1 00:00:10 daemon warn kernel: dgasp: kerSysRegisterDyingGaspHandler: bcmsw registered
Jan 1 00:00:10 daemon warn kernel: eth0: MAC Address: 60:03:47:05:C8:0D
Jan 1 00:00:10 daemon warn kernel: eth1: MAC Address: 60:03:47:05:C8:0D
Jan 1 00:00:10 daemon warn kernel: eth2: MAC Address: 60:03:47:05:C8:0D
Jan 1 00:00:10 daemon warn kernel: eth3: MAC Address: 60:03:47:05:C8:0D
Jan 1 00:00:10 daemon warn kernel: ^[[0;34m[NTC arl] arlEnable : Enabled ARL binding to FAP^[[0m
Jan 1 00:00:10 daemon warn kernel: Broadcom Address Resolution Logic Processor (ARL) Char Driver v0.1 Feb 10 2015 21:26:33 Registered <245>
Jan 1 00:00:10 daemon warn kernel: --SMP support
Jan 1 00:00:10 daemon warn kernel: wl: dsl_tx_pkt_flush_len=338
Jan 1 00:00:10 daemon warn kernel: wl: high_wmark_tot=12298
Jan 1 00:00:10 daemon debug kernel: PCI: Setting latency timer of device 0000:00:00.0 to 64
Jan 1 00:00:10 daemon warn kernel: wl: passivemode=1
Jan 1 00:00:10 daemon warn kernel: wl: napimode=0
Jan 1 00:00:10 daemon warn kernel: wl0: allocskbmode=1 currallocskbsz=512
Jan 1 00:00:10 daemon warn kernel: Neither SPROM nor OTP has valid image
Jan 1 00:00:10 daemon warn kernel: wl:srom/otp not programmed, using main memory mapped srom info(wombo board)
Jan 1 00:00:10 daemon warn kernel: wl:loading /etc/wlan/bcm6362_map.bin
Jan 1 00:00:10 daemon warn kernel: srom rev:8
Jan 1 00:00:10 daemon warn kernel: wl: reading /etc/wlan/bcmcmn_nvramvars.bin, file size=32
Jan 1 00:00:10 daemon warn kernel: wl0: Broadcom BCM435f 802.11 Wireless Controller 6.30.102.7.cpe4.12L08.4
Jan 1 00:00:10 daemon warn kernel: dgasp: kerSysRegisterDyingGaspHandler: wl0 registered
Jan 1 00:00:10 daemon warn kernel: PCI: Enabling device 0000:02:00.0 (0000 -> 0002)
Jan 1 00:00:10 daemon debug kernel: PCI: Setting latency timer of device 0000:02:00.0 to 64
Jan 1 00:00:10 daemon warn kernel: wl: passivemode=1
Jan 1 00:00:10 daemon warn kernel: wl: napimode=0
Jan 1 00:00:10 daemon warn kernel: wl1: allocskbmode=1 currallocskbsz=3500
Jan 1 00:00:10 daemon warn kernel: Neither SPROM nor OTP has valid image
Jan 1 00:00:10 daemon warn kernel: wl:srom/otp not programmed, using main memory mapped srom info(wombo board)
Jan 1 00:00:10 daemon warn kernel: wl:loading /etc/wlan/bcm43228_map.bin
Jan 1 00:00:10 daemon warn kernel: srom rev:8
Jan 1 00:00:10 daemon warn kernel: wl: reading /etc/wlan/bcmcmn_nvramvars.bin, file size=32
Jan 1 00:00:10 daemon warn kernel: wl1: Broadcom BCMa8dc 802.11 Wireless Controller 6.30.102.7.cpe4.12L08.4
Jan 1 00:00:10 daemon warn kernel: dgasp: kerSysRegisterDyingGaspHandler: wl1 registered
Jan 1 00:00:10 daemon warn kernel: Loading DECT Shim driver
Jan 1 00:00:10 daemon warn kernel: Initialize DECT Shim layer....
Jan 1 00:00:10 daemon warn kernel: p8021ag: p8021ag_init entry
Jan 1 00:00:10 daemon info kernel: Broadcom 802.1Q VLAN Interface, v0.1
Jan 1 00:00:10 daemon warn kernel: usb r:0
Jan 1 00:00:11 daemon warn kernel: wait instruction: disabled
Jan 1 00:00:11 daemon warn kernel: Ethernet Auto Power Down and Sleep is disabled
Jan 1 00:00:11 daemon warn kernel: Energy Efficient Ethernet is disabled
Jan 1 00:00:11 daemon info kernel: ip_tables: (C) 2000-2006 Netfilter Core Team
Jan 1 00:00:12 daemon info kernel: ip6_tables: (C) 2000-2006 Netfilter Core Team
Jan 1 00:00:12 daemon warn kernel: Netfilter messages via NETLINK v0.30.
Jan 1 00:00:13 daemon info kernel: device eth0 entered promiscuous mode
Jan 1 00:00:13 daemon info kernel: ADDRCONF(NETDEV_UP): eth0: link is not ready
Jan 1 00:00:15 daemon info kernel: device eth1 entered promiscuous mode
Jan 1 00:00:15 daemon info kernel: ADDRCONF(NETDEV_UP): eth1: link is not ready
Jan 1 00:00:18 daemon info kernel: device eth2 entered promiscuous mode
Jan 1 00:00:18 daemon info kernel: ADDRCONF(NETDEV_UP): eth2: link is not ready
Jan 1 00:00:21 daemon info kernel: device eth3 entered promiscuous mode
Jan 1 00:00:21 daemon info kernel: ADDRCONF(NETDEV_UP): eth3: link is not ready
Jan 1 00:00:24 daemon warn kernel: *** dslThread dslPid=781
Jan 1 00:00:24 daemon warn kernel: BcmAdsl_Initialize=0xC0211E2C, g_pFnNotifyCallback=0xC02478A4
Jan 1 00:00:24 daemon warn kernel: pSdramPHY=0xAFFFFFF8, 0x1B783F 0xDEADBEEF
Jan 1 00:00:24 daemon warn kernel: *** XfaceOffset: 0x21F90 => 0x21F90 ***
Jan 1 00:00:24 daemon warn kernel: *** PhySdramSize got adjusted: 0x8D394 => 0xA2E88 ***
Jan 1 00:00:24 daemon warn kernel: AdslCoreSharedMemInit: shareMemSize=381261(381264)
Jan 1 00:00:24 daemon warn kernel: AdslCoreHwReset: pLocSbSta=8a568000 bkupThreshold=1600
Jan 1 00:00:24 daemon warn kernel: AdslCoreHwReset: AdslOemDataAddr = 0xAFF82044
Jan 1 00:00:24 daemon warn kernel: ***BcmDiagsMgrRegisterClient: 0 ***
Jan 1 00:00:24 daemon warn kernel: dgasp: kerSysRegisterDyingGaspHandler: dsl0 registered
Jan 1 00:00:24 daemon warn kernel: fapDrv_psmAlloc: fapIdx=0, size: 1600, offset=b1012be0 bytes remaining 584
Jan 1 00:00:24 daemon warn kernel: XTM Init: 200 rx BDs at 0xb1012be0
Jan 1 00:00:24 daemon warn kernel: fapDrv_psmAlloc: fapIdx=0, size: 128, offset=b1013220 bytes remaining 456
Jan 1 00:00:24 daemon warn kernel: XTM Init: 16 rx BDs at 0xb1013220
Jan 1 00:00:24 daemon warn kernel: nf_conntrack version 0.5.0 (4080 buckets, 32640 max)
Jan 1 00:00:26 daemon info kernel: xt_time: kernel timezone is -0000
Jan 1 00:00:26 daemon info kernel: monitor task is initialized pid= 338
Jan 1 00:00:28 user info syslog: WLAN Schedule Control on wl0 exit
Jan 1 00:00:32 user info syslog: WLAN Schedule Control on wl1 exit
Jan 1 00:00:33 daemon crit kernel: eth1 (switch port: 3) Link UP 1000 mbps full duplex
Jan 1 00:00:33 daemon crit kernel: eth3 (switch port: 1) Link UP 1000 mbps full duplex
Jan 1 00:00:33 daemon info kernel: ADDRCONF(NETDEV_CHANGE): eth3: link becomes ready
Jan 1 00:00:33 daemon info kernel: br0: bridge group port 4(eth3) entering forwarding state
Jan 1 00:00:33 daemon info kernel: ADDRCONF(NETDEV_CHANGE): eth1: link becomes ready
Jan 1 00:00:33 daemon info kernel: br0: bridge group port 2(eth1) entering forwarding state
Jan 1 00:00:39 daemon crit kernel: Line 0: ADSL G.992 started
Jan 1 00:00:41 daemon crit kernel: Line 0: ADSL G.992 channel analysis
Jan 1 00:00:46 daemon crit kernel: Line 0: ADSL link down
Jan 1 00:00:58 daemon crit kernel: Line 0: ADSL G.992 started
Jan 1 00:01:01 daemon crit kernel: Line 0: ADSL G.992 channel analysis
Jan 1 00:01:05 daemon crit kernel: Line 0: ADSL G.992 message exchange
Jan 1 00:01:05 daemon crit kernel: Line 0: ADSL link up, interleaved, us=800, ds=7424
Jan 1 00:01:05 daemon warn kernel: bcmxtmcfg: XTM Link Information, port = 0, State = UP, Service Support = ATM
Jan 1 00:01:05 daemon warn kernel: bcmxtmrt: MAC address: 60 03 47 05 c8 10
Jan 1 00:01:05 daemon warn kernel: [DoCreateDeviceReq.3269]: register_netdev
Jan 1 00:01:05 daemon warn kernel: [DoCreateDeviceReq.3271]: register_netdev done
Jan 1 00:01:05 daemon warn kernel: [FAP0] xtmCreateDevice : devId 0, encapType 0, headerLen 10
Jan 1 00:01:05 daemon warn kernel: bcmxtmrt: DSD(8a6e649c) - 128
Jan 1 00:01:05 daemon warn kernel: XTM Init: 400 tx BDs at 0xaa554000
Jan 1 00:01:05 daemon warn kernel: bcmxtmcfg: Connection UP, LinkActiveStatus=0x1, US=800000, DS=7424000
Jan 1 00:01:05 daemon warn kernel: [FAP0] xtmLinkUp : devId 0, matchId 0
Jan 1 00:01:06 daemon warn kernel: netdev path : atm0.1
Jan 1 00:01:06 daemon info kernel: ->
Jan 1 00:01:06 daemon info kernel: atm0
Jan 1 00:01:06 daemon warn kernel: BCMVLAN : atm0 mode was set to RG
Jan 1 00:01:06 daemon info kernel: device atm0.1 entered promiscuous mode
Jan 1 00:01:06 daemon info kernel: device atm0 entered promiscuous mode
Jan 1 00:01:06 daemon info kernel: br0: bridge group port 5(atm0.1) entering forwarding state
Jan 1 00:01:42 daemon warn kernel: snmpd/837: potentially unexpected fatal signal 11.
Jan 1 00:01:42 daemon warn kernel: Cpu 0
Jan 1 00:01:42 daemon warn kernel: $ 0 :
Jan 1 00:01:42 daemon info kernel: 00000000
Jan 1 00:01:42 daemon info kernel: 00000001 0042dab0
Jan 1 00:01:42 daemon info kernel: 000009a4
Jan 1 00:01:42 daemon warn kernel: $ 4 : 0042dab0
Jan 1 00:01:42 daemon info kernel: 00000000
Jan 1 00:01:42 daemon info kernel: 00000014
Jan 1 00:01:42 daemon info kernel: 00000200
Jan 1 00:01:42 daemon warn kernel: $ 8 :
Jan 1 00:01:42 daemon info kernel: 00000014
Jan 1 00:01:42 daemon info kernel: 00000000 00000031
Jan 1 00:01:42 daemon info kernel: 00000000
Jan 1 00:01:42 daemon warn kernel: $12 : 00000000
Jan 1 00:01:42 daemon info kernel: 00000000 00000000
Jan 1 00:01:42 daemon info kernel: 00000000
Jan 1 00:01:42 daemon warn kernel: $16 : 0042ccf4
Jan 1 00:01:42 daemon info kernel: 0042c0d4
Jan 1 00:01:42 daemon info kernel: 00000000
Jan 1 00:01:42 daemon info kernel: 2aeba000
Jan 1 00:01:42 daemon warn kernel: $20 : 00402328
Jan 1 00:01:42 daemon info kernel: 2ae98230 7fc84138
Jan 1 00:01:42 daemon info kernel: 00407e70
Jan 1 00:01:42 daemon warn kernel: $24 : 00000001
Jan 1 00:01:42 daemon info kernel: 2ae98230
Jan 1 00:01:42 daemon info kernel:
Jan 1 00:01:42 daemon warn kernel: $28 : 004351b0
Jan 1 00:01:42 daemon info kernel: 7fc81fa0
Jan 1 00:01:42 daemon info kernel: 7fc81fa0 00415764
Jan 1 00:01:42 daemon warn kernel: Hi : 00000000
Jan 1 00:01:42 daemon warn kernel: Lo : 00000046
Jan 1 00:01:42 daemon warn kernel: epc : 2ae9827c 0x2ae9827c
Jan 1 00:01:42 daemon warn kernel: Tainted: P
Jan 1 00:01:42 daemon warn kernel: ra : 00415764 0x415764
Jan 1 00:01:42 daemon warn kernel: Status: 00008d13
Jan 1 00:01:42 daemon info kernel: USER
Jan 1 00:01:42 daemon info kernel: EXL IE
Jan 1 00:01:42 daemon warn kernel: Cause : 00000008
Jan 1 00:01:42 daemon warn kernel: BadVA : 00000000
Jan 1 00:01:42 daemon warn kernel: PrId : 0002a070 (Broadcom4350)
Jan 1 00:48:06 daemon warn kernel: snmpd/17292: potentially unexpected fatal signal 11.
Jan 1 00:48:06 daemon warn kernel: Cpu 0
Jan 1 00:48:06 daemon warn kernel: $ 0 :
Jan 1 00:48:06 daemon info kernel: 00000000
Jan 1 00:48:06 daemon info kernel: 00000001 0042dab0 0000002d
Jan 1 00:48:06 daemon warn kernel: $ 4 : 0042dab0
Jan 1 00:48:06 daemon info kernel: 00000000 00000014 00000200
Jan 1 00:48:06 daemon warn kernel: $ 8 : 00000014 00000000
Jan 1 00:48:06 daemon info kernel: 00000021 00000000
Jan 1 00:48:06 daemon warn kernel: $12 : 00000001
Jan 1 00:48:06 daemon info kernel: 2ab34bc6
Jan 1 00:48:06 daemon info kernel: 00401d14
Jan 1 00:48:06 daemon info kernel: 2ab342c8
Jan 1 00:48:06 daemon warn kernel: $16 : 0042ccf4
Jan 1 00:48:06 daemon info kernel: 0042c0d4 00000000
Jan 1 00:48:06 daemon info kernel: 2aeba000
Jan 1 00:48:06 daemon warn kernel: $20 : 00402328
Jan 1 00:48:06 daemon info kernel: 2ae98230 7fff49d8
Jan 1 00:48:06 daemon info kernel: 00407e70
Jan 1 00:48:06 daemon warn kernel: $24 : 2ab32bc8
Jan 1 00:48:06 daemon info kernel: 2ae98230
Jan 1 00:48:06 daemon info kernel:
Jan 1 00:48:06 daemon warn kernel: $28 : 004351b0
Jan 1 00:48:06 daemon info kernel: 7fff2840 7fff2840
Jan 1 00:48:06 daemon info kernel: 00415764
Jan 1 00:48:06 daemon warn kernel: Hi : 0000009b
Jan 1 00:48:06 daemon warn kernel: Lo : 000c8b73
Jan 1 00:48:06 daemon warn kernel: epc : 2ae9827c 0x2ae9827c
Jan 1 00:48:06 daemon warn kernel: Tainted: P
Jan 1 00:48:06 daemon warn kernel: ra : 00415764 0x415764
Jan 1 00:48:06 daemon warn kernel: Status: 00008d13 USER EXL IE
Jan 1 00:48:06 daemon warn kernel: Cause : 00000008
Jan 1 00:48:06 daemon warn kernel: BadVA : 00000000
Jan 1 00:48:06 daemon warn kernel: PrId : 0002a070 (Broadcom4350)

=>

Jan 1 00:01:42 daemon warn kernel: snmpd/837: potentially unexpected fatal signal 11.

[Arkoth]

and I'm not alone...

http://forums.whirlpool.net.au/archive/2286737
viewtopic.php?f=19&t=3173

for information: reboot modem don't solve the snmpd crash...

it's like the wifi problem which crash randomly the modem...
maybe a day your firmware will be without bug

[billion_fan]

and I'm not alone...

http://forums.whirlpool.net.au/archive/2286737
viewtopic.php?f=19&t=3173

for information: reboot modem don't solve the snmpd crash...

it's like the wifi problem which crash randomly the modem...
maybe a day your firmware will be without bug

Issue reported to our engineers, I will drop a update in due course

[Arkoth]

still no news ?