Broadband-Hamnet™ Forum :: Applications
Welcome Guest   [Register]  [Login]
 Subject :OLSR Switch on Windows works to connect directly to the mesh... 2013-10-29- 16:24:13 
kv4pc
Member
Joined: 2013-09-30- 20:06:03
Posts: 47
Location: Madison, AL
 

I was able to get an old version of OLSR Switch working with BBHN on my laptop.

This one:

http://www.olsr.org/releases/0.5/olsrd-0.5.6-r3-pre-cac1df64dcd5-setup.exe

Found here:

http://www.olsr.org/?q=download

... is apparently the last binary they posted on olsr.org for windows. They are currently on V0.6.6, and you can go through some back flips to set up a development environment and compile it, but I have not gotten that to work so far. But the last binary does work. Id be very excited to find someone who can compile it - maybe you can post it on  hsmm-mesh.org for general consumption?


I connected to BroadbandHamnet-v1 using my built in wifi, went in and configured a static IP in the 10.x.x.x range (used the LSB triple of the MAC address for x.x.x). Then I fired up OLSR Switch. In the interfaces window, I checked on the 10.x.x.x address of my wifi interfaces and clicked off all the other interfaces. Then I hit Start. In the nodes tab I could immediately see my lone QTH node. I checked to see if I could ping it and that was good. Then I connected to the GUI interface with the web browser. That was good. Its all good! Windows on the mesh!!


I am going use OLSR Switch with a USB WIFI adapter so I can use two wifi interfaces at the same time (one for Part 15 and one for Part 97). Then I am going to write a little batch script to run under Cygwin and nc to put out hamcall beacon packets every 5 minutes to keep it all Part 97.


This is very good! I have been irritated about having to connect to the ethernet to use the node when I am around the house but not in the hamshack.


Now I need to figure out how to get it onto my old obsolete android phone and tablet.... and this looks promising...

https://guardianproject.info/builds/OLSRMeshTether/

I suspect that only the latest olsr versions support IPV6 and that would be highly preferable to making up a 10. IPV4 address and increase the risk of an eventual address collision. But right now I cant get it to compile.


Cheers;

Bob KV4PC


IP Logged
Last Edited On: 2013-10-29- 16:30:13 By kv4pc for the Reason
 Subject :Re:OLSR Switch on Windows works to connect directly to the mesh... 2013-11-07- 14:05:59 
W5LMM
Member
Joined: 2012-02-13- 18:18:04
Posts: 126
Location: Albuquerque, NM
 
That's AWESOME!
IP Logged
 Subject :Re:OLSR Switch on Windows works to connect directly to the mesh... 2013-11-08- 07:32:39 
kv4pc
Member
Joined: 2013-09-30- 20:06:03
Posts: 47
Location: Madison, AL
 

Here is a little bash script that I use under Cygwin to ID the laptop:

fccid:

#!/usr/bin/bash

while true;

do

cat callsign.txt | nc -uw1 10.255.255.255 5555

sleep 300

done


Where callsign.txt is:

Callsign: KV4PC


In a bash shells I do:

$ ./fccid &


"&" to back ground it, and then close the shell. It runs to the next shutdown.

I probably ought to simply kick it off from my start up folder.

Cheers;

Bob KV4PC

IP Logged
Last Edited On: 2013-11-08- 07:34:49 By kv4pc for the Reason
 Subject :Re:OLSR Switch on Windows works to connect directly to the mesh... 2013-12-16- 17:54:45 
W5LMM
Member
Joined: 2012-02-13- 18:18:04
Posts: 126
Location: Albuquerque, NM
 
I can't get it to work. Did you mean putting a static-ip on the computer? or forcing one on the node? Can you give me more information? Thanks!
IP Logged
 Subject :Re:OLSR Switch on Windows works to connect directly to the mesh... 2013-12-17- 01:28:56 
kv4pc
Member
Joined: 2013-09-30- 20:06:03
Posts: 47
Location: Madison, AL
 

