© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
73416ba
(Get the code!)
I'm somewhat confused from above connections. I have similar need to that of Martin Jackson's. That is I would like network manager to automatically connect to say wlan0, but on the same time, it would let me do what ever I want on eth0. (It could just the same be other way around).
Rationale is that I have some own experiment running on eth0, but I also want to be connected to Internet via wlan0. Or, that I have Internet in eth0, and I want to share it in wlan0.
Now it does not work, since lets assume that I'm currently happily connected to Internet via NM on wlan0, if I plug-in my eth0 for my experiements, wlan0 is torn down and is unconfigurable by NM, even if eth0 is seen as 'unmanaged' by NM, it still tears down wlan0 when eth0 sees link up.
Now I just need to kill whole NM, and configure everything by hand.
What I'd want to see, as solution, is ability to tell NM from configuration to completely ignore some interface, just
forget it exists from NM point of view. This way I could easily do ad'hoc hacks, by connecting to Internet normally
and then ignoring the remaining interface, connect it and configure it manually.
Thanks.