Re: Sick DSL modem causes WRT54GS to hang.

Jeff Liebermann <jeffl@xxxxxxxxxx> hath wroth:

Jeff Liebermann <jeffl@xxxxxxxxxx> hath wroth:

eth0 = WAN ethernet eth1 = LAN ethernet

Ooops. Backwards. eth0 = LAN. eth1 = WAN.
That makes more sense as the errors are now at the DSL modem to router
ethernet connection. NWAY problem I guess.

Problem and mystery mostly solved. It was an NWAY negotiation problem
between the WRT54GS and the Efficient DSL modems. The router crashes
went away when I locked down the interface speed and protocol on the
WRT54GS to 10Mbits/sec half-duplex. Finding where to do that was a
bit of a challenge in DD-WRT. It's under:
Setup -> VLAN's
at the bottom of the page. Uncheck the boxes under the "W" column for
"Auto-Negotiate", "100Mbit", and "Full Duplex". Apply and Save.

However, there are still some mysterious problems remaining (probably
for another day).

1. The large number of framing errors are stil there. The results of
ifconfig after running about 12 hours is:

eth0 Link encap:Ethernet HWaddr 00:14:BF:B9:10:13
UP BROADCAST RUNNING PROMISC MULTICAST MTU:1500 Metric:1
RX packets:37911 errors:0 dropped:0 overruns:0 frame:0
TX packets:63331 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:25643053 (24.4 MiB) TX bytes:11167400 (10.6 MiB)
Interrupt:4

eth1 Link encap:Ethernet HWaddr 00:14:BF:B9:10:15
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
=====> RX packets:12620 errors:0 dropped:0 overruns:0 frame:181201
TX packets:43403 errors:241 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:1632528 (1.5 MiB) TX bytes:21759628 (20.7 MiB)
Interrupt:2 Base address:0x5000

It's working, so I shouldn't complain, but it would be nice to know
from where the errors are coming from.

2. The mystery of why a protocol negotiation failure at the WAN
interface would trash the router, probably overscribbling working
memory, remains unsolved. Similarly, why it would have an effect on
DNS forwarding and LAN port operation, is also unknown.


--
Jeff Liebermann jeffl@xxxxxxxxxx
150 Felker St #D http://www.LearnByDestroying.com
Santa Cruz CA 95060 http://802.11junk.com
Skype: JeffLiebermann AE6KS 831-336-2558
.

Relevant Pages

  • Re: Sick DSL modem causes WRT54GS to hang.
    ... Jeff Liebermann hath wroth: ... That makes more sense as the errors are now at the DSL modem to router ... ethernet connection. ... NWAY problem I guess. ...
    (alt.internet.wireless)
  • Re: Getting an IP Address
    ... the Westell Versalink is a DSL Modem and a router. ... > and the Verizon DSL Modem connected, maybe via a USB port? ... > the NIC is going to error out because it has no connection. ...
    (microsoft.public.windowsxp.network_web)
  • Re: bouncing connection and a netgear router..
    ... The WGR614 wireless router does NOT have a built in DSL modem. ... benchmark test between the 2nd laptop and her wireless laptop. ...
    (alt.internet.wireless)
  • Re: Newbie first-time install advice: Highpoint Rocket 133SB
    ... > router and a working NIC you have working internet. ... > Chances are VERY good the Rocket 133SB uses a standard controller. ... >> someone can tell me how to finesse it to work with my DSL modem. ... That is what debian-user is here for. ...
    (Debian-User)
  • Re: Wireless Router and DSL
    ... So I've done some Googling and I've come to the conclusion they'll need a router. ... I also think that since they plan to put the gift computer in a part of the house a couple of rooms away from their current computer (and DSL modem) they'll need a PCI wireless card. ... Which means it will stay connected to the ISP and any computers that are part of the network will also be automatically connected to the internet. ...
    (alt.comp.hardware.pc-homebuilt)