[Olsr-users] OLSR setup on XP/CE with iPhone, Vista and 802.11n thrown in

[Sven-Ola Tuecke]

Jeremy,

most windoze users stumble over their optimized-for-personal-use network 
config (means: only admin can set routes, firewalling prevents forwarding 
etc).

Try setting up that stuff manually first. If it runs, automate with olsrd. 
Example:

A:
route add 192.168.0.2 255.255.255.255 192.168.0.2
route add 192.168.0.3 255.255.255.255 192.168.0.2
B:
route add 192.168.0.1 255.255.255.255 192.168.0.1
route add 192.168.0.3 255.255.255.255 192.168.0.3
C:
route add 192.168.0.1 255.255.255.255 192.168.0.2
route add 192.168.0.2 255.255.255.255 192.168.0.2
ping 192.168.0.1

If the ping command works, start using olsrd. Otherwise use brains and/or 
wireshark.

// Sven-Ola

""Jeremy King"" <(spam-protected)> schrieb im Newsbeitrag 
news:!&!AAAAAAAAAAAYAAAAAAAAAA0pJ/KKqwxFubYY6DsXY2/CgAAAEAAAAAYhVRgvWmtNkEF9KwVZ6wQBAAAAAA==@uieinc.com...
> Hello,
>
> I've been trying to get OLSR to work on a number of machines, but I cannot
> get packets forwarded. I've a number of questions.
>
> Problem #1.
> Here's my setup. All are on the same ad-hoc network, running WEP.
> A. XP Laptop. Running Switch 0.5.5. IP address 192.168.0.2
> B. XP Laptop. Running Switch 0.5.5. IP address 192.168.0.1
> C. Win CE.    Running olsrd.exe 0.5.4.  IP address 192.168.0.3
>
> In this setup, I have A <--> B <--> C. Devices C and A cannot see each 
> other
> directly, but see the other as a second off B Neither A nor C can ping 
> each
> other. Both can ping B, and B can ping them. Neither route table for A or 
> C
> include the other. How can I get A to talk to C? This is the route table 
> for
> A:
> ===========================================================================
> Interface List
> 0x1 ........................... MS TCP Loopback interface
> 0x2 ...00 e0 00 61 62 31 ...... Intersil PRISM Wireless LAN PCI Card -
> Packet Scheduler Miniport
> ===========================================================================
> ===========================================================================
> Active Routes:
> Network Destination        Netmask          Gateway       Interface 
> Metric
>          0.0.0.0          0.0.0.0      192.168.2.1     192.168.2.2   30
>        127.0.0.0        255.0.0.0        127.0.0.1       127.0.0.1   1
>      192.168.2.0    255.255.255.0      192.168.2.2     192.168.2.2   30
>      192.168.2.1  255.255.255.255      192.168.2.4     192.168.2.2   30
>      192.168.2.2  255.255.255.255        127.0.0.1       127.0.0.1   30
>      192.168.2.4  255.255.255.255      192.168.2.2     192.168.2.2   30
>    192.168.2.255  255.255.255.255      192.168.2.2     192.168.2.2   30
>        224.0.0.0        240.0.0.0      192.168.2.2     192.168.2.2   30
>  255.255.255.255  255.255.255.255      192.168.2.2     192.168.2.2   1
> Default Gateway:       192.168.2.1
> ===========================================================================
> Persistent Routes:
>  None
>
> I tried to use my iPhone (192.168.2.4) as a node in this network, as well,
> but I removed it to remove another variable.
>
> Problem #2.
> Machine B, listed above, has a Ethernet connection to my intranet (with IP
> 192.168.0.38). How can I route default traffic from my mesh sub-net
> (192.168.2.x) to my Internet gateway (192.168.0.1) on my Ethernet network.
> Will having "HNA4 {0.0.0.0   0.0.0.0}" give me this route? and will adding
> "192.168.0.0   255.255.255.0" in the brackets give me access to the
> 912.168.0.x subnet from the mesh subnet?
>
> Problem #3.
> I've tried to include two Vista machines, each running 802.11n. They can 
> see
> the other nodes, but the other nodes can't see them, and they can't ping
> anyone. Is this a problem with mixing N and G? Or is it due to the problem
> I've read with N not working in ad-hoc mode?
>
> Other questions:
> I've looked at the conf file that Switch can generate. It has the 
> following
> entry:
>   # FIBMetric ("flat", "correct", or "approx")
>   FIBMetric  "flat"
> What does this do?
>
> Whenever the Vista and CE machines start OSLR, I get "ERROR -
> EnableRouter():" right after the interfaces detail output. When I stop 
> OLSR,
> I get "ERROR - UnenableRouter():". The XP builds do not have the message
> showing up. I'm not sure what's not working, but I can't help but wonder 
> if
> it's causing/resulting some of my connection problems.
>
> One of the things that I see when watching the debug output from the Vista
> machines is comments about receiving TC/HNA from NON SYM neighbors. What
> does it take to be a SYM or NON SYM node?
>
> The Vista machines have "--- SPF-stats for 1 nodes, 0 routes
> (total/init/run/route/kern): 7000, 0, 7000, 0, 0" in the DIJKSTRA area of
> the debug output, while I never see anything on the other machines in this
> area.
>
> Sorry for all the questions. :-\
>
> ---
> Jeremy
>
>
>
> -- 
> Olsr-users mailing list
> (spam-protected)
> http://lists.olsr.org/mailman/listinfo/olsr-users