The static IP is placed on the Windows WIFI interface that you intend to use.

I used 10.x.y.z where x.y.z are the decimal equivalents of the 3 least significant hex bytes of the MAC address to make an address to use.

I connect the interface to BroadbandHamnet-v1 first, then start OLSR Switch (it should start with Default.olsr). I look for the interface address in the OLSR Switch Interface list and check it. Then I hit save and start. I switch to the Nodes tab and in a few seconds the members on my mesh appear.

I can then ping or connect using 10.x.x.x addresses with relevant apps like IRC, Mumble, web browser, ssh, etc.

DNS does NOT work. OLSR Switch does not have the DNS Plugin. You might be able to use your 

hosts file:

%SystemRoot%\system32\drivers\etc\hosts

to record DNS names on your mesh as a hack to fix this (I havent bothered).

IPV6 does NOT work. Version 5.6-r3 does not have IPV6.

But IPV4 using numerical addresses works just fine.

73;

Bob KV4PC

IP Logged
 Subject :Re:OLSR Switch on Windows works to connect directly to the mesh... 2013-12-17- 08:39:11 
W5LMM
Member
Joined: 2012-02-13- 18:18:04
Posts: 126
Location: Albuquerque, NM
 

OK, now here's where it gets WEIRD.   I am connected to the BBHN node  and have FULL internet access with DNS working just fine. (yes my mesh is normally internet connected)


The odd thing is, the OLSR Switch shows no nodes at all....

What the heck??

Look at this screen shot.




IP Logged
 Subject :Re:OLSR Switch on Windows works to connect directly to the mesh... 2013-12-17- 08:53:33 
kv4pc
Member
Joined: 2013-09-30- 20:06:03
Posts: 47
Location: Madison, AL
 

I agree that is strange. But I have seen a straight "ad-hoc" connection to a mesh node's SSID work intermittently. I suspect that OLSR did not come up and that might be what you have and why no nodes are showing. Can you ping everything on your mesh? Or just the strongest neighbor?

It might be useful to see a screen shot of the Routes and Settings tabs in OLSR Switch as well as the output from route -print and ipconfig /all.

You can write me at kv4pc@qsl.net if you would rather not share with the everyone.

73;

Bob KV4PC

IP Logged
 Subject :Re:OLSR Switch on Windows works to connect directly to the mesh... 2013-12-19- 18:55:37 
W5LMM
Member
Joined: 2012-02-13- 18:18:04
Posts: 126
Location: Albuquerque, NM
 

