ASUS RT-AC51U doesn't seem to route

[Kamphuis]

Hi,

Yesterday I purchased an ASUS RT-AC51U router in order to have a better WIFI signal then the FRITZbox I got from my ISP. I've connected the ASUS WAN port to the FRITZbox LAN with network 192.168.178.0, the ASUS LAN has 192.168.10.0, I have the following route table on my ASUS:

Destination Gateway Genmask Flags Metric Ref Use Type Iface
192.168.178.254 * 255.255.255.255 UH 0 0 0 WAN0 vlan2
239.255.255.250 * 255.255.255.255 UH 0 0 0 LAN br0
192.168.178.0 * 255.255.255.0 U 0 0 0 WAN0 vlan2
192.168.10.0 * 255.255.255.0 U 0 0 0 LAN br0
default 192.168.178.254 0.0.0.0 UG 0 0 0 WAN0 vlan2

LAN clients from the ASUS cannot access the Internet (although DNS queries resolve), so it looks like the ASUS router doesn't seem to route. The ASUS has internet connection an LAN connection. Can anyone help me with this? Many thanks!

 

[ColinTaylor]

The only thing that looks out of place there is this entry which I don't have:

239.255.255.250 * 255.255.255.255 UH 0 0 0 LAN br0

Are you using some sort of IPTV? If so try disabling that configuration.

 

[dave14305]

If you ping something on the internet, do you get any TTL expired in transit messages? If routing looks OK, maybe the ISP is playing with the Time-to-live.

 

[Kamphuis]

Thanks for your replies. I checked the transit messages, by pinging google.com from the ASUS. There is nothing strange in my opinion:

PING www.google.com (172.217.20.100): 56 data bytes
64 bytes from 172.217.20.100: seq=0 ttl=56 time=7.897 ms
64 bytes from 172.217.20.100: seq=1 ttl=56 time=6.639 ms
64 bytes from 172.217.20.100: seq=2 ttl=56 time=6.654 ms
64 bytes from 172.217.20.100: seq=3 ttl=56 time=6.671 ms
64 bytes from 172.217.20.100: seq=4 ttl=56 time=6.509 ms

--- www.google.com ping statistics ---
5 packets transmitted, 5 packets received, 0% packet loss
round-trip min/avg/max = 6.509/6.874/7.897 ms

As far as the 239.255.255.250 record in the routing table of the ASUS, it has something to do with UPnP. But after disabeling that, the record didn't disappear from the routing table.

Switching off the firewall also has no effect.

 

[Kamphuis]

Well... It's working now... After disabling NAT and enabling it again, the ASUS is routing. Don't know if this is a bug in the ASUS GUI or whatever, but anyhow... I'm happy!