If it is an inappropriate place to post, please direct me to the right place. I could not find relevant info with google.
I have an ad hoc network using batman. The network config of backbone nodes: 10.42.0.N/24 :wireless interface, network for backbone nodes 10.42.N.1/24 : wireless interface, network for user nodes. dhcp served here 10.43.N.1/24 : wired interface, network for user nodes. dhcp served here
This setup works with linux as a user node. It tries its old ip with dhcp request, but after that it asks for a new address with dhcp discover. But with a windows 7 there is a problem. The windows gets an address with DHCP from one node. When it roams to another nodes' area, it cannot get an ip address for the new area. It seems that the windows box do not want to forget the first IP it got. We have tried: ipconfig /renew shutting down and restarting wifi connection setting dhcp lease time to 1 min in all nodes, going to the old node area, getting the old ip, and renew, shut down, etc.
The windows seems to use dhcp request all times, never dhcp discover, even after it obviosly figured out that the old IP won't work. The dhcp servers aren't set to be authoritative, as it would create problems where their area overlap.
I would be glad to have any suggestions.
Thank you
On Thursday 07 October 2010 11:07:55 Magosányi Árpád wrote:
The windows seems to use dhcp request all times, never dhcp discover, even after it obviosly figured out that the old IP won't work. The dhcp servers aren't set to be authoritative, as it would create problems where their area overlap.
Sorry, can't help much with your windows7 problem but if you are interested in using DHCP and roaming you rather should be using the batman-adv kernel module.
Regards, Marek
b.a.t.m.a.n@lists.open-mesh.org