Hi,
I spent a few days on this, hope you guys can help out.
While running Mepis, I have the ability to unplug my ethernet cord while not on the internet, then simply reconnect it and immediately surf away.
This is something I cannot do in Antix.
Upon reconnecting, the network connection stays down until I open up the
"wicd network manager" and hit the reconnect button.
Is there a script or something I can alter to get Antix to automatically reconnect?
Most of my network scripts are similar between the two partitions,
here are a few of the Mepis settings:
Interfaces:
Settings for eth0
Use DHCP to get IP settings
Start at boot
Network Assistant:
Connect to internet directly
Automatic ( Network manager)
Use static DNS
(example) 123.12.34.56
Secondary DNS
( example) 123.12.34.57
Thank You for the assistance,
b.
topic title: Auto reconnect
-
Posts: 70
- Joined: 19 May 2013
-
Posts: 2,238
- Joined: 16 Dec 2007
#2
Hi,
what you want is to look into the wicd preferences (it may be a hidden menu off to the right under a triangle) and make sure the following two boxes are checked:"automaticly reconnect on connection loss" and"always switch to a wired connection when available". the later will give you the behavior you are looking for, although its a tad slow to refresh the network/dhcp. If you are using the icon in the toolbar, you may have a connection before the icon says you do.
what you want is to look into the wicd preferences (it may be a hidden menu off to the right under a triangle) and make sure the following two boxes are checked:"automaticly reconnect on connection loss" and"always switch to a wired connection when available". the later will give you the behavior you are looking for, although its a tad slow to refresh the network/dhcp. If you are using the icon in the toolbar, you may have a connection before the icon says you do.
-
Posts: 70
- Joined: 19 May 2013
#3
That was a nice spot you showed me, Dolphin.
However, my machine might be a little stupid, the fix didn't take.
I fiddled around with a few other check boxes to no avail.
Waited 5 min, never reconnected .... usually mepis will reconnect in 5 sec.
I could check a script to see if the gui wrote to it.......... ( don't know which one)
However, my machine might be a little stupid, the fix didn't take.
I fiddled around with a few other check boxes to no avail.
Waited 5 min, never reconnected .... usually mepis will reconnect in 5 sec.
I could check a script to see if the gui wrote to it.......... ( don't know which one)
-
Posts: 2,238
- Joined: 16 Dec 2007
#4
I have one more box checked, with the"wired-connection" shown as a default profile. Other than that all I did was close wicd the wicd gui.
-
Posts: 70
- Joined: 19 May 2013
#5
hmmmm,
got that checked also,
I'll keep fiddleing
when you tested your box, how long did it take to auto reconnect after reconnecting your cord?
got that checked also,
I'll keep fiddleing
when you tested your box, how long did it take to auto reconnect after reconnecting your cord?
-
anticapitalista
Posts: 5,955
- Site Admin
- Joined: 11 Sep 2007
#6
Have you tried using ceni and then see if it auto-reconnects,
-
Posts: 70
- Joined: 19 May 2013
#7
Well,
I was working with that yesterday,
I just reconfigured as you asked, after the Dolphin fix,
not working yet
Ceni settings:
Method:
DHCP
Class
Auto
I was working with that yesterday,
I just reconfigured as you asked, after the Dolphin fix,
not working yet
Ceni settings:
Method:
DHCP
Class
Auto
-
Posts: 2,238
- Joined: 16 Dec 2007
#8
bbwf,
it took about 5-10 seconds. I will say that sometimes I had a connection even if the wicd-tooltip said I didn't. The wicd-icon-tooltip information is not very responsive.
it took about 5-10 seconds. I will say that sometimes I had a connection even if the wicd-tooltip said I didn't. The wicd-icon-tooltip information is not very responsive.
-
Posts: 2,238
- Joined: 16 Dec 2007
#9
if this computer has wireless as well, you may want to disable it. I just realized I had my wireless disabled while I was testing the wired configuration.
-
Posts: 70
- Joined: 19 May 2013
#10
It's an old school machine, no wireless
HP P3 dual processor Katmai
Ethernet amd 79c970 ( pcnet32 Lance)
HP P3 dual processor Katmai
Ethernet amd 79c970 ( pcnet32 Lance)
-
Posts: 2,238
- Joined: 16 Dec 2007
#11
one more idea,
check in /etc/wicd/wired-settings.conf and see if you have a blank profile. it should look something like this [] . If you do you can try deleting it.
check in /etc/wicd/wired-settings.conf and see if you have a blank profile. it should look something like this [] . If you do you can try deleting it.
-
Posts: 70
- Joined: 19 May 2013
#12
That's a good spot to look at:
Wireless-settings.conf ( blank..... as it should be )
wired settings.conf
[wired-default]
afterscript = None
dhcphostname = antiX1
postdisconnectscript = None
dns_domain = None
gateway = None
use_global_dns = False
lastused = True
encryption_enabled = False
beforescript = None
ip = None
broadcast = None
netmask = None
usedhcphostname = 0
predisconnectscript = None
enctype = None
default = 1
dns2 = None
search_domain = None
use_static_dns = False
dns3 = None
profilename = wired-default
dns1 = None
Wireless-settings.conf ( blank..... as it should be )
wired settings.conf
[wired-default]
afterscript = None
dhcphostname = antiX1
postdisconnectscript = None
dns_domain = None
gateway = None
use_global_dns = False
lastused = True
encryption_enabled = False
beforescript = None
ip = None
broadcast = None
netmask = None
usedhcphostname = 0
predisconnectscript = None
enctype = None
default = 1
dns2 = None
search_domain = None
use_static_dns = False
dns3 = None
profilename = wired-default
dns1 = None
-
Posts: 2,238
- Joined: 16 Dec 2007
#13
everything in there matches mine. How about manger-settings.conf?
here's mine
here's mine
Code: Select all
[Settings]
backend = external
wireless_interface = wlan0
wired_interface = eth0
wpa_driver = wext
always_show_wired_interface = False
use_global_dns = True
global_dns_1 = 8.8.8.8
global_dns_2 = 8.8.4.4
global_dns_3 = None
global_dns_dom = None
global_search_dom = None
auto_reconnect = True
debug_mode = 0
wired_connect_mode = 1
signal_display_type = 0
should_verify_ap = 1
dhcp_client = 0
link_detect_tool = 0
flush_tool = 0
sudo_app = 0
prefer_wired = True
show_never_connect = True
-
Posts: 70
- Joined: 19 May 2013
#14
manager settings shows autoreconnect as true, don't know if last line is correct
[Settings]
backend = external
wireless_interface =
wired_interface = eth0
wpa_driver = wext
always_show_wired_interface = False
use_global_dns = False
global_dns_1 = None
global_dns_2 = None
global_dns_3 = None
global_dns_dom = None
global_search_dom = None
auto_reconnect = True
debug_mode = 0
wired_connect_mode = 1
signal_display_type = 0
should_verify_ap = 1
dhcp_client = 0
link_detect_tool = 0
flush_tool = 0
sudo_app = 0
prefer_wired = True
show_never_connect = True
[Settings]
backend = external
wireless_interface =
wired_interface = eth0
wpa_driver = wext
always_show_wired_interface = False
use_global_dns = False
global_dns_1 = None
global_dns_2 = None
global_dns_3 = None
global_dns_dom = None
global_search_dom = None
auto_reconnect = True
debug_mode = 0
wired_connect_mode = 1
signal_display_type = 0
should_verify_ap = 1
dhcp_client = 0
link_detect_tool = 0
flush_tool = 0
sudo_app = 0
prefer_wired = True
show_never_connect = True
-
Posts: 2,238
- Joined: 16 Dec 2007
#15
well, I'm stumped. Sorry. You could try changing the setting for the link connect tool under preferences to one of the two options shown. Maybe one will work better than the other for your hardware. Its under"External Programs".
The last line simply defines whether wicd displays networks which you've designated never to connect to. Its handy for wireless networks where you don't really want to see your neighbors networks. It corresponds to the"Never Connect" setting in the gui.
The last line simply defines whether wicd displays networks which you've designated never to connect to. Its handy for wireless networks where you don't really want to see your neighbors networks. It corresponds to the"Never Connect" setting in the gui.