Re: Network Manager and NFS
On August 14, 2008 01:00:19 pm The Holy ettlz wrote: > On Thu, 2008-08-14 at 11:29 -0700, Robert Smits wrote: > > > I think what you're asking for is called Network Location Awareness --- > > > how an interface distinguishes to which network it is attached, and > > > then the machine configures itself as appropriate. I think there a few > > > implementations of this [standards, anybody?] but personally I like > > > this one: authenticated DHCP, since it should also work securely for > > > plain old wired Ethernet. > > > > Will that also work with fixed IP addresses? > > Not unless said addresses are dished out by the DHCP server from its own > fixed database. Otherwise, one would have to resort to something more > exotic to determine the network, or do it manually. > > > From my point of view, SCMP already works, but I can't use it together > > with Network Manager. Can we either configure Network Manager to work > > with SCMP or SCMP to work with Network Manager? I don't know which route > > is more feasible, largely because I don't understand from a technical > > viewpoint why the programs don't play nicely together. Is there a > > solution here that's easier than re-inventing the wheel? > > The "best" solution is probably a dbus-aware module for SCMP that > listens for changes announced by NM, and reacts accordingly. This is > something you might wish to discuss with the SCMP developers. > > James Ok. I'll go looking for them. Thanks, James. Bob -- Robert Smits CEP525G Nanaimo, Duncan & District Labour Council Box 822 Nanaimo, V9R 5N2 Ph 250-753-0201 Fax 250-753-2954 Email [EMAIL PROTECTED] ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: Network Manager and NFS
On Thu, 2008-08-14 at 11:29 -0700, Robert Smits wrote: > > I think what you're asking for is called Network Location Awareness --- > > how an interface distinguishes to which network it is attached, and then > > the machine configures itself as appropriate. I think there a few > > implementations of this [standards, anybody?] but personally I like this > > one: authenticated DHCP, since it should also work securely for plain > > old wired Ethernet. > > Will that also work with fixed IP addresses? Not unless said addresses are dished out by the DHCP server from its own fixed database. Otherwise, one would have to resort to something more exotic to determine the network, or do it manually. > From my point of view, SCMP already works, but I can't use it together with > Network Manager. Can we either configure Network Manager to work with SCMP or > SCMP to work with Network Manager? I don't know which route is more feasible, > largely because I don't understand from a technical viewpoint why the > programs don't play nicely together. Is there a solution here that's easier > than re-inventing the wheel? The "best" solution is probably a dbus-aware module for SCMP that listens for changes announced by NM, and reacts accordingly. This is something you might wish to discuss with the SCMP developers. James -- The Holy ettlz [EMAIL PROTECTED] PGP key ID: 03F94B5D --- signature.asc Description: This is a digitally signed message part ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: Network Manager and NFS
On Thu, 2008-08-14 at 11:29 -0700, Robert Smits wrote: > On August 13, 2008 03:30:21 pm The Holy ettlz wrote: > > On Wed, 2008-08-13 at 14:37 -0700, Robert Smits wrote: > > > My workaround, which isn't entirely satisfactory, is to use ifup and > > > dispense with network manager altogether. Unfortunately, that doesn't > > > allow me to see other possible network connections and make quick and > > > easy connections when I'm on the road. > > > > > > What I still don't understand, though, is why Network Manager isn't > > > configured to deal with managing changing nfs networks. > > > > I think what you're asking for is called Network Location Awareness --- > > how an interface distinguishes to which network it is attached, and then > > the machine configures itself as appropriate. I think there a few > > implementations of this [standards, anybody?] but personally I like this > > one: authenticated DHCP, since it should also work securely for plain > > old wired Ethernet. > > Will that also work with fixed IP addresses? > > From my point of view, SCMP already works, but I can't use it together with > Network Manager. Can we either configure Network Manager to work with SCMP or > SCMP to work with Network Manager? I don't know which route is more feasible, > largely because I don't understand from a technical viewpoint why the > programs don't play nicely together. Is there a solution here that's easier > than re-inventing the wheel? You'd use the currently connected network as _input_ to scpm to get it to change the current profile, if I understand scpm correctly. When NM connects to a known network, then you can poke scpm to update your scpm "profile" to the one you want for that specific network. You could do this based on the SSID of the wifi network (and the AP's security options too, hopefully) or the MAC address of the DHCP server obtained via ARP or something like that. How do you change scpm profiles now? Manually? Dan > > http://www.cl.cam.ac.uk/~sjm217/papers/securecomm07authdhcp.pdf > > > > I've got a bit of time on my hands, I might code up my earlier HTTPS > > idea. > > > > There's a whole bunch of things you can hook into changes in network > > such as iptables, service daemons, etc., and of course NFS mounts. But > > before that the relevant NLA infrastructure needs to be in place. This > > means having (1) a mechanism to identify the network, and (2) telling > > other processes (such as other config daemons) that we're on that > > network. It should be up to the latter what action we take. NM already > > has "network link awareness", viz. Pidgin and Evolution. Am I right in > > thinking that the replacement for init is also dbus-aware? > > > > Of course, all this takes time ...and planning ;) > > Yes, it does. And thanks for thinking about the issue. I appreciate it. > > ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: Network Manager and NFS
On August 13, 2008 03:30:21 pm The Holy ettlz wrote: > On Wed, 2008-08-13 at 14:37 -0700, Robert Smits wrote: > > My workaround, which isn't entirely satisfactory, is to use ifup and > > dispense with network manager altogether. Unfortunately, that doesn't > > allow me to see other possible network connections and make quick and > > easy connections when I'm on the road. > > > > What I still don't understand, though, is why Network Manager isn't > > configured to deal with managing changing nfs networks. > > I think what you're asking for is called Network Location Awareness --- > how an interface distinguishes to which network it is attached, and then > the machine configures itself as appropriate. I think there a few > implementations of this [standards, anybody?] but personally I like this > one: authenticated DHCP, since it should also work securely for plain > old wired Ethernet. Will that also work with fixed IP addresses? >From my point of view, SCMP already works, but I can't use it together with Network Manager. Can we either configure Network Manager to work with SCMP or SCMP to work with Network Manager? I don't know which route is more feasible, largely because I don't understand from a technical viewpoint why the programs don't play nicely together. Is there a solution here that's easier than re-inventing the wheel? > http://www.cl.cam.ac.uk/~sjm217/papers/securecomm07authdhcp.pdf > > I've got a bit of time on my hands, I might code up my earlier HTTPS > idea. > > There's a whole bunch of things you can hook into changes in network > such as iptables, service daemons, etc., and of course NFS mounts. But > before that the relevant NLA infrastructure needs to be in place. This > means having (1) a mechanism to identify the network, and (2) telling > other processes (such as other config daemons) that we're on that > network. It should be up to the latter what action we take. NM already > has "network link awareness", viz. Pidgin and Evolution. Am I right in > thinking that the replacement for init is also dbus-aware? > > Of course, all this takes time ...and planning ;) Yes, it does. And thanks for thinking about the issue. I appreciate it. -- Robert Smits CEP525G Nanaimo, Duncan & District Labour Council Box 822 Nanaimo, V9R 5N2 Ph 250-753-0201 Fax 250-753-2954 Email [EMAIL PROTECTED] ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: Network Manager and NFS
On Wed, 2008-08-13 at 14:37 -0700, Robert Smits wrote: > My workaround, which isn't entirely satisfactory, is to use ifup and dispense > with network manager altogether. Unfortunately, that doesn't allow me to see > other possible network connections and make quick and easy connections when > I'm on the road. > > What I still don't understand, though, is why Network Manager isn't > configured > to deal with managing changing nfs networks. I think what you're asking for is called Network Location Awareness --- how an interface distinguishes to which network it is attached, and then the machine configures itself as appropriate. I think there a few implementations of this [standards, anybody?] but personally I like this one: authenticated DHCP, since it should also work securely for plain old wired Ethernet. http://www.cl.cam.ac.uk/~sjm217/papers/securecomm07authdhcp.pdf I've got a bit of time on my hands, I might code up my earlier HTTPS idea. There's a whole bunch of things you can hook into changes in network such as iptables, service daemons, etc., and of course NFS mounts. But before that the relevant NLA infrastructure needs to be in place. This means having (1) a mechanism to identify the network, and (2) telling other processes (such as other config daemons) that we're on that network. It should be up to the latter what action we take. NM already has "network link awareness", viz. Pidgin and Evolution. Am I right in thinking that the replacement for init is also dbus-aware? Of course, all this takes time ...and planning ;) James -- The Holy ettlz [EMAIL PROTECTED] PGP key ID: 03F94B5D --- signature.asc Description: This is a digitally signed message part ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: Network Manager and NFS
On August 10, 2008 08:04:51 pm Dan Williams wrote:
> On Fri, 2008-08-08 at 22:43 +0100, The Holy ettlz wrote:
> > Hello,
> >
> > > I like the way Knetwork Manager and Network Manager work for the most
> > > part, but I find I cannot use them - why - because I need to change my
> > > nfs networks at each site I log into. And because network manager
> > > doesn't understand this, I have to use ifup and scpm to do it.
> >
> > The "semi-canonical" way to do it probably to add some hook scripts
> > into /etc/NetworkManager/dispatcher.d/. Last time I checked, the
> > dispatcher ran each of these scripts in alphanumeric order with
> > arguments
>
> Right. Dispatcher scripts are the best way to do this sort of thing if
> all you need are a few lines of shell.
>
> > {up|down}
> >
> > You'll probably need to cook up some of your own wizardry in order to
> > automatically decide what network you're on, then change the NFS mounts,
> > etc. (I don't think there's any way at present to automate this on a
> > per-user basis, although as far as I understand it'd certainly be
> > possible with the current NM to write a user session daemon that waits
> > for a particular network connection and then, say, does a FUSE mount.)
>
> We can certainly export the connection name, path, id, and settings
> service, which should be enough to ID the connection. That can be
> stuffed into the environment that the script gets executed with. The
> DHCP4 config is already exported in this manner, which you could use in
> the mean time.
>
> Dan
Thanks, Fellows, both of you for responding with your suggestions. I'm not
competent to write either "hook" or "dispatcher" scripts (are they one and
the same thing?)
However, I've looked at the scripts in this folder, and they're full of
references that mean nothing whatever to me. I appreciate your advice, but I
know nothing about user session daemons or FUSE mounts. If that's what it
will take, I'll forget about it.
My workaround, which isn't entirely satisfactory, is to use ifup and dispense
with network manager altogether. Unfortunately, that doesn't allow me to see
other possible network connections and make quick and easy connections when
I'm on the road.
What I still don't understand, though, is why Network Manager isn't configured
to deal with managing changing nfs networks.
--
Robert Smits CEP525G
Nanaimo, Duncan & District Labour Council
Box 822 Nanaimo, V9R 5N2 Ph 250-753-0201
Fax 250-753-2954 Email [EMAIL PROTECTED]
___
NetworkManager-list mailing list
NetworkManager-list@gnome.org
http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: Network Manager and NFS
On Fri, 2008-08-08 at 22:43 +0100, The Holy ettlz wrote:
> Hello,
>
> > I like the way Knetwork Manager and Network Manager work for the most part,
> > but I find I cannot use them - why - because I need to change my nfs
> > networks
> > at each site I log into. And because network manager doesn't understand
> > this,
> > I have to use ifup and scpm to do it.
>
> The "semi-canonical" way to do it probably to add some hook scripts
> into /etc/NetworkManager/dispatcher.d/. Last time I checked, the
> dispatcher ran each of these scripts in alphanumeric order with
> arguments
Right. Dispatcher scripts are the best way to do this sort of thing if
all you need are a few lines of shell.
> {up|down}
>
> You'll probably need to cook up some of your own wizardry in order to
> automatically decide what network you're on, then change the NFS mounts,
> etc. (I don't think there's any way at present to automate this on a
> per-user basis, although as far as I understand it'd certainly be
> possible with the current NM to write a user session daemon that waits
> for a particular network connection and then, say, does a FUSE mount.)
We can certainly export the connection name, path, id, and settings
service, which should be enough to ID the connection. That can be
stuffed into the environment that the script gets executed with. The
DHCP4 config is already exported in this manner, which you could use in
the mean time.
Dan
___
NetworkManager-list mailing list
NetworkManager-list@gnome.org
http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: Network Manager and NFS
Hello,
> I like the way Knetwork Manager and Network Manager work for the most part,
> but I find I cannot use them - why - because I need to change my nfs networks
> at each site I log into. And because network manager doesn't understand this,
> I have to use ifup and scpm to do it.
The "semi-canonical" way to do it probably to add some hook scripts
into /etc/NetworkManager/dispatcher.d/. Last time I checked, the
dispatcher ran each of these scripts in alphanumeric order with
arguments
{up|down}
You'll probably need to cook up some of your own wizardry in order to
automatically decide what network you're on, then change the NFS mounts,
etc. (I don't think there's any way at present to automate this on a
per-user basis, although as far as I understand it'd certainly be
possible with the current NM to write a user session daemon that waits
for a particular network connection and then, say, does a FUSE mount.)
James.
--
The Holy ettlz [EMAIL PROTECTED]
PGP key ID: 03F94B5D
---
signature.asc
Description: This is a digitally signed message part
___
NetworkManager-list mailing list
NetworkManager-list@gnome.org
http://mail.gnome.org/mailman/listinfo/networkmanager-list
Network Manager and NFS
I like the way Knetwork Manager and Network Manager work for the most part, but I find I cannot use them - why - because I need to change my nfs networks at each site I log into. And because network manager doesn't understand this, I have to use ifup and scpm to do it. I'm using a Lenovo T61 with openSUSE 11.0 64bit. Does anyone have suggestions how I can configure Knetwork manager to work with SCPM? Or alternate ways I can use Knetwork Manager to automatically change my nfs networks when I change connections? Thanks, Bob -- Robert Smits CEP525G Nanaimo, Duncan & District Labour Council Box 822 Nanaimo, V9R 5N2 Ph 250-753-0201 Fax 250-753-2954 Email [EMAIL PROTECTED] ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
