Hi all, I am having a networking problem, and for the life of me I cannot figure it out. The setup is simple: "fortress" machine = firewall/router "lancelot" machine = workstation fortress has 2 ethernet cards: eth0 = dhcp eth1 = 192.168.0.1 (out to Intel 8 port 10/100 hub on port #1) Lancelot has 2 ethernet cards: eth0 = 192.168.0.2 (out to Intel 8 port 10/100 hub on port #2) eth1 = not used (this machine used to be the firewall, but I've switched the machines around.. so this ethernet card is no longer used) The problem is that I cannot get fortress to ping lancelot, and vica versa. I have to ctrl-c the ping and it says 100% packet loss. If I do rcnetwork stop, the respective light goes out on the hub for each machine... so the cables are good, and the hub "sees" them. When I ping each machine, I see the hub lights blinking, but I get 100% packet loss. I'm not running a firewall on either machine, and iptables is installed but not running when I do this.. I'm just trying to get raw connectivity at this point! I've attached all of the information that I can think to include... please let me know if I can provide any more info. Any help is greatly appreciated! Thanks, Steven -- -+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+- Steven Hatfield http://www.knightswood.net Linux User #220336 ICQ: 7314105 Useless Machine Data: 3:17pm up 25 min, 1 user, load average: 0.12, 0.05, 0.04 -+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+- Random Quote: "By the time they had diminished from 50 to 8, the other dwarves began to suspect 'Hungry' ..." -- Gary Larson, "The Far Side"
I seem to remember you having this problem before, and that the problem then was a faulty firewall script. Has it been working since then, and what have you changed? Also, the output from ifconfig on both machines might help regards Anders On Friday 10 August 2001 21:26, Steven Hatfield wrote:
Hi all, I am having a networking problem, and for the life of me I cannot figure it out.
The setup is simple: "fortress" machine = firewall/router "lancelot" machine = workstation
fortress has 2 ethernet cards: eth0 = dhcp eth1 = 192.168.0.1 (out to Intel 8 port 10/100 hub on port #1)
Lancelot has 2 ethernet cards: eth0 = 192.168.0.2 (out to Intel 8 port 10/100 hub on port #2) eth1 = not used (this machine used to be the firewall, but I've switched the machines around.. so this ethernet card is no longer used)
The problem is that I cannot get fortress to ping lancelot, and vica versa. I have to ctrl-c the ping and it says 100% packet loss.
If I do rcnetwork stop, the respective light goes out on the hub for each machine... so the cables are good, and the hub "sees" them. When I ping each machine, I see the hub lights blinking, but I get 100% packet loss.
I'm not running a firewall on either machine, and iptables is installed but not running when I do this.. I'm just trying to get raw connectivity at this point!
I've attached all of the information that I can think to include... please let me know if I can provide any more info. Any help is greatly appreciated!
Thanks, Steven
Well, I figured out what was wrong. The configuration was correct, but the 2 nic cards in fortress were the exact same card. I would boot up one time, and see the lights on the hub and gateway blinking just like they should, where eth0->gateway and eth1->hub. Boot up another time, and eth1->gateway and eth0->hub, without changing the cables! So I took the unused 3com nic out of Lancelot and replaced eth1 in fortress with it.. modded /etc/modules.conf and here I am :-) Just plain weird.. note to self.. do NOT use 2 of the same nic cards in the same machine! O_o Sorry for the post, I wish I would have seen that earlier! -Steven --snip-- -- -+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+- Steven Hatfield http://www.knightswood.net Linux User #220336 ICQ: 7314105 Useless Machine Data: 4:22pm up 11 min, 1 user, load average: 0.05, 0.13, 0.12 -+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+- Random Quote: I've noticed lately that the paranoid fear of computers becoming intelligent and taking over the world has almost entirely disappeared from the common culture. Near as I can tell, this coincides with the release of MS-DOS. -- Larry DeLuca
Steven Hatfield wrote:
Well, I figured out what was wrong. The configuration was correct, but the 2 nic cards in fortress were the exact same card. I would boot up one time, and see the lights on the hub and gateway blinking just like they should, where eth0->gateway and eth1->hub. Boot up another time, and eth1->gateway and eth0->hub, without changing the cables!
So I took the unused 3com nic out of Lancelot and replaced eth1 in fortress with it.. modded /etc/modules.conf and here I am :-)
Just plain weird.. note to self.. do NOT use 2 of the same nic cards in the same machine! O_o
Sorry for the post, I wish I would have seen that earlier! -Steven
--snip--
<Snip> Do not apologize, that is useful information for the database and may well end up saving someone else. Matt
Steven Hatfield wrote:
Well, I figured out what was wrong. The configuration was correct, but
nic cards in fortress were the exact same card. I would boot up one time, and see the lights on the hub and gateway blinking just like they should, where eth0->gateway and eth1->hub. Boot up another time, and eth1->gateway and eth0->hub, without changing the cables!
So I took the unused 3com nic out of Lancelot and replaced eth1 in fortress with it.. modded /etc/modules.conf and here I am :-)
Just plain weird.. note to self.. do NOT use 2 of the same nic cards in
I wonder if there is someway to define what card is what by using the mac
address during it's startup, they are at least suppose to be individual?
That would get around this problem.
scsijon
----- Original Message -----
From: "StarTux"
same machine! O_o
Sorry for the post, I wish I would have seen that earlier! -Steven
--snip--
<Snip>
Do not apologize, that is useful information for the database and may well end up saving someone else.
Matt
-- To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com For additional commands send e-mail to suse-linux-e-help@suse.com Also check the FAQ at http://www.suse.com/support/faq and the archives at http://lists.suse.com
On Friday 10 August 2001 8:25 pm, Steven Hatfield wrote:
Well, I figured out what was wrong. The configuration was correct, but the 2 nic cards in fortress were the exact same card. I would boot up one time, and see the lights on the hub and gateway blinking just like they should, where eth0->gateway and eth1->hub. Boot up another time, and eth1->gateway and eth0->hub, without changing the cables!
So I took the unused 3com nic out of Lancelot and replaced eth1 in fortress with it.. modded /etc/modules.conf and here I am :-)
Just plain weird.. note to self.. do NOT use 2 of the same nic cards in the same machine! O_o
Really? What cards were they, and were they ISA or PCI? I've been using 2x3C905B (3Com PCI 10/100 cards) for a year or so and have never comes across that sort of thing. Most recently, under 7.2, I set the NICs up with Yast2, and they've never complained once. Odd... Gideon. Relevant bit of modules.conf: -------- # # YaST2: Network card # alias eth0 3c59x # # YaST2: Network card # alias eth1 3c59x --------
On Friday 10 August 2001 05:45 pm, Gideon Hallett wrote:
On Friday 10 August 2001 8:25 pm, Steven Hatfield wrote:
Well, I figured out what was wrong. The configuration was correct, but the 2 nic cards in fortress were the exact same card. I would boot up one time, and see the lights on the hub and gateway blinking just like they should, where eth0->gateway and eth1->hub. Boot up another time, and eth1->gateway and eth0->hub, without changing the cables!
So I took the unused 3com nic out of Lancelot and replaced eth1 in fortress with it.. modded /etc/modules.conf and here I am :-)
Just plain weird.. note to self.. do NOT use 2 of the same nic cards in the same machine! O_o
Really? What cards were they, and were they ISA or PCI?
I've been using 2x3C905B (3Com PCI 10/100 cards) for a year or so and have never comes across that sort of thing. Most recently, under 7.2, I set the NICs up with Yast2, and they've never complained once.
Odd...
Gideon.
Relevant bit of modules.conf: -------- # # YaST2: Network card # alias eth0 3c59x
# # YaST2: Network card # alias eth1 3c59x --------
They were both Linksys Etherfast 10/100 PCI ethernet cards. One was revision 4.1 and the other was 5.0 (the only way I could tell them apart!). I replaced the 4.1 with the 3COM 3C905B PCI card, and it seemed to work just fine.. all I did was reboot after adjusting /etc/modules.conf! Pretty wild :) -Steven -- -+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+- Steven Hatfield http://www.knightswood.net Linux User #220336 ICQ: 7314105 Useless Machine Data: 5:15pm up 1:03, 1 user, load average: 0.35, 0.27, 0.13 -+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+- Random Quote: To iterate is human; to recurse, is divine.
On Fri, Aug 10, 2001 at 09:45:58PM +0000, Gideon Hallett wrote:
<snip>
Just plain weird.. note to self.. do NOT use 2 of the same nic cards in the same machine! O_o
Really? What cards were they, and were they ISA or PCI?
I've been using 2x3C905B (3Com PCI 10/100 cards) for a year or so and have never comes across that sort of thing. Most recently, under 7.2, I set the NICs up with Yast2, and they've never complained once.
Mmm.. this can't be the problem, there is no reason on earth why you cannot use two cards of the same make and model. One of my PC's has 2 identical cards in it, and it works a treat as my gateway. The problem is (was) elsewhere I am sure. Cliff
eth0 Link encap:Ethernet HWaddr 00:04:5A:54:33:20 inet addr:64.192.118.153 Bcast:64.192.118.155 Mask:255.255.255.252 inet6 addr: fe80::204:5aff:fe54:3320/10 Scope:Link inet6 addr: fe80::4:5a54:3320/10 Scope:Link UP BROADCAST NOTRAILERS RUNNING MTU:1500 Metric:1 RX packets:107 errors:0 dropped:0 overruns:0 frame:0 TX packets:61 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:100 RX bytes:12186 (11.9 Kb) TX bytes:10528 (10.2 Kb) Interrupt:5 Base address:0xf400
eth1 Link encap:Ethernet HWaddr 00:A0:CC:30:95:BF inet addr:192.168.0.1 Bcast:192.168.0.255 Mask:255.255.255.0 inet6 addr: fe80::2a0:ccff:fe30:95bf/10 Scope:Link inet6 addr: fe80::a0:cc30:95bf/10 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:18 errors:0 dropped:0 overruns:0 frame:0 TX packets:136 errors:34 dropped:0 overruns:0 carrier:48 collisions:0 txqueuelen:100 RX bytes:3200 (3.1 Kb) TX bytes:10210 (9.9 Kb) Interrupt:10 Base address:0xf800
Ouch, Errors:34 carrier:48 This is where the problem maybe.....Check your /var/log/messages after pinging see if it gives more. Its claiming carrier problems. What card is this? Has this ever worked? I have had the exact same problem once after I changed DSL providers and I recieved a new hub, in fact it only worked with rcnetwork restart. To cut the story short it failed in almost the exactly the same way as yours has done with one exception, it was the Internet side card that failed. I fixed it by changing the cable and the card. Maybe its a compatibility problem? Maybe the smplest thing to try and do is swap the internel to hub cable with the cable on eth0, just to be sure. I know you said cables were fine, but just because you get the lights does not mean that those data packets are any good... Also, I remember someone getting the same too and it turned out to be a bad firewall script, are you positive its not running? Keep us updated. Matt
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:32 errors:0 dropped:0 overruns:0 frame:0 TX packets:32 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:2996 (2.9 Kb) TX bytes:2996 (2.9 Kb)
------------------------------------------------------------------------
# # hosts This file describes a number of hostname-to-address # mappings for the TCP/IP subsystem. It is mostly # used at boot time, when no name servers are running. # On small systems, this file can be used instead of a # "named" name server. # Syntax: # # IP-Address Full-Qualified-Hostname Short-Hostname # # special IPv6 addresses
127.0.0.1 localhost 192.168.0.1 fortress.knightswood.net fortress 192.168.0.2 lancelot.knightswood.net lancelot #::1 localhost ipv6-localhost ipv6-loopback #fe00::0 ipv6-localnet #ff00::0 ipv6-mcastprefix #ff02::1 ipv6-allnodes #ff02::2 ipv6-allrouters #ff02::3 ipv6-allhosts
------------------------------------------------------------------------
# # hosts This file describes a number of hostname-to-address # mappings for the TCP/IP subsystem. It is mostly # used at boot time, when no name servers are running. # On small systems, this file can be used instead of a # "named" name server. # Syntax: # # IP-Address Full-Qualified-Hostname Short-Hostname # # special IPv6 addresses #24.6.209.110 ryu
127.0.0.1 localhost 192.168.0.1 fortress.knightswood.net fortress 192.168.0.2 lancelot.knightswood.net lancelot #::1 localhost ipv6-localhost ipv6-loopback #fe00::0 ipv6-localnet #ff00::0 ipv6-mcastprefix #ff02::1 ipv6-allnodes #ff02::2 ipv6-allrouters #ff02::3 ipv6-allhosts
Which box does this belong to? Not sure if it makes a difference, but shouldn't the local IP address be the one after the localhost?
Please, Mr. Webmaster, delete this person's privileges!!!! Nobody should attach anything to the message, and he has attached about 5! Every time I find an attachment, I hunt it down and shoot it. I don't really have time to do this all the time. There just should NEVER be any. Thanx. --doug At 15:26 08/10/2001 -0400, Steven Hatfield wrote:
Hi all, I am having a networking problem, and for the life of me I cannot figure it out.
The setup is simple: "fortress" machine = firewall/router "lancelot" machine = workstation
fortress has 2 ethernet cards: eth0 = dhcp eth1 = 192.168.0.1 (out to Intel 8 port 10/100 hub on port #1)
Lancelot has 2 ethernet cards: eth0 = 192.168.0.2 (out to Intel 8 port 10/100 hub on port #2) eth1 = not used (this machine used to be the firewall, but I've switched the machines around.. so this ethernet card is no longer used)
The problem is that I cannot get fortress to ping lancelot, and vica versa. I have to ctrl-c the ping and it says 100% packet loss.
If I do rcnetwork stop, the respective light goes out on the hub for each machine... so the cables are good, and the hub "sees" them. When I ping each machine, I see the hub lights blinking, but I get 100% packet loss.
I'm not running a firewall on either machine, and iptables is installed but not running when I do this.. I'm just trying to get raw connectivity at this point!
I've attached all of the information that I can think to include... please let me know if I can provide any more info. Any help is greatly appreciated!
Thanks, Steven
-- -+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+- Steven Hatfield http://www.knightswood.net Linux User #220336 ICQ: 7314105 Useless Machine Data: 3:17pm up 25 min, 1 user, load average: 0.12, 0.05, 0.04 -+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-
Random Quote: "By the time they had diminished from 50 to 8, the other dwarves began to suspect 'Hungry' ..." -- Gary Larson, "The Far Side"
-- To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com For additional commands send e-mail to suse-linux-e-help@suse.com
Also check the FAQ at http://www.suse.com/support/faq and the archives at http://lists.suse.com
participants (7)
-
Anders Johansson -
Cliff Sarginson -
Doug McGarrett -
Gideon Hallett -
scsijon -
StarTux -
Steven Hatfield