public inbox for b.a.t.m.a.n@lists.open-mesh.org
 help / color / mirror / Atom feed
From: Simon Wunderlich <simon.wunderlich@s2003.tu-chemnitz.de>
To: The list for a Better Approach To Mobile Ad-hoc Networking
	<b.a.t.m.a.n@open-mesh.net>
Subject: Re: [B.A.T.M.A.N.] Help in batman advanced configuration
Date: Mon, 26 Jan 2009 22:24:12 +0100	[thread overview]
Message-ID: <20090126212412.GA16326@pandem0nium> (raw)
In-Reply-To: <238a15490901261228t3b1ae9d1l1ced88b416698731@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 3825 bytes --]

Hello Gargi,

your setup looks correct from what you've pasted. Some questions to find
the reason:

1. Have you set "up" all the interfaces by doing "ifconfig <dev> up"? 

2. If you set IPs on br0 of open-mesh1 and br0 of open-mesh2 manually, 
can they ping each other? 

3. If yes (and configured within the subnet of PIX): 
Can you ping PIX from open-mesh2?

4. If you do udhcpc on open-mesh2, do you receive the packet on br0 on
open-mesh1? Please check with tcpdump, this should work. If yes, do you
also receive it on the PIX? (Maybe the answer is getting lost somewhere).

BTW, i've set up similar scenarios yet, this is supposed to work. ;)

best regards,
	Simon



On Mon, Jan 26, 2009 at 02:28:44PM -0600, Gargi Purohit wrote:
> On Mon, Jan 26, 2009 at 1:41 PM, Marek Lindner <lindner_marek@yahoo.de> wrote:
> > On Tuesday 27 January 2009 01:34:16 Gargi Purohit wrote:
> >> I hope other than setting the interface "ath0" in
> >> /proc/net/batman-advanced/interfaces - i dont
> >> need any other configuration changes.
> >>
> >> Since I can batping between the two routers i guess the layer 2
> >> connectivity is established between
> >> these guys - am just wondering if they should be able to forward
> >> requests like dhcp over multiple hop
> >> (1 hop and above)....
> >
> > Yes, a working batping indicates that the connection between both modules is
> > given. The DHCP request should be forwarded without problems. Your setup is
> > misconfigured somewhere.
> >
> > Could you please show the output of "brctl show br0" and "cat
> > /proc/net/batman-adv/interfaces" on both nodes. You can check where the dhcp
> > request dies by using tcpdump or batdump.
> 
> On node 1 (Which is wired)
> ---------------------------------------
> 
> root@open-mesh:~# brctl show br0
> bridge name     bridge id               STP enabled     interfaces
> br0             8000.00180a0145b0       no              bat0
>                                                         ath1
>                                                         ath2
>                                                         eth0
> root@open-mesh:~# cat /proc/net/batman-adv/interfaces
> ath0
> 
> root@open-mesh:~# cat /proc/net/batman-adv/originators
>   Originator     (#/255)           Nexthop [outgoingIF]:   Potential
> nexthops ... [B.A.T.M.A.N. Adv 0.1-beta rv1103, MainIF/MAC:
> ath0/00:18:0a:01:45:b0]
> 00:18:0a:01:44:d0  (255) 00:18:0a:01:44:d0 [      ath0]: 00:18:0a:01:44:d0 (255)
> 
> On node 2 (Which is connected wirelessly to node 1 - eth0 is down)
> --------------------------------------------------------------------------------------------------
> root@open-mesh:/proc/net# brctl show br0
> bridge name     bridge id               STP enabled     interfaces
> br0             8000.00ff678aa75f       no                    ath1
>                                                         bat0
>                                                         ath2
> root@open-mesh:/proc/net# cat /proc/net/batman-adv/interfaces
> ath0
> 
> root@open-mesh:/proc/net# cat /proc/net/batman-adv/originators
>   Originator     (#/255)           Nexthop [outgoingIF]:   Potential nexthops ..
> . [B.A.T.M.A.N. Adv 0.1-beta rv1103, MainIF/MAC: ath0/00:18:0a:01:44:d0]
> 00:18:0a:01:45:b0  (255) 00:18:0a:01:45:b0 [      ath0]: 00:18:0a:01:45:b0 (255)
> 
> root@open-mesh:/proc/net#
> 
> 
> 
> > Regards,
> > Marek
> >
> > _______________________________________________
> > B.A.T.M.A.N mailing list
> > B.A.T.M.A.N@open-mesh.net
> > https://lists.open-mesh.net/mm/listinfo/b.a.t.m.a.n
> >
> _______________________________________________
> B.A.T.M.A.N mailing list
> B.A.T.M.A.N@open-mesh.net
> https://lists.open-mesh.net/mm/listinfo/b.a.t.m.a.n
> 

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

  reply	other threads:[~2009-01-26 21:24 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-01-24  0:30 [B.A.T.M.A.N.] Help in batman advanced configuration Gargi Purohit
2009-01-24  8:42 ` Marek Lindner
2009-01-26 17:34   ` Gargi Purohit
2009-01-26 19:41     ` Marek Lindner
2009-01-26 20:28       ` Gargi Purohit
2009-01-26 21:24         ` Simon Wunderlich [this message]
2009-01-27  1:41           ` Gargi Purohit

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20090126212412.GA16326@pandem0nium \
    --to=simon.wunderlich@s2003.tu-chemnitz.de \
    --cc=b.a.t.m.a.n@open-mesh.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox