Hello everyone,I am having a minor issue with the default network manager. I can connect fine, but it seems that I cannot change anything about my connection.
So my WiFi can connect with WICD, but not the default KDE network manager. I would like to know why. Do both these applications handle the connection differently? If so what would the difference be?
My hardware is a Broadcom 4313. I've tried the STA drivers and the open source drivers, and a few other options with Network Manager. None of which worked.
Hi to all,
Newbie to Ubuntu (and *loving* it & the community!), but long time Unix hacker (when that term meant something positive ;-))
Hi,
I am facing a strange issue when connecting to SQLPLUS via a shell scripts.
I am using Linux 2.6.18-274.18.1 and gbash shell.
When I connect to SQLPLUS through scripts then it throws TNS Time Out error ""sometimes"" and connects successfully other times.This is only happening when sqlplus is called within scripts and working fine when called directly from termin
On Xubuntu Karmic I access the net using a RaLink RT2561/RT61 802.11g PCI and a WiFi network that uses WPA/WPA2, EAP-TTLS, PAP security. The network sometimes "hangs" and Gnome's network manager usually reconnects automatically. Every once in a while (I'm unable to recreate it) the network-manager seems to hang and a reboot is required to get it working again.
My wifi connection drops sometimes and, for some reason, Network Manager attempts to connect to my neighbor's network, which requires a password (which I don't know). Is there any way to blacklist a wireless network so that the Network Manager will never attempt to connect to it?
I am trying to connect multiple USB 3G modem (two, in my case) in Ubuntu 12.04.
You wind up with this deal where network-manager doesn't start when eth0 doesn't connect, i.e. when you are 'a goin mo-bile (i.e. wireless). It's irritating. So I wrote this script:
#!/bin/bash
ifconfig eth0 | grep inet
if [[ $? != 0 ]];then
service network-manager stop
service network-manager start
fi
...and called it networkManagerFix.sh.
I've been using WICD on my eeepc 1005HA and have been able to connect to my wireless network flawlessly. Today I was unable to connect until I noticed that both WICD and Network-Manager were trying to make the connection - seemingly fighting for control. The problem was resolved when I killed network-manager (followed by a "chkconfig network-manager off" to keep it that
Email this page
