From: Marc Shapiro <mshapiro_42@yahoo.com>
To: linux-admin@vger.kernel.org
Subject: Re: Local network hosts unreachable
Date: Mon, 2 May 2005 15:53:37 -0700 (PDT) [thread overview]
Message-ID: <20050502225337.39012.qmail@web54108.mail.yahoo.com> (raw)
> --- gerardo juarez-mondragon
> <gjuarezmondragon@metacrawler.com> wrote:
>
> > Just wondering,
> >
> > Did your setup ever work?
Yes. Everything worked fine until about a week ago.
> If yes, does your 4
> port switch have one of these buttons to select
> Uplink on/off? If yes, is it in the correct
> position?
Nothing is using the uplink/5th port, so it really
does not matter which position it is in.
Any help in gettin this to work will be greatly
appreciated. I am currently reduced to reading e-mail
and web-browsing on a Windows laptop with a 'g' key
that sometimes works and a broken hinge that could
fall off at any time.
Here is what information I have gathered, or been
asked for by others attempting to help me solve this
problem:
I am able to 'ping localhost' from either box.
I am unable to ping my gateway box from the desktop,
or ping the desktop from the gateway.
When I attempt a ping from either box to the other,
both sets of lights on the switch blink, suggesting
that data is going through the switch, both NICs and
both cables. The lights on the switch correctly
show 100Mb/sec full-duplex connections from both
machines. I have already changed the NIC on the
gateway machine in an attempt to solve this. The
desktop machine has a built in NIC and is only a few
months old.
Everything worked fine until about a week ago.
----------------------------------
On the desktop box (xander -- 192.168.0.3):
/etc/network/interfaces:
# /etc/network/interfaces -- configuration file for
ifup(8), ifdown(8)
# The loopback interface
auto lo
iface lo inet loopback
# The first network card - this entry was created
during the Debian installation
# (network, broadcast and gateway are optional)
auto eth0
iface eth0 inet static
address 192.168.0.3
netmask 255.255.255.0
network 192.168.0.0
broadcast 192.168.0.255
--------------------
output of ifconfig:
eth0 Link encap:Ethernet HWaddr
00:11:5B:1B:8F:1F
inet addr:192.168.0.3 Bcast:192.168.0.255
Mask:255.255.255.0
inet6 addr: fe80::211:5bff:fe1b:8f1f/64
Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500
Metric:1
RX packets:0 errors:0 dropped:0 overruns:0
frame:0
TX packets:223 errors:0 dropped:0
overruns:0
carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 b) TX bytes:9534 (9.3
KiB)
Interrupt:19 Base address:0xe400
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:193 errors:0 dropped:0
overruns:0
frame:0
TX packets:193 errors:0 dropped:0
overruns:0
carrier:0
collisions:0 txqueuelen:0
RX bytes:72672 (70.9 KiB) TX bytes:72672
(70.9 KiB)
---------------------
/etc/hosts:
127.0.0.1 local.net xander localhost
loopback
192.168.0.1mareschal
192.168.0.2alexander
192.168.0.3xander
# The following lines are desirable for IPv6 capable
hosts
# (added automatically by netbase upgrade)
::1 ip6-localhost ip6-loopback
fe00::0 ip6-localnet
ff00::0 ip6-mcastprefix
ff02::1 ip6-allnodes
ff02::2 ip6-allrouters
ff02::3 ip6-allhosts
--------------------
/etc/networks:
localnet 192.168.0.0
--------------------
output of mii-tool:
eth0: negotiated 100baseTx-FD, link ok
--------------------------------------------
On the gateway box (mareschal -- 192.168.0.1):
/etc/network/interfaces:
# Used by ifup(8) and ifdown(8). See the
interfaces(5)
manpage or
# /usr/share/doc/netbase/examples for more
information.
#
iface lo inet loopback
iface ppp0 inet ppp
iface eth0 inet static
address 192.168.0.1
netmask 225.225.225.0
broadcast 192.168.0.225
network 192.168.0.0
up route add default ppp0
down route del ppp0
-----------------
output of ifconfig:
eth0 Link encap:Ethernet HWaddr
00:12:17:54:0D:EF
inet addr:192.168.0.1 Bcast:192.168.0.255
Mask:255.255.255.0
UP BROADCAST RUNNING MULTICAST MTU:1500
Metric:1
RX packets:0 errors:0 dropped:0 overruns:0
frame:0
TX packets:48 errors:0 dropped:0
overruns:0
carrier:0
collisions:0 txqueuelen:100
RX bytes:0 (0.0 b) TX bytes:2016 (1.9
KiB)
Interrupt:11 Base address:0x2400
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:67 errors:0 dropped:0
overruns:0
frame:0
TX packets:67 errors:0 dropped:0
overruns:0
carrier:0
collisions:0 txqueuelen:0
RX bytes:7028 (6.8 KiB) TX bytes:7028
(6.8
KiB)
----------------------
/etc/hosts:
127.0.0.1 local.net mareschal
localhost loopback
92.168.0.1mareschal
192.168.0.2alexander
192.168.0.3xander
# The following lines are desirable for IPv6 capable
hosts
# (added automatically by netbase upgrade)
::1 ip6-localhost ip6-loopback
fe00::0 ip6-localnet
ff00::0 ip6-mcastprefix
ff02::1 ip6-allnodes
ff02::2 ip6-allrouters
ff02::3 ip6-allhosts
----------------------
/etc/networks:
localnet 127.0.0.0
-----------------------
output of mii-tool:
eth0: negotiated 100baseTx-FD flow-control, link ok
------------------------------------------------
Marc
next reply other threads:[~2005-05-02 22:53 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-02 22:53 Marc Shapiro [this message]
2005-05-03 1:00 ` Local network hosts unreachable chuck gelm
2005-05-03 6:35 ` Andrew Kelly
2005-05-03 16:05 ` Marc Shapiro
2005-05-03 20:40 ` Glynn Clements
-- strict thread matches above, loose matches on Subject: below --
2005-05-04 3:17 gerardo juarez-mondragon
2005-05-02 21:42 gerardo juarez-mondragon
2005-04-27 20:09 Marc Shapiro
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20050502225337.39012.qmail@web54108.mail.yahoo.com \
--to=mshapiro_42@yahoo.com \
--cc=linux-admin@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).