Posted: Fri Sep 02, 2022 2:17 Post subject: [SOLVED] Routing to access cable modem
I am running DD-WRT v49599 on a Netgear R9000.
A Netgear CM1200 cable modem is connected to the DD-WRT router to connect to my ISP. The config page of the cable modem is located at 192.168.100.1. My local subnet is other than 192.168.x.x. I normally can connect fine to this config page.
However, when my WireGuard tunnel on the DD-WRT router is up I can no longer connect to the cable modem config page. I figured that this is because the tunnel is routing 192.168.100.1 out to the internet. So on the WireGuard config page I added to the section Route Selected Destinations via WAN and set an IP of 192.168.100.1/32. I can see in the DD-WRT routing table that a route has been added to route 192.168.100.1 to the IP address assigned by the cable company to the DD-WRT router on interface vlan2.
Unfortunately this still doesn't work. I suspect this may be because now 192.168.100.1 is still routed out to the internet bypassing the modem, just not through the WireGuard tunnel. When I try to ping the cable modem, the DD-WRT router responds Destination Port Unreachable.
I have tried setting up a special route on the Advanced Routing/Routing Tables page but can't come up with anything that works.
Is there a way to route this, or must I always disable the WireGuard tunnel if I want to talk to the modem config page?
By playing with the routing tables, I was able to create this route:
0.0.0.0/1 dev oet1 scope link
default via 71.236.228.1 dev vlan2
10.255.255.2 dev oet1 scope link
71.236.228.0/22 dev vlan2 scope link src 71.236.228.176
100.104.252.0/24 dev oet1 scope link src 100.104.252.39
104.129.56.68 via 71.236.228.1 dev vlan2
127.0.0.0/8 dev lo scope link
128.0.0.0/1 dev oet1 scope link
192.1.1.0/24 dev br0 scope link src 192.1.1.250
192.168.100.0/24 via 71.236.228.1 dev vlan2
192.168.100.1 via 192.1.1.250 dev br0
The last entry should route traffic to the cable modem (192.168.100.1) through the DD-WRT router (192.1.1.250).
Unfortunately this still doesn't work. Can't ping the cable modem (destination host unreachable).
Joined: 18 Mar 2014 Posts: 12917 Location: Netherlands
Posted: Fri Sep 02, 2022 8:19 Post subject:
howard@sci1.com wrote:
Update:
By playing with the routing tables, I was able to create this route:
0.0.0.0/1 dev oet1 scope link
default via 71.236.228.1 dev vlan2
10.255.255.2 dev oet1 scope link
71.236.228.0/22 dev vlan2 scope link src 71.236.228.176
100.104.252.0/24 dev oet1 scope link src 100.104.252.39
104.129.56.68 via 71.236.228.1 dev vlan2
127.0.0.0/8 dev lo scope link
128.0.0.0/1 dev oet1 scope link
192.1.1.0/24 dev br0 scope link src 192.1.1.250
192.168.100.0/24 via 71.236.228.1 dev vlan2
192.168.100.1 via 192.1.1.250 dev br0
The last entry should route traffic to the cable modem (192.168.100.1) through the DD-WRT router (192.1.1.250).
Unfortunately this still doesn't work. Can't ping the cable modem (destination host unreachable).
What am I doing wrong?
I moved this thread to the more appropriate Advanced Networking forum.
It looks like you added the last two lines?
The last line is not making much sense to me but it is still early and I have not had my morning coffee.
But line:
I would have thought the next-to-last line would be sufficient as well, but it didn't work so I manually added the last line.
Yes, I have the kill switch enabled. I deleted the extra route and disabled the kill switch, and I can talk to the cable modem now.
To verify that that was the issue, I re-enabled the kill switch and then couldn't talk to the cable modem.
What is the interaction here? I like having a kill switch. Do I have to choose kill switch or talk to the cable modem?
Thank you for your help.
The routing table with it working is:
0.0.0.0/1 dev oet1 scope link
default via 71.236.228.1 dev vlan2
10.255.255.2 dev oet1 scope link
71.236.228.0/22 dev vlan2 scope link src 71.236.228.176
100.104.252.0/24 dev oet1 scope link src 100.104.252.39
104.129.56.68 via 71.236.228.1 dev vlan2
127.0.0.0/8 dev lo scope link
128.0.0.0/1 dev oet1 scope link
192.1.1.0/24 dev br0 scope link src 192.1.1.250
192.168.100.0/24 via 71.236.228.1 dev vlan2
But this is a different scenario. The wiki still uses `nvram get wan_ifname` ...
Access To Modem Configuration - DD-WRT Wiki _________________ "The woods are lovely, dark and deep,
But I have promises to keep,
And miles to go before I sleep,
And miles to go before I sleep." - Robert Frost
"I am one of the noticeable ones - notice me" - Dale Frances McKenzie Bozzio
Correct, didn't think it would be as you didn't configure a virtual IP for the WAN interface as in that Wiki. <wink> _________________ "The woods are lovely, dark and deep,
But I have promises to keep,
And miles to go before I sleep,
And miles to go before I sleep." - Robert Frost
"I am one of the noticeable ones - notice me" - Dale Frances McKenzie Bozzio