TL-WDR4300 upgrade to 19.07 - No WAN IPv4 anymore

Hi,

I upgraded from 18.06.05 to 19.07 (and to ath79) by downloading the sysupgrade image(1) and upgraded via the Luci interface without keeping the configuration. However, my WAN interface doesn't get an IP assigned anymore, atleast, not permanently. When rebooting the cable modem I get an IP briefly (but not internet access) but that disappears again. Any suggestions are welcome. Thanks!

Some log lines from Luci:

Mon Jan  6 18:31:25 2020 daemon.info dnsmasq[1649]: read /tmp/hosts/odhcpd - 4 addresses
Mon Jan  6 18:31:25 2020 daemon.info dnsmasq[1649]: read /tmp/hosts/dhcp.cfg01411c - 2 addresses
Mon Jan  6 18:31:25 2020 daemon.info dnsmasq-dhcp[1649]: read /etc/ethers - 0 addresses
Mon Jan  6 18:31:26 2020 daemon.notice netifd: wan (2201): udhcpc: sending select for 192.168.178.10
Mon Jan  6 18:31:27 2020 daemon.notice netifd: wan (2201): udhcpc: lease of 192.168.178.10 obtained, lease time 122
Mon Jan  6 18:31:28 2020 daemon.notice netifd: Interface 'wan' is now up
Mon Jan  6 18:31:28 2020 user.notice firewall: Reloading firewall due to ifup of wan (eth0.2)
Mon Jan  6 18:32:28 2020 daemon.notice netifd: wan (2201): udhcpc: sending renew to 192.168.178.1
Mon Jan  6 18:32:58 2020 daemon.notice netifd: wan (2201): udhcpc: sending renew to 0.0.0.0
Mon Jan  6 18:33:13 2020 daemon.notice netifd: wan (2201): udhcpc: sending renew to 0.0.0.0
Mon Jan  6 18:33:20 2020 daemon.notice netifd: wan (2201): udhcpc: sending renew to 0.0.0.0
Mon Jan  6 18:33:23 2020 daemon.notice netifd: wan (2201): udhcpc: sending renew to 0.0.0.0
Mon Jan  6 18:33:24 2020 daemon.notice netifd: wan (2201): udhcpc: sending renew to 0.0.0.0
Mon Jan  6 18:33:24 2020 daemon.notice netifd: wan (2201): udhcpc: lease lost, entering init state
Mon Jan  6 18:33:24 2020 daemon.notice netifd: Interface 'wan' has lost the connection

I'm using the default configuration for my interfaces, /etc/config/network

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 'fd4d:3135:43d3::/48'

config interface 'lan'
        option type 'bridge'
        option ifname 'eth0.1'
        option proto 'static'
        option ipaddr '192.168.1.1'
        option netmask '255.255.255.0'
        option ip6assign '60'

config interface 'wan'
        option ifname 'eth0.2'
        option proto 'dhcp'

config device 'wan_eth0_2_dev'
        option name 'eth0.2'
        option macaddr '64:66:b3:fa:b4:75'

config interface 'wan6'
        option ifname 'eth0.2'
        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 0t'

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

(1) http://downloads.openwrt.org/releases/19.07.0/targets/ath79/generic/openwrt-19.07.0-ath79-generic-tplink_tl-wdr4300-v1-squashfs-sysupgrade.bin

I´m running a wdr4300 as router behind a cable modem without problems!

Why do you have a custom mac on the wan interface?

Your cable modem is a Fritz!Box and you are doing double NAT, right?
Why do you have this setup?
Probably a dump ap setup or pass through mode in your cable modem would be a better setup.

I didn't configure the custom mac, its the default configuration after flashing the new firmware.

No, I'm not using a Fritz!Box and also not using double NAT. I have a pass though in my cable modem (so called bridge mode). The IP addressed assigned to my WAN interface should be something totally different and not some internal IP address.

When downgrading back to 18.06.6 everything works as expected again.

Any idea what could be the issue or what I should change? I wanted to start with a fresh config, but apparently that doesn't work.

Thanks.

Same issue here. TL-WDR4300 v1, tried 19.07.2 without success. The same problem as described in this thread. 18.06 is working without any problems.

1 Like