[Solved] network-manager-applet - connects but does not work

ScottArch · 2009-11-02 21:43:42

Hi folks,

I am just configuring my first Arch install. I have looked at the various Wikis and on the forums, but I cannot find an exact answer to my problem.

I want to use the Gnome network manager applet (in Gnome) to connect to my 3G modem (3 network, Ireland). After much messing around I finally go the applet to start at boot and connect automatically. However, although it says I am connected, there seems to be no connection (it seems to be blocked). I initially thought that it may be because my user was not part of the network group, but adding myself to this group seems to have not worked. Here is my rc.conf file:

#
# /etc/rc.conf - Main Configuration for Arch Linux
#

# -----------------------------------------------------------------------
# LOCALIZATION
# -----------------------------------------------------------------------
#
# LOCALE: available languages can be listed with the 'locale -a' command
# HARDWARECLOCK: set to "UTC" or "localtime", any other value will result
#   in the hardware clock being left untouched (useful for virtualization)
# TIMEZONE: timezones are found in /usr/share/zoneinfo
# KEYMAP: keymaps are found in /usr/share/kbd/keymaps
# CONSOLEFONT: found in /usr/share/kbd/consolefonts (only needed for non-US)
# CONSOLEMAP: found in /usr/share/kbd/consoletrans
# USECOLOR: use ANSI color sequences in startup messages
#
LOCALE="en_GB.UTF-8"
HARDWARECLOCK="UTC"
TIMEZONE="Europe/Dublin"
KEYMAP="uk"
CONSOLEFONT=
CONSOLEMAP=
USECOLOR="no"

# -----------------------------------------------------------------------
# HARDWARE
# -----------------------------------------------------------------------
#
# MOD_AUTOLOAD: Allow autoloading of modules at boot and when needed
# MOD_BLACKLIST: Prevent udev from loading these modules
# MODULES: Modules to load at boot-up. Prefix with a ! to blacklist.
#
# NOTE: Use of 'MOD_BLACKLIST' is deprecated. Please use ! in the MODULES array.
#
MOD_AUTOLOAD="yes"
#MOD_BLACKLIST=() #deprecated
MODULES=()

# Scan for LVM volume groups at startup, required if you use LVM
USELVM="no"

# -----------------------------------------------------------------------
# NETWORKING
# -----------------------------------------------------------------------
#
# HOSTNAME: Hostname of machine. Should also be put in /etc/hosts
#
HOSTNAME="laptop"

# Use 'ifconfig -a' or 'ls /sys/class/net/' to see all available interfaces.
#
# Interfaces to start at boot-up (in this order)
# Declare each interface then list in INTERFACES
#   - prefix an entry in INTERFACES with a ! to disable it
#   - no hyphens in your interface names - Bash doesn't like it
# 
# DHCP:     Set your interface to "dhcp" (eth0="dhcp")
# Wireless: See network profiles below
#

#Static IP example
#eth0="dhcp"
eth0="dhcp"
ppp0="dhcp"
wlan0="dhcp"
INTERFACES=(!eth0 !ppp0 !wlan0)

# Routes to start at boot-up (in this order)
# Declare each route then list in ROUTES
#   - prefix an entry in ROUTES with a ! to disable it
#
gateway="default gw 192.168.0.1"
ROUTES=(!gateway)
 
# Enable these network profiles at boot-up.  These are only useful
# if you happen to need multiple network configurations (ie, laptop users)
#   - set to 'menu' to present a menu during boot-up (dialog package required)
#   - prefix an entry with a ! to disable it
#
# Network profiles are found in /etc/network.d
#
# This now requires the netcfg package
#
#NETWORKS=(main)

# -----------------------------------------------------------------------
# DAEMONS
# -----------------------------------------------------------------------
#
# Daemons to start at boot-up (in this order)
#   - prefix a daemon with a ! to disable it
#   - prefix a daemon with a @ to start it up in the background
#
DAEMONS=(syslog-ng !network netfs crond hal dbus fam networkmanager portmap)

I think my network settings are set up as per the instructions in the Wiki and the daemons are correct, so I am not really sure what the problem is. If anyone can help me out that would be great.

Cheers,

Scott

Last edited by ScottArch (2009-11-03 18:38:23)

guzz46 · 2009-11-02 22:00:49

Have you tried removing !

my rc.conf is standard

#Static IP example
#eth0="eth0 192.168.0.2 netmask 255.255.255.0 broadcast 192.168.0.255"
eth0="dhcp"
INTERFACES=(eth0)

But i can use network-manager-applet with no problems without needing to blacklist wlan0

ScottArch · 2009-11-03 18:24:54

Hi guz46

I have already tried removing the ! and the same thing happened ... but I realised today that I was being automatically connected to "Auto eth0" despite there being no cable present. When automatic connection was disabled on "Auto eth0" my 3G connection (ppp0) connected fine.

Could you clarify that the preferred set-up in the /etc/rc.conf for the interfaces is without the !. The Wiki for networkmanager says to disable them, but then states that some may need to be reenabled with no explanation. The purpose of this confuses me!

Thanks for you help anyways,

Scott

EDIT:

I appear to have fixed my problem with the auto connection on the various interfaces by updating my /etc/rc.conf file to:

#Static IP example
#eth0="dhcp"
ppp0="dhcp"
wlan0="dhcp"
eth0="dhcp"
INTERFACES=(ppp0 wlan0 eth0)

Thus ensuring that I can connect in order of preference.

Last edited by ScottArch (2009-11-03 18:48:47)

guzz46 · 2009-11-03 20:36:40

I'm not sure if there is a preferred setup, it's probably more of a guide and just use whatever seems to work for you.

I know when i set up network-manager-applet I didn't even touch my rc.conf apart from adding networkmanager to the daemons array and it worked fine

Arch Linux

#1 2009-11-02 21:43:42

[Solved] network-manager-applet - connects but does not work

#2 2009-11-02 22:00:49

Re: [Solved] network-manager-applet - connects but does not work

#3 2009-11-03 18:24:54

Re: [Solved] network-manager-applet - connects but does not work

#4 2009-11-03 20:36:40

Re: [Solved] network-manager-applet - connects but does not work

Board footer