Elshar
02-26-2008, 04:19 PM
Hey guys,
Just started messing around with OLSR today. I've got a small setup going so far with a few machines, but for some reason there is sporadic routing information being passed between any of them. They all seem to mostly neighbor up okay though.
Here's the topology of the network. They all communicate on 10.31.3.0/24:
Internet
|
Star
/---------|------------\
FBSD1 FBSD2 Linux
| | |
Internal1 Internal2 Internal3
Star's interfaces:
eth0 (internal)
192.168.1.1/24
192.168.254.1/24
public_ip/28
10.31.3.1/24
192.168.251.1/24
wpci1 (External interface - su mode)
10.30.49.65/24
wpci2 (internal - ap mode)
192.168.17.1/24
192.168.20.1/24
FBSD1's interfaces:
fxp0 (external ether)
10.31.3.2/24
virt0 (internal virtual)
10.250.1.1/24
FBSD2's interfaces:
em0 (external ether)
10.31.3.4/24
fxp0 (internal ether)
192.168.100.1/24
10.250.0.1/24
Linux's interfaces:
eth2 (external ether)
10.31.3.7/24
eth3 (internal ether)
10.250.2.1/24
For some reason my two FBSD boxes "see" the 10.250.2.0/24 route from the linux box, and the linux box sees the 10.250.0.0/24 from FBSD2.
None of them are being sent, (or are accepting; I haven't done a tcpdump yet) the default route from 10.31.3.1.
None of them show 10.31.3.1 in their neighbors or topology, but 10.31.3.1 shows all of them.
Also oddly enough, FBSD2 and Linux both have a route to 192.168.100.1/32 on FBSD1. I'm not sure why this is either. There's no 192.x's in any host's Hna4 section.
Also, they are all running olsrd 0.5.4, which is the same as the version in star, which is running on XSCALE-WAR V3 1.3.13
Hopefully someone can point me in the right direction here. :)
Just started messing around with OLSR today. I've got a small setup going so far with a few machines, but for some reason there is sporadic routing information being passed between any of them. They all seem to mostly neighbor up okay though.
Here's the topology of the network. They all communicate on 10.31.3.0/24:
Internet
|
Star
/---------|------------\
FBSD1 FBSD2 Linux
| | |
Internal1 Internal2 Internal3
Star's interfaces:
eth0 (internal)
192.168.1.1/24
192.168.254.1/24
public_ip/28
10.31.3.1/24
192.168.251.1/24
wpci1 (External interface - su mode)
10.30.49.65/24
wpci2 (internal - ap mode)
192.168.17.1/24
192.168.20.1/24
FBSD1's interfaces:
fxp0 (external ether)
10.31.3.2/24
virt0 (internal virtual)
10.250.1.1/24
FBSD2's interfaces:
em0 (external ether)
10.31.3.4/24
fxp0 (internal ether)
192.168.100.1/24
10.250.0.1/24
Linux's interfaces:
eth2 (external ether)
10.31.3.7/24
eth3 (internal ether)
10.250.2.1/24
For some reason my two FBSD boxes "see" the 10.250.2.0/24 route from the linux box, and the linux box sees the 10.250.0.0/24 from FBSD2.
None of them are being sent, (or are accepting; I haven't done a tcpdump yet) the default route from 10.31.3.1.
None of them show 10.31.3.1 in their neighbors or topology, but 10.31.3.1 shows all of them.
Also oddly enough, FBSD2 and Linux both have a route to 192.168.100.1/32 on FBSD1. I'm not sure why this is either. There's no 192.x's in any host's Hna4 section.
Also, they are all running olsrd 0.5.4, which is the same as the version in star, which is running on XSCALE-WAR V3 1.3.13
Hopefully someone can point me in the right direction here. :)