No WAN ip after reboot

[11freddy]

OK.

I will upgrade- likely on the weekend as there is a fair amount of manual provisioning I need to do assuming you shouldn't attempt to 'preserve settings'.

Will report back on whether this update resolves the issue.

Thanks.

[chaos40]

That would be great as I am having the exact same problem with the same TP-Link model.

Thanks!

[chaos40]

All,

I found another work-around on another site. It isn't elegant, but it works. Apparently if you connect your modem to a switch, and connect the WAN / Internet port of the Archer to the switch and have NO OTHER Ethernet connections to that external switch, then you can reliably get a DHCP lease from the cable modem.

So right now I'm "wasting" a TP-Link 8 port gigabit switch with on only two connections going to it - one from the WAN port on the Archer and the other from the cable modem.

I restarted the modem to be safe, and when it was up, I just clicked "renew lease" on the Gargoyle Management Utility (build 1.9.0) and it was able to pull a lease. So far all systems are a go...

Hopefully a permanent fix is available soon.

Thanks!

[Lantis]

That makes me wonder if a Crossover cable would work.

[11freddy]

If Chaos40 is running 1.9.0, maybe the supposed 'fix' from OpenWRT site isn't...

Guess I'll upgrade anyway.

[11freddy]

As expected I suppose, the move to 1.9 didn't address the issue.

Just for laughs, I'll make a crossover cable and try it out a bit later.

[11freddy]

The crossover cable didn't fix it either...

It was useable, but didn't change the behavior on reset of router.

Any other thoughts?

Thanks.

[Lantis]

Ah. Sorry I've now read this more carefully. They never fixed it in that version. People were just saying that the suggested fix could be successfully applied to that version.

Can you post the contents of your /etc/config/network file for me? Remember to remove your PPPoE login details, just replace them with USERNAMEREMOVED and PASSWORDREMOVED so I know what's up.

Basically I'm going to see if your config is the same as they suggested, if not we'll switch to it and see.

If it works, I can patch it into gargoyle.

[11freddy]

As requested... and thanks for your interest and help.

config interface 'loopback'
option ifname 'lo'
option proto 'static'
option ipaddr '127.0.0.1'
option netmask '255.0.0.0'

config globals 'globals'
option ula_prefix 'fd3b7a1b::/48'

config interface 'lan'
option ifname 'eth1'
option force_link '1'
option type 'bridge'
option proto 'static'
option netmask '255.255.255.0'
option ip6assign '60'
option ipaddr '172.16.16.1'
option dns '172.16.16.1'

config interface 'wan'
option ifname 'eth0'
option proto 'pppoe'
option username PPPoEUSERNAMEREMOVED
option password PPPoEPASSWORDREMOVED
option keepalive '3 5'

config interface 'wan6'
option ifname 'eth0'
option proto 'dhcpv6'

config switch
option name 'switch0'
option reset '1'
option enable_vlan '1'

config switch_vlan
option device 'switch0'
option vlan '1'
option ports '0 2 3 4 5'

config switch_vlan
option device 'switch0'
option vlan '2'
option ports '1 6'

[Lantis]

Code: Select all

config interface 'loopback'
	option ifname 'lo'
	option proto 'static'
	option ipaddr '127.0.0.1'
	option netmask '255.0.0.0'

config globals 'globals'
	option ula_prefix 'fd3b:39c0:7a1b::/48'

config interface 'lan'
	option ifname 'eth0'
	option force_link '1'
	option type 'bridge'
	option proto 'static'
	option netmask '255.255.255.0'
	option ip6assign '60'
	option ipaddr '172.16.16.1'
	option dns '172.16.16.1'

config interface 'wan'
	option ifname 'eth1'
	option proto 'pppoe'
	option username PPPoEUSERNAMEREMOVED
	option password PPPoEPASSWORDREMOVED
	option keepalive '3 5'

config interface 'wan6'
	option ifname 'eth1'
	option proto 'dhcpv6'

config switch
	option name 'switch0'
	option reset '1'
	option enable_vlan '1'

config switch_vlan
	option device 'switch0'
	option vlan '1'
	option ports '2 3 4 5 6'

config switch_vlan
	option device 'switch0'
	option vlan '2'
	option ports '0 1'

See the changes above.
A quick summary:
Port 0 is "eth1", Port 6 is "eth0".
Conventionally eth1 is WAN and eth0 is LAN. The default config has this reversed.
For the two vlan configs I swapped out 0 and 6 so that WAN and LAN are now mapped to a more conventional interface.
And to match this change, under wan, wan6 and LAN I changed the "eth" assignment accordingly.

Before you make this change, make a backup. If it all goes bad, just drop the router into failsafe, mount the file system, edit the config and revert it back. If that fails then do a hard reset and restore backup.
It shouldn't go bad, but it pays to be prepared lol.

To make the change, edit the config, save, and reboot.
There's probably a way of doing it without a reboot but I think it's safer to do it this way.
If the fix works as suggested, you should get an ip from the modem even under situations where you didn't previously.

Edit;
Oh and don't forget when you're copy pasting the config back in to put your proper PPPoE details!