You are not logged in.

Pages: 1

#1 2009-07-24 04:21:12

murderbymodem
Member
From: New Jersey
Registered: 2008-07-24
Posts: 41

[SOLVED] Arch machines conflicting with each other? 100% packet loss

Okay, here's my problem: I have a second computer running Arch, and my main rig that I switch between Windows XP and Arch. When my main rig is in Windows, everything is fine. When both machines are in Arch, I can no longer connect to any new IRC networks,however networks I'm already connected to are fine. I can browse the web only getting a connection refused (iirc) error, and when I ping google, I have 100% packet loss. I get connection reset errors when trying to download something from pacman. This occurs on both machines. Once my main computer is shut off or is in Windows, all is fine.

Both computers connect up using dhcpcd, and using the router(192.168.1.1 for their DNS. The DNS in my router is set to OpenDNS. I turned off my main machine, and started tcpdump on the secondary computer. tcpdump started spewing out information very fast, and at a consistent rate. I then turn on my main rig and booted into Arch. tcpdump slowed down, and even came to a halt at times. I'd post tcpdump info but I'm not sure how to make tcpdump save to a file as of yet. I'm looking through the man page as I type this.

I brought this issue up in IRC and everyone seemed pretty baffled. I was asked info about my router (Linksys WRT54G v5) but that just led to router talk and it never really came back to discussing my issue, so I let it go for a bit and went out, and now here I am :P

EDIT: OH! ALMOST FORGOT! I didn't mention this on IRC either.
I have a Netgear switch that splits the connection coming into my room from the router. Linksys WRT54G v5 > Netgear FS105 v2 switch > the 2 machines I'm talking about.

Last edited by murderbymodem (2009-07-25 05:44:56)

Offline

#2 2009-07-24 07:15:04

madeye
Member
From: Denmark
Registered: 2006-07-19
Posts: 331
Website

Re: [SOLVED] Arch machines conflicting with each other? 100% packet loss

Did you check the IP address on both computers to make certain they are different?
You could try to release the IP address on one of them and see if that changes anything.

Maybe it could be IPv6 related? If you don't use IPv6 you can disable the autoloading of the module. Instructions are in the wiki.
http://wiki.archlinux.org/index.php/IPv … the_Module


Let's see if we can't tackle this problem. You know actually there are no problems. There are only challenges. smile

MadEye | Registered Linux user #167944 since 2000-02-28 | Homepage

Offline

#3 2009-07-24 09:44:04

ngoonee
Forum Fellow
From: Between Thailand and Singapore
Registered: 2009-03-17
Posts: 7,355

Re: [SOLVED] Arch machines conflicting with each other? 100% packet loss

Perhaps both of them have the same hostname...? A very elementary error, but I've done it before...

Allan-Volunteer on the (topic being discussed) mailn lists. You never get the people who matters attention on the forums.
jasonwryan-Installing Arch is a measure of your literacy. Maintaining Arch is a measure of your diligence. Contributing to Arch is a measure of your competence.
Griemak-Bleeding edge, not bleeding flat. Edge denotes falls will occur from time to time. Bring your own parachute.

Offline

#4 2009-07-24 09:58:12

Allan
Pacman
From: Brisbane, AU
Registered: 2007-06-09
Posts: 11,385
Website

Re: [SOLVED] Arch machines conflicting with each other? 100% packet loss

ngoonee wrote:

Perhaps both of them have the same hostname...? A very elementary error, but I've done it before...

That was my guess too.

PGP Key: F99FFE0FEAE999BD

Offline

#5 2009-07-24 17:09:58

murderbymodem
Member
From: New Jersey
Registered: 2008-07-24
Posts: 41

Re: [SOLVED] Arch machines conflicting with each other? 100% packet loss

Nope, both have different host names.

I'll check the IPs in a minute.

EDIT: Nope, different IPs. 192.168.107 and 192.168.127.

EDIT2: Disabling IPv6 on both computers didn't worth either. Still 100% packet loss pinging google from either computer once I boot the second machine into Arch and start browsing around in Firefox for a bit. Every once in awile I'll get a "Firefox can't establish a connection to the server at " error.

Last edited by murderbymodem (2009-07-24 17:30:18)

Offline

#6 2009-07-24 20:22:56

R00KIE
Forum Fellow
From: Between a computer and a chair
Registered: 2008-09-14
Posts: 4,734

Re: [SOLVED] Arch machines conflicting with each other? 100% packet loss

Are you sure the IPs just have 3 groups of numbers? Something doesn't look right there.

Didn't know about that one of the hostname, thats one of the things that can slip by unnoticed and cause a big headache.

R00KIE
Tm90aGluZyB0byBzZWUgaGVyZSwgbW92ZSBhbG9uZy4K

Offline

#7 2009-07-24 23:57:06

murderbymodem
Member
From: New Jersey
Registered: 2008-07-24
Posts: 41

Re: [SOLVED] Arch machines conflicting with each other? 100% packet loss

I don't think it's an IP problem, since when the machine I dual boot is in windows, it has the same IP. (192.168.1.127)

Offline

#8 2009-07-25 03:07:17

arkham
Member
From: Stockholm
Registered: 2008-10-26
Posts: 516
Website

Re: [SOLVED] Arch machines conflicting with each other? 100% packet loss

murderbymodem wrote:

tcpdump slowed down, and even came to a halt at times. I'd post tcpdump info but I'm not sure how to make tcpdump save to a file as of yet. I'm looking through the man page as I type this.

tcpdump -w file

"I'm Winston Wolfe. I solve problems."

~ Need moar games? [arch-games] ~ [aurcheck] AUR haz updates? ~

Offline

#9 2009-07-25 03:09:21

murderbymodem
Member
From: New Jersey
Registered: 2008-07-24
Posts: 41

Re: [SOLVED] Arch machines conflicting with each other? 100% packet loss

More info:

Machine running only Arch:
Route

Kernel IP routing table
Destination     Gateway         Genmask         Flags Metric Ref    Use Iface
192.168.1.0     *               255.255.255.0   U     203    0        0 eth0
default         192.168.1.1     0.0.0.0         UG    203    0        0 eth0

ifconfig -a

eth0      Link encap:Ethernet  HWaddr 00:E0:18:E6:27:6F  
          inet addr:192.168.1.107  Bcast:192.168.1.255  Mask:255.255.255.0
          inet6 addr: fe80::2e0:18ff:fee6:276f/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:3788963 errors:0 dropped:0 overruns:0 frame:0
          TX packets:3359467 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000 
          RX bytes:1801256729 (1717.8 Mb)  TX bytes:344293063 (328.3 Mb)
          Interrupt:17 Base address:0x6000 

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:112 errors:0 dropped:0 overruns:0 frame:0
          TX packets:112 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0 
          RX bytes:5980 (5.8 Kb)  TX bytes:5980 (5.8 Kb)

wlan0     Link encap:Ethernet  HWaddr 00:40:05:B3:FA:92  
          BROADCAST MULTICAST  MTU:1500  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000 
          RX bytes:0 (0.0 b)  TX bytes:0 (0.0 b)
          Interrupt:19 Base address:0x9400

/etc/rc.conf

#
# /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="UTC"
USEDIRECTISA="no"
TIMEZONE="America/New_York"
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=(ndiswrapper)

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

# 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 192.168.0.2 netmask 255.255.255.0 broadcast 192.168.0.255"
eth0="dhcp"
INTERFACES=(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.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 hal network netfs crond alsa dbus slim)

Info from the other machine in a sec.

Offline

#10 2009-07-25 03:14:04

murderbymodem
Member
From: New Jersey
Registered: 2008-07-24
Posts: 41

Re: [SOLVED] Arch machines conflicting with each other? 100% packet loss

Dual boot machine:

Route: 

Kernel IP routing table
Destination     Gateway         Genmask         Flags Metric Ref    Use Iface
192.168.1.0     *               255.255.255.0   U     202    0        0 eth0
default         192.168.1.1     0.0.0.0         UG    202    0        0 eth0

ifconfig -a

eth0      Link encap:Ethernet  HWaddr 00:1D:7D:9C:88:A1  
          inet addr:192.168.1.127  Bcast:192.168.1.255  Mask:255.255.255.0
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:1295 errors:0 dropped:0 overruns:0 frame:0
          TX packets:1223 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000 
          RX bytes:730564 (713.4 Kb)  TX bytes:146679 (143.2 Kb)
          Interrupt:29 Base address:0x6000 

lo        Link encap:Local Loopback  
          inet addr:127.0.0.1  Mask:255.0.0.0
          UP LOOPBACK RUNNING  MTU:16436  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0 
          RX bytes:0 (0.0 b)  TX bytes:0 (0.0 b)

/etc/rc.conf

#
# /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="UTC"
SEDIRECTISA="no"
TIMEZONE="America/New_York"
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.
#
OD_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="Eric"

# 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 192.168.0.2 netmask 255.255.255.0 broadcast 192.168.0.255"
eth0="dhcp"
INTERFACES=(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.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 alsa mpd hal slim)

Offline

#11 2009-07-25 03:49:44

murderbymodem
Member
From: New Jersey
Registered: 2008-07-24
Posts: 41

Re: [SOLVED] Arch machines conflicting with each other? 100% packet loss

Well, thanks to Arkham for pointing out that IPv6 wasn't disabled yet on the Arch only machine because I hadn't restarted. :doh:

Seems to be fine now.

Last edited by murderbymodem (2009-07-25 03:50:00)

Offline

#12 2009-07-25 05:24:42

ngoonee
Forum Fellow
From: Between Thailand and Singapore
Registered: 2009-03-17
Posts: 7,355

Re: [SOLVED] Arch machines conflicting with each other? 100% packet loss

IPv6 conflicts on the network? I know its working for you now, but I'm wondering (more as an aside) how it is that having IPv6 enabled on both machines would screw up connectivity. Is it because no IPs are assigned (do current DHCP implementations pass off IPv6 addresses, for example?

Anyway, please mark [solved] by editing OP.

Allan-Volunteer on the (topic being discussed) mailn lists. You never get the people who matters attention on the forums.
jasonwryan-Installing Arch is a measure of your literacy. Maintaining Arch is a measure of your diligence. Contributing to Arch is a measure of your competence.
Griemak-Bleeding edge, not bleeding flat. Edge denotes falls will occur from time to time. Bring your own parachute.

Offline

#13 2009-07-25 05:45:15

murderbymodem
Member
From: New Jersey
Registered: 2008-07-24
Posts: 41

Re: [SOLVED] Arch machines conflicting with each other? 100% packet loss

Not sure. IPV6 has always cause problems for me on my main machine.

Offline

Pages: 1

Board footer

Powered by FluxBB