wicd cannot change subnets

Bug #483276 reported by strider22 on 2009-11-15
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
wicd
Medium
Andrew Psaltis

Bug Description

wicd does not appear to be able to change subnets.

The wan router and DHCP server is IP 192.168.2.1
In this uncontrolled environments (student housing) users will get a router and plug it in.
The default IP for routers is either 192.168.0.1 or 192.168.1.1 They also serve dhcp.

Any PCs turned on or reboots will obtain IPs from the new router (as the wan router is busier)
As this new router is not the wan router, no internet access is provided.

An Ubuntu laptop in this environment will get an IP like 192.168.0.100 from the rouge router.
When the rouge router is removed, the Ubuntu laptop will not connect to the wan router.

The dhclient has to be cleared using
    sudo dhclient -r wlan0
and then WICD will connect.

The code needs to compare subnets and if different, then it needs to release the client.

strider22 (chris-priestdata) wrote :

After releasing the 192.168.0 subnet then WICD can obtain the 192.168.2.* IP

Andrew Psaltis (nacl) wrote :

Someone else came into the IRC channel and noticed that this was also occurring on his machine.

So, here's how we're probably going to fix this:

We're going to add a "-k" flag to wicd that will call the disconnect routine and kill the wicd daemon with pid in /var/run/wicd/wicd.pid. The initscripts will call this on "stop", but not "restart".

Changed in wicd:
importance: Undecided → Medium
milestone: none → 1.6.3
status: New → Confirmed
Andrew Psaltis (nacl) on 2009-12-29
Changed in wicd:
assignee: nobody → Andrew Psaltis (nacl)
Adam Blackburn (adamblackburn) wrote :

Fix committed by Andrew yesterday.

Changed in wicd:
status: Confirmed → Fix Committed
Changed in wicd:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers