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
1sec dhcp releases? so it worsened?
on 3 september i noticed they were only 2 minutes long....my skype sessions got even disconnected everytime... and it took some time to reconnect ... a wget of a 1mbyte file was even impossible
Ethernet adapter Local Area Connection:
Connection-specific DNS Suffix . : Description . . . . . . . . . . . : LevelOne 32/64-Bit Gigabit Ethernet Adapter Physical Address. . . . . . . . . : 00-11-6B-35-4A-FA Dhcp Enabled. . . . . . . . . . . : Yes Autoconfiguration Enabled . . . . : Yes IP Address. . . . . . . . . . . . : 10.59.132.100 Subnet Mask . . . . . . . . . . . : 255.255.255.0 Default Gateway . . . . . . . . . : 10.59.132.1 DHCP Server . . . . . . . . . . . : 10.59.132.1 DNS Servers . . . . . . . . . . . : 151.99.125.2 Lease Obtained. . . . . . . . . . : zondag 2 september 2007 10:35:12 ---> he just got a new lease again due to these dhcp boot? Lease Expires . . . . . . . . . . : zondag 2 september 2007 10:37:12 -> a short dhcp leases might be the cause...
2007/9/21, a.anselmi@oltrelinux.com a.anselmi@oltrelinux.com:
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
Ok,
Just had a short look on the code and recognized that the ip adress assigned from the gateway is several times just copied from a data buffer to an interger and back. Maybe its related to your HW, because foneros and Merakis are mips MSB and mispel based Buffalos and WRTs is LSB architecture. That would also explain why it worked just fine on the Buffalos and WRTs we are using here. We'll check that,..
ciao, axel
On Freitag 21 September 2007, a.anselmi@oltrelinux.com wrote:
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
thanks Axel, I was sure you would have found the problem
ciauz Antonio
Ok,
Just had a short look on the code and recognized that the ip adress assigned from the gateway is several times just copied from a data buffer to an interger and back. Maybe its related to your HW, because foneros and Merakis are mips MSB and mispel based Buffalos and WRTs is LSB architecture. That would also explain why it worked just fine on the Buffalos and WRTs we are using here. We'll check that,..
ciao, axel
On Freitag 21 September 2007, a.anselmi@oltrelinux.com wrote:
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
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
b.a.t.m.a.n@lists.open-mesh.org