B.A.T.M.A.N October 2008

b.a.t.m.a.n@lists.open-mesh.org

18 participants
13 discussions

Re: [B.A.T.M.A.N.] Problem with gateway-dhcp
by Marek Lindner 15 Oct '08

15 Oct '08

Hi, > For example (can't remember the exact messages but this was about their > content): > Message on Gateway, Debugmode3: > "Gateway assigned IP adress 169.254.0.1 to client 192.168.100.2" > Message on Client, Debugmode3: > "Got IP adress 169.254.0.1 from Gateway 192.168.100.1" so far, everything as expected. > According to the batman manual the gateway should act as "a tiny DHCP > server" but as I always get these 169. adresses I assume it isn't > running properly. I did not touch the firewall or the iptables because I > don't know anything about it. There might be some entries which would > solve the problem, but I could not find those in the manual or the > mailing-list archive. Batman has its internal DHCP server for the gateway tunneling via the gate0 interfaces. This address space was chosen to avoid configuration as it should not be in use. You could try to ping the gateway via the virtual address (169.254.0.0) to check whether the tunnel connection works or not. If you run into a timeout you should disable the firewall on the gateway. Ping again to feel the difference. ;-) May be you are lacking the the masquerading rules on gate0. Issue: iptables -t nat -I POSTROUTING -o gate0 -j MASQUERADE on the client and on the gateway. Regards, Marek

2 1

[B.A.T.M.A.N.] Problem with gateway-dhcp
by Tobias Gieseke 14 Oct '08

14 Oct '08

Hi there, I'm using batmand 0.3 rv1057 on six Buffalo WHR-HP-G54 with WhiteRussian 0.9 Open-WRT. The mesh works fine, even the vis-server does its job. But I'm having some Problems with the Gateway: One of the routers is connected to a LAN with internet access via WAN-Port and should act as a gateway for the mesh. When the Gateway-Router is started interface gate0 is up and runnig but always has the Adress 169.254.0.0. The clients recognize the gateway (entry in debugmode 2) but can't get a connection to the internet or the standard gateway of the LAN. Clients get IP-adress 169.254.0.x (x starting at 1) for their gate0 interface and the gateway is aware of that. For example (can't remember the exact messages but this was about their content): Message on Gateway, Debugmode3: "Gateway assigned IP adress 169.254.0.1 to client 192.168.100.2" Message on Client, Debugmode3: "Got IP adress 169.254.0.1 from Gateway 192.168.100.1" According to the batman manual the gateway should act as "a tiny DHCP server" but as I always get these 169. adresses I assume it isn't running properly. I did not touch the firewall or the iptables because I don't know anything about it. There might be some entries which would solve the problem, but I could not find those in the manual or the mailing-list archive. As I've found a lot of Debug outputs where the Gateway-DHCP was running, I'm sure someone can help me out with that little problem. wireless greetings, Tobi

1 0

[B.A.T.M.A.N.] [PATCH] Let the compiler interpret the noreturn situation in restore_and_exit correct
by Sven Eckelmann 13 Oct '08

13 Oct '08

It is just implicit that raise will not return in this case because we are in a sighandler right now. So let call exit always afterwards even if it will not be reached. Signed-off-by: Sven Eckelmann <sven.eckelmann(a)gmx.de> --- batman/posix/posix.c | 5 ++--- 1 files changed, 2 insertions(+), 3 deletions(-) diff --git a/batman/posix/posix.c b/batman/posix/posix.c index 4423345..bbeac38 100644 --- a/batman/posix/posix.c +++ b/batman/posix/posix.c @@ -497,11 +497,10 @@ void restore_and_exit( uint8_t is_sigsegv ) { } - if (!is_sigsegv) - exit(EXIT_FAILURE); - else + if (is_sigsegv) raise(SIGSEGV); + exit(EXIT_FAILURE); } -- 1.6.0.1

3 2

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

B.A.T.M.A.N October 2008