@Adrian<br><br>My apologies for not getting back to you... too many posts to go through and other issues.<br>>- what do you want to achieve?<br>I am attempting (currently in a lab situation) to build a self sustaining mesh network (similar to *cough* locust *cough*)<br>
<br>>- what is your current setup?<br>Currently, I have 3 ALIX.3D3 SBCs each with 2 Wistron-DNMA92 which supports A/B/G/N. One radio is for my backhaul and the other is for hostap. So In a sense, I am mixing the two routing protocols ONLY because of the two seperate WLAN cards. Voyage build installed is 24-12-2011 (interesting thing is that this worked under 0.7.0, do not remember the build date - mid may 2011)<br>
<br>>- what is the actual problem?<br>Unable to get the nodes to communicate via WLAN even in ad-hoc mode. once the eth0 is disconnected, the node is basically a paperweight.<br><br>>- is there an error message?<br>
No error messages at this time.<br><br>
>- what did you do to get this error message?<br>
n/a<br><br>>- not in ad-hoc mode<br>Only did this once to see if there was any communication at all<br><br>>- wrong channel<br>
all on 149<br><br>>- encryption will only work with wep, you can as well use unencrypted links, <br>> wep is broken. Use encrypted protocols instead<br>
none enabled at this point in time<br><br>>- bad signal strength<br>
nodes are like 2 meters apart<br><br>>- mesh networks with olsr won't work with dhcp in a reasonable way, every <br>> node needs a fixed IP within the same broadcast domain<br>they do, node one is 10.0.1.2, node 2 is 10.0.2.2 and node 3 is 10.0.3.2<br>
<br>>- ip_forwarding disabled, check /etc/sysctl.conf<br>
> net.ipv4.ip_forward=1<br>> depending on your setup as well:<br>> net.ipv4.conf.default.rp_filter=1<br>> net.ipv4.conf.all.rp_filter=1<br>
all 3 are as you mention<br><br>> for a quick check if it is enabled: cat /proc/sys/net/ipv4/ip_forward must be 1<br>this is also set as you mention<br><br>>- firewall/iptables that block the wrong traffic<br><div>
Have not touched the firewall, was planning on taking it down for this purpose alone.<br><br>Thanks for the help in advance,<br>John<br></div><br><div class="gmail_quote">On Fri, Feb 10, 2012 at 04:08, Adrian Reyer <span dir="ltr"><<a href="mailto:voyage-linux@lihas.de">voyage-linux@lihas.de</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Hi John,<br>
<div><div class="h5"><br>
On Thu, Feb 09, 2012 at 12:28:32PM -0700, John Schultz wrote:<br>
> I am attempting to get 3 appliances to communicate with each oth and i am<br>
> not having the best of luck. I need a Linux GOD to help me out PLEASE<br>
> !!!!!!.<br>
<br>
</div></div>I think I have pointed out various things and not recieved feedback on<br>
them, your last reply had been on Jan 1st.<br>
I know voyage-linux to some extend, I know OLSR from a few years back, I<br>
know WLAN, I know ad-hoc networks. If I am a Linux GOD in your eyes<br>
depends on your level of knowledge.<br>
I am even willing to help, despite I earn my living by actually charging<br>
people for my help.<br>
However, to be able to help, not just me, but everyone on this list<br>
needs certain information.<br>
- what do you want to achieve?<br>
- what is your current setup?<br>
- what is the actual problem?<br>
- is there an error message?<br>
- what did you do to get this error message?<br>
<br>
Typical things that fail in mesh networks<br>
- misunderstanding on how it works, e.g. hostap and mesh won't work<br>
together in most cases. hostap is infrastructure mode.<br>
- not in ad-hoc mode<br>
- wrong channel<br>
- encryption will only work with wep, you can as well use unencrypted<br>
links, wep is broken. Use encrypted protocols instead<br>
- bad signal strength<br>
- mesh networks with olsr won't work with dhcp in a reasonable way,<br>
every node needs a fixed IP within the same broadcast domain<br>
- ip_forwarding disabled, check /etc/sysctl.conf<br>
net.ipv4.ip_forward=1<br>
depending on your setup as well:<br>
net.ipv4.conf.default.rp_filter=1<br>
net.ipv4.conf.all.rp_filter=1<br>
for a quick check if it is enabled: cat /proc/sys/net/ipv4/ip_forward<br>
must be 1<br>
- firewall/iptables that block the wrong traffic<br>
<br>
Again: giving useful information about the matter helps in recieving<br>
useful information.<br>
<br>
Regards,<br>
Adrian<br>
<span class="HOEnZb"><font color="#888888">--<br>
LiHAS - Adrian Reyer - Hessenwiesenstraße 10 - D-70565 Stuttgart<br>
Fon: <a href="tel:%2B49%20%287%2011%29%2078%2028%2050%2090" value="+4971178285090">+49 (7 11) 78 28 50 90</a> - Fax: <a href="tel:%2B49%20%287%2011%29%2078%2028%2050%2091" value="+4971178285091">+49 (7 11) 78 28 50 91</a><br>
Mail: <a href="mailto:lihas@lihas.de">lihas@lihas.de</a> - Web: <a href="http://lihas.de" target="_blank">http://lihas.de</a><br>
Linux, Netzwerke, Consulting & Support - USt-ID: DE 227 816 626 Stuttgart<br>
</font></span></blockquote></div><br>