C:\Users\W5LMM>route print =========================================================================== Interface List 14...00 19 c1 ea 8a e5 ......Bluetooth Device (Personal Area Network) 11...00 0b 97 50 ef 91 ......Marvell Yukon 88E8055 PCI-E Gigabit Ethernet Contr oller 10...00 1d e0 07 ae 15 ......Intel(R) Wireless WiFi Link 4965AG 1...........................Software Loopback Interface 1 19...00 00 00 00 00 00 00 e0 Microsoft ISATAP Adapter 12...00 00 00 00 00 00 00 e0 Teredo Tunneling Pseudo-Interface 15...00 00 00 00 00 00 00 e0 Microsoft ISATAP Adapter #2 20...00 00 00 00 00 00 00 e0 Microsoft ISATAP Adapter #3 =========================================================================== IPv4 Route Table =========================================================================== Active Routes: Network Destination Netmask Gateway Interface Metric 0.0.0.0 0.0.0.0 10.143.7.121 10.7.174.21 25 10.7.174.0 255.255.255.0 On-link 10.7.174.21 281 10.7.174.21 255.255.255.255 On-link 10.7.174.21 281 10.7.174.255 255.255.255.255 On-link 10.7.174.21 281 127.0.0.0 255.0.0.0 On-link 127.0.0.1 306 127.0.0.1 255.255.255.255 On-link 127.0.0.1 306 127.255.255.255 255.255.255.255 On-link 127.0.0.1 306 224.0.0.0 240.0.0.0 On-link 127.0.0.1 306 224.0.0.0 240.0.0.0 On-link 10.7.174.21 281 255.255.255.255 255.255.255.255 On-link 127.0.0.1 306 255.255.255.255 255.255.255.255 On-link 10.7.174.21 281 =========================================================================== Persistent Routes: None IPv6 Route Table =========================================================================== Active Routes: If Metric Network Destination Gateway 12 58 ::/0 On-link 1 306 ::1/128 On-link 12 58 2001::/32 On-link 12 306 2001:0:5ef5:79fd:c89:3946:f5f8:51ea/128 On-link 12 306 fe80::/64 On-link 12 306 fe80::c89:3946:f5f8:51ea/128 On-link 1 306 ff00::/8 On-link 12 306 ff00::/8 On-link =========================================================================== Persistent Routes: None C:\Users\W5LMM>ipconfig /all Windows IP Configuration Host Name . . . . . . . . . . . . : W5LMM-HMMWV-PC Primary Dns Suffix . . . . . . . : Node Type . . . . . . . . . . . . : Hybrid IP Routing Enabled. . . . . . . . : Yes WINS Proxy Enabled. . . . . . . . : No Ethernet adapter Bluetooth Network Connection: Media State . . . . . . . . . . . : Media disconnected Connection-specific DNS Suffix . : Description . . . . . . . . . . . : Bluetooth Device (Personal Area Network) Physical Address. . . . . . . . . : 00-19-C1-EA-8A-E5 DHCP Enabled. . . . . . . . . . . : Yes Autoconfiguration Enabled . . . . : Yes Ethernet adapter Local Area Connection: Media State . . . . . . . . . . . : Media disconnected Connection-specific DNS Suffix . : maiseldata.com Description . . . . . . . . . . . : Marvell Yukon 88E8055 PCI-E Gigabit Ether net Controller Physical Address. . . . . . . . . : 00-0B-97-50-EF-91 DHCP Enabled. . . . . . . . . . . : Yes Autoconfiguration Enabled . . . . : Yes Wireless LAN adapter TB Wifi: Connection-specific DNS Suffix . : Description . . . . . . . . . . . : Intel(R) Wireless WiFi Link 4965AG Physical Address. . . . . . . . . : 00-1D-E0-07-AE-15 DHCP Enabled. . . . . . . . . . . : Yes Autoconfiguration Enabled . . . . : Yes IPv4 Address. . . . . . . . . . . : 10.7.174.21(Preferred) Subnet Mask . . . . . . . . . . . : 255.255.255.0 Default Gateway . . . . . . . . . : 10.143.7.121 DNS Servers . . . . . . . . . . . : 8.8.8.8 NetBIOS over Tcpip. . . . . . . . : Enabled Tunnel adapter isatap.maiseldata.com: Media State . . . . . . . . . . . : Media disconnected Connection-specific DNS Suffix . : Description . . . . . . . . . . . : Microsoft ISATAP Adapter Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0 DHCP Enabled. . . . . . . . . . . : No Autoconfiguration Enabled . . . . : Yes Tunnel adapter Local Area Connection* 11: Connection-specific DNS Suffix . : Description . . . . . . . . . . . : Teredo Tunneling Pseudo-Interface Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0 DHCP Enabled. . . . . . . . . . . : No Autoconfiguration Enabled . . . . : Yes IPv6 Address. . . . . . . . . . . : 2001:0:5ef5:79fd:c89:3946:f5f8:51ea(Prefe rred) Link-local IPv6 Address . . . . . : fe80::c89:3946:f5f8:51ea%12(Preferred) Default Gateway . . . . . . . . . : :: NetBIOS over Tcpip. . . . . . . . : Disabled Tunnel adapter isatap.{57A0507A-576B-4C41-9FFD-79F47E67F1C7}: Media State . . . . . . . . . . . : Media disconnected Connection-specific DNS Suffix . : Description . . . . . . . . . . . : Microsoft ISATAP Adapter #2 Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0 DHCP Enabled. . . . . . . . . . . : No Autoconfiguration Enabled . . . . : Yes Tunnel adapter isatap.{A99A3B0D-5C80-4F08-A744-5CB511866893}: Media State . . . . . . . . . . . : Media disconnected Connection-specific DNS Suffix . : Description . . . . . . . . . . . : Microsoft ISATAP Adapter #3 Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0 DHCP Enabled. . . . . . . . . . . : No Autoconfiguration Enabled . . . . : Yes C:\Users\W5LMM> Interesting.......



