[Pluto-help] ...la rete WAN non funziona ancora ...

Fabio Pifferini 101097 a ticino.com
Sab 24 Feb 2001 18:38:29 CET 

Sto' ancora litigando con il mio Server Linux (RH 7) !!!

Il mio Linux non vuol saperne di connettersi al ISP via WAN.

Io ho installato 2 schede di rete sul PC, una è collegata alla mia rete LAN ed
è
configurata con
IP         192.168.1.0
Netmask    255.255.255.0

L'altra è collegata alla WAN mediante sistema WIreless
I dati che mi hanno fornito l'ISP sono:

IP             XXX.YYY.ZZZ.83
Subnet Mask    255.255.255.0
Gateway        XXX.YYY.ZZZ.1
DNS primario   XXX.YYY.166.166


questo è il risultato di IFCONFIG:

eth0      Link encap:Ethernet  HWaddr 00:20:78:18:77:47
          inet addr:XXX.YYY.ZZZ.83  Bcast:XXX.YYY.ZZZ.255
Mask:255.255.255.0
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:115 errors:0 dropped:0 overruns:0 frame:0
          TX packets:12 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:100
          Interrupt:11 Base address:0x2040

eth1      Link encap:Ethernet  HWaddr 00:50:8B:C7:E8:0D
          inet addr:192.168.1.10  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:10 Base address:0x1c00

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:18 errors:0 dropped:0 overruns:0 frame:0
          TX packets:18 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0


se faccio NETSTAT -NR ottengo:

Kernel IP routing table
Destination     Gateway         Genmask         Flags   MSS Window  irtt
Iface
192.168.1.0     0.0.0.0         255.255.255.0   U         0 0          0
eth1
XXX.YYY.ZZZ.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
0.0.0.0         XXX.YYY.ZZZ.1   0.0.0.0         UG        0 0          0
eth0


il comando IPCHAINS -L mi ritorna:

Chain input (policy ACCEPT):
Chain forward (policy ACCEPT):
Chain output (policy ACCEPT):


e questi sono i risultati dei ping:

PING 192.168.1.10 (192.168.1.10) from 192.168.1.10 : 56(84) bytes of
data.
64 bytes from 192.168.1.10: icmp_seq=0 ttl=255 time=56 usec
64 bytes from 192.168.1.10: icmp_seq=1 ttl=255 time=54 usec
64 bytes from 192.168.1.10: icmp_seq=2 ttl=255 time=25 usec
64 bytes from 192.168.1.10: icmp_seq=3 ttl=255 time=20 usec
64 bytes from 192.168.1.10: icmp_seq=4 ttl=255 time=27 usec
64 bytes from 192.168.1.10: icmp_seq=5 ttl=255 time=23 usec
64 bytes from 192.168.1.10: icmp_seq=6 ttl=255 time=23 usec
64 bytes from 192.168.1.10: icmp_seq=7 ttl=255 time=27 usec
64 bytes from 192.168.1.10: icmp_seq=8 ttl=255 time=24 usec
64 bytes from 192.168.1.10: icmp_seq=9 ttl=255 time=26 usec
64 bytes from 192.168.1.10: icmp_seq=10 ttl=255 time=22 usec
64 bytes from 192.168.1.10: icmp_seq=11 ttl=255 time=25 usec
64 bytes from 192.168.1.10: icmp_seq=12 ttl=255 time=24 usec
64 bytes from 192.168.1.10: icmp_seq=13 ttl=255 time=24 usec

--- 192.168.1.10 ping statistics ---
14 packets transmitted, 14 packets received, 0% packet loss
round-trip min/avg/max/mdev = 0.020/0.028/0.056/0.012 ms


PING XXX.YYY.ZZZ.83 (XXX.YYY.ZZZ.83) from XXX.YYY.ZZZ.83 : 56(84) bytes
of data.
64 bytes from XXX.YYY.ZZZ.83: icmp_seq=0 ttl=255 time=58 usec
64 bytes from XXX.YYY.ZZZ.83: icmp_seq=1 ttl=255 time=37 usec
64 bytes from XXX.YYY.ZZZ.83: icmp_seq=2 ttl=255 time=24 usec
64 bytes from XXX.YYY.ZZZ.83: icmp_seq=3 ttl=255 time=24 usec
64 bytes from XXX.YYY.ZZZ.83: icmp_seq=4 ttl=255 time=25 usec
64 bytes from XXX.YYY.ZZZ.83: icmp_seq=5 ttl=255 time=24 usec
64 bytes from XXX.YYY.ZZZ.83: icmp_seq=6 ttl=255 time=25 usec
64 bytes from XXX.YYY.ZZZ.83: icmp_seq=7 ttl=255 time=24 usec
64 bytes from XXX.YYY.ZZZ.83: icmp_seq=8 ttl=255 time=25 usec
64 bytes from XXX.YYY.ZZZ.83: icmp_seq=9 ttl=255 time=23 usec
64 bytes from XXX.YYY.ZZZ.83: icmp_seq=10 ttl=255 time=24 usec
64 bytes from XXX.YYY.ZZZ.83: icmp_seq=11 ttl=255 time=25 usec
64 bytes from XXX.YYY.ZZZ.83: icmp_seq=12 ttl=255 time=23 usec
64 bytes from XXX.YYY.ZZZ.83: icmp_seq=13 ttl=255 time=24 usec
64 bytes from XXX.YYY.ZZZ.83: icmp_seq=14 ttl=255 time=24 usec

--- XXX.YYY.ZZZ.83 ping statistics ---
15 packets transmitted, 15 packets received, 0% packet loss
round-trip min/avg/max/mdev = 0.023/0.027/0.058/0.009 ms



PING XXX.YYY.ZZZ.1 (XXX.YYY.ZZZ.1) from XXX.YYY.ZZZ.83 : 56(84) bytes of
data.
>From XXX.YYY.ZZZ.83: Destination Host Unreachable
>From XXX.YYY.ZZZ.83: Destination Host Unreachable
>From XXX.YYY.ZZZ.83: Destination Host Unreachable
>From XXX.YYY.ZZZ.83: Destination Host Unreachable
>From XXX.YYY.ZZZ.83: Destination Host Unreachable
>From XXX.YYY.ZZZ.83: Destination Host Unreachable
>From XXX.YYY.ZZZ.83: Destination Host Unreachable
>From XXX.YYY.ZZZ.83: Destination Host Unreachable
>From XXX.YYY.ZZZ.83: Destination Host Unreachable
>From XXX.YYY.ZZZ.83: Destination Host Unreachable

--- XXX.YYY.ZZZ.1 ping statistics ---
14 packets transmitted, 0 packets received, +10 errors, 100% packet loss



...e il risultato di un TRACEROUTE XXX.YYY.ZZZ.1

 1  XXX.YYY.ZZZ.83 (XXX.YYY.ZZZ.83)  2998.861 ms !H  2999.855 ms !H 2999.966 ms
!H


....attualmente il sistema Linux è attivo e collegato alle reti, ma se faccio
un PING dall'esterno sul XXX.YYY.ZZZ.83, questo non risponde.

Gli stessi dati, immessi in un PC con Windows 2000, funzionano (posso navigare
e il PC è visibile da internet....)


Grazie per l'aiuto.

Fabio

More information about the pluto-help mailing list