[m-snel]

Hello,

I have a configuration where I have a modem from my ISP (Technicolor TG789bvn with firmware of my ISP). In this modem I have configured assign public IP to my router TP-LINK TL-WR1043ND. In the WAN section I then see my public IP and everything worked as it should be.

By accident I did a release and renew on the WAN IP address (without changing anything else in the configuration) and the WAN IP is also appointed again so everything looks good with the renewing. Problem is that since this I can't access the internet anymore (I can access the local network). Also pinging to the WAN gateway that is appointed through DHCP to the WAN interface times out (pinging to my WAN IP does work).

Anybody any idea why traffic from the network to the internet isn't forwarded to the WAN connection anymore and how to solve this?

[nskware]

Did rebooting modem and Router fixed the issue?

[m-snel]

I rebooted both of them several times.

When I look at the WAN it seems to have a connection (see screenprint). But pinging the gateway gives timeouts.

I think traffic isn't routed to the internet (I also enclosed the routing table as it is now).

My situation:

1. ISP modem (Technicolor TG789bvn) with the public IP adress assigned to my TP Link (unfortunately bridging isn't possible with my ISP, but with this configuration it worked perfectly). This has an IP of 192.168.1.1

2. TP Link TL-WR1042ND V2 (with IP adresses in the 192.168.2.x range)

Anybody any idea why DD-WRT won't route internet traffic to the WAN?

Ps. If I ping my WAN address it also times out

[Per Yngve Berg]

You do not have a Default Route 0.0.0.0

[m-snel]

How can I add/obtain the default route?

[Per Yngve Berg]

Your wan ip is on 69.x.x.x, while the gateway is on 87.x.x.x

The default route may have gone disabled while the gateway is not reachable.

[m-snel]

Very strange because it has always worked.

If I turn off the assign public IP to the DD-WRT TP Link (so it gets a 192.168.1.x IP address) it doe get a default route.

If i then appoint the public IP address to my desktop it also gets the 69.58.242.x address and then I can ping 87.209.240.1 (so the gateway is good).

As soon as I appoint the public IP to DD-WRT again (so the IP is 69.58.242.x again) no default route

I don't understand why (especially as this configuration has always worked, but the default route got lost with IP release and renew and I can't seem to get it back.

[Per Yngve Berg]

With a netmask of 255.0.0.0, the gateway must be on 69.x.x.x

If your ips's network is from 64-95.x.x.x, netmask must be 224.0.0.0

Give your isp a call and ask what they are doing.

[m-snel]

Thank you, I'll contact my ISP.

[m-snel]

One more question though, how is it possible that I can ping the gateway when I appoint the public IP to my desktop? Then my desktop sees the gateway, why doesn't DD-WRT?

[Per Yngve Berg]

Why do things accidentally work when they are mis-configured?

Report it as a bug to your desktop OS developer.