Netgear test thread

[andy m]

dump i have gave you were from my ambit 300 an alpha 1.1 is working on mine now

[Canis-Major]

I have no doubt in your dump's, pmsl, but eth is disabled, I enabled all those DOCSIS Modules, and got a lock, ip's and everything, but eth is still off.. it's not my nic, I have tested it on 3.. it's this damn modem, and I dont yet know where to look to try enabling it myself..

[andy m]

throw it out

---

give up on tht modem find some thing else to use got a 6580 here bcm 3380 chip set

[Canis-Major]

Now why do that when I can gain experience in setting it back up manually? Do you really give in so easily?

[daviddds]

how is it "off", is it not showing up in console? can you post a copy of the dmesg/bootlog, i've seen ubee's do that disabled/disabled shit when they are corrupted nvram.. but a full reflash with a ubee image should fix it, if you dont have an image, let me know what model it is..

[Canis-Major]

If I knew how it was off, it would'nt be.. but if all docsis modules were switched off, when supposed to be on, (are they supposed to all be off?) I spent all night reading sbh, and I blame them, for only year's later do even they discover the 6120 is NOT an ubee.. my model is vmng300v2 model: edm3528 (u10c035 rev.0 gp). With regard's to firmware's I have, or 8mb dump's, it has crossed my mind that most folks would have written/copied these dumps using the 6120 xml, which is actually wrong, and probably the cause of the problem.

I can only assume an 8mb would fix it if it was the CORRECT xml used, and not made up from a 6120 motorola board, since cert locations were changed.. so 6120 copies for a v2 ubee is a no-no. Unless they are as identical as sbh had many believe for years.. craziest thing is, Even though my 8mb was corrupted, I have succesfully rekr8'ed (lol) the nvram, by restoring env1 and env2, from another dump, OVER a reflash of the corrupt 8mb I posted, cert's etc look good, but if you ask me, it's as if any possible option has been set to off.. I actually suspect dhcp has been removed, because my modem get's an ip on a d1 20 golden mac, but no fucking ethernet appear's FOR my pc.

Log's.. wow.. it's like, one thing to learn puma, another to discover we need bash, and another to discover that in these modems, dont even ask for the find command, cause I never saw it.. never mind where/how to set dhcp.. and half the command's/directories either dont work, or wont run. Seems anything coming from sbh is as corrupt as they deserve to be..

to daviddds, thanks for the offer, but since I'm a complete noob to puma, and I cant trust 6120 firmwares, (due to sbh's later admission they were wrong) and dont know if I have an ACTUAL 8mb backup of a V2 vmng300, (not v1) I find it difficult at best right now to log anything other than a serial boot, and even then, with origional firmware's, wonder how anyone could repair the ORIGIONAL 8mb, which aint exactly corrupt, apart from having the start of each tab (usbjatgnt software) deleted.. (powered off when mistake realised) hence why I was able to recover the cert's/serials etc..

The eth switched off after trying to restore from an sbh alpha 1.1 flash, and I aint the only one to experience this, it has been mentioned on sbh by other people, but not one single fuckin solution.

Hi sbh, can I load sbh alpha 1.1 onto my ubee v2? Yeah, it's basically a 6120, use usbjtag to create backup, and dont tell anyone the 6120.xml will be different from the u10c035 xml..

Hi sbh, I have an ubee.. yo, use 6120.. is that xml, or firmware? neither, it's the alpha 1.1.. idiot's.. can I use u10c035.xml?

So here's the best bit.. decided to load only u10c035 8mb (v1) I got from another dude, into usbjtagnt to save nvram.. guess what.. saved nvram corrupted.. identically to mine. When I load all flash, it is fine, switch to nvram, it's fine, but when I click save, half the nvram is gone, it is NOT being saved correctly by USBJTAGNT software, Fact!! That's a warning to you all by the way.. daviddds, look back a few posts, the 8mb I posted should be more than enough if you know your stuff, pray tell me what's wrong.. I loaded it, then corrected u-boot, env1 + 2, and both ubfi's, left blank and nvram alone, rebooted, and got in. log's wont do jack shit if the eth cant be logged, but I'll post one after I walk the dog..

