Re: An Idea
Please excuse me for reply to this message. I know that this isn't a help forum but I cannot stop myself from asking... How do you trigger process of checking the subnet we've moved on? Hasan Ceylan Casey Harkins wrote: > > On Wed, 2008-08-13 at 12:43 +0100, The Holy ettlz wrote: >> On Wed, 2008-08-13 at 14:36 +0300, Tambet Ingo wrote: >> > This can (and should) be done easily with dispatcher scripts. There's >> > a lot of things that might need to be changed depending on location >> > (things like printers, browser proxies, SMTP server, firewall, ...) >> >> I've been thinking about this recently --- is there an established, >> medium-neutral way of securely identifying a network? I was thinking of >> doing something like adding an extra option to DHCP that gave clients a >> HTTPS URL which they could use to identify and authenticate a network >> (triggered by an NMD hook), and then configure themselves according to a >> local database. >> >> James > > > The approach we've taken is to use separate private subnets for various > networks, avoiding the commonly used ones (192.168.0.0/24, > 192.168.1.0/24, 192.168.100.0/24). From this we can deduce which subnet > we are on (never hit an airport/hotel/coffee shop that uses any of our > subnets). One of the things we do with this (which gets back to the > original poster's idea) is to automatically add/remove printers based on > the subnet using a dispatcher script. Our script even pops up a > libnotify message letting you know when printers were added/removed and > which one it set as the system default. As we add new printers at > various offices, we just drop a ppd file and simple config file into our > package, push out an updated rpm, and all machines will support the new > printer if they are connected to that subnet. I can think of better ways > to handle this, but this is a simple low-tech solution that has worked > well for a few years now. > > > -casey > > > > > ___ > NetworkManager-list mailing list > NetworkManager-list@gnome.org > http://mail.gnome.org/mailman/listinfo/networkmanager-list > > -- View this message in context: http://www.nabble.com/An-Idea-tp18954271p18988268.html Sent from the Gnome - NetworkManager mailing list archive at Nabble.com. ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: An Idea
I agree that NM should not try to do everything and I am not saying it should do... Well, I still think, fixing DNS servers based on connection is at the same distance to the core functionality NM offers as fixing the hosts file... Hasan Ceylan Tambet Ingo-2 wrote: > > On Wed, Aug 13, 2008 at 2:15 AM, Hasan Ceylan <[EMAIL PROTECTED]> wrote: > >> Now, then the dynamic hosts file idea came on my mind. Wouldn't it be >> nice >> to have some hosts definitions in the connection properties so that they >> become effective based on the connection just like the IP and DNS setting >> based on connection profile in Network Manager > > This can (and should) be done easily with dispatcher scripts. There's > a lot of things that might need to be changed depending on location > (things like printers, browser proxies, SMTP server, firewall, ...) > and NM should not try to do everything. Instead, it should provide an > easy way to add hooks and that's what the dispatcher is for. > > Tambet > ___ > NetworkManager-list mailing list > NetworkManager-list@gnome.org > http://mail.gnome.org/mailman/listinfo/networkmanager-list > > -- View this message in context: http://www.nabble.com/An-Idea-tp18954271p18988180.html Sent from the Gnome - NetworkManager mailing list archive at Nabble.com. ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: An Idea
On Wed, 2008-08-13 at 12:43 +0100, The Holy ettlz wrote: > On Wed, 2008-08-13 at 14:36 +0300, Tambet Ingo wrote: > > This can (and should) be done easily with dispatcher scripts. There's > > a lot of things that might need to be changed depending on location > > (things like printers, browser proxies, SMTP server, firewall, ...) > > I've been thinking about this recently --- is there an established, > medium-neutral way of securely identifying a network? I was thinking of > doing something like adding an extra option to DHCP that gave clients a > HTTPS URL which they could use to identify and authenticate a network > (triggered by an NMD hook), and then configure themselves according to a > local database. > > James The approach we've taken is to use separate private subnets for various networks, avoiding the commonly used ones (192.168.0.0/24, 192.168.1.0/24, 192.168.100.0/24). From this we can deduce which subnet we are on (never hit an airport/hotel/coffee shop that uses any of our subnets). One of the things we do with this (which gets back to the original poster's idea) is to automatically add/remove printers based on the subnet using a dispatcher script. Our script even pops up a libnotify message letting you know when printers were added/removed and which one it set as the system default. As we add new printers at various offices, we just drop a ppd file and simple config file into our package, push out an updated rpm, and all machines will support the new printer if they are connected to that subnet. I can think of better ways to handle this, but this is a simple low-tech solution that has worked well for a few years now. -casey ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: An Idea
On Wed, 2008-08-13 at 14:36 +0300, Tambet Ingo wrote: > This can (and should) be done easily with dispatcher scripts. There's > a lot of things that might need to be changed depending on location > (things like printers, browser proxies, SMTP server, firewall, ...) I've been thinking about this recently --- is there an established, medium-neutral way of securely identifying a network? I was thinking of doing something like adding an extra option to DHCP that gave clients a HTTPS URL which they could use to identify and authenticate a network (triggered by an NMD hook), and then configure themselves according to a local database. 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: An Idea
On Wed, Aug 13, 2008 at 2:15 AM, Hasan Ceylan <[EMAIL PROTECTED]> wrote: > Now, then the dynamic hosts file idea came on my mind. Wouldn't it be nice > to have some hosts definitions in the connection properties so that they > become effective based on the connection just like the IP and DNS setting > based on connection profile in Network Manager This can (and should) be done easily with dispatcher scripts. There's a lot of things that might need to be changed depending on location (things like printers, browser proxies, SMTP server, firewall, ...) and NM should not try to do everything. Instead, it should provide an easy way to add hooks and that's what the dispatcher is for. Tambet ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
An Idea
Hello, I have an idea and would like to share with the Network Manager developers before posting an enhancement request to the bugzilla. I use my laptop mainly home and at the office. I have a vpn that connects me to the office when I am working at home. Not the VPN IP address and the lAN IP address of the SVN server are obviously different. And the vpn server is neither at home nor at the office. So it fine to go the svn by the VPN IP when I am out of the office but when I am in the office, in order to reach the SVN server, I'll have to travel through the VPN server (thus the internet -> slow) So there is one option, As I move around I'll have to keep different hosts files and change them according to my current location. ie: change the SVN server's IP address from VPN IP to Office LAN IP. I looked into the possibility of using DNS to return *closer* IP of the destination server but AFAIK, this is not possible. Now, then the dynamic hosts file idea came on my mind. Wouldn't it be nice to have some hosts definitions in the connection properties so that they become effective based on the connection just like the IP and DNS setting based on connection profile in Network Manager Regards, Hasan Ceylan -- View this message in context: http://www.nabble.com/An-Idea-tp18954271p18954271.html Sent from the Gnome - NetworkManager mailing list archive at Nabble.com. ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
