So I did an "erase nvram" and started fresh. eth0 works at that point properly (DHCP and everything).
Once I go in configuring the rest of the stuff, at some point, eth0 stopped working so it has to be some type of configuration I'm setting up which makes eth0 basically, die.
Also, this is weird:
<6>[ 5.330000] eth1: Atheros AG71xx at 0xba000000, irq 5, mode:GMII
<6>[ 7.320000] eth1: link up (1000Mbps/Full duplex)
<6>[ 13.670000] device eth1 entered promiscuous mode
That can't be correct. I thought the two ports on these units were 10/100's only? And when eth0 stops working also, I never see the "eth0: link up" in dmesg anymore. I know the OpenWRT team had a bunch of bugs with ag71xx the past 6 months. Wonder if I'm running into them.
I think the problem is with the Thunderbolt-to-Ethernet adapter that you use.
Can you try connecting by cable another PC with regular ethernet LAN card (not adapter), to the router's LAN port (eth0) ? _________________ THERE ARE NO STRANGERS HERE; ONLY FRIENDS YOU HAVEN'T YET MET.
________________________________________________________________________________________________________
DD-WRT CHANGELOG | DEVICES | DD-WRT BUILDS | KONG BUILDS | UNOFFICIAL BUILDS | DD-WRT in VIRTUALBOX
I had time to test other builds on my device and 26839 is the only build that is working for me. All other later builds boot up fine, but no IP adress is obtained through WAN DHCP.
I had time to test other builds on my device and 26839 is the only build that is working for me. All other later builds boot up fine, but no IP adress is obtained through WAN DHCP.
This is strange because there are no changes between 26839 and 26854 that would impact the WR710N. So the WAN is getting an IP with Automatic DHCP setting in 26839, but doesn't in 26854 ?
Are you sure you're setting it up properly ? Have you tried an "erase nvram" and then "reboot" command from Telnet or SSH ? (do you know how to do it ?) _________________ THERE ARE NO STRANGERS HERE; ONLY FRIENDS YOU HAVEN'T YET MET.
________________________________________________________________________________________________________
DD-WRT CHANGELOG | DEVICES | DD-WRT BUILDS | KONG BUILDS | UNOFFICIAL BUILDS | DD-WRT in VIRTUALBOX
I'll try to telnet into the machine and erase nvram. With 26839 the machine boots up and is connected to the internet (without configuration). Later builds will always show WAN IP 0.0.0.0 regardless of DHCP lease and renew in WAN tab.
So if settings changed to get WAN DHCP working, please tell me.
I think the problem is with the Thunderbolt-to-Ethernet adapter that you use.
Can you try connecting by cable another PC with regular ethernet LAN card (not adapter), to the router's LAN port (eth0) ?
I will test with a normal PC after I'm done with business travel. Though I would be surprised if it was the Thunderbolt-to-Ethernet adapter for my MacBook Air causing the issue.
popilein wrote:
So if settings changed to get WAN DHCP working, please tell me.
Something changed because with the default nvram cleared, DD-WRT sets the WAN to be eth0 instead of eth1. Check under 'Setup', 'Networking', 'Port Setup', and 'WAN Port Assignment'. If it's set to eth0, change it to eth1 and check your WAN DHCP again. According to DD-WRT, least the last several builds, 'eth0' is the port marked LAN and 'eth1' is the port marked WAN/LAN.
Nothing WAN-related has changed, as far as I can tell, between 26839 and 26854. I mean... after all there are only 15 commits, which one can it be ? You can check starting here:
http://svn.dd-wrt.com/changeset/26840 _________________ THERE ARE NO STRANGERS HERE; ONLY FRIENDS YOU HAVEN'T YET MET.
________________________________________________________________________________________________________
DD-WRT CHANGELOG | DEVICES | DD-WRT BUILDS | KONG BUILDS | UNOFFICIAL BUILDS | DD-WRT in VIRTUALBOX
Something changed because with the default nvram cleared, DD-WRT sets the WAN to be eth0 instead of eth1. Check under 'Setup', 'Networking', 'Port Setup', and 'WAN Port Assignment'. If it's set to eth0, change it to eth1 and check your WAN DHCP again. According to DD-WRT, least the last several builds, 'eth0' is the port marked LAN and 'eth1' is the port marked WAN/LAN.
lol, that did the trick! WAN DHCP working now. Where is this change mentioned?
Nothing WAN-related has changed, as far as I can tell, between 26839 and 26854. I mean... after all there are only 15 commits, which one can it be ? You can check starting here:
http://svn.dd-wrt.com/changeset/26840
There's nothing I can tell either. I need to go back to the first supported WIP revision and test a couple different builds after an NVRAM erase to see what the default behavior is.
popilein wrote:
lol, that did the trick! WAN DHCP working now. Where is this change mentioned?
I'm starting to think... It's always been that way after the WIP support was added when the NVRAM is cleared. I'm going to do some testing over the weekend.
On my other router WNDR3800, the default has always been WAN = eth1 and LAN = eth0. That's the "standard" default from what I can tell.
If WAN changed to eth0 (instead of the correct eth1) between 26839 and 26854, we should open a ticket for that. There might be a bug somewhere, but can't find it. _________________ THERE ARE NO STRANGERS HERE; ONLY FRIENDS YOU HAVEN'T YET MET.
________________________________________________________________________________________________________
DD-WRT CHANGELOG | DEVICES | DD-WRT BUILDS | KONG BUILDS | UNOFFICIAL BUILDS | DD-WRT in VIRTUALBOX
On my other router WNDR3800, the default has always been WAN = eth1 and LAN = eth0. That's the "standard" default from what I can tell.
If WAN changed to eth0 (instead of the correct eth1) between 26839 and 26854, we should open a ticket for that. There might be a bug somewhere, but can't find it.
*Nod* -- This is from my WNDR3800:
<6>[ 6.350000] eth0: Atheros AG71xx at 0xb9000000, irq 4, mode:RGMII
<6>[ 6.660000] ag71xx ag71xx.1: connected to PHY at rtl8366s:04 [uid=001cc960, driver=Generic PHY]
<6>[ 6.670000] eth1: Atheros AG71xx at 0xba000000, irq 5, mode:RGMII
<7>[ 6.830000] ar71xx: pll_reg 0xb8050010: 0x11110000
<6>[ 6.830000] eth0: link up (1000Mbps/Full duplex)
And this is from the TL-WR710N:
<6>[ 4.110000] libphy: ag71xx_mdio: probed
<6>[ 4.660000] ag71xx ag71xx.0: connected to PHY at ag71xx-mdio.1:04 [uid=004dd041, driver=Generic PHY]
<6>[ 4.670000] eth0: Atheros AG71xx at 0xb9000000, irq 4, mode:MII
<6>[ 5.230000] ag71xx-mdio.1: Found an AR7240/AR9330 built-in switch
<6>[ 5.330000] eth1: Atheros AG71xx at 0xba000000, irq 5, mode:GMII
The WNDR3800 has a Realtek switch but that shouldn't affect the designations of the ethX devices. I'll do some more testing when I get back from my business trip before I can confirm it's a real bug.
Cheers,
Kermee
P.S. From the dmesg, looks like eth1 is definitely a GbE interface...
This device drives me crazy right now
With WAN set to eth1 (on 26839 it is set to eth0), an IP is obtained but LAN-Port is not functional. Bridging is set to
Code:
Bridge Name STP enabled Interface
br0 no eth1 ath0
... *sigh*
From my understanding eth1 should change to eth0 under Port Setup. But it doesn't.
Bridging table should be:
br0 -> eth0 ath0
and WAN port assignment: eth1
Save, Apply, Wait 1 minute, then reboot router and check. _________________ THERE ARE NO STRANGERS HERE; ONLY FRIENDS YOU HAVEN'T YET MET.
________________________________________________________________________________________________________
DD-WRT CHANGELOG | DEVICES | DD-WRT BUILDS | KONG BUILDS | UNOFFICIAL BUILDS | DD-WRT in VIRTUALBOX
