[cellis]

I have a routing issue and suspect it to be a bug but any will do as I have struggled with this for a few days.

I have 3 Routers A B C. they A and B are Linksys WRT160Nv3 and C is a Linksys WRT54G/GL/GS V5
Router A Has firmware DD-WRT v24-sp2 (08/07/10) std-nokaid-small - build 14896
Router B Has firmware DD-WRT v24-sp2 (08/07/10) micro - build 14896
Router C Has Firmware DD-WRT v24-sp2 (07/22/09) micro - build 12548M NEWD Eko

Router A (Lan 10.0.10.X. WAN is 41.186.15.109 configed as gatway). is on a remote site connecting to a PPPoE connection to Router B (LAN 192.168.10.2 WAN is 41.186.15.111 configured as router ). Router sits on the same LAN as router C ( LAN 192.168.10.1 configured as gatway) and connects to the internet. Router A is configured as a gateway to send all packets to Router B. That’s fine I can see the network on B and can access both router on the local network from A. From the local network I can see Router A so we communicate between lans

My problem is that I want A to access the internet so I added the following rule to B
0.0.0.0 0.0.0.0 192.168.10.1
10.0.10.0 255.255.255.0 41.186.15.110( this is the next router on the wan side.)
41.186.15.0 255.255.255.0 41.186.15.10

I then added the rule this rule to Router C
10.0.10.0 255.255.255.0 192.168.10.2
41.186.15.0 255.255.255.0 192.168.10.2

As soon as I add the rule to router B I can’t see Router A If I do a trace route the packets bounce between router B and C.
It seems to me that router B ignores the other routes and just user 0.0.0.0 it does this if the rule is the first or last in the routing table.
Can anyone help on how I get router B to check the other rules before using 0.0.0.0 route.
Thanks

[phuzi0n]

It's not really clear what routes you're adding. You said "rule" which is singular but then listed multiple routes.

The only route you need on router B is this:

10.0.10.0 255.255.255.0 41.186.15.109

[cellis]

I Have attached a drawing of the network with all relevant IP address to reduce any confusion as I may not be explaining myself clearly.

The issue I have is that when I put in the route 0.0.0.0 in router B as the catch all to route to the internet. Router A stops seeing router B and C or the LAN they sit on and Router A can’t get to the internet.

If I remove the route 0.0.0.0 and put in the ip address for cnn.com . the LAN side of router A can access the cnn page only and see router B and C.
When the route 0.0.0.0 is in router B and I do a trace route the packets bounce between routers B and C. It ignores all other routes in the static routing table.

As I have only 50 possible static routes in the router I cannot enter all possible routes to the internet. I assumed the router would first read all the routes before using 0.0.0.0 but it seems as soon as that is entered in the static table it becomes the first rout that the router looks at.

[cellis]

Thanks for that but still have the same problem. I set up the routers as you suggested and I hit the same problem
When I look at the routing tables this is what I get.

Routing Table Entry List for 192.168.10.1 (Router C)
Destination LAN NET Subnet Mask Gateway Interface
10.194.113.0 255.255.255.0 0.0.0.0 WAN
192.168.10.0 255.255.255.0 0.0.0.0 LAN & WLAN
10.0.10.0 255.255.255.0 192.168.10.2 LAN & WLAN
169.254.0.0 255.255.0.0 0.0.0.0 LAN & WLAN
0.0.0.0 0.0.0.0 10. 194.113.129 WAN


Routing Table Entry List (Router B) Before 0.0.0.0 0.0.0.0 192.168.10.1 is added

Destination LAN NET Subnet Mask Gateway Interface
41.186.15.110 255.255.255.255 0.0.0.0 ppp0
41.186.15.110 255.255.255.255 0.0.0.0 ppp0
192.168.10.0 255.255.255.0 0.0.0.0 LAN & WLAN
169.254.0.0 255.255.0.0 0.0.0.0 LAN & WLAN
0.0.0.0 0.0.0.0 41.186.15.110 ppp0


Routing Table Entry List for 192.168.10.2 (router B) after 0.0.0.0 0.0.0.0 192.168.10.1 is added

Destination LAN NET Subnet Mask Gateway Interface
41.186.15.110 255.255.255.255 0.0.0.0 ppp0
41.186.15.110 255.255.255.255 0.0.0.0 ppp0
192.168.10.0 255.255.255.0 0.0.0.0 LAN & WLAN
169.254.0.0 255.255.0.0 0.0.0.0 LAN & WLAN
0.0.0.0 0.0.0.0 192.168.10.2 LAN & WLAN

These are the trace routes carried out.

(Router B) Before 0.0.0.0 0.0.0.0 192.168.10.1 is added

IP DNS Current Response Time Current Response Time Packet Loss Machine Type
192.168.10.133 Clifford-PC 0 ms 0 ms 0% Windows
192.168.10.1 1 ms 1 ms 0%
192.168.10.2 1 ms 1 ms 0%
41.186.15.110 no response 100%
41.186.15.108 no response 100%
10.0.10.1 197 ms 197 ms 0%


(router B) after 0.0.0.0 0.0.0.0 192.168.10.1 is added


IP DNS Current Response Time Current Response Time Packet Loss Machine Type
192.168.10.133 Clifford-PC 0 ms 0 ms 0% Windows
192.168.10.1 2 ms 2 ms 0%
192.168.10.2 1 ms 1 ms 0%
192.168.10.1 2 ms 2 ms 0%
192.168.10.2 2 ms 2 ms 0%
192.168.10.1 2 ms 2 ms 0%
192.168.10.2 2 ms 2 ms 0%
192.168.10.1 2 ms 2 ms 0%
192.168.10.2 2 ms 2 ms 0%
192.168.10.1 2 ms 2 ms 0%
192.168.10.2 2 ms 2 ms 0%
192.168.10.1 2 ms 2 ms 0%
192.168.10.2 2 ms 2 ms 0%
192.168.10.1 2 ms 2 ms 0%
192.168.10.2 2 ms 2 ms 0%

It seems to me that the router software ignores the route 10.0.10.0 255.255.255.0 41.186.15.108 even though when entered it saves the route but does not add it to
the routing table hence the data can never find its way back to router A (10.0.10.1) Even after a reboot you can still see the root on the page it was entered
but if you look at the routing table it is not there.

If you enter the destnation web page IP address and remove the route 0.0.0.0 it has no problem routing it according to the staic route. I am beging to belive
that the problem is the route 0.0.0.0 with PPPoE.

[phuzi0n]

Since the PPPoE cloud is using a /32 mask you also need to give router B a route to 41.186.15.108/32 via ppp0 before you can create a route to 10.0.10.0/24 with 41.186.15.108 as the gateway for it.

41.186.15.108 255.255.255.255 0.0.0.0 ppp0

IIRC the GUI has problems creating routes on interfaces that aren't up when the router boots so you may have to use the route or ip commands to create your routes in the firewall script.

[cellis]

thank you it worked once i used the ip commands.