RIP setting

[gunther_01]

I have been trying to get a private subnet assigned to one of my customers. So I placed another subnet on my WAR1 Ether1 interface to route a /30 over to this customers new router.

After turning on RIP on the WAR1 client, I realized I was broadcasting my "normal" eth1 subnet 10.0.0.0/24. And that probably isn't a good idea. It took me a bit to get things to work. But can someone please verify this as functional at the dynamic side of things. It is pingable from everywhere, I just don't like surprises. And I have this "I forgot something feeling"

Client eth1 IP settings
10.254.3.1/30
10.0.0.1/24

WAR1 RIP info
router rip
network 10.254.3.0/30
neighbor 10.3.1.1(this IP is the AP the WAR connects to)

I played hell getting this far. But in the end it seemed I HAD to have the neighbor command in there again. Which I thought we didn't have to do anymore. Both AP and Client are on 1.3.23b.

I know this topic seems moot to some, but routing tables.... It would be great to take my edge box to a better version, instead of keeping it lower so I can keep my tables viewable.

[DrLove73]

I know this topic seems moot to some, but routing tables.... It would be great to take my edge box to a better version, instead of keeping it lower so I can keep my tables viewable.

You can pull sysinfo via starutil on regular basis via script (or only when you need it), and then all you have to do is to go to that folder and view last sysinfo file.

[gunther_01]

You can pull sysinfo via starutil on regular basis via script (or only when you need it), and then all you have to do is to go to that folder and view last sysinfo file.

Cool, so it's just not in the GUI sysinfo. That's good to know. I'd still prefer it in the GUI also ;) Even selectable somewhere would be nice for those monster routing tables that others don't want to deal with regularly.

[DrLove73]

GUI sysinfo routing tables were disabled because of the complaints when BGP? was used.

Maybe 1.3.24b (or just 1.3.24 could be created with just that change (like 1.1.14 was published) so we with small number of routes could troubleshoot them easy. It would also give VNC a chance to publish last 1.3.x version as stable.

[Elshar]

It was because of OLSR, and because it reports the routing table for the entire network (including routes that would normally be covered by the default route, as well as host routes to the individual nodes). Makes the routing table huge.

You can still access it in the radios by going into the system shell, typing sh and then typing ip route.

Also, there's the ability to show routes going out specific interfaces, and all kinds of interesting things.

[lonnie]

No it was for BGP which can have 250,000 routes.