wired network

viperskunk · 2008-11-14 16:41:41

I just installed Arch from Opensuse 11 following this guide http://wiki.archlinux.org/index.php/Ins … ting_Linux .
I installed Gnome 2.24 desktop through OpenSuse also. However, when I log into Arch, the internet (wired) is not working.
I have installed networkmanager. In order to get it working, i messed around with /etc/rc.conf a lot. And now the internet is even more messed up.
As a first time user of Arch, I have no idea what wrong I have done. Now I cannot even install packages onto Arch through opensuse chroot /bin/bash -ing into the Arch system. The internet on opensuse is working fine, but not on Arch.
I have read the myriad of guides on the Arch site regarding networking and network manager. I would like to shift to wicd now.
However, if the problem can be solved through networkmanager itself, then I won't shift.

So here is my question:
Say I have a wired eth0 connection whose IP address 10.10.1x.xx and primary DNS is 10.10.0.x and the subnet mask is 255.255.xxx.xxx.
What should be my entry in rc.conf and hosts files? (I do not know how to find my broadcast address).

at present my rc.conf reads:

HOSTNAME="myhost"

# 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
#
eth0="eth0 10.10.xx.x netmask 255.255.xxx.xxx broadcast 10.10.xx.xx"
INTERFACES=(lo !eth0 !wlan0 wmaster0)

# 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 10.10.xx.xx"
ROUTES=(gateway)

DAEMONS=(syslog-ng !network netfs @crond avahi-daemon avahi-dnsconfd hal dbus dhcdbd networkmanager gdm @fam  dhclient)

and my /etc/hosts/ file reads

#
# /etc/hosts: static lookup table for host names
#

#<ip-address>    <hostname.domain.org>    <hostname>
127.0.0.1        localhost.localdomain    localhost

# End of file

I also am very confused about what to enable and disable in rc.conf, for the networkmanager to work.
Could someone please please help me out with this setup? I have read a lot on the site and gotten more confused. I would really appreciate if you could just walk me through this step.
Thanks a ton in advance.

Last edited by viperskunk (2008-11-14 16:43:31)

viperskunk · 2008-11-14 16:47:27

There was one more thing. I had installed gnome-system-tools in Gnome in Arch. When I logged into Arch, and went to System > Admin >Network, it was all locked. and said device not configured or something like that.
With the current settings (the one quoted above), it is all frozen, but it says device in roaming mode or somthing. The important thing is that System > Admin > Network is all frozen, and doesn't seem to be working at all. I mean all the tabs work, but the options and devices, I just cannot click on.

Please help.

viperskunk · 2008-11-14 16:50:05

Maybe if you could suggest, how to configure the system so that the internet works through opensuse, then i could download wicd and uninstall network manager altogether. But then I would need help again how to set up wicd, and the corresponding entries in rc.conf / hosts etc.

Sorry to be so ignorant about Arch, but I would really like to use Arch. And I am going paranoid at present.
Any help is greatly appreciated.

Thanks.

perbh · 2008-11-14 16:57:39

