<quote who="Martin Barry">
> i need two active interfaces though. wireless holds default route but
> wired has crossover cable to a desktop to run synergy, rsync etc.etc.
>
> can NM handle that? i can't tell from the threadbare doco in the man page
> and on gnome.org...
It's not a use case that NM (in its early days) is really concentrating on,
but you can do it.
On Ubuntu systems, NM will adopt an interface if it's not listed in /e/n/i,
or if it's configured for auto+dhcp (see the previous mail for an example).
So if your wired interface was manually configured, you'd be fine. If it is
not manually configured, and you really do want it to be auto+dhcp (which is
mostly the case), then you're in a bit of a pickle. NM will adopt both, so
it'll be back to either/or.
However, you can trick NM into ignoring an interface by adding something to
its configuration stanza in /e/n/i. Something token like hostname. NM should
ignore an interface configured like this:
auto eth0
iface eth0 inet dhcp
hostname pants
There are other options you could add, but hostname is a good choice - it
doesn't really impact much. When NM comes up, it should ignore eth0, and set
the default route on the wireless interface. Matches up with your use case.
Let me know if this doesn't work!
- Jeff
--
linux.conf.au 2007: Sydney, Australia http://lca2007.linux.org.au/
What do you give a bird when it has a headache?
Parakeetamol.
--
SLUG - Sydney Linux User's Group Mailing List - http://slug.org.au/
Subscription info and FAQs: http://slug.org.au/faq/mailinglists.html
