Verizon DSL → Westell 6100g with WRT54G losing DSL link

I've been having growing issues lately with the 6100g dropping the DSL connection and I'm wondering if part of it might be my router. I've been able to set the 6100g into bridge mode successfully but I have been unable to get my WRT54G to pick up an IP address so my modem is still running in routed bridge.

When the problem happens I've gone in to the modem's interface and the DSL link status is actually disconnected. Any advice on what I can do?

Can you post up the modem's transceiver statistics? You can find it at one of these two links when you're able to access the modem's admin page.

»192.168.1.1/transtat.htm
»192.168.1.1/htmlV/transtat.asp

Here's the tranceiver stats:

Transceiver Information Down/Up
DSL Speed (Kbits/Sec) 3360/704
Margin (dB) 15.3/9.0
Line Attenuation (dB) 51.8/31.0
Transmit Power (dBm) 19.2/11.9

Connect an ethernet cable between your computer and the linksys WRTG54G. Open any browser and type in »192.168.1.1. On the Basic Setup page you should see Network Address with an entry for DHCP Server. Click on Enable. On the Wireless Network page you should see Wireless Network Mode. Choose the mode that your cards are using ex. B, G . You should also see the Wireless Network Name, either linksys if you have not changed from default or the name you have chosen. On the Wireless Security page select the security mode you wish to use. This must match the security you select on each computer wireless card. On the Security page with the VPN Passthrough select IPSec Passthrough as enable. On the Administration page under Web Access select HTTP. You should now see on the Status page under Internet Configuration type PPPoE and Login Status as Connected.
This can be easily be setup using the setup disk you received with the router or go to the individual pages to select the options. The description looks more complex than it actually is if you use the linksys disk.
Good luck

I've got all that done already and it still doesn't want to cooperate. On the setup page I've changed the type to PPPoE and entered my information and that didn't work. I've tried cloning the 6100g's MAC address, my PC's MAC address and not using the cloning option at all and still nothing.

I'm just not sure what part of the setup I seem to be missing as getting the WRT54G configured to do this shouldn't be this complicated.

EDIT - I've also not dropped today yet but I notice it happens in the evenings. I'll double check the transceiver statistics later on tonight when I start having issues as well as post up a connection log.

Since these routers are designed to work with the default settings try doing a reset with the button on the rear to get to the mfg settings. Try another attempt then with the linksys setup disk and change the 6100g modem to bridge from routed bridge.
»www22.verizon.com/Reside ··· 3756.htm
Follow this link to properly configure the 6100g with the linksys router.

Actually the instructions in that link don't put the 6100 in transparent bridge mode. They advise using a Bridge Mode of "routed bridge", and that doesn't work. One should choose a Bridge Mode of "bridge", as in this FAQ: »Verizon DSL FAQ »How do I use a router with the Westell 6100? to get a transparent bridge mode that works with a separate router.

But if the DSL link is disconnecting, the problem is a sync problem between the modem and the ISP's DSLAM, therefore not related to any router configuration.

When the DSL link is down, the DSL light on the 6100 should blink, (whether in bridge mode or not), to tell you that sync has been lost. The stats posted so far from that line don't look too bad but do seem to indicate an issue with the upstream, (low noise margin and incorrect sync rate). Watching for changes in those stats may help tell the tale.

Earlier today the issue came back. I had a disconnect at 10:30, 10:41, and a repeated string of disconnects from about 10:47 until 10:51. The transceiver stats during these remained the same as they were from my post. Below is the system log during this morning's outages. Each time the modem lost connection it was preceeded by the OMB_REBOOT_INTERRUPT_CODE. I can post the connection log as well if that might be of use.