first try it 'by hand' (I'm assuming 10.10.10.1 and a class 'C' network with 255 hosts, gw=10.10.10.254)
bash# ifconfig eth0 10.10.10.1 netmask 255.255.255.0 broadcast 10.10.10.255 up
bash# ifconfig default gw 10.10.10.254

You need a nameserver as well (/etc/resolv.conf) - assume that it is the same as the gateway:
bash# echo "nameserver 10.10.10.254" >/etc/resolv.conf

Now try pinging:
bash# ping www.google.com

If you are using a fixed ip-address (which is the case here) you also need an entry for it in /etc/hosts
bash# echo -e "10.10.10.1\tmyarchbox" >>/etc/hosts

Last edited by perbh (2008-11-14 16:59:27)

viperskunk · 2008-11-14 17:40:11

Hi. Thanks for the quick reply.
I did what you wrote. When I am pinging, I still get unknown host error.

viperskunk · 2008-11-14 18:53:36

Please help!

Majorix · 2008-11-14 18:58:37

I would re-install and this time use wicd instead of networkmanager -- no need to edit rc.conf (well except for adding the daemon to the list).

viperskunk · 2008-11-14 19:18:54

Majorix wrote:

I would re-install and this time use wicd instead of networkmanager -- no need to edit rc.conf (well except for adding the daemon to the list).

Hi thanks for the response. But I din't get you clearly there.
reinstall what? Like the whole Gnome desktop? or Arch? or networkmanager?

ralvez · 2008-11-14 19:58:56

Well ... let me ask you something:
You say you have a wired network, which therefore would require that you have enabled eth0 but in your set up (/etc/rc.conf) that is not the case.
(INTERFACES=(lo !eth0 !wlan0 wmaster0) ) since the exclamation mark means "no" or "disable" for all practical purposes.

What interface are you using in your wired network?

what's the result of : ifconfig

R.

marxav · 2008-11-14 20:12:57

ralvez wrote:

Well ... let me ask you something:
You say you have a wired network, which therefore would require that you have enabled eth0 but in your set up (/etc/rc.conf) that is not the case.
(INTERFACES=(lo !eth0 !wlan0 wmaster0) ) since the exclamation mark means "no" or "disable" for all practical purposes.
What interface are you using in your wired network?
what's the result of : ifconfig

R.

And in addition to what ralvez wrote, your network is not enabled. There is a ! infront of the network deamons...

viperskunk · 2008-11-14 21:01:21

ralvez wrote:

Well ... let me ask you something:
You say you have a wired network, which therefore would require that you have enabled eth0 but in your set up (/etc/rc.conf) that is not the case.
(INTERFACES=(lo !eth0 !wlan0 wmaster0) ) since the exclamation mark means "no" or "disable" for all practical purposes.
What interface are you using in your wired network?
what's the result of : ifconfig

R.

This is exactly why i am so confused.
Here it says the exact opposite.
http://wiki.archlinux.org/index.php/Networkmanager

Please have a look at the Configure section.

ralvez · 2008-11-15 02:39:40

OK. Let's make things simpler.
Here is a sample of a working /etc/rc.d 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"
# 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_CA.utf8"
HARDWARECLOCK="UTC"
TIMEZONE="Canada/Eastern"
KEYMAP="us"
CONSOLEFONT=
CONSOLEMAP=
USECOLOR="yes"

#
# -----------------------------------------------------------------------
# HARDWARE
# -----------------------------------------------------------------------
#
# Scan hardware and load required modules at bootup
MOD_AUTOLOAD="yes"
# Module Blacklist - modules in this list will never be loaded by udev
MOD_BLACKLIST=(snd-pcsp)
#
# Modules to load at boot-up (in this order)
#   - prefix a module with a ! to blacklist it
#
MODULES=(skge vboxdrv) 
# Scan for LVM volume groups at startup, required if you use LVM
USELVM="no"

#
# -----------------------------------------------------------------------
# NETWORKING
# -----------------------------------------------------------------------
#
HOSTNAME="dragonfly"
#
# 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
#
# Note: to use DHCP, set your interface to be "dhcp" (eth0="dhcp")
#
lo="lo 127.0.0.1"
eth0="eth0 192.168.1.21 netmask 255.255.255.0 broadcast 192.168.1.255"
INTERFACES=(lo eth0)
#
# 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.1.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-profiles
#
#NET_PROFILES=(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 @cups ntpd @crond @alsa @hal gdm)


# End of file

A few things to notice:
1. the line MODULES=(skge vboxdrv) will be different in your machine, so for starters; unless you know you need some specific modules live it blank eg: MODULES=()
2. HOSTNAME='THE_NAME_OF_YOUR_MACHINE' is the name you give the machine to identify it in the network. I called mine dragonfly.
3. Notice that I', using the 192.168. range (as opposed to 10.10.x.x) so in your case just use the IP address values you chose for your network and notice also that the gateway **has** a value.
4. In the DAEMONS line you will see some applications preceded by '@' like @cups. This loads the appps in the background which will speed up your boot time but you **do not have ** to use it that way and you can safely remove the '@' symbol without causing any problems.

Use this file as an example (or even copy and paste it into your system) to modify your /etc/rc.conf so that your system will work.

If you need help after doing this ... just ask

R.

viperskunk · 2008-11-15 20:43:31

Thank you. But even after using, your rc.conf, and changing it as you suggested, i am unable to connect to internet. No matter, what I do, change, edit, I just cannot seem to be able to connect.
The only option left for me now, I guess, would be to do a fresh install and not change the rc.conf at all. At the same time, install gnome/xfce and this time include wicd (instead of network-manager).
Will that work?
Will putting in values in wicd, instead of rc.conf work the internet?
What do you suggest?
Thanks once again.

ralvez · 2008-11-15 20:55:01

I do not think a re-install will do you much good.
Open a console and type: "ifconfig" then post the result of that here, so we can analyze what your machine is doing.

R.

Last edited by ralvez (2008-11-15 20:55:22)

viperskunk · 2008-11-16 18:07:26

ralvez wrote:

I do not think a re-install will do you much good.
Open a console and type: "ifconfig" then post the result of that here, so we can analyze what your machine is doing.
R.

bash-3.2# ifconfig
eth0      Link encap:Ethernet  HWaddr 00:16:D3:0x:xx:xx  
          inet addr:10.10.12.4  Bcast:10.10.12.63  Mask:255.255.255.192
          inet6 addr: fe80::216:d3ff:fe0e:54ec/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:75364 errors:0 dropped:0 overruns:0 frame:0
          TX packets:58163 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000 
          RX bytes:52444831 (50.0 Mb)  TX bytes:8913640 (8.5 Mb)

lo        Link encap:Local Loopback  
          inet addr:127.0.0.1  Mask:255.0.0.0
          inet6 addr: ::1/128 Scope:Host
          UP LOOPBACK RUNNING  MTU:16436  Metric:1
          RX packets:2898 errors:0 dropped:0 overruns:0 frame:0
          TX packets:2898 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0 
          RX bytes:85712 (83.7 Kb)  TX bytes:85712 (83.7 Kb)

Last edited by viperskunk (2008-11-16 19:43:00)

ralvez · 2008-11-16 21:57:08

OK.
Now we know that your settings, as it pertains to your Nic card are accepted by your system.
I take that this machine is connected to a network that has a router or gateway with the address (10.10.12.1 or something like that) on its green Nic card and that the second Nic (red) is connected to your public address. Correct?

Now let us verify that this NIC is working in relation to the rest of the network.

1. Post the results of the command "route"
2. As root issue the command "mii-tool" and post the result here.
3. Also post the contents of your /etc/resolv.conf

R.

viperskunk · 2008-11-16 22:38:17

bash-3.2# route
Kernel IP routing table
Destination     Gateway         Genmask         Flags Metric Ref    Use Iface
10.10.12.0      *               255.255.255.192 U     0      0        0 eth0
127.0.0.0       *               255.0.0.0       U     0      0        0 lo
default         10.10.12.1      0.0.0.0         UG    0      0        0 eth0

and my rc. conf is

#
# /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"
# USEDIRECTISA: use direct I/O requests instead of /dev/rtc for hwclock
# 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_US.utf8"
HARDWARECLOCK="localtime"
USEDIRECTISA="no"
TIMEZONE="Canada/Pacific"
KEYMAP="us"
CONSOLEFONT=
CONSOLEMAP=
USECOLOR="yes"

# -----------------------------------------------------------------------
# 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="myhost"

# 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
#
lo="lo 127.0.0.1"
eth0="eth0 10.10.12.4 netmask 255.255.255.192 broadcast 10.10.12.63"
INTERFACES=(lo eth0)

# 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 10.10.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 @crond cups @hal @alsa gdm @fam)

and the result of mii-tool

bash-3.2# mii-tool
eth0: negotiated 100baseTx-FD flow-control, link ok

Last edited by viperskunk (2008-11-16 22:41:55)

viperskunk · 2008-11-16 22:40:31

As you can probably see, i haven't the slightest idea regarding the questions you are asking. (This is my first time with Arch). But i am just trusting you and following whatever you are saying.
Thanks a TON. I cannot express my gratitude to you properly in words.
But I am trying. THANK YOU!!!

viperskunk · 2008-11-16 22:59:01

OOPS!!!! Sorry.
The above results I posted of mii-tool was taken from my working opensuse system, after chroot-ing into my Arch install.
However, the real result after booting into the actual arch install is this:

[viper@myhost ~]$ mii-tool
SIOCGMIIPHY on 'eth0' failed: Operation not permitted
SIOCGMIIPHY on 'eth1' failed: Operation not permitted
SIOCGMIIPHY on 'eth2' failed: Operation not permitted
SIOCGMIIPHY on 'eth3' failed: Operation not permitted
SIOCGMIIPHY on 'eth4' failed: Operation not permitted
SIOCGMIIPHY on 'eth5' failed: Operation not permitted
SIOCGMIIPHY on 'eth6' failed: Operation not permitted
SIOCGMIIPHY on 'eth7' failed: Operation not permitted
no MII interfaces found

and of ifconfig

[viper@myhost ~]$ ifconfig
eth0      Link encap:Ethernet  HWaddr 00:16:D3:0x:xx:xx  
          inet addr:10.10.12.4  Bcast:10.10.12.63  Mask:255.255.255.192
          inet6 addr: fe80::216:d3ff:fe0e:54ec/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:26 errors:0 dropped:0 overruns:0 frame:0
          TX packets:6 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000 
          RX bytes:1647 (1.6 Kb)  TX bytes:468 (468.0 b)

lo        Link encap:Local Loopback  
          inet addr:127.0.0.1  Mask:255.0.0.0
          inet6 addr: ::1/128 Scope:Host
          UP LOOPBACK RUNNING  MTU:16436  Metric:1
          RX packets:24 errors:0 dropped:0 overruns:0 frame:0
          TX packets:24 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0 
          RX bytes:1728 (1.6 Kb)  TX bytes:1728 (1.6 Kb)

and of route

[viper@myhost ~]$ route
Kernel IP routing table
Destination     Gateway         Genmask         Flags Metric Ref    Use Iface
10.10.12.0      *               255.255.255.192 U     0      0        0 eth0

I apologise for the mistake. But maybe the difference between the two can give you a clue regarding what might be wrong....

Last edited by viperskunk (2008-11-16 23:00:59)

my0pic · 2008-11-16 23:07:04

Is your gateway supposed to be 10.10.12.1
You have 10.10.0.1 as your gateway in rc.conf.

ralvez · 2008-11-17 02:41:55

my0pic wrote:

Is your gateway supposed to be 10.10.12.1
You have 10.10.0.1 as your gateway in rc.conf.

He is a 100% correct.
Your gateway in arch is wrong, therefore, you will not be able to access anything on the "outside".
Change your gateway from 10.10.0.1 to 10.10.12.1

BTW, the mii-tool command failed because you have to be root in order for this to work. Issue the command like this:
su -c 'mii-tool'

You will be asked for the root password, type it in and you will get the correct result.

Also, try to connect to the web after you changed the gateway address, perhaps that's the only problem.

R.

viperskunk · 2008-11-17 12:37:15

Okay so i changed the gateway, as specified. and still the same result. can't even do pacman -Syu.
I am in tears.

ralvez · 2008-11-17 12:43:27

Very well then.
Post your /etc/hosts and your /etc/resolv.conf see what we find.

R.

viperskunk · 2008-11-17 16:22:27

funnily enough, i have TWO resolv.conf files.
they are:

### BEGIN INFO
#
# Modified_by:  NetworkManager
# Process:      /usr/bin/NetworkManager
# Process_id:   2636
#
### END INFO

nameserver 10.10.0.1

and my hosts file is

#
# /etc/hosts: static lookup table for host names
#

#<ip-address>    <hostname.domain.org>    <hostname>
127.0.0.1        localhost.localdomain    localhost

# End of file
10.10.12.4    myarchbox
10.10.12.4    myarchbox

perbh · 2008-11-17 17:06:54

You can't have _two_ /etc/resolv.conf files - that's a physical impossibility (unless you are running a filesystem with versioning!! - ala vax-vms)

And as for /etc/hosts - you have just copied what I said earlier - ie. 'myarchbox'.
What I really meant was:
10.10.12.4 the-name-you-have-chosen-for-the-computer-where-arch-is-the-os

In this case - and according to your /etc/rc.conf - the name should be 'myhost'

Arch Linux

#1 2008-11-14 16:41:41

wired network

#2 2008-11-14 16:47:27

Re: wired network

#3 2008-11-14 16:50:05

Re: wired network

#4 2008-11-14 16:57:39

Re: wired network

#5 2008-11-14 17:40:11

Re: wired network

#6 2008-11-14 18:53:36

Re: wired network

#7 2008-11-14 18:58:37

Re: wired network

#8 2008-11-14 19:18:54

Re: wired network

#9 2008-11-14 19:58:56

Re: wired network

#10 2008-11-14 20:12:57

Re: wired network

#11 2008-11-14 21:01:21

Re: wired network

#12 2008-11-15 02:39:40

Re: wired network

#13 2008-11-15 20:43:31

Re: wired network

#14 2008-11-15 20:55:01

Re: wired network

#15 2008-11-16 18:07:26

Re: wired network

#16 2008-11-16 21:57:08

Re: wired network

#17 2008-11-16 22:38:17

Re: wired network

#18 2008-11-16 22:40:31

Re: wired network

#19 2008-11-16 22:59:01

Re: wired network

#20 2008-11-16 23:07:04

Re: wired network

#21 2008-11-17 02:41:55

Re: wired network

#22 2008-11-17 12:37:15

Re: wired network

#23 2008-11-17 12:43:27

Re: wired network

#24 2008-11-17 16:22:27

Re: wired network

#25 2008-11-17 17:06:54

Re: wired network

Board footer