[Voyage-linux] wireless assistance needed (ad-hoc, olsr, ibss, etc...)

John Schultz (spam-protected)
Fri Feb 10 20:24:21 HKT 2012


@Adrian

My apologies for not getting back to you... too many posts to go through
and other issues.
>- what do you want to achieve?
I am attempting (currently in a lab situation) to build a self sustaining
mesh network (similar to *cough* locust *cough*)

>- what is your current setup?
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)

>- what is the actual problem?
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.

>- is there an error message?
No error messages at this time.

>- what did you do to get this error message?
n/a

>- not in ad-hoc mode
Only did this once to see if there was any communication at all

>- wrong channel
all on 149

>- encryption will only work with wep, you can as well use unencrypted
links,
>  wep is broken. Use encrypted protocols instead
none enabled at this point in time

>- bad signal strength
nodes are like 2 meters apart

>- mesh networks with olsr won't work with dhcp in a reasonable way, every
>  node needs a fixed IP within the same broadcast domain
they do, node one is 10.0.1.2, node 2 is 10.0.2.2 and node 3 is 10.0.3.2

>- ip_forwarding disabled, check /etc/sysctl.conf
>   net.ipv4.ip_forward=1
> depending on your setup as well:
>   net.ipv4.conf.default.rp_filter=1
>   net.ipv4.conf.all.rp_filter=1
all 3 are as you mention

> for a quick check if it is enabled: cat /proc/sys/net/ipv4/ip_forward
must be 1
this is also set as you mention

>- firewall/iptables that block the wrong traffic
Have not touched the firewall, was planning on taking it down for this
purpose alone.

Thanks for the help in advance,
John

On Fri, Feb 10, 2012 at 04:08, Adrian Reyer <voyage-linux at lihas.de> wrote:

> Hi John,
>
> On Thu, Feb 09, 2012 at 12:28:32PM -0700, John Schultz wrote:
> > I am attempting to get 3 appliances to communicate with each oth and i am
> > not having the best of luck. I need a Linux GOD to help me out PLEASE
> > !!!!!!.
>
> I think I have pointed out various things and not recieved feedback on
> them, your last reply had been on Jan 1st.
> I know voyage-linux to some extend, I know OLSR from a few years back, I
> know WLAN, I know ad-hoc networks. If I am a Linux GOD in your eyes
> depends on your level of knowledge.
> I am even willing to help, despite I earn my living by actually charging
> people for my help.
> However, to be able to help, not just me, but everyone on this list
> needs certain information.
> - what do you want to achieve?
> - what is your current setup?
> - what is the actual problem?
>  - is there an error message?
>  - what did you do to get this error message?
>
> Typical things that fail in mesh networks
> - misunderstanding on how it works, e.g. hostap and mesh won't work
>  together in most cases. hostap is infrastructure mode.
> - not in ad-hoc mode
> - wrong channel
> - encryption will only work with wep, you can as well use unencrypted
>  links, wep is broken. Use encrypted protocols instead
> - bad signal strength
> - mesh networks with olsr won't work with dhcp in a reasonable way,
>  every node needs a fixed IP within the same broadcast domain
> - ip_forwarding disabled, check /etc/sysctl.conf
>    net.ipv4.ip_forward=1
>  depending on your setup as well:
>    net.ipv4.conf.default.rp_filter=1
>    net.ipv4.conf.all.rp_filter=1
>  for a quick check if it is enabled: cat /proc/sys/net/ipv4/ip_forward
>  must be 1
> - firewall/iptables that block the wrong traffic
>
> Again: giving useful information about the matter helps in recieving
> useful information.
>
> Regards,
>        Adrian
> --
> LiHAS - Adrian Reyer - Hessenwiesenstraße 10 - D-70565 Stuttgart
> Fon: +49 (7 11) 78 28 50 90 - Fax:  +49 (7 11) 78 28 50 91
> Mail: lihas at lihas.de - Web: http://lihas.de
> Linux, Netzwerke, Consulting & Support - USt-ID: DE 227 816 626 Stuttgart
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://list.voyage.hk/pipermail/voyage-linux/attachments/20120210/e33c4ce7/attachment.html>


More information about the Voyage-linux mailing list