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

Re: problema connessione wireless




route -n
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use Iface
192.168.0.0     0.0.0.0         255.255.255.0   U     0      0        0 eth2
0.0.0.0         192.168.0.1     0.0.0.0         UG    0      0        0 eth2

ifconfig <interfaccia-wireless>
eth2      Link encap:Ethernet  HWaddr 00:18:DE:6E:0B:D4
         inet addr:192.168.0.2  Bcast:192.168.0.255  Mask:255.255.255.0
         inet6 addr: fe80::218:deff:fe6e:bd4/64 Scope:Link
         UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
         RX packets:8244 errors:1 dropped:1690 overruns:0 frame:0
         TX packets:4763 errors:0 dropped:0 overruns:0 carrier:0
         collisions:0 txqueuelen:1000
         RX bytes:45386572 (43.2 MiB)  TX bytes:2534258 (2.4 MiB)
         Interrupt:193 Base address:0x2000 Memory:d2100000-d2100fff

iwconfig <interfaccia-wireless>
eth2      IEEE 802.11g  ESSID:"Casa_wifi"
         Mode:Managed  Frequency:2.437 GHz  Access Point: 00:18:4D:BB:8C:CA
         Bit Rate:54 Mb/s   Tx-Power:15 dBm
         Retry limit:15   RTS thr:off   Fragment thr:off
         Encryption key:ED0A-3D03-AD   Security mode:restricted
         Power Management:off
         Link Quality=88/100  Signal level=-47 dBm  Noise level=-48 dBm
         Rx invalid nwid:0  Rx invalid crypt:0  Rx invalid frag:0
         Tx excessive retries:0  Invalid misc:1689   Missed beacon:0

cat /etc/resolv.conf
nameserver 192.168.0.1
E poi prova a pingare prima il router
PING 192.168.0.1 (192.168.0.1) 56(84) bytes of data.
64 bytes from 192.168.0.1: icmp_seq=1 ttl=255 time=1.42 ms
64 bytes from 192.168.0.1: icmp_seq=2 ttl=255 time=1.42 ms
64 bytes from 192.168.0.1: icmp_seq=3 ttl=255 time=1.54 ms
64 bytes from 192.168.0.1: icmp_seq=4 ttl=255 time=1.49 ms
64 bytes from 192.168.0.1: icmp_seq=5 ttl=255 time=1.45 ms
64 bytes from 192.168.0.1: icmp_seq=6 ttl=255 time=1.46 ms
64 bytes from 192.168.0.1: icmp_seq=7 ttl=255 time=1.51 ms

--- 192.168.0.1 ping statistics ---
7 packets transmitted, 7 received, 0% packet loss, time 5997ms
rtt min/avg/max/mdev = 1.423/1.474/1.544/0.062 ms

e poi un server che sai che
risponde ai ping (non tutti lo fanno, al momento non so suggerirtene
uno che lo faccia. Per cui se lo conosci bene, altrimenti niente ping
test!).
PING web01.polito.it (130.192.73.1) 56(84) bytes of data.
64 bytes from web01.polito.it (130.192.73.1): icmp_seq=1 ttl=50 time=90.8 ms
64 bytes from web01.polito.it (130.192.73.1): icmp_seq=2 ttl=50 time=90.0 ms
64 bytes from web01.polito.it (130.192.73.1): icmp_seq=3 ttl=50 time=91.5 ms
64 bytes from web01.polito.it (130.192.73.1): icmp_seq=4 ttl=50 time=95.5 ms
64 bytes from web01.polito.it (130.192.73.1): icmp_seq=5 ttl=50 time=80.4 ms
64 bytes from web01.polito.it (130.192.73.1): icmp_seq=6 ttl=50 time=83.9 ms

--- web01.polito.it ping statistics ---
6 packets transmitted, 6 received, 0% packet loss, time 5002ms
rtt min/avg/max/mdev = 80.482/88.717/95.534/5.027 ms

A quel punto potremo provare a vedere se c'è qualcosa che non torna!
Comunque è anche mia esperienza che il DHCP con le schede wireless non
è facilissimo da usare!
Gio.
comunque come ho già scritto adesso funziona. Se da quasti dati riuscite a capire vi ringrazio.
Ciao a tutti
Edoardo



Reply to: