public inbox for b.a.t.m.a.n@lists.open-mesh.org
 help / color / mirror / Atom feed
From: Axel Neumann <axel@open-mesh.net>
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.] routing problem?
Date: Sat, 10 Nov 2007 12:43:28 +0100	[thread overview]
Message-ID: <200711101243.28980.axel@open-mesh.net> (raw)
In-Reply-To: <2bda28cd0711090623r2e7b8750g558aebab35247da0@mail.gmail.com>

On Freitag 09 November 2007, Stefano Scipioni wrote:
> I'm testing batman 0.3 exp rv 777
>
> traceroute give me a problem
>
> root@sala:~$ traceroute  10.0.1.1
> traceroute: can't find interface
> root@sala:~$ ip route ls tab 66
> 10.1.5.104 dev ath0  proto static  scope link  src 10.1.5.102
> 10.1.5.130 via 10.1.5.104 dev ath0  proto static
> 10.1.5.129 via 10.1.5.1 dev ath0  proto static
> 10.1.5.1 via 10.1.5.104 dev ath0  proto static
> root@sala:~$ ip route ls tab 65
> 10.0.1.0/24 via 10.1.5.1 dev ath0  proto static
> root@sala:~$ traceroute  10.0.1.1
> traceroute: can't find interface
> root@sala:~$ ping 10.0.1.1
> PING 10.0.1.1 (10.0.1.1): 56 data bytes
> 64 bytes from 10.0.1.1: seq=0 ttl=61 time=9.119 ms
> 64 bytes from 10.0.1.1: seq=1 ttl=61 time=8.486 ms
>
> traceroute works If I utilize source address option.
> What is my mistake?

i think theres no mistake, busybox-traceroute is just to stupid to figure out 
the correct src ip. In my test, tcpdump showed that it uses the first 
(non-alias) address of the outgoing interface. No matter if the route to the 
destination specifies the src address or not. Did you use an alias interfaces 
for this scenrio?

And even better, the traceroute on my notebook chooses the correct outgoing 
src address but unless i specify it also manually it does not work either. 
The reason is a corrupted udp checksum which is verified by the final 
destination of the packet.


>
> Also if one of nodes has no batman-exp running on it I can't reach it
> from neighbours (I use batmand on ath0 interface, not an alias)?
> Perhaps I have to use --no-unreachable-rule?

For correct routing between batman-nodes and non-batman nodes you need to set 
routes manually. If a multi-homed node is involved with the same netmask on 
multiple interfaces then you must also specify the src address for the manual 
routing entry like: ip r add 10.0.1.1/32 dev ath0 src 10.1.5.102 
And on the batman-node you must either HNA announce the ip of the non-batman 
node using -a (this will automaticall disable the unreachable rule to hit for 
the ip address of the non-batman node).

Or, just as you suggested, launch batman with the --no-unreachable-rule.


ciao,
axel

>
> Stefano
> _______________________________________________
> B.A.T.M.A.N mailing list
> B.A.T.M.A.N@open-mesh.net
> https://list.open-mesh.net/mm/listinfo/b.a.t.m.a.n



  reply	other threads:[~2007-11-10 11:43 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-11-09 14:23 [B.A.T.M.A.N.] routing problem? Stefano Scipioni
2007-11-10 11:43 ` Axel Neumann [this message]
2007-11-11 15:55   ` Stefano Scipioni
2007-11-11 17:16     ` [B.A.T.M.A.N.] routing problem? / Changes in exp rv790 Axel Neumann
2007-11-11 20:41       ` [B.A.T.M.A.N.] batmand crash / core dump Michael Burmeister-Brown
2007-11-11 22:30         ` [B.A.T.M.A.N.] batman gw nodes and routing (rv792) Predrag Balorda
2007-11-12 14:31           ` Axel Neumann
2007-11-11 22:34         ` [B.A.T.M.A.N.] vis and batman-exp (rv780-792) Predrag Balorda
2007-11-12  7:57           ` Stefano Scipioni
2007-11-12 13:53             ` Axel Neumann
2007-11-12 14:00               ` Predrag Balorda
2007-11-12 17:13         ` [B.A.T.M.A.N.] batmand crash / core dump Axel Neumann
2007-11-24 13:02           ` Marek Lindner

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=200711101243.28980.axel@open-mesh.net \
    --to=axel@open-mesh.net \
    --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