Remember.. usbjtag now corrupt's SAVED backup's. I aint paid to troubleshoot for them considering dictapone's attitude..

[andy m]

how comes when i read and save my dumps using 6230 or u10c35 xml writer back to the shanion they all work ano ethernet light does comes as ano never works anyways but a can still get an ip address go into putty change the mac address

[Canis-Major]

Log of a working dump:

From andym:


  a300 a1.1.txt (Size: 34.71 KB / Downloads: 22)

Has it occured to you andy, that the isp can change ranges in modems with nothing more than a firmware update?

[andy m]

nothing wrong with it at all should work on yours

---

CM have you flashed back a stock dump

[Canis-Major]

Nothing wrong with 'it'? If you mean your files, I'm sure they're fine, said they're fine, and even told you what is wrong, I never once said anything about your files being wrong in anyway, so why am I answering a stuck record? To say what I say is wrong, as in address range's have been re-written in modem, by an old 6120 xml, since the ubee xml was not out at that time, and since updating usbjtag software, I now know why, that usbjtag SOFTWARE is no longer correctly saving nvram's when copied from loaded 8mb dump's, or backup's. Your one liner posts with no advice are becoming cumbersomeb to say the least.. tell me, how to repair address ranges in a modem that was flashed with wrong ones.. use an 8mb.. but if latest software from usbjtag has been messed with..?

Quite simply I need the directories REBUILT, since sbh's or Bad_Adz claim these are same as 6120's was later proven to be wrong.. 5 years of virgin handing these out, and no-one mentions them on most website's? Most likely because they were bricked beyond usefulness by the 6120 xml ranges, and since every ass kisser of sbh would 'support' sbh in SAYING the 6120 worked, which I'm sure it did back then, but would they know of certain files/dir's being deleted upon access to flash?

They should, I wrote it there in 2010.

Now please up an origional V2 <- yours is for 1!!!!!!!! (joke.. )

Tell em what is wrong in the log..?

---

Incidently, when I found where to put script I posted, the modem told me EXACTLY what is wrong, but in testing, I forgot where I left it, so away to find it.. ps, it works in scotland, yehaaa...

---

U-Boot 1.2.0 (Aug 29 2008 - 17:07:37)
6.1.1c

DRAM: 32 MB
Macronix MX25l6405D flash found
MXic Flash: Man id c2, Mem Type 20, Mem Density 17 {c2, 20}
Flash: 8 MB
In: serial
Out: serial
Err: serial


ver="U-Boot 1.2.0 (Aug 29 2008 - 17:07:37)
6.1.1c" unchanged

Press SPACE to abort autoboot in 3 second(s)
*** ACTIMAGE = 1, will try to boot UBFI1 stored @0x48040000
## Executing script at 48040000
============== Running script =========
*** Running from UBFI1 partition @0x48040000
Load address = 0x48040f9c (0xf9c)
Kernel address = 0x48040fe8 (0xfe8)
kernel size = 0xc7c18
FS address = 0x48108c00 (0xc8c00)
FS size = 0x226800
NVRAM offset = 0x7b0000
NVRAM size = 0x50000
*** UBFI1 bootscript executed successfully.
Start booting...
## Booting image at 48040f9c ...
Image Name: Multi Image File
Image Type: ARM Linux Multi-File Image (uncompressed)
Data Size: 3073060 Bytes = 2.9 MB
Load Address: 80a00000
Entry Point: 80a00000
Contents:
Image 0: 818200 Bytes = 799 kB
Image 1: 2254848 Bytes = 2.2 MB
Verifying Checksum ... OK
OK

Starting kernel ...

Starting LZMA Uncompression Algorithm.
Compressed file is LZMA format.
Linux version 2.6.18_pro500 (root@localhost.localdomain) (gcc version 4.2.0 20070126 (prerelease) (MontaVista 4.2.0-2.0.0.custom 2007-02-12)) #1 PREEMPT Thu Dec 3 11:59:44 CST 2009
CPU: ARMv6-compatible processor [410fb764] revision 4 (ARMv6TEJ), cr=00c538ff
Machine: puma5
Ignoring unrecognised tag 0x00000000
Memory policy: ECC disabled, Data cache writethrough
Reserved 0k DSP memory starting from Physical 0x82000000
CPU0: D VIPT write-back cache
CPU0: I cache: 32768 bytes, associativity 4, 32 byte lines, 256 sets
CPU0: D cache: 16384 bytes, associativity 4, 32 byte lines, 128 sets
Real-Time Preemption Support © 2004-2006 Ingo Molnar
Built 1 zonelists. Total pages: 8192
Kernel command line: root=/dev/mtdblock6 mtdparts=sfl0:0x20000(U-Boot)ro,0x10000(env1),0x10000(env2),0x3b0000@0x40000(UBFI1),0x3b0000@0x3f0000(UBFI2),0xc7c18@0x40fe8(Kernel),0x226800(RootFileSystem),0x50000@0x7b0000(nvram) console=ttyS0,115200n8 ethaddr0=00:01:02:03:04:05 usbhostaddr=
WARNING: experimental RCU implementation.
Interrupt controller revision : 4e822100
PID hash table entries: 256 (order: 8, 1024 bytes)
Power & Sleep Controller @ 0xd8621000 Initialized [id-0x44822905]
Initialized Peripheral Port Remap Register to base : 0x50000000
Puma5 Timer0 initialized
Dentry cache hash table entries: 4096 (order: 2, 16384 bytes)
Inode-cache hash table entries: 2048 (order: 1, 8192 bytes)
Memory: 32MB = 32MB total
Memory: 30040KB available (1840K code, 490K data, 76K init)
Mount-cache hash table entries: 512
CPU: Testing write buffer coherency: ok
NET: Registered protocol family 16
Off chip memory allocated: 153088
QMgr Init: buffer after alignment: 80340000
avalanche_ppd_init: PP system initialized successfully.
avalanche_ppd_init(494):return code 0x00
HIL Core: Profile intrusive has been Loaded.
NET: Registered protocol family 2
IP route cache hash table entries: 256 (order: -2, 1024 bytes)
TCP established hash table entries: 1024 (order: 3, 32768 bytes)
TCP bind hash table entries: 512 (order: 1, 14336 bytes)
TCP: Hash tables configured (established 1024 bind 512)
TCP reno registered
squashfs: version 3.3 (2007/10/31) Phillip Lougher
squashfs: LZMA suppport for slax.org by jro
JFFS2 version 2.2. (NAND) © 2001-2006 Red Hat, Inc.
Initializing Cryptographic API
io scheduler noop registered (default)
watchdog: TI Avalanche Watchdog Timer: timer margin 42 sec
TI LED driver initialized [major=254]
Serial: 8250/16550 driver $Revision: 1.90 $ 2 ports, IRQ sharing disabled
serial8250: ttyS0 at MMIO map 0x8610f03 mem 0xd8610f03 (irq = 8) is a TI 16550A
serial8250: ttyS1 at MMIO map 0x8610e03 mem 0xd8610e03 (irq = 7) is a TI 16550A
loop: loaded (max 8 devices)
Loading cpgmac driver for puma5
TI CPGMAC_F Linux DDA version 0.1 - CPGMAC_F DDC version 0.2
Cpmac: Installed 1 instances.
i2c /dev entries driver
Serial Flash [Bus:0 CS:0] : mx25l6405 8192KB, 128 sectors each 64KB
8 cmdlinepart partitions found on MTD device sfl0
partitions[0] = {.name = U-Boot, .offset = 0x00000000,.size = 0x00020000 (128K) }
partitions[1] = {.name = env1, .offset = 0x00020000,.size = 0x00010000 (64K) }
partitions[2] = {.name = env2, .offset = 0x00030000,.size = 0x00010000 (64K) }
partitions[3] = {.name = UBFI1, .offset = 0x00040000,.size = 0x003b0000 (3776K) }
partitions[4] = {.name = UBFI2, .offset = 0x003f0000,.size = 0x003b0000 (3776K) }
partitions[5] = {.name = Kernel, .offset = 0x00040fe8,.size = 0x000c7c18 (799K) }
partitions[6] = {.name = RootFileSystem, .offset = 0x00108c00,.size = 0x00226800 (2202K) }
partitions[7] = {.name = nvram, .offset = 0x007b0000,.size = 0x00050000 (320K) }
Creating 8 MTD partitions on "sfl0":
0x00000000-0x00020000 : "U-Boot"
0x00020000-0x00030000 : "env1"
0x00030000-0x00040000 : "env2"
0x00040000-0x003f0000 : "UBFI1"
0x003f0000-0x007a0000 : "UBFI2"
0x00040fe8-0x00108c00 : "Kernel"
mtd: partition "Kernel" doesn't start on an erase block boundary -- force read-only
0x00108c00-0x0032f400 : "RootFileSystem"
mtd: partition "RootFileSystem" doesn't start on an erase block boundary -- force read-only
0x007b0000-0x00800000 : "nvram"
Serial Flash [Bus:0 CS:1] : No device found
ti_spi.0: AVALANCHE SPI Controller driver at 0xd8612500 (irq = 0)
ti_codec_spi.0: TI Codec SPI Controller driver at 0xd86040c8 (irq = 0)
TCP bic registered
Initializing XFRM netlink socket
NET: Registered protocol family 1
NET: Registered protocol family 10
IPv6 over IPv4 tunneling driver
NET: Registered protocol family 17
NET: Registered protocol family 15
VFS: Mounted root (squashfs filesystem) readonly.
Freeing init memory: 76K

