LinuxQuestions.org - Wireless configuration NetworkManager for Etch

- Debian (https://www.linuxquestions.org/questions/debian-26/)

- - Wireless configuration NetworkManager for Etch (https://www.linuxquestions.org/questions/debian-26/wireless-configuration-networkmanager-for-etch-631250/)

Wireless configuration NetworkManager for Etch

I have successfully negotiated a wireless connection to my router in Debian Etch on my Gateway 450SX4 laptop. However, I would like NetworkManager to automatically connect to the wireless network upon boot up each time, or at least have the option to save the network settings each time so that I may connect when needed, instead of having to enter the information each time. Currently, I set my router to act as a DHCP server in order to establish a connection, but also want to set a static value for this connection. If I attempt to configure my wireless connection using the Network settings option, I cannot establish wireless connectivity for some reason, only through NetworkManager. Any assistance is appreciated. Thanks.

hi, NM can only do so much.
check this out.

/usr/share/doc/network-manager

and
http://www.debian.org/doc/manuals/re...ateway.en.html

here's a sample for static

Code:

allow-hotplug ath0

iface ath0 inet static

    pre-up /etc/network/firewall.sh start

        address 192.168.2.116

        netmask 255.255.255.0

        gateway 192.168.2.1

        broadcast 192.168.0.255

        dns-nameservers 192.168.1.254

        dns-search localnet.net 

        wireless-mode managed

        wireless-essid virusinfected

    post-down /etc/network/firewall.sh clear

Quote:

Originally Posted by swampdog2002 (Post 3103112)

it's simpler to assign the static ip address at the router not via network manager. I do this and it works fine, my desktop's wireless adapter is managed by nm and configured for dhcp and the router always assigns static ip based on hostname. you could assign it by mac address just as well.

As for connecting automatically on boot I don't think this is possible using nm in Etch, it will always want to use the gnome-keyring and ask you for the keyring password. I assume that because it's a laptop and you're sometimes using it elsewhere you prefer to have a good gui tool for scanning and connecting, I'd suggest Wicd, that's what I use on my Debian based (antiX) laptops. It will connect on boot if you prefer, with no user intervention, and it's also much easier for setting static IP.

Quote:

Some of Wicd's features include:

1. No Gnome dependencies (although it does require GTK), so it is easy to use in XFCE, Fluxbox, Openbox, Enlightenment, etc.
2. Ability to connect to wired and wireless networks
3. Profiles for each wireless network and wired network
4. Many encryption schemes, some of which include WEP/WPA/WPA2
5. Remains compatible with wireless-tools
6. Tray icon showing network activity and signal strength

Other alternatives might be wpa_gui (must be run as root), ceni (see sidux) (also needs to be run as root), or wifi-wiz (also needs to be run as root).

wifi-wiz is quite similar to wicd but wicd imo is better as non-root users can use it and it can also handle wired connections.

Thanks for the information regarding wicd. I installed this application, but I was unable to negotiate a connection to my WAP using this, and when I had DHCP enabled on my router, the wireless card was unable to obtain an IP address for some reason. I went back to using Network Manager since it appears to work, for the most part anyway. What I am having trouble understanding is that, if I am disconnected either voluntarily or involuntarily from the wireless network here, I am unable to re-establish a connection in the same session. I have to reboot in order to reconnect wirelessly.

/usr/share/doc/network-manager/README

read it ;-)

nm won't necessarily reconnect when a connection is dropped. Some of the other tools I mentioned will. wifi-wiz will do this. Even if the connection is dropped there is no need to reboot, you can more easily restart networking. In terminal as root:

Code:

/etc/init.d/networking restart

Wicd: if you installed by using the wicd debian repo or the deb package then it should have removed network-manager and worked normally. If you installed by compiling from source and nm was still installed then expect problems.

No, I did use the Debian repository and it did uninstall Network Manager, I just had to reinstall after I uninstalled wicd. I realize that Network Manager may not automatically reconnect after a connection is dropped, but when I attempt to reconnect manually I am unable to do so.