Multiple nics but no ping

jeffkn · 2008-06-04 04:10:54

Hello-
I suck at Linux and networking, especially when someone takes away all the extras.... That said I really like Arch because I'm finally learning what I really need (or am missing) and what it's used for. I'm currently running Arch64 in a box with 3 nics as a host for VirtualBox. All of the nics appear to setup with their static IP correctly and even respond to pings from outside. Unfortunately, when I try to test connectivity with the following command, I just get errors:

ping 4.2.2.2 -I eth2

eth1 is my default for the system and I want eth0 and eth2 assigned to the virtual servers using 'internal networking'. But I can't seem to get anything through eth0 or eth2. Here's my rc.conf file followed by 'route' output, not sure what else I can provide to help. Thanks in advance!
-Jeff

#
# /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="yes"
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=(3c59x atl1 mii slhc tulip snd-mixer-oss snd-pcm-oss snd-hwdep snd-page-alloc snd-pcm snd-timer snd snd-hda-intel soundcore)
# 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="windsor"
# 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 172.20.20.5 netmask 255.255.255.0 broadcast 172.20.20.255"
eth1="eth1 172.20.20.10 netmask 255.255.255.0 broadcast 172.20.20.255"
eth2="eth2 172.20.20.15 netmask 255.255.255.0 broadcast 172.20.20.255"
INTERFACES=(lo eth1 eth0 eth2)
# 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 172.20.20.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 sshd crond)

Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use Iface
172.20.20.0 0.0.0.0 255.255.255.0 U 0 0 0 eth1
172.20.20.0 0.0.0.0 255.255.255.0 U 0 0 0 eth0
172.20.20.0 0.0.0.0 255.255.255.0 U 0 0 0 eth2
0.0.0.0 172.20.20.1 0.0.0.0 UG 0 0 0 eth1

fukawi2 · 2008-06-04 05:36:59

I suspect asymmetric routing perhaps?

Can you run `mtr -a 172.20.20.15 4.2.2.2` and post the o/p?

Last edited by fukawi2 (2008-06-04 05:37:13)

jeffkn · 2008-06-04 05:46:44

Thanks for the response!
Here's the output:

My traceroute [v0.72]
windsor (0.0.0.0) Tue Jun 3 22:44:16 2008
Keys: Help Display mode Restart statistics Order of fields quit
Packets Pings
Host Loss% Snt Last Avg Best Wrst StDev
1. ???
2. ge-4-9-ur01.fremont.ca.sfba.comcast.net 0.0% 47 9.8 10.0 7.0 23.3 3.2
3. pos-0-7-0-0-ar01.sfsutro.ca.sfba.comcast.net 0.0% 47 11.9 13.4 10.9 22.2 2.3
4. COMCAST-IP.edge1.SanJose1.Level3.net 15.2% 47 15.3 16.2 12.5 36.6 5.2
5. xe-10-2-0.edge1.SanJose1.Level3.net 0.0% 47 13.4 18.3 11.9 88.3 13.4
6. vlan79.csw2.SanJose1.Level3.net 0.0% 47 15.9 19.3 12.3 31.8 5.6
7. ge-11-0.core1.SanJose1.Level3.net 0.0% 47 25.6 14.2 11.8 25.6 2.5
8. vnsc-bak.sys.gtei.net 0.0% 46 13.3 14.3 12.0 27.9 3.2

fukawi2 · 2008-06-04 09:07:42

Can you run `mtr -a 172.20.20.10 4.2.2.2` and post the o/p so we can compare?
I assume it works if you ping through eth1 which is your default route?

tomk · 2008-06-04 13:39:40

I'm not familiar with any vbox-specific requirements, but if you look at your routing table, you have created three routes to the 172.20.20.0 subnet. How does your system know which one to use? And your ping example tries to get to an external address through eth2, but that's not going to work, because you have routed all traffic except 172.20.20.0 through eth1.

jeffkn · 2008-06-04 22:03:55

It sounds from Tomks post that it's now confirmed that I don't know what I'm doing... Putting all the nics on separate subnets would not be an issue, i was just being lazy and trying to use the existing dmz with no modifications. What's the best way to configure the extra nics? If I put them all on separate subnets, would I need to specify the other gateways in rc.conf?

Here's the output previously requested:

My traceroute [v0.72]
windsor (0.0.0.0) Wed Jun 4 14:55:30 2008
Keys: Help Display mode Restart statistics Order of fields quit
Packets Pings
Host Loss% Snt Last Avg Best Wrst StDev
1. ???
2. ge-4-9-ur01.fremont.ca.sfba.comc 0.0% 18 9.4 10.4 7.3 19.4 3.4
3. pos-0-7-0-0-ar01.sfsutro.ca.sfba 0.0% 18 12.4 14.5 10.8 24.1 3.5
4. COMCAST-IP.edge1.SanJose1.Level3 0.0% 18 13.5 15.7 13.1 27.7 3.5
5. xe-10-1-0.edge1.SanJose1.Level3. 5.6% 18 14.8 17.6 12.2 40.6 7.6
6. vlan79.csw2.SanJose1.Level3.net 0.0% 18 23.3 21.8 13.3 27.9 4.0
7. ge-11-0.core1.SanJose1.Level3.ne 0.0% 18 14.6 16.2 12.4 30.3 4.7
8. vnsc-bak.sys.gtei.net 0.0% 18 14.8 17.0 12.2 36.0 5.7

Arch Linux

#1 2008-06-04 04:10:54

Multiple nics but no ping

#2 2008-06-04 05:36:59

Re: Multiple nics but no ping

#3 2008-06-04 05:46:44

Re: Multiple nics but no ping

#4 2008-06-04 09:07:42

Re: Multiple nics but no ping

#5 2008-06-04 13:39:40

Re: Multiple nics but no ping

#6 2008-06-04 22:03:55

Re: Multiple nics but no ping

Board footer