Apr 24 10:52:00 daemon.err cwmpd[175]: cwmpDDNSCallback: Result of DDNS Update (ipupdate_once) ->3
Apr 24 10:51:50 user.warn kernel: g_showtime set to 1
Apr 24 10:51:32 user.info kernel: [AMAZON_SE_MEI_IrqHandle 2074]:OMB_REBOOT_INTERRUPT_CODE
Apr 24 10:51:32 user.info kernel: [AMAZON_SE_MEI_IrqHandle 2074]:OMB_REBOOT_INTERRUPT_CODE
Apr 24 10:51:26 daemon.err cwmpd[175]: ddnsWanIPCallback WAN State Down
Apr 24 10:51:16 user.info kernel: [AMAZON_SE_MEI_IrqHandle 2074]:OMB_REBOOT_INTERRUPT_CODE
Apr 24 10:51:16 user.info kernel: [AMAZON_SE_MEI_IrqHandle 2074]:OMB_REBOOT_INTERRUPT_CODE
Apr 24 10:50:55 daemon.err cwmpd[175]: cwmpDDNSCallback: Result of DDNS Update (ipupdate_once) ->3
Apr 24 10:50:44 user.warn kernel: g_showtime set to 1
Apr 24 10:50:32 daemon.err cwmpd[175]: ddnsWanIPCallback WAN State Down
Apr 24 10:50:24 user.info kernel: [AMAZON_SE_MEI_IrqHandle 2074]:OMB_REBOOT_INTERRUPT_CODE
Apr 24 10:50:24 user.info kernel: [AMAZON_SE_MEI_IrqHandle 2074]:OMB_REBOOT_INTERRUPT_CODE
Apr 24 10:50:02 daemon.err cwmpd[175]: cwmpDDNSCallback: Result of DDNS Update (ipupdate_once) ->3
Apr 24 10:49:52 user.warn kernel: g_showtime set to 1
Apr 24 10:49:39 daemon.err cwmpd[175]: ddnsWanIPCallback WAN State Down
Apr 24 10:49:32 user.info kernel: [AMAZON_SE_MEI_IrqHandle 2074]:OMB_REBOOT_INTERRUPT_CODE
Apr 24 10:49:32 user.info kernel: [AMAZON_SE_MEI_IrqHandle 2074]:OMB_REBOOT_INTERRUPT_CODE
Apr 24 10:48:20 daemon.err cwmpd[175]: cwmpDDNSCallback: Result of DDNS Update (ipupdate_once) ->3
Apr 24 10:48:11 user.warn kernel: g_showtime set to 1
Apr 24 10:48:03 daemon.err cwmpd[175]: ddnsWanIPCallback WAN State Down
Apr 24 10:47:55 user.info kernel: [AMAZON_SE_MEI_IrqHandle 2074]:OMB_REBOOT_INTERRUPT_CODE
Apr 24 10:47:55 user.info kernel: [AMAZON_SE_MEI_IrqHandle 2074]:OMB_REBOOT_INTERRUPT_CODE
Apr 24 10:41:57 daemon.err cwmpd[175]: cwmpDDNSCallback: Result of DDNS Update (ipupdate_once) ->3
Apr 24 10:41:47 user.warn kernel: g_showtime set to 1
Apr 24 10:41:38 daemon.err cwmpd[175]: ddnsWanIPCallback WAN State Down
Apr 24 10:41:31 user.info kernel: [AMAZON_SE_MEI_IrqHandle 2074]:OMB_REBOOT_INTERRUPT_CODE
Apr 24 10:41:31 user.info kernel: [AMAZON_SE_MEI_IrqHandle 2074]:OMB_REBOOT_INTERRUPT_CODE
Apr 24 10:34:55 daemon.err cwmpd[175]: cwmpDDNSCallback: Result of DDNS Update (ipupdate_once) ->3
Apr 24 10:34:54 user.warn kernel: flash sector 15 at address b0080000 erased
Apr 24 10:34:53 user.warn kernel: flash sector 14 at address b0070000 erased
Apr 24 10:34:53 user.warn kernel: flash sector 13 at address b0060000 erased
Apr 24 10:34:52 user.warn kernel: flash sector 12 at address b0050000 erased
Apr 24 10:34:52 user.warn kernel: flash sector 11 at address b0040000 erased
Apr 24 10:34:51 user.warn kernel: flash sector 10 at address b0030000 erased
Apr 24 10:34:51 user.warn kernel: flash sector 9 at address b0020000 erased
Apr 24 10:34:43 user.warn kernel: g_showtime set to 1
Apr 24 10:34:34 daemon.err cwmpd[175]: ddnsWanIPCallback WAN State Down
Apr 24 10:34:26 user.info kernel: [AMAZON_SE_MEI_IrqHandle 2074]:OMB_REBOOT_INTERRUPT_CODE
Apr 24 10:34:26 user.info kernel: [AMAZON_SE_MEI_IrqHandle 2074]:OMB_REBOOT_INTERRUPT_CODE
Apr 24 10:34:15 daemon.err cwmpd[175]: cwmpDDNSCallback: Result of DDNS Update (ipupdate_once) ->3
Apr 24 10:33:57 user.warn kernel: g_showtime set to 1
Apr 24 10:33:47 daemon.err cwmpd[175]: ddnsWanIPCallback WAN State Down
Apr 24 10:33:41 user.info kernel: [AMAZON_SE_MEI_IrqHandle 2074]:OMB_REBOOT_INTERRUPT_CODE
Apr 24 10:33:41 user.info kernel: [AMAZON_SE_MEI_IrqHandle 2074]:OMB_REBOOT_INTERRUPT_CODE