On Thu, 10 Nov 2005, Marcelo M. Garcia wrote:
Matthew Saltzman wrote:
On Thu, 10 Nov 2005, Derek Martin wrote:
On Tue, Nov 08, 2005 at 07:02:51PM -0500, Matthew Saltzman wrote:
NetworkManager is a real whiz-bang app that detects network connections
dynamically. Plug in a cable and it switches to cable, unplug it and it
looks for wireless connections. It manages keys, allows you to select
among in-range WAPs or create an ad-hoc net, controls VPN access (using
vpnc only at the moment), controls modems (untested by me ATM) and
rescans
on suspend/resume to find the new connections.
Is it smart enough to deal with cases where you are connected via
wireless, then connect via cable ALSO? (One would need a way to
select which connection should be used as the default route.)
Currently, NM doesn't handle simultaneous connections through two
interfaces. If you want to discuss NM features, the place is
networkmanager-list@xxxxxxxxxx
Hi,
I posted this question looking from advice of people who uses a laptop at
work or university and at home, using the same ethernet interface. NM does
not seens to handle this kind of connection, say two IP addresses with the
same network card, so I remebered this utility called "netenv".
No, this is exactly what NM is supposed to handle correctly. When at
work, it finds my office WAP, and when at home it finds my home WAP. (And
when I'm on the road it finds my hotel WAP.) And as I said, it manages
keys and everything. And all automatically (learning new WAPs as it
encounters them). And when I plug in a cable, it switches to the cable,
and when I unplug the cable, it scans for wireless.
Modulo a few bugs, of course--some in wireless drivers and some in NM
itself. But it's coming along pretty nicely these days.
What I said it won't do is connect the same computer through cable and
wireless *at the same time*.
Thanks
Marcelo M. Garcia
--
Matthew Saltzman
Clemson University Math Sciences
mjs AT clemson DOT edu
http://www.math.clemson.edu/~mjs
