On Thu, 20 Nov 2014 16:36:27 -0800
John Jason Jordan <[email protected]> dijo:

>On Thu, 20 Nov 2014 15:37:45 -0800
>wes <[email protected]> dijo:
>
>>> Any ideas what I have done wrong?
>
>>you still have to do sudo ifconfig blah blah, the difference is that
>>it should not ask for a password.
>
>Bingo! Thanks!

I can now disable / enable eth1 in a script without needing my
password, but it's not working quite the way I need it to work yet.

The first line in the script is 'sudo ifconfig eth1 down' and the last
line is '... up.' These are working as expected, except that the last
line does not actually connect to eth1. I still have to use the GUI to
reconnect to eth1. Note that this is a trivial matter; if I have to
stop and reconnect to eth1 once a day it is not the end of the world.
But scripts are supposed to automate things, so getting this thing to
work the way I want it to is a point of honor. 

Note also that I do not really need to completely disable eth1; all I
need to do is disconnect / reconnect it. I was using '... down' and
'... up' just because I couldn't find a command to just disconnect and
reconnect. 

I read the man pages for ifconfig, ifup and interfaces, but I didn't
find a way to automatically connect eth1. Of course, I didn't understand
everything that I read, so what I am looking for might still be in
there.

Also, when I reboot my computer it automatically brings up and connects
eth1. Shouldn't it automatically connect to it with the '... up'
command? Maybe I just need to fix something in the parameters of eth1,
or maybe the router?

_______________________________________________
PLUG mailing list
[email protected]
http://lists.pdxlinux.org/mailman/listinfo/plug

Reply via email to