init started: BusyBox v1.4.2 (2009-12-03 12:01:34 CST) multi-call binary

init started: BusyBox v1.4.2 (2009-12-03 12:01:34 CST) multi-call binary

Starting pid 116, console /dev/tts/0: '/bin/sh'


========================================================
TI DSDK release 3.10.1205.
Build date: Thursday, December 03 2009, 12:12:13
Copyright © 2006 - 2008 Texas Instruments Incorporated
========================================================


+---------------------------------------------+
+-------------- FW Version Begin -------------+
IMAGE_NAME=dsdk-3.10.1205.-091203.img
VERSION=3.10.1205.
BOARD=tnetc550w
FSSTAMP=20091203124237
+-------------- FW Version End -------------+
+---------------------------------------------+
## Error: "CALIBRATION_MODE" not defined
[: 1: unknown operand
****************************
*** Running Normal Mode ***
****************************
Using DOCSIS Initialization process parameters: -ds_channels 4 -us_channels 4
+ setenvpcd: Starting TI Process Control Daemon.
pcd: Loaded 46 rules.
pcd: Initialization complete.
silent 0
pcd: Starting process /usr/sbin/watchdog_rt (Rule SYSTEM_WATCHDOG).
pcd: Starting process /usr/sbin/logger (Rule SYSTEM_LOGGER).
pcd: Rule SYSTEM_WATCHDOG: Success (Process /usr/sbin/watchdog_rt (212)).
TI Watchdog-RT daemon started <kick interval = 10 seconds>
+ utelnetd -l /bin/foxlogin -p 64623
+ echo enable
+ echo tdox

Starting pid 218, console /dev/tts/0: '/bin/sh'
pcd: Rule SYSTEM_LOGGER: Success (Process /usr/sbin/logger (213)).
telnetd: starting
port: 64623; interface: any; login program: /bin/foxlogin
TI Logger: Init complete
pcd: Starting process /usr/sbin/gptimer (Rule SYSTEM_GPTIMER).
pcd: Rule SYSTEM_GPTIMER: Success (Process /usr/sbin/gptimer (219)).
pcd: Rule SYSTEM_LASTRULE: Success.
pcd: Starting process echo (Rule DOCSIS_APPRUN).
pcd: Rule DOCSIS_APPRUN: Success (Process echo (224)).
pcd: Starting process /usr/sbin/docsis_init_once (Rule DOCSIS_INITONCE).
pcd: Starting process insmod (Rule DOCSIS_BRIDGE).
Dbridge MDF control init done
pcd: Rule DOCSIS_BRIDGE: Success (Process insmod (226)).
pcd: Starting process insmod (Rule DOCSIS_CNI).
pcd: Rule DOCSIS_CNI: Success (Process insmod (228)).


>>>
Console, CLI version 1.0.0.5
Type 'help' for list of commands

mainMenu> pcd: Rule DOCSIS_INITONCE: Success (Process /usr/sbin/docsis_init_once (225)).
pcd: Starting process /usr/sbin/ledd (Rule DOCSIS_LED).
pcd: Rule DOCSIS_LED: Success (Process /usr/sbin/ledd (233)).
pcd: Starting process insmod (Rule DOCSIS_HALVLYNQ).
pcd: Starting process /usr/sbin/cm_status (Rule DOCSIS_CMSTATUS).
VLYNQ driver initialization complete.
pcd: Rule DOCSIS_HALVLYNQ: Success (Process insmod (234)).
pcd: Starting process insmod (Rule DOCSIS_SOCIFDRV).
pcd: Rule DOCSIS_CMSTATUS: Success (Process /usr/sbin/cm_status (235)).
pcd: Rule DOCSIS_SOCIFDRV: Success (Process insmod (239)).
pcd: Starting process mknod (Rule DOCSIS_MKNODSOCIFDRV).
pcd: Rule DOCSIS_MKNODSOCIFDRV: Success (Process mknod (241)).
pcd: Starting process insmod (Rule DOCSIS_MNG).
pcd: Rule DOCSIS_MNG: Success (Process insmod (242)).
pcd: Starting process mknod (Rule DOCSIS_MKNODMNG).
pcd: Starting process insmod (Rule DOCSIS_KINTR).
pcd: Rule DOCSIS_MKNODMNG: Success (Process mknod (244)).
pcd: Starting process insmod (Rule DOCSIS_FILTERCLASS).
pcd: Rule DOCSIS_KINTR: Success (Process insmod (245)).
pcd: Starting process /usr/sbin/hal_event_mbox (Rule DOCSIS_HALEVENTMBOX).
pcd: Starting process /usr/sbin/hal_cmd_mbox (Rule DOCSIS_HALCMDMBOX).
pcd: Rule DOCSIS_FILTERCLASS: Success (Process insmod (248)).
pcd: Starting process /bin/sh (Rule DOCSIS_FCDEV).
pcd: Rule DOCSIS_FCDEV: Success (Process /bin/sh (257)).
pcd: Rule DOCSIS_HALCMDMBOX: Success (Process /usr/sbin/hal_cmd_mbox (255)).
pcd: Rule DOCSIS_HALEVENTMBOX: Success (Process /usr/sbin/hal_event_mbox (254)).
pcd: Starting process /usr/sbin/mlx (Rule DOCSIS_MLX).
pcd: Starting process /usr/sbin/dbridge_init (Rule DOCSIS_DBRIDGEINIT).
pcd: Rule DOCSIS_MLX: Success (Process /usr/sbin/mlx (263)).
pcd: Starting process /usr/sbin/hal_tuner_mgr (Rule DOCSIS_HALTUNERMGR).
Ingress Hook on eth0
Dbridge Init SUCSESS
Autoconfiguration disabled for br0
HAL_MacDsUnicastDataFilterAdd: system_rev = 1
Autoconfiguration disabled for lbr0
HAL_MacDsUnicastDataFilterAdd: system_rev = 1
Autoconfiguration disabled for lan0
Autoconfiguration disabled for wan0
HAL_MacDsUnicastDataFilterAdd: system_rev = 1
pcd: Rule DOCSIS_HALTUNERMGR: Success (Process /usr/sbin/hal_tuner_mgr (271)).
pcd: Rule DOCSIS_HALREADY: Success.
pcd: Starting process /usr/sbin/qos_dsx_sm (Rule DOCSIS_QOSDSXSM).
pcd: Starting process /usr/sbin/dispatcher (Rule DOCSIS_DISPATCHER).
netlink_open: initialized fd 6
pcd: Starting process /usr/sbin/bpi_auth (Rule DOCSIS_BPIAUTH).
pcd: Rule DOCSIS_DISPATCHER: Success (Process /usr/sbin/dispatcher (279)).
pcd: Starting process /usr/sbin/docsis_mac_driver (Rule DOCSIS_MACDRIVER).
Autoconfiguration disabled for cni0
pcd: Rule DOCSIS_DBRIDGEINIT: Success (Process /usr/sbin/dbridge_init (270)).
pcd: Starting process ti_webserver (Rule DOCSIS_WEBSERVER).
pcd: Starting process udhcpd (Rule DOCSIS_UDHCPD).
pcd: Starting process /usr/sbin/snmp_agent_cm (Rule DOCSIS_SNMPAGENT).
pcd: Starting process /bin/sh (Rule DOCSIS_DBRIDGEMDFINIT).
pcd: Rule DOCSIS_QOSDSXSM: Success (Process /usr/sbin/qos_dsx_sm (278)).
pcd: Rule DOCSIS_UDHCPD: Success (Process udhcpd (286)).
pcd: Rule DOCSIS_WEBSERVER: Success (Process ti_webserver (285)).
pcd: Rule DOCSIS_BPIAUTH: Success (Process /usr/sbin/bpi_auth (280)).
pcd: Starting process /usr/sbin/bpi_tek (Rule DOCSIS_BPITEK).
pcd: Starting process /usr/sbin/bpi_sa_map (Rule DOCSIS_BPISAMAP).
info, udhcp server (v0.9.7) started
error, Unable to open /var/tmp/landhcps0.leases for reading
error, Unable to open /var/lib/misc/udhcpd01.leases for reading
error, Unable to open /var/lib/misc/udhcpd02.leases for reading
error, Unable to open /var/lib/misc/udhcpd03.leases for reading
info, interface: lan0, start : c0a8640a end : c0a864fe

pcd: Starting process /usr/sbin/downstream_manager (Rule DOCSIS_DSMNGR4).
pcd: Rule DOCSIS_DBRIDGEMDFINIT: Success (Process /bin/sh (288)).
pcd: Starting process insmod (Rule DOCSIS_PP).
pcd: Starting process /usr/sbin/downstream_manager (Rule DOCSIS_DSMNGR3).
pcd: Starting process /usr/sbin/downstream_manager (Rule DOCSIS_DSMNGR2).
pcd: Starting process /usr/sbin/downstream_manager (Rule DOCSIS_DSMNGR1).
Create DOCSIS Packet Processor counters char device done
Init Docsis Packet Processor counters DB done.
DOCSIS Packet Processor counters control init done
DOCSIS Packet Processor control init done
pcd: Rule DOCSIS_PP: Success (Process insmod (297)).
pcd: Starting process /bin/sh (Rule DOCSIS_PPDEV).
pcd: Rule DOCSIS_BPITEK: Success (Process /usr/sbin/bpi_tek (290)).
pcd: Rule DOCSIS_BPISAMAP: Success (Process /usr/sbin/bpi_sa_map (291)).
WebSrv Warning: No CGI pattern specified; CGI Processing is disabled.
pcd: Rule DOCSIS_SNMPAGENT: Success (Process /usr/sbin/snmp_agent_cm (287)).
pcd: Starting process /usr/sbin/eventmgr_cm (Rule DOCSIS_EVENTMNGR).
SNMPA_CreateSocketEntry : type 0, addr = 0, port = 0, ifname = /var/tmp/cm_snmp_ctrl List = (nil)
Cntl Entry created
pcd: Rule DOCSIS_DSMNGR4: Success (Process /usr/sbin/downstream_manager (296)).
pcd: Rule DOCSIS_DSMNGR3: Success (Process /usr/sbin/downstream_manager (298)).
pcd: Rule DOCSIS_DSMNGR2: Success (Process /usr/sbin/downstream_manager (299)).
pcd: Rule DOCSIS_DSMNGR1: Success (Process /usr/sbin/downstream_manager (300)).
pcd: Starting process /usr/sbin/upstream_manager (Rule DOCSIS_USMNGR1).
pcd: Starting process /usr/sbin/upstream_manager (Rule DOCSIS_USMNGR2).
pcd: Starting process /usr/sbin/upstream_manager (Rule DOCSIS_USMNGR3).
pcd: Starting process /usr/sbin/upstream_manager (Rule DOCSIS_USMNGR4).
pcd: Rule DOCSIS_PPDEV: Success (Process /bin/sh (302)).
pcd: Rule DOCSIS_EVENTMNGR: Success (Process /usr/sbin/eventmgr_cm (304)).
pcd: Rule DOCSIS_USMNGR1: Success (Process /usr/sbin/upstream_manager (306)).
pcd: Rule DOCSIS_USMNGR2: Success (Process /usr/sbin/upstream_manager (307)).
pcd: Rule DOCSIS_USMNGR3: Success (Process /usr/sbin/upstream_manager (308)).
pcd: Rule DOCSIS_USMNGR4: Success (Process /usr/sbin/upstream_manager (309)).
pcd: Rule DOCSIS_MACDRIVER: Success (Process /usr/sbin/docsis_mac_driver (281)).
pcd: Starting process /usr/sbin/docsis_mac_manager (Rule DOCSIS_MACMANAGER).
SNMPA_CreateSocketEntry : type 1, addr = c0a86401, port = 161, ifname = lan0 List = 0x62620
SNMPA_CreateSocketEntry : type 1, addr = c0a86401, port = 162, ifname = lan0 List = 0x62620
FcUtils_AddSysInterface: Failed to get net device struct for mta0
pcd: Rule DOCSIS_MACMANAGER: Success (Process /usr/sbin/docsis_mac_manager (314)).
pcd: Rule DOCSIS_LASTRULE: Success.

======GetNextFrequency ==> 402750000======
======GetNextFrequency ==> 434250000======
======GetNextFrequency ==> 93000000======
======GetNextFrequency ==> 94000000======
======GetNextFrequency ==> 95000000======
======GetNextFrequency ==> 96000000======
======GetNextFrequency ==> 97000000======
======GetNextFrequency ==> 98000000======
======GetNextFrequency ==> 99000000======
======GetNextFrequency ==> 100000000======
======GetNextFrequency ==> 101000000======
======GetNextFrequency ==> docsis/scan 0102000000======
======GetNextFrequency ==>
Halt scan <---- True
mainMenu> shell
Exiting to shell. Type "exit" to return back to CLI


BusyBox v1.4.2 (2009-12-03 12:01:34 CST) Built-in shell (ash)
Enter 'help' for a list of built-in commands.

# cat /proc/net/dbrctl/show

Docsis bridge mode is: 2 (0=off; 1=reg; 2=pre reg; 3=standby)
--------------------------------------------------------------
index Interface Type
0 cni0 CABLE
1 lbr0 CMCI
2 lan0 LAN IP
3 wan0 WAN IP
--------------------------------------------------------------

Esafe configuration
-------------------
# echo registered > /proc/net/dbrctl/mode
DEBUG: Register selective packet handler successful
# brctl --?
never heard of command [--?]
# brctl show
bridge name bridge id STP enabled interfaces
br0 8000.000102030405 no eth0
lbr0
# brctl stp br0 on
# brctl show
bridge name bridge id STP enabled interfaces
br0 8000.000102030405 yes eth0
lbr0

# brctl showmacs 8000.000102030405
read of forward table fail

So then, how to forward the eth huh?

---

As I've said already, no dhcp:

info, udhcp server (v0.9.7) started
error, Unable to open /var/tmp/landhcps0.leases for reading
error, Unable to open /var/lib/misc/udhcpd01.leases for reading
error, Unable to open /var/lib/misc/udhcpd02.leases for reading
error, Unable to open /var/lib/misc/udhcpd03.leases for reading
info, interface: lan0, start : c0a8640a end : c0a864fe

No matter what firmware.. too good to be bad huh