Methinks OLSR Switch doth nothing here. 

IP Logged
Last Edited On: 2013-12-19- 19:15:33 By W5LMM for the Reason
 Subject :Re:OLSR Switch on Windows works to connect directly to the mesh... 2013-12-19- 20:52:40 
kv4pc
Member
Joined: 2013-09-30- 20:06:03
Posts: 47
Location: Madison, AL
 

It looks like QuickReply scrogged your columns. Im sorry but I cant make head or tails of this.Try a regular post.

73;

Bob KV4PC

IP Logged
 Subject :Re:OLSR Switch on Windows works to connect directly to the mesh... 2013-12-19- 21:41:24 
W5LMM
Member
Joined: 2012-02-13- 18:18:04
Posts: 126
Location: Albuquerque, NM
 


C:\Users\W5LMM>route print
===========================================================================
Interface List
14...00 19 c1 ea 8a e5 ......Bluetooth Device (Personal Area Network)
11...00 0b 97 50 ef 91 ......Marvell Yukon 88E8055 PCI-E Gigabit Ethernet Cont
oller
10...00 1d e0 07 ae 15 ......Intel(R) Wireless WiFi Link 4965AG
1...........................Software Loopback Interface 1
19...00 00 00 00 00 00 00 e0 Microsoft ISATAP Adapter
12...00 00 00 00 00 00 00 e0 Teredo Tunneling Pseudo-Interface
15...00 00 00 00 00 00 00 e0 Microsoft ISATAP Adapter #2
20...00 00 00 00 00 00 00 e0 Microsoft ISATAP Adapter #3
===========================================================================

IPv4 Route Table
===========================================================================
Active Routes:
Network Destination        Netmask          Gateway       Interface  Metric
0.0.0.0          0.0.0.0     10.143.7.121      10.7.174.21     25
10.7.174.0    255.255.255.0         On-link       10.7.174.21    281
10.7.174.21  255.255.255.255         On-link       10.7.174.21    281
10.7.174.255  255.255.255.255         On-link       10.7.174.21    281
127.0.0.0        255.0.0.0         On-link         127.0.0.1    306
127.0.0.1  255.255.255.255         On-link         127.0.0.1    306
127.255.255.255  255.255.255.255         On-link         127.0.0.1    306
224.0.0.0        240.0.0.0         On-link         127.0.0.1    306
224.0.0.0        240.0.0.0         On-link       10.7.174.21    281
255.255.255.255  255.255.255.255         On-link         127.0.0.1    306
255.255.255.255  255.255.255.255         On-link       10.7.174.21    281
===========================================================================
Persistent Routes:
None

IPv6 Route Table
===========================================================================
Active Routes:
If Metric Network Destination      Gateway
12     58 ::/0                     On-link
1    306 ::1/128                  On-link
12     58 2001::/32                On-link
12    306 2001:0:5ef5:79fd:24ad:2b0c:f5f8:51ea/128
On-link
12    306 fe80::/64                On-link
12    306 fe80::24ad:2b0c:f5f8:51ea/128
On-link
1    306 ff00::/8                 On-link
12    306 ff00::/8                 On-link
===========================================================================
Persistent Routes:
None

C:\Users\W5LMM>

IP Logged
 Subject :Re:OLSR Switch on Windows works to connect directly to the mesh... 2013-12-19- 21:45:04 
W5LMM
Member
Joined: 2012-02-13- 18:18:04
Posts: 126
Location: Albuquerque, NM
 

C:\Users\W5LMM>ipconfig /all

