Spent some time in the wicd gui, changing and testing each item one at a time,
no cigar
Well Dolphin,
thank you for the help - you showed me some new stuff
b.
topic title: Auto reconnect
-
Posts: 70
- Joined: 19 May 2013
-
Posts: 2,238
- Joined: 16 Dec 2007
#17
sorry it didn't work out. I'll be on the lookout for any solutions...
-
Posts: 70
- Joined: 19 May 2013
#18
I really prefer the action of Antix over mepis in many ways, I too will not give up.
but seeing that the mepis network works quite well, has given me an idea - project for the weekend:
Stuff all the Antix network folders into a storage folder..... in home, or another partition.
Copy all the network related folders from Mepis and paste them into Antix
__{{emoticon}}__
but seeing that the mepis network works quite well, has given me an idea - project for the weekend:
Stuff all the Antix network folders into a storage folder..... in home, or another partition.
Copy all the network related folders from Mepis and paste them into Antix
__{{emoticon}}__
-
Posts: 2,238
- Joined: 16 Dec 2007
#19
In reading through the bug reports for wicd last night, i noticed a report that said auto-reconnect would not work unless notifications were turned on. If you haven't tried that yet, you might. Its under the same wicd preferences screen. I noticed when I went to check that I have mine enabled.
-
Posts: 70
- Joined: 19 May 2013
#20
yup,
mine too was checked
mine too was checked
-
Posts: 70
- Joined: 19 May 2013
#21
Hey Dolphin,
before I start moving folders, can you look these two files over with a fine tooth comb - thanks
manager-settings.conf
[Settings]
backend = external
wireless_interface =
wired_interface = eth0
wpa_driver = wext
always_show_wired_interface = True
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
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
before I start moving folders, can you look these two files over with a fine tooth comb - thanks
manager-settings.conf
[Settings]
backend = external
wireless_interface =
wired_interface = eth0
wpa_driver = wext
always_show_wired_interface = True
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
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
#22
these files look ok. I should caution the moving folders from mepis to antix could cause all sorts of havoc.
also, its been a long time since I used mepis, but doesn't mepis use knetworkmanager for its connection management? The behavior you need may be a function of the manager.
also, its been a long time since I used mepis, but doesn't mepis use knetworkmanager for its connection management? The behavior you need may be a function of the manager.
-
Posts: 70
- Joined: 19 May 2013
#23
Uses Mepis network assistant -
Which has me using Static DNS, not dhcp for dns
It's available via synaptic, was also thinking about installing it after moving folders around,
got it in the mepis repositories.
If I hose the antix - a reinstall is no big deal.
I'm looking around in antix to check these settings..... still looking
Which has me using Static DNS, not dhcp for dns
It's available via synaptic, was also thinking about installing it after moving folders around,
got it in the mepis repositories.
If I hose the antix - a reinstall is no big deal.
I'm looking around in antix to check these settings..... still looking
-
Posts: 2,238
- Joined: 16 Dec 2007
#24
are you also using a static ip address under mepis? If so, you might try setting up a static ip on antix and see if that helps. Part of the problem may be waiting on wicd to issue a dhcp request.
-
Posts: 137
- Joined: 19 Sep 2012
#25
I have no idea whether this will be any use at all, but, I have always had trouble with holding a wireless signal on my netbook and the only distro I've been able to manage it with is antiX.
1) I set my system up using ceni - you've tried this & say it doesn't work. I have to say, I find it unbeatable for wireless.
2) I have 2 aliases:
When things go wrong, dlan closes the network; uplan brings it up again & checks that it's working. (
========= SCRAPER REMOVED AN EMBEDDED LINK HERE ===========
url was:"http://www.example.com"
linktext was:"www.example.com"
====================================
appears to be a site set up purely to test ping.). The output looks like this:
(I also have 3ping set up as a stand alone alias to test whether everything is working when things get slow.)
3} I have found from bitter experience with this machine that network managers like wicd or knetworkmanager don't make anything easier - infact, they complicate things, that's why I love ceni
I really struggled with this machine - different distros, different software Etc - and this is the answer I came up with. It may be irrelevant for you (obviously wlan0 becomes eth0) but there may be something here you can use. I hope so - I know what it's like, you have my sympathy.
1) I set my system up using ceni - you've tried this & say it doesn't work. I have to say, I find it unbeatable for wireless.
2) I have 2 aliases:
Code: Select all
alias uplan="su -c 'ifup wlan0'; ping -c 3 www.example.com"
alias dlan="su -c 'ifdown wlan0'"
========= SCRAPER REMOVED AN EMBEDDED LINK HERE ===========
url was:"http://www.example.com"
linktext was:"www.example.com"
====================================
appears to be a site set up purely to test ping.). The output looks like this:
Code: Select all
$ dlan
Password:
Internet Systems Consortium DHCP Client 4.2.2
Copyright 2004-2011 Internet Systems Consortium.
All rights reserved.
For info, please visit https://www.isc.org/software/dhcp/
Listening on LPF/wlan0/0c:60:76:3f:54:c6
Sending on LPF/wlan0/0c:60:76:3f:54:c6
Sending on Socket/fallback
DHCPRELEASE on wlan0 to 192.168.1.1 port 67
cat: /sys/module/p80211/parameters/wlan_wext_write: No such file or directory
dmk-antiX@antiXdell:~
$ ping -c 1 http://www.example.com
ping: unknown host http://www.example.com # The computer is disconnected
dmk-antiX@antiXdell:~
$ uplan
Password:
FATAL: Module p80211 not found.
Failed to load p80211.ko.
run-parts: /etc/network/if-pre-up.d/linux-wlan-ng-pre-up exited with return code 1
Internet Systems Consortium DHCP Client 4.2.2
Copyright 2004-2011 Internet Systems Consortium.
All rights reserved.
For info, please visit https://www.isc.org/software/dhcp/
Listening on LPF/wlan0/0c:60:76:3f:54:c6
Sending on LPF/wlan0/0c:60:76:3f:54:c6
Sending on Socket/fallback
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 5
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 8
DHCPREQUEST on wlan0 to 255.255.255.255 port 67
DHCPOFFER from 192.168.1.1
DHCPACK from 192.168.1.1
bound to 192.168.1.7 -- renewal in 37896 seconds.
PING http://www.example.com (192.0.43.10) 56(84) bytes of data.
64 bytes from 43-10.any.icann.org (192.0.43.10): icmp_req=1 ttl=240 time=142 ms
64 bytes from 43-10.any.icann.org (192.0.43.10): icmp_req=2 ttl=240 time=140 ms
64 bytes from 43-10.any.icann.org (192.0.43.10): icmp_req=3 ttl=240 time=141 ms
--- http://www.example.com ping statistics ---
3 packets transmitted, 3 received, 0% packet loss, time 2002ms
rtt min/avg/max/mdev = 140.991/141.470/142.225/0.621 ms
3} I have found from bitter experience with this machine that network managers like wicd or knetworkmanager don't make anything easier - infact, they complicate things, that's why I love ceni
I really struggled with this machine - different distros, different software Etc - and this is the answer I came up with. It may be irrelevant for you (obviously wlan0 becomes eth0) but there may be something here you can use. I hope so - I know what it's like, you have my sympathy.
Last edited by duncan_mk on 24 May 2013, 12:32, edited 1 time in total.
-
Posts: 1,062
- Joined: 20 Jan 2010
#26
maybe these will help
========= SCRAPER REMOVED AN EMBEDDED LINK HERE ===========
url was:"https://bbs.archlinux.org/viewtopic.php?id=104519"
linktext was:"https://bbs.archlinux.org/viewtopic.php?id=104519"
====================================
========= SCRAPER REMOVED AN EMBEDDED LINK HERE ===========
url was:"http://forums.gentoo.org/viewtopic-t-806656-view-previous.html"
linktext was:"http://forums.gentoo.org/viewtopic-t-80 ... 36a54ce280"
====================================
I would say the main thing is to check the wicd log like stated in the second link
========= SCRAPER REMOVED AN EMBEDDED LINK HERE ===========
url was:"https://bbs.archlinux.org/viewtopic.php?id=104519"
linktext was:"https://bbs.archlinux.org/viewtopic.php?id=104519"
====================================
========= SCRAPER REMOVED AN EMBEDDED LINK HERE ===========
url was:"http://forums.gentoo.org/viewtopic-t-806656-view-previous.html"
linktext was:"http://forums.gentoo.org/viewtopic-t-80 ... 36a54ce280"
====================================
I would say the main thing is to check the wicd log like stated in the second link
-
Posts: 70
- Joined: 19 May 2013
#27
More good stuff
will keep on it
b.
will keep on it
b.
-
Posts: 70
- Joined: 19 May 2013
#28
FIXED !
Thank you everyone, I learned alot, you've been very supportive,
especially Dolphin who put in alot of time researching.
Rereading Dolphin's"Applet" word started me down the right trail.
I never saw one one in my tray, I was always checking it from the wicd words.
So I tried a few days to get the Mepis / kde stuff in working order.
It really never loaded in all the correct files, it worked but still left me in a buggy situation,
So the problem was not solved.
I came across a great web page:
========= SCRAPER REMOVED AN EMBEDDED LINK HERE ===========
url was:"https://wiki.archlinux.org/index.php/NetworkManager"
linktext was:"https://wiki.archlinux.org/index.php/NetworkManager"
====================================
Today I tried to fix up the kde manager to no avail,
in reality it just loaded a bunch of bloat.... especially the plasma stuff.
My last resort before reinstalling a clean OS was to try the Gnome manager stuff.
I removed almost all the kde manager stuff
Installed The Gnome manager stuff.
Viola, saw a gnome applet in the toolbar.
And yes
Autoreconnect is working without a hitch.
Did a shutdown - reboot
Network still reconnects automatically
( but the applet disappeared.... hmmmmm? )
THANKS GUYS
Thank you everyone, I learned alot, you've been very supportive,
especially Dolphin who put in alot of time researching.
Rereading Dolphin's"Applet" word started me down the right trail.
I never saw one one in my tray, I was always checking it from the wicd words.
So I tried a few days to get the Mepis / kde stuff in working order.
It really never loaded in all the correct files, it worked but still left me in a buggy situation,
So the problem was not solved.
I came across a great web page:
========= SCRAPER REMOVED AN EMBEDDED LINK HERE ===========
url was:"https://wiki.archlinux.org/index.php/NetworkManager"
linktext was:"https://wiki.archlinux.org/index.php/NetworkManager"
====================================
Today I tried to fix up the kde manager to no avail,
in reality it just loaded a bunch of bloat.... especially the plasma stuff.
My last resort before reinstalling a clean OS was to try the Gnome manager stuff.
I removed almost all the kde manager stuff
Installed The Gnome manager stuff.
Viola, saw a gnome applet in the toolbar.
And yes
Autoreconnect is working without a hitch.
Did a shutdown - reboot
Network still reconnects automatically
( but the applet disappeared.... hmmmmm? )
THANKS GUYS
-
Posts: 2,238
- Joined: 16 Dec 2007
#29
glad you got it working. If i recall correctly, knetworkmanager and gnomenetworkmanager both utilize the network-manager dameon to manage the connections. The network-manager dameon is probably still loading at boot-time for you, but the gui-interface tray icon is not. If you add the appropriate launch command to your startup folder the icon should show up.
-
Posts: 70
- Joined: 19 May 2013
#30
Thank You -
was just looking at that
Have a wonderful weekend
was just looking at that
Have a wonderful weekend