I’m running Diablo_5.2008.43-7_PR-MR0 and am having problems with the configuration of a static IP address inside the Connection Manager. If I use a WLAN connection that has DHCP on it, all works as advertised. The problem comes when I have to use a WLAN connection that doesn’t have DHCP.

I’ve used the advanced tab on the connection manager to include an IP address and a /25 netmask (255.255.255.128), also a gateway, DNS servers, and a proxy server (all stuff that I have to use at work).

If I check what is configured with ifconfig, I see that I have the correct IP address, but the wrong netmask (so my broadcast address is wrong too, basically instead of my /25 mask, I’m getting a /16 mask). If I use netstat, I can see that I have the correct gateway, but the wrong netmask is preventing me from using it to access my proxy server (it’s on a segment of the network that is on the other side of the router).

If try to run the browser, I get an error message about my proxy server can’t be contacted. I would guess that the netmask is preventing the proper segmentation of my network.

If I down the network with ifdown –a, I get an error message about /etc/network/if-post-down.d/zz_proxy_unset exited with return code 1.

Then if I try and bring the network back up with ifup –a, I get an error message about

/etc/network/if-up.d/00_proxy_set exited with return code 1; I also get ifup: don’t seem to have all the variable for eth0/inet; ifconfig: SIOCGIFFLAGS: No such device; ifconfig: SIOCSIFADDR: No such device; route: SIOC[ADD|DEL]RT: No such device

I’m not sure where the problem lies, but am open to suggestions on what to try next. Thanks for your time and help.

Scott

That's bug 3830, fixed internally but not released so far.

Ima,

Thanks for information! Do you know how to find out what was changed with the fix? Would it be possible to implement the changes to the script myself? It looks like in the past they made 4 versions releases in 2007 and 3 versions in 2008, but nothing yet in 2009. If I'm reading the bug report correctly, it looks like it was fixed a couple of weeks after the software I'm running now, but still almost 10 months ago.

Just curious, I can probably cobble together an ifconfig and route script to get it to work, but that would require some work with every reboot/reconnect. I just wish it would work like it does with DHCP.

Thanks again,

Scott

The problem is not in the script, but in that /usr/lib/icd2/libicd_network_ipv4.so doesn't set the $subnet environment variable before running it. Unfortunately that's a closed source component so you can't fix it yourself.

I think the only thing you could do is modify the script to check whether $ip falls inside your /25 and if so set $netmask and $subnet accordingly, but that would only work for the network(s) you hardcode into it.