On Mon, 2009-01-19 at 15:56 -0500, Mail Lists wrote: > On 01/19/2009 03:52 PM, Mail Lists wrote: > > On 01/19/2009 03:42 PM, Mail Lists wrote: > > > > seems like some of the arguments can be up, down, vpn-up or vpn-down > > > > There must be some way to know which connection and which interface > > is being up'ed or downed ... i cannot find the docs anywhere ... where > > are the docs for this anyone know ? > > > > I still need help. Best I can tell > > $1 - is an interface (eth1, wlan0, etc) > $2 - is one of "up", "down", "vpn-up", "vpn-down" > > I still have no idea which connection - the NM name - "work-ny-wired", > "work-london-wifdi", or "home-wifi" or whatever the name used in NM. It > does not seem to be passed to the scripts - so how can the scripts know > what the right thing to do is ? ---- standard shell conventions for 2 arguments being passed, $1 is the first and $2 is the second and $0 is the command itself Honestly, I don't know what you're trying to accomplish by adding static routes - generally they are unnecessary unless you need to hop to a second vlan from vpn. If say your normal network is 192.168.1.0 and your default gateway is 192.168.1.254 and you connect via VPN to another LAN, say, 192.168.2.88. Assuming that you have a netmask of 255.255.255.0 on that VPN, you shouldn't have any problem communicating with any of the computers on either the 192.168.1.0 or 192.168.2.0 networks. Craig -- fedora-list mailing list fedora-list@xxxxxxxxxx To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
