Hello :-)

This usage scenario is not unusual but I have not found any solutions yet.

I want my netbook to connect automatically to both the office wired/static network and to the usual wired/DHCP networks.

wicd is wicked but netsearching hasn't revealed how to configure it for both wired/static and wired/DHCP except by manually switching profiles.

wicd's profiles can use pre/post(dis)connect scripts but I don't know how to integrate them into wicd when they are upping/downing connections on cable (un)plugging.

If it is not practical to solve this within wicd, I'll explore standalone scripts to configure eth0 on cable (un)plugging, as detected by ifplugd.

Happy to explore this and share results but would like the community's suggestions and knowledge before starting.

Best

Charles

If this is in different locations rather than simultaneous, ifupdown
provides ping-places.sh to be used in "/etc/network/interfaces" to
determine which configuration to use.
http://www.cyberciti.biz/faq/setting...terfaces-file/

Thanks tkmsr

Yes - different places/networks, not simultaneous.

Some interesting ideas in that sample /etc/interfaces file. I prefer to identify the LAN by the MAC address of the default gateway because there are so many 192.168.0.0 and 192.168.1.0 networks and "always up" systems on a LAN are not always up (!) and can change address whereas the default gateway is more likely to be up and its MAC address is less likely to change. It's not a very robust solution but I don't know of anything better and it has been "good enough" for a while.

Design-wise, I was thinking along the lines of parallel processes to:

1. Bring up eth0 as a DHCP interface.
2. For each known static network: bring up eth0:x configured with static values and try to get the default gateway's MAC address to identify the network.
3. Wait with a reasonable time to see if DHCP configures eth0 (abandon if the network is identified by any of the step 2 processes) and, if it does, identify the appropriate by the default gateway's MAC address.
4. Remove useless/unwanted interfaces including the DHCP one even if it got a lease if it's for a network we have static settings for.
5. At this point the network is identified as known or unknown and the script can, as appropriate, configure routing; configure DNS resolution; mount networked file systems; start services such as cups, NFS, samba, sshd ... .