Windows IP Configuration

Host Name . . . . . . . . . . . . : W5LMM-HMMWV-PC
Primary Dns Suffix  . . . . . . . :
Node Type . . . . . . . . . . . . : Hybrid
IP Routing Enabled. . . . . . . . : Yes
WINS Proxy Enabled. . . . . . . . : No

Ethernet adapter Bluetooth Network Connection:

Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix  . :
Description . . . . . . . . . . . : Bluetooth Device (Personal Area Network)
Physical Address. . . . . . . . . : 00-19-C1-EA-8A-E5
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes

Ethernet adapter Local Area Connection:

Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix  . : maiseldata.com
Description . . . . . . . . . . . : Marvell Yukon 88E8055 PCI-E Gigabit Ether
net Controller
Physical Address. . . . . . . . . : 00-0B-97-50-EF-91
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes

Wireless LAN adapter TB Wifi:

Connection-specific DNS Suffix  . :
Description . . . . . . . . . . . : Intel(R) Wireless WiFi Link 4965AG
Physical Address. . . . . . . . . : 00-1D-E0-07-AE-15
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
IPv4 Address. . . . . . . . . . . : 10.7.174.21(Preferred)
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 10.143.7.121
DNS Servers . . . . . . . . . . . : 8.8.8.8
NetBIOS over Tcpip. . . . . . . . : Enabled

Tunnel adapter isatap.maiseldata.com:

Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix  . :
Description . . . . . . . . . . . : Microsoft ISATAP Adapter
Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes

Tunnel adapter Local Area Connection* 11:

Connection-specific DNS Suffix  . :
Description . . . . . . . . . . . : Teredo Tunneling Pseudo-Interface
Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes
IPv6 Address. . . . . . . . . . . : 2001:0:5ef5:79fd:24ad:2b0c:f5f8:51ea(Pref
erred)
Link-local IPv6 Address . . . . . : fe80::24ad:2b0c:f5f8:51ea%12(Preferred)
Default Gateway . . . . . . . . . : ::
NetBIOS over Tcpip. . . . . . . . : Disabled

Tunnel adapter isatap.{57A0507A-576B-4C41-9FFD-79F47E67F1C7}:

Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix  . :
Description . . . . . . . . . . . : Microsoft ISATAP Adapter #2
Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes

Tunnel adapter isatap.{A99A3B0D-5C80-4F08-A744-5CB511866893}:

Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix  . :
Description . . . . . . . . . . . : Microsoft ISATAP Adapter #3
Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes

C:\Users\W5LMM>

IP Logged
 Subject :Re:OLSR Switch on Windows works to connect directly to the mesh... 2013-12-19- 21:49:01 
W5LMM
Member
Joined: 2012-02-13- 18:18:04
Posts: 126
Location: Albuquerque, NM
 
Yeah, quick reply mangled it. I am usig the mesh at this moment, and am able to connect to both nodes. I am also able to connect to shares etc on the local network (since one node is gateway.
IP Logged
 Subject :Re:OLSR Switch on Windows works to connect directly to the mesh... 2013-12-20- 01:38:16 
kv4pc
Member
Joined: 2013-09-30- 20:06:03
Posts: 47
Location: Madison, AL
 

I would also like to see what is on your "Settings" tab and "Output" tabs.

It all looks good except the default gateway entry.

I left mine blank for the interface I connected to the mesh with and instead added persistent routes (IPv4) with high metric numbers (4 digits) for each way I reach the internet(mesh or AP or wired ethernet - I routinely use my laptop several different ways). On the mesh I usually get a 0.0.0.0 and a 10.0.0.0 route automatically with a low metric (3 digits or less) when I fire things up but if I dont it all still works anyway.

Less important, I set my nearest "HNA" router advertising the internet exit as the "first DNS" and 8.8.8.8 and 8.8.4.4 (google) as the second and third. DNS has never worked right for me, and the windows version of OLSRd lacks the DNS plug-in, but that configuration has given me the best results wrt the external internet.

I also just noticed I have set up OLSR Switch to run as Administrator. I cant remember why I decided to do that but it could be a factor.

Im glad adhoc is working for you! But it has always been very fragile for me if I try to roam or if events are causing topology changes on the mesh. Or even if I have two overlapping nodes at about the same signal strength at my location. If OLSR Switch is working, any streams or connections I may have running tend to survive topology changes. Straight adhoc doesnt.

It is also very handy to look on the nodes tab and see everything on the mesh. Mine lists every node including my GRE tunnels and the nodes on the other side.

73;

Bob KV4PC

IP Logged
Last Edited On: 2013-12-20- 01:40:36 By kv4pc for the Reason
 Subject :Re:OLSR Switch on Windows works to connect directly to the mesh... 2013-12-20- 01:48:08 
kv4pc
Member
Joined: 2013-09-30- 20:06:03
Posts: 47
Location: Madison, AL
 
Another thought... if you have local firewall service running on your host you might need to punch a hole for the olsr protocol. Port 698 has to be passed through and may not be by defaut.
IP Logged
 Subject :Re:OLSR Switch on Windows works to connect directly to the mesh... 2013-12-20- 06:03:20 
W5LMM
Member
Joined: 2012-02-13- 18:18:04
Posts: 126
Location: Albuquerque, NM
 

Hi Bob!


Opened 698 UDP/TCP in windows firewall, also I do run OLSR Switch as admin too.


Here's some scrapes of the various tabs in Switch.  Thanks!




IP Logged
 Subject :Re:OLSR Switch on Windows works to connect directly to the mesh... 2013-12-20- 15:18:18 
kv4pc
Member
Joined: 2013-09-30- 20:06:03
Posts: 47
Location: Madison, AL
 

Your settings are same as mine. There arent any errors in your Output window. I dont know what else to say or try.

Im posting my Nodes tab so you can see what it looks like with a connected mesh. The 172.30.1.2 address is my end of a GRE tunnel connecting the two 10.x.x.x nodes.

I have also post my Default.olsr file so you can see what is in it FWIW.

73;

Bob KV4PC



#

# Configuration file for solsr.org - pre-0.5.6-r3

# automatically generated by olsrd-cnf parser v. 0.1.2

#

 

# Debug level(0-9)

# If set to 0 the daemon runs in the background

 

DebugLevel 0

 

# IP version to use (4 or 6)

 

IpVersion 4

 

# FIBMetric ("flat", "correct", or "approx")

 

FIBMetric "flat"

 

# HNA IPv4 routes

# syntax: netaddr/prefix

 

Hna4 {

}

 

# Should olsrd keep on running even if there are

# no interfaces available? This is a good idea

# for a PCMCIA/USB hotswap environment.

# "yes" OR "no"

 

AllowNoInt yes

 

# TOS(type of service) to use. Default is 16

 

TosValue 16

 

# Policy Routing Table to use. Default is 254

 

RtTable 254

 

# Policy Routing Table to use for the default Route. Default is 0 (Take the same table as specified by RtTable)

 

RtTableDefault 0

 

# The fixed willingness to use(0-7)

# If not set willingness will be calculated

# dynammically based on battery/power status

 

#Willingness 4

 

# Allow processes like the GUI front-end

# to connect to the daemon.

 

IpcConnect {

MaxConnections 1

Host 127.0.0.1

Net 10.0.0.0/8

Net 192.168.1.0/24

}

 

# Hysteresis adds more robustness to the

# link sensing.

# Used by default. 'yes' or 'no'

 

UseHysteresis no

 

# Hysteresis parameters

# Do not alter these unless you know

# what you are doing!

# Set to auto by default. Allowed

# values are floating point values

# in the interval 0,1

# THR_LOW must always be lower than

# THR_HIGH!!

 

#HystScaling 0.50

#HystThrHigh 0.80

#HystThrLow 0.30

 

# Polling rate in seconds(float).

# Auto uses default value 0.05 sec

 

Pollrate 0.05

# Interval to poll network interfaces for configuration

# changes. Defaults to 2.5 seconds

NicChgsPollInt 2.50

# TC redundancy

# Specifies how much neighbor info should

# be sent in TC messages

# Possible values are:

# 0 - only send MPR selectors

# 1 - send MPR selectors and MPRs

# 2 - send all neighbors

#

# defaults to 0

 

TcRedundancy 2

 

# MPR coverage

# Specifies how many MPRs a node should

# try select to reach every 2 hop neighbor

# Can be set to any integer >0

# defaults to 1

 

MprCoverage 7

 

# Link quality level

# 0 = do not use link quality

# 1 = use link quality for MPR selection

# 2 = use link quality for MPR selection and routing

 

LinkQualityLevel 2

 

# Fish Eye algorithm

# 0 = do not use fish eye

# 1 = use fish eye

 

LinkQualityFishEye 1

 

# Link quality algorithm (if LinkQualityLevel > 0)

# etx_fpm (hello loss, fixed point math)

# etx_float (hello loss, floating point)

# etx_ff (packet loss for freifunk compat)

 

LinkQualityAlgorithm "etx_ff"

 

# Link quality aging factor

 

LinkQualityAging 0.100000

 

# NAT threshold

 

NatThreshold 1.000000

 

# Clear screen when printing debug output?

 

ClearScreen no

 

# Olsrd plugins to load

# This must be the absolute path to the file

# or the loader will use the following scheme:

# - Try the paths in the LD_LIBRARY_PATH

# environment variable.

# - The list of libraries cached in /etc/ld.so.cache

# - /lib, followed by /usr/lib

 

LoadPlugin "olsrd_txtinfo.dll" {

PlParam "Accept" "127.0.0.1"

}

LoadPlugin "olsrd_dot_draw.dll" {

PlParam "Accept" "127.0.0.1"

}

LoadPlugin "olsrd_httpinfo.dll" {

PlParam "port" "8080"

PlParam "Host" "127.0.0.1"

PlParam "Net" "10.0.0.0 255.0.0.0"

PlParam "Net" "192.168.0.0 255.255.0.0"

}

 

# Interfaces

# Multiple interfaces with the same configuration

# can shar the same config block. Just list the

# interfaces(e.g. Interface "eth0" "eth2"

 

Interface "IF35" {

 

# IPv4 broadcast address to use. The

# one usefull example would be 255.255.255.255

# If not defined the broadcastaddress

# every card is configured with is used

 

#Ip4Broadcast 255.255.255.255

 

# IPv6 address scope to use.

# Must be 'site-local' or 'global'

 

Ip6AddrType global

 

# IPv6 multicast address to use when

# using site-local addresses.

# If not defined, ff05::15 is used

Ip6MulticastSite ff05::15

 

# IPv6 multicast address to use when

# using global addresses

# If not defined, ff0e::1 is used

Ip6MulticastGlobal ff0e::1

 

# Olsrd can autodetect changes in

# interface configurations. Enabled by default

# turn off to save CPU.

AutoDetectChanges: yes

# Emission and validity intervals.

# If not defined, RFC proposed values will

# in most cases be used.

 

HelloInterval 5.00

HelloValidityTime 125.00

TcInterval 3.00

TcValidityTime 375.00

MidInterval 25.00

MidValidityTime 375.00

HnaInterval 25.00

HnaValidityTime 375.00

#LinkQualityMult default 1.0

# When multiple links exist between hosts

# the weight of interface is used to determine

# the link to use. Normally the weight is

# automatically calculated by olsrd based

# on the characteristics of the interface,

# but here you can specify a fixed value.

# Olsrd will choose links with the lowest value.

# Note:

# Interface weight is used only when LinkQualityLevel is 0.

# For any other value of LinkQualityLevel, the interface ETX

# value is used instead.

 

#Weight 0

 

}

 

 

# END AUTOGENERATED CONFIG

IP Logged
Page # 


Powered by ccBoard


SPONSORED AD: