[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: a crazy connectivity issue. unable to ping anything

Michael Habashy wrote:

On 8/15/07, Joachim Fahnenmüller <jfahnenmueller@web.de> wrote:

Hi Michael

On Tue, Aug 14, 2007 at 07:17:46PM -0400, Michael Habashy wrote:

Hi -i got a crazy connectivity issue on my hands.
THis machine was running fine for about a month or so --then i lost
connectivity.
I have no errors to tell me what is going on.
i have switched the built-in nic on the motherboard and the hub ports
--there are other devices that working fine.
I have disabled a lot of services..and trying to get bear vinalla as
possible.
I can not ping to any other host..then just my local interface.
THe last things done were to install courier-imap and courier-ssl.
i was sending an email  to the box..and bam..there is notthing there..

the interfaces initialize just fine..but do not talk to anythhign...i

have

apache and other apps running..and their ports are open..just not

talking to

anyone outside the box...and yes..there is no iptables or ipchains..
I am running out of options..and do not want to rebuild box...so

help!!!!!!

here are the ifconfig and netstat:


eth0      Link encap:Ethernet  HWaddr 00:E0:81:74:60:6A
          inet addr:192.168.2.22  Bcast:192.168.2.255  Mask:

255.255.255.0

          inet6 addr: fe80::2e0:81ff:fe74:606a/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:86 errors:0 dropped:0 overruns:0 frame:0
          TX packets:164 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:6985 (6.8 KiB)  TX bytes:9962 (9.7 KiB)
          Interrupt:50

eth1      Link encap:Ethernet  HWaddr 00:E0:81:74:60:6B
          inet addr:192.168.2.12  Bcast:192.168.2.255  Mask:

255.255.255.0

          UP 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:58 Base address:0x2000

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:139 errors:0 dropped:0 overruns:0 frame:0
          TX packets:139 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:10919 (10.6 KiB)  TX bytes:10919 (10.6 KiB)

sit0      Link encap:IPv6-in-IPv4
          NOARP  MTU:1480  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)

 Kernel IP routing table
Destination     Gateway         Genmask         Flags   MSS Window  irtt
Iface
192.168.2.0 0.0.0.0 255.255.255.0 U 0 0 
0

eth0
192.168.2.0 0.0.0.0 255.255.255.0 U 0 0 
0

eth1
0.0.0.0 192.168.2.1 0.0.0.0 UG 0 0 
0

eth1
0.0.0.0 192.168.2.1 0.0.0.0 UG 0 0 
0

eth0

192.168.2.1 _is_ your gateway, right?
You have routes to the same destinations using different interfaces. To
which
interface (eth0 or eth1) is the gateway connected? What is connected to
the
other one?

If the gw is connected to eth0, try
route del 0.0.0.0 eth1
(or vice versa).

Post your /etc/network/interfaces file.

HTH
--
Joachim Fahnenmüller


--
To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact
listmaster@lists.debian.org





Thanks for getting back to me.
I have 2 nics on the motherboard.
I only have one connected to the network.
eth0 is the only active nic -nothing is connected to eth1 and it is disabled
in network-admin
What i found strange last night is that i have to manually add these 2 lines
to interfaces to make it work:
broadcast 192.168.2.255
network 192.168.2.0

this is very bizarre.
I furhter found lines added to my hosts file like 127.0.0.1 .(that i did not
add -and rem-ed out when i initiatley installed the box.
I will delete the route...but nothing is connected to the adapter.

my interfaces file is:

rider:~# more  /etc/network/interfaces
# This file describes the network interfaces available on your system
# and how to activate them. For more information, see interfaces(5).

# The loopback network interface
auto lo
iface lo inet loopback

# The primary network interface
allow-hotplug eth0
# auto eth0

iface eth0 inet static
address 192.168.2.22
netmask 255.255.255.0
gateway 192.168.2.1
broadcast 192.168.2.255
network 192.168.2.0

auto eth0



I would recommend that you add a stanza for eth1 and assign a different
network address to it. I know you say it is disabled, but I like to be
sure about these things. You definitely should not have it appear in
the routing list with the same parameters as eth0. That seems likely
to cause confusion to something.
Reply to: