Post #61,463
11/6/02 5:40:35 PM
|
Re: Wierd Debian Networking problem
[link|http://www.linuxgazette.com/issue65/tag/12.html|http://www.linuxgaze...sue65/tag/12.html]
Post output of ifconfig -a, please.
Peter
[link|http://www.debian.org|Shill For Hire]
[link|http://www.kuro5hin.org|There is no K5 Cabal]
[link|http://guildenstern.dyndns.org|Blog]
|
Post #61,587
11/7/02 9:43:29 AM
|
ifconfig -a output:
Here ya go! \r\n eth0 Link encap:Ethernet HWaddr 00:80:C8:EC:0C:A4 \r\n UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 \r\n RX packets:399023 errors:0 dropped:0 overruns:0 frame:0 \r\n TX packets:308045 errors:0 dropped:0 overruns:0 carrier:0 \r\n collisions:6 txqueuelen:100 \r\n RX bytes:467950913 (446.2 MiB) TX bytes:76631874 (73.0 MiB) \r\n Interrupt:11 Base address:0x240 \r\n \r\neth1 Link encap:Ethernet HWaddr 00:50:BA:2B:57:1B \r\n inet addr:192.168.0.1 Bcast:192.168.0.255 Mask:255.255.255.0 \r\n UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 \r\n RX packets:307634 errors:0 dropped:0 overruns:0 frame:0 \r\n TX packets:398189 errors:135 dropped:0 overruns:0 carrier:4 \r\n collisions:3571 txqueuelen:100 \r\n RX bytes:0 (0.0 b) TX bytes:0 (0.0 b) \r\n Interrupt:15 Base address:0x4000 \r\n \r\nlo Link encap:Local Loopback \r\n LOOPBACK MTU:3924 Metric:1 \r\n RX packets:0 errors:0 dropped:0 overruns:0 frame:0 \r\n TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 \r\n collisions:0 txqueuelen:0 \r\n RX bytes:0 (0.0 b) TX bytes:0 (0.0 b) \r\n \r\nppp0 Link encap:Point-to-Point Protocol \r\n inet addr:65.94.178.182 P-t-P:64.230.254.252 Mask:255.255.255.255 \r\n UP POINTOPOINT RUNNING NOARP MULTICAST MTU:1492 Metric:1 \r\n RX packets:399013 errors:0 dropped:0 overruns:0 frame:0 \r\n TX packets:308043 errors:0 dropped:0 overruns:0 carrier:0 \r\n collisions:0 txqueuelen:10 \r\n RX bytes:530824637 (506.2 MiB) TX bytes:83650892 (79.7 MiB) \r\n \r\n Do you think the patient is going to live, doctor?;) --\r\n-------------------------------------------------------------------\r\n* Jack Troughton jake at consultron.ca *\r\n* [link|http://consultron.ca|http://consultron.ca] [link|irc://irc.ecomstation.ca|irc://irc.ecomstation.ca] *\r\n* Laval Qu\ufffdbec Canada [link|news://news.consultron.ca|news://news.consultron.ca] *\r\n-------------------------------------------------------------------
|
Post #61,599
11/7/02 10:20:20 AM
|
eth1 is having collision issues and eth0 is not addressed
will work for cash and other incentives [link|http://home.tampabay.rr.com/boxley/resume/Resume.html|skill set]
"Money for jobs? No first you get the job, then you get the money" Raimondo
|
Post #61,601
11/7/02 10:23:33 AM
|
Re: eth1 is having collision issues and eth0 is not addresse
Yes. The hub in this office was the cheapest piece of shit they could buy... these guys are pals and don't have much money. Eth0 is not addressed because it's being used as a conduit for a DSL connection using PPPoE. That's the ppp0 interface you see... --\r\n-------------------------------------------------------------------\r\n* Jack Troughton jake at consultron.ca *\r\n* [link|http://consultron.ca|http://consultron.ca] [link|irc://irc.ecomstation.ca|irc://irc.ecomstation.ca] *\r\n* Laval Qu\ufffdbec Canada [link|news://news.consultron.ca|news://news.consultron.ca] *\r\n-------------------------------------------------------------------
|
Post #61,603
11/7/02 10:25:36 AM
|
Re: eth1 is having collision issues and eth0 is not addresse
Again, this sounds like an interaction of your driver and the hub in regards to linking - probably related to 10/100 capability. Define everything to run at either 10 or 100 but not "auto".
-drl
|
Post #61,609
11/7/02 10:34:06 AM
|
also swap the cable and see if it makes a difference
will work for cash and other incentives [link|http://home.tampabay.rr.com/boxley/resume/Resume.html|skill set]
"Money for jobs? No first you get the job, then you get the money" Raimondo
|
Post #61,614
11/7/02 10:46:44 AM
|
This is using the mii-diag program, I take it?
--\r\n-------------------------------------------------------------------\r\n* Jack Troughton jake at consultron.ca *\r\n* [link|http://consultron.ca|http://consultron.ca] [link|irc://irc.ecomstation.ca|irc://irc.ecomstation.ca] *\r\n* Laval Qu\ufffdbec Canada [link|news://news.consultron.ca|news://news.consultron.ca] *\r\n-------------------------------------------------------------------
|
Post #61,616
11/7/02 10:51:38 AM
|
Re: This is using the mii-diag program, I take it?
Uh, no - this is using the "I've seen every fucked up thing imaginable" intuition generation process.
-drl
|
Post #61,626
11/7/02 11:21:41 AM
|
:)
Yeah... I was just wondering if you happened to know if that was the right tool. I'm going to have to dl and compile it if I want to use it, so I want to make sure that it's the one I need.
--\n-------------------------------------------------------------------\n* Jack Troughton jake at consultron.ca *\n* [link|http://consultron.ca|http://consultron.ca] [link|irc://irc.ecomstation.ca|irc://irc.ecomstation.ca] *\n* Laval Qu\ufffdbec Canada [link|news://news.consultron.ca|news://news.consultron.ca] *\n-------------------------------------------------------------------
|
Post #61,806
11/8/02 3:45:15 AM
|
Re: ifconfig -a output:
jake123 wrote: lo Link encap:Local Loopback \n LOOPBACK MTU:3924 Metric:1 \n RX packets:0 errors:0 dropped:0 overruns:0 frame:0 \n TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 \n collisions:0 txqueuelen:0 \n RX bytes:0 (0.0 b) TX bytes:0 (0.0 b) You'll notice the complete and utter lack of any IP address in there. That's your problem. You know, a line like "inet addr:127.0.0.1 Mask:255.0.0.0". So, time to fix yr. loopback network. And make sure /etc/hosts has "127.0.0.1 localhost" in it. Rick Moen rick@linuxmafia.com
If you lived here, you'd be $HOME already.
|
Post #61,857
11/8/02 10:58:09 AM
|
Yikes
I can't believe that one slipped by me.
I've fixed it in /etc/network/interfaces.
Thanks!
--\n-------------------------------------------------------------------\n* Jack Troughton jake at consultron.ca *\n* [link|http://consultron.ca|http://consultron.ca] [link|irc://irc.ecomstation.ca|irc://irc.ecomstation.ca] *\n* Laval Qu\ufffdbec Canada [link|news://news.consultron.ca|news://news.consultron.ca] *\n-------------------------------------------------------------------
|
Post #61,918
11/8/02 6:11:20 PM
|
Re: Yikes
You're welcome.
In case I was too cryptic, that was the cause of your "neighbour table overflow" errors. It wasn't a driver bug, a hardware error, hub or switch negotiation, RIP malfunctions, frame collisions, or cabling problems. Yes, it was an overflowing ARP table, but that was in turn just a result of the underlying cause: /dev/lo being invalid.
Rick Moen
rick@linuxmafia.com
If you lived here, you'd be $HOME already.
|
Post #62,006
11/9/02 11:31:04 PM
|
Well, time will tell
as in all things:). It's set up properly now... we'll see if it happens again or not.
--\r\n-------------------------------------------------------------------\r\n* Jack Troughton jake at consultron.ca *\r\n* [link|http://consultron.ca|http://consultron.ca] [link|irc://irc.ecomstation.ca|irc://irc.ecomstation.ca] *\r\n* Laval Qu\ufffdbec Canada [link|news://news.consultron.ca|news://news.consultron.ca] *\r\n-------------------------------------------------------------------
|
Post #61,933
11/8/02 8:42:45 PM
|
Re: Yikes
How did it happen? This must be a Debian thing. I've never seen a single IP machine with a misconfigured loopback address.
Good eyes to Rick for spotting that.
-drl
|
Post #61,937
11/8/02 9:18:29 PM
|
Debian thing?
Doubt that.
I mean, I REALLY doubt that.
Debian has the best QA in the Linux business.
More like a slip of the fingers whilst editing the file.
Peter
[link|http://www.debian.org|Shill For Hire]
[link|http://www.kuro5hin.org|There is no K5 Cabal]
[link|http://guildenstern.dyndns.org|Blog]
|
Post #61,940
11/8/02 9:23:09 PM
|
Slip of fingers?
lo is automatically configured when you install IP networking. Why did it get the wrong address? I can't see any scenario other than deliberately setting lo=0.0.0.0, which I'm sure Jack would not have done.
-drl
|
Post #61,941
11/8/02 9:44:27 PM
|
Re: Slip of fingers?
All it would take, in emacs, would be, on the wrong line:
CTRL-SPACE
down-arrow
CTRL-W
and poof! It's gone.
I can execute the above keystrokes in well under a second. It's easily done.
Peter
[link|http://www.debian.org|Shill For Hire]
[link|http://www.kuro5hin.org|There is no K5 Cabal]
[link|http://guildenstern.dyndns.org|Blog]
|
Post #61,947
11/9/02 12:36:59 AM
|
Re: Yikes
deSitter wrote:
Good eyes to Rick for spotting that.
Thanks. Truth to tell, it had to percolate through my brain for a while. That is, the original problem description with the "neighbour table overflow" message rang a distant bell when Jack posted it, but I couldn't remember what it was supposed to remind me of. Much later, he posted that /sbin/ifconfig output, and my unconscious tapped me on the shoulder, saying "Hello. That's the loopback misconfiguration problem I was trying to remind you about, earlier."
I've encountered the problem before, but not recently.
Rick Moen
rick@linuxmafia.com
If you lived here, you'd be $HOME already.
|
Post #61,961
11/9/02 6:09:12 AM
|
lo (and bug, incidentally)
I saw the problem and recognized, it, but kept losing my posts here from a w3m session. I'll try to track this down further. \r\n\r\n I'm not sure what the cause of the unconfigured lo was, but I've seen this show up from time to time, I don't believe the ifupdown package configures /etc/network/interfaces in all instances. If any other Debian types know where this configuration is initated from normally (as opposed to manually) please share. --\r\nKarsten M. Self [link|mailto:kmself@ix.netcom.com|kmself@ix.netcom.com]\r\n[link|http://kmself.home.netcom.com/|http://kmself.home.netcom.com/]\r\n
What part of "gestalt" don't you understand?\r\n
[link|http://twiki.iwethey.org/twiki/bin/view/Main/|TWikIWETHEY] -- an experiment in collective intelligence. Stupidity. Whatever.\r\n
\r\n
Keep software free. Oppose the CBDTPA. Kill S.2048 dead.\r\n[link|http://www.eff.org/alerts/20020322_eff_cbdtpa_alert.html|http://www.eff.org/alerts/20020322_eff_cbdtpa_alert.html]\r\n
|
Post #62,007
11/9/02 11:39:07 PM
|
Re: lo (and bug, incidentally)
Yes... there's no way I would have disabled loopback... and being a dedicated ViM user, I know that I didn't kill that in interfaces. The thing I was going yikes about was that I never noticed that loopback didn't have an address defined in the output of ifconfig... I can't believe that I looked over that output so many times without noticing that. Forest -> Trees, I guess.
--\r\n-------------------------------------------------------------------\r\n* Jack Troughton jake at consultron.ca *\r\n* [link|http://consultron.ca|http://consultron.ca] [link|irc://irc.ecomstation.ca|irc://irc.ecomstation.ca] *\r\n* Laval Qu\ufffdbec Canada [link|news://news.consultron.ca|news://news.consultron.ca] *\r\n-------------------------------------------------------------------
|
Post #62,019
11/10/02 1:57:14 AM
|
Re: lo (and bug, incidentally)
Jack wrote:
The thing I was going yikes about was that I never noticed that loopback didn't have an address defined in the output of ifconfig... I can't believe that I looked over that output so many times without noticing that. Forest -> Trees, I guess.
It's easy to miss. I'm pretty much conditioned to look for it. ;-)
Rick Moen
rick@linuxmafia.com
If you lived here, you'd be $HOME already.
|
