Re: NETWERK-PRBLEME !!!

Article View: ch.comp.os.linux

Article #22382

#22382

From: Julius Longauer
Date: Mon, 17 May 1999 00:00

62 lines
2942 bytes

Marco Cerqui schrieb:
> 
> [...]
>
> /sbin/ifconfig
> 
> dummy0    Link encap:Ethernet  HWaddr 00:00:00:00:00:00
>           inet addr:192.168.1.20  Bcast:192.168.1.255
> Mask:255.255.255.255
>           UP BROADCAST RUNNING NOARP  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:0
> 
> eth0      Link encap:Ethernet  HWaddr 00:60:97:9E:64:5F
>           inet addr:192.168.1.20  Bcast:192.168.1.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:0 errors:0 dropped:0 overruns:0 carrier:0
>           collisions:0 txqueuelen:100
>           Interrupt:11 Base address:0xd000
> 
> lo        Link encap:Local Loopback
>           inet addr:127.0.0.1  Mask:255.0.0.0
>           UP LOOPBACK RUNNING  MTU:3924  Metric:1
>           RX packets:24 errors:0 dropped:0 overruns:0 frame:0
>           TX packets:24 errors:0 dropped:0 overruns:0 carrier:0
>           collisions:0 txqueuelen:0
> 
> netstat -rn
> 
> Kernel IP routing table
> Destination     Gateway         Genmask         Flags   MSS Window  irtt
> Iface
> 192.168.1.20    0.0.0.0         255.255.255.255 UH        0 0          0
> dummy0
> 192.168.1.0     0.0.0.0         255.255.255.0   U         0 0          0
> eth0
> 127.0.0.0       0.0.0.0         255.0.0.0       U         0 0          0
> lo
> 
>> [...]

Ich nehme mal an, dass diese Werte von der Maschine 192.168.1.10
stammen.
Kann es sein, dass alle an 192.168.1.20 gerichteten Pakete in dummy0
landen?
Versuch mal dummy0 abzuschalten: ifconfig dummy0 down.

Zusatzfragen:

1) Geht 'ping localhost' auf beiden Maschinen?
2) Geht 'ping 192.168.1.10' auf 192.168.1.10 und
   'ping 192.168.1.20' auf 192.168.1.20?

Julius




Julius

Technical Details

Message-ID: <373FD30D.B576F16@balcab.ch>

Path: arc1-ca.pugleaf.net!unknown!not-for-mail

References: <373CAC10.35682586@datacomm.ch> <7hjtk0$hg1$1@vulcan.alphanet.ch> <373EA579.89FAE6B0@datacomm.ch>

Show Full Headers

Complete Article Headers

X-Google-Language: ENGLISH,ASCII-7-bit
X-Google-Thread: f4b73,785ffa5dabb9a0e1
X-Google-Attributes: gidf4b73,public
X-Google-Thread: 10acab,785ffa5dabb9a0e1
X-Google-Attributes: gid10acab,public
X-Google-Thread: f55df,785ffa5dabb9a0e1
X-Google-Attributes: gidf55df,public
From: Julius Longauer <Julius.Longauer@balcab.ch>
Subject: Re: NETWERK-PRBLEME !!!
Date: 1999/05/17
Message-ID: <373FD30D.B576F16@balcab.ch>
X-Deja-AN: 478750167
Content-Transfer-Encoding: 7bit
References: <373CAC10.35682586@datacomm.ch> <7hjtk0$hg1$1@vulcan.alphanet.ch> <373EA579.89FAE6B0@datacomm.ch>
Content-Type: text/plain; charset=us-ascii
X-Complaints-To: news@ip-plus.net
X-Trace: pollux.ip-plus.net 926929760 19661 193.5.216.70 (17 May 1999 08:29:20 GMT)
Organization: Swisscom IP+ (post doesn't reflect views of Swisscom)
Mime-Version: 1.0
NNTP-Posting-Date: 17 May 1999 08:29:20 GMT
Newsgroups: ch.comp.os.linux,de.comp.os.linux.networking,de.comp.os.unix.linux.misc

Reply to Parent Message