public inbox for b.a.t.m.a.n@lists.open-mesh.org
 help / color / mirror / Atom feed
From: Andreas Langer <an.langer@gmx.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.] Problems with 0.3-beta rv963 and kmod-batgat
Date: Fri, 1 Feb 2008 16:20:28 +0100	[thread overview]
Message-ID: <200802011620.28653.an.langer@gmx.de> (raw)
In-Reply-To: <a934d3f30801312219s59d740bcr9b6a0597e8cc51d9@mail.gmail.com>

that sounds great, please contact me if there are more problems with the 
kernel module, i developed it and i want to know if there any bugs ;)

regards, andreas

Am Freitag, 1. Februar 2008 07:19:39 schrieb Vinay Menon:
> sorry,i was hasty in posting its working now. the problem was at my end.
> things working fine :)
> thanks
>
> On Jan 31, 2008 10:08 AM, Andreas Langer <an.langer@gmx.de> wrote:
> > hi,
> > i try to help....with batgat on the gateway please check the kernel
> > log.....on
> > the client side run batman with -d 3 and check if you get a virtual ip
> > from
> > the gateway, on a fresh restart it can be a delay until you get an ip.
> >
> > Am Mittwoch, 30. Januar 2008 23:20:44 schrieb Vinay Menon:
> > > Hi,
> > > I am testing out batman 0.3-beta rv963 with openwrt-trunk (r10219) .
> > > I could get the expected results when i am using tun instead of
> >
> > kmod-batgat
> >
> > > .
> > >
> > > but when i use kmod-batgat even tho the tunnel gate0 is established 
> > > the routing rules and firewall is same as with kmod-tun i cant get
> > > traffic
> >
> > thru
> >
> > > gate0
> > >
> > > My Setup:
> > >
> > > ---- Wired
> > > - - - - WiFi
> > >
> > >  192.168.111.1-----(WAN)-192.168.111.74(Gateway)10.1.125.158 - - - - -
> > > - 10-1-125-158 (Node2)
> >
> > your setup is :
> >
> > wan with 192.168.111.1
> > gateway with 10.1.125.158, 192.168.111.74
> > node with 10.1.125.158
> >
> > ???
> >
> > > *With kmod-batgat:*
> > >
> > > from
> > > ping 192.168.111.1 -I gate0
> > >
> > > ##on gateway
> > > root@10-1-125-158:~# lsmod |grep batgat
> > > batgat                 10976  1
> > >
> > > ##Ping from Node
> > > root@Node2:~# ping 192.168.111.1 -I gate0
> > > PING 192.168.111.1 (192.168.111.1): 56 data bytes
> > > --- 192.168.111.1 ping statistics ---
> > > 46 packets transmitted, 0 packets received, 100% packet loss
> > >
> > >
> > > ##tcpdump on node
> > > root@10-1-125-158:~# tcpdump -i gate0 proto \\icmp
> > > tcpdump: verbose output suppressed, use -v or -vv for full protocol
> >
> > decode
> >
> > > listening on gate0, link-type EN10MB (Ethernet), capture size 96 bytes
> > >
> > > 0 packets captured
> > > 0 packets received by filter
> > > 0 packets dropped by kernel
> > >
> > >
> > >
> > > *With kmod-tun:*
> > > root@10-1-125-158:/# lsmod |grep tun
> > > tun                     6592  1
> > >
> > > *##on Node*
> > >
> > > batman -cd2
> > >      Gateway     (#/255)         Nexthop [outgoingIF], gw_class ... [
> > > B.A.T.M.A.N. 0.3-beta rv963, MainIF/IP: ath0/10.1.124.248, UT: 0d
> > > 0h52m] => 10.1.125.158    (255 + 0)    10.1.125.158 [      ath0],
> > > gw_class  49
> >
> > -
> >
> > > 4MBit/1024KBit, reliability: 0
> > >
> > >
> > > *##Ping from Node*
> > > root@Node2:~# ping 192.168.111.1
> > > PING 192.168.111.1 (192.168.111.1): 56 data bytes
> > > 64 bytes from 192.168.111.1: seq=0 ttl=63 time=8.473 ms
> > > 64 bytes from 192.168.111.1: seq=1 ttl=63 time=6.585 ms
> > >
> > >
> > > *##tcpDump on gateway's gate0*
> > >
> > > root@10-1-125-158:/# tcpdump -i gate0 proto \\icmp
> > > tcpdump: WARNING: arptype 65534 not supported by libpcap - falling back
> >
> > to
> >
> > > cooked socket
> > > tcpdump: verbose output suppressed, use -v or -vv for full protocol
> >
> > decode
> >
> > > listening on gate0, link-type LINUX_SLL (Linux cooked), capture size 96
> > > bytes
> > > 00:50:45.798376 IP 169.254.0.1 > 192.168.111.1: ICMP echo request, id
> >
> > 1004,
> >
> > > seq 0, length 64
> > > 00:50:46.614360 IP 192.168.111.1 > 169.254.0.1: ICMP echo reply, id
> >
> > 1004,
> >
> > > seq 0, length 64
> > > 00:50:46.805310 IP 169.254.0.1 > 192.168.111.1: ICMP echo request, id
> >
> > 1004,
> >
> > > seq 1, length 64
> > > 00:50:46.806369 IP 192.168.111.1 > 169.254.0.1: ICMP echo reply, id
> >
> > 1004,
> >
> > > seq 1, length 64
> > >
> > > *##tcpDump on gateway's eth0*
> > > root@10-1-125-158:/# tcpdump -i eth0 proto \\icmp
> > > tcpdump: verbose output suppressed, use -v or -vv for full protocol
> >
> > decode
> >
> > > listening on eth0, link-type EN10MB (Ethernet), capture size 96 bytes
> > > 00:48:29.108148 IP 192.168.111.74 > 192.168.111.1: ICMP echo request,
> > > id 1003, seq 6, length 64
> > > 00:48:29.145367 IP 192.168.111.1 > 192.168.111.74: ICMP echo reply, id
> > > 1003, seq 6, length 64
> > >
> > >
> > > Also at times  ip rules dont appear on node and i have to restart
> >
> > batmand
> >
> > > to get the network working.
> >
> > _______________________________________________
> > 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:[~2008-02-01 15:20 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-01-30 22:20 [B.A.T.M.A.N.] Problems with 0.3-beta rv963 and kmod-batgat Vinay Menon
2008-01-31 15:08 ` Andreas Langer
2008-02-01  6:19   ` Vinay Menon
2008-02-01 15:20     ` Andreas Langer [this message]

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=200802011620.28653.an.langer@gmx.de \
    --to=an.langer@gmx.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