So how do we fix?

----- Original Message -----
From: b.a.t.m.a.n-bounces@open-mesh.net <b.a.t.m.a.n-bounces@open-mesh.net>
To: b.a.t.m.a.n@open-mesh.net <b.a.t.m.a.n@open-mesh.net>
Sent: Fri Sep 21 10:04:55 2007
Subject: [B.A.T.M.A.N.] assigned IP life

Hi
mybe these lines form -d3 level at client node 5.1.7.251 can help:

Gateway client - got IP (1.0.254.169) from gateway: 5.1.7.254
Gateway client - gateway (5.1.7.254) says: IP (1.0.254.169) is expired
Gateway client - got IP (1.0.254.169) from gateway: 5.1.7.254
Gateway client - gateway (5.1.7.254) says: IP (1.0.254.169) is expired
Gateway client - got IP (1.0.254.169) from gateway: 5.1.7.254
Gateway client - gateway (5.1.7.254) says: IP (1.0.254.169) is expired
Gateway client - got IP (1.0.254.169) from gateway: 5.1.7.254
Gateway client - disconnecting from unresponsive gateway: 5.1.7.254
Deleting default route via bat0 0.0.0.0 (table 67)
-- after some seconds --
Adding default route to 5.1.7.254 (49,64,64)
Adding default route via bat0 0.0.0.0 (table 67)

...seems that lease assigned by gateway to client (IP 1.0.254.169) have a
less than 1 sec of life... almost in my case.

Antonio


_______________________________________________
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