Ciao a tutti.. premetto che sono nuovissimo di linux, e in effetti lo stò praticamente testando.
Ho quindi scaricato la versione cd di Knoppix 5.1.1
Riavvio il mio winzozz xp, dò i 2-3 comandi al bios e avvio knoppix da cd.
Ho visto subito che non connetteva ad internet... quindi mi sono informato in giro.. quindi ho trovato che dovevo controllare con i comandi a shell ifconfig e simili se le connessioni erano configurate.. ho provato un pò di tutto, ma continuo a non potermi connettere, anche se effettivamente pingando ottengo risposte...
Ecco gli output che ho ricevuto con le varie prove:
Come faccio?? Voglio usare linuxxxxxx!! xDcodice:MESSAGGI FORNITi lavorando sulla root shell _____________________________________ root@Knoppix:~# ifconfig eth0 Link encap:Ethernet HWaddr 00:13:D4: inet addr:192.168.0.2 Bcast:192.168. UP BROADCAST RUNNING MULTICAST MTU:6 RX packets:373696 errors:0 dropped:0 TX packets:1051 errors:0 dropped:0 ov collisions:0 txqueuelen:1000 RX bytes:511542375 (487.8 MiB) TX by Interrupt:20 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 Metri RX packets:1722 errors:0 dropped:0 ov TX packets:1722 errors:0 dropped:0 ov collisions:0 txqueuelen:0 RX bytes:145035 (141.6 KiB) TX bytes _____________________________________ root@Knoppix:~# ifconfig -a eth0 Link encap:Ethernet HWaddr 00:13:D4:0F:68:F8 inet addr:192.168.0.2 Bcast:192.168.0.255 Mask:255.255.255.0 UP BROADCAST RUNNING MULTICAST MTU:64 Metric:1 RX packets:548808 errors:0 dropped:0 overruns:223 frame:5808 TX packets:1479 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:751287793 (716.4 MiB) TX bytes:94652 (92.4 KiB) Interrupt:20 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:2881 errors:0 dropped:0 overruns:0 frame:0 TX packets:2881 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:242623 (236.9 KiB) TX bytes:242623 (236.9 KiB) _____________________________________ root@Knoppix:~# ifconfig eth0 192.168.0.2 root@Knoppix:~# route add default gw 192.168.0.2 SIOCADDRT: Il file esiste root@Knoppix:~# ping 192.168.0.2 PING 192.168.0.2 (192.168.0.2) 56(84) bytes of data. 64 bytes from 192.168.0.2: icmp_seq=1 ttl=64 time=0.159 ms 64 bytes from 192.168.0.2: icmp_seq=2 ttl=64 time=0.087 ms 64 bytes from 192.168.0.2: icmp_seq=3 ttl=64 time=0.083 ms 64 bytes from 192.168.0.2: icmp_seq=4 ttl=64 time=0.075 ms 64 bytes from 192.168.0.2: icmp_seq=5 ttl=64 time=0.079 ms 64 bytes from 192.168.0.2: icmp_seq=6 ttl=64 time=0.079 ms 64 bytes from 192.168.0.2: icmp_seq=7 ttl=64 time=0.086 ms 64 bytes from 192.168.0.2: icmp_seq=8 ttl=64 time=0.093 ms 64 bytes from 192.168.0.2: icmp_seq=9 ttl=64 time=0.089 ms 64 bytes from 192.168.0.2: icmp_seq=10 ttl=64 time=0.089 ms 64 bytes from 192.168.0.2: icmp_seq=11 ttl=64 time=0.089 ms 64 bytes from 192.168.0.2: icmp_seq=12 ttl=64 time=0.090 ms _____________________________________ root@Knoppix:~# ifconfig eth0 192.168.0.1 root@Knoppix:~# route add default gw 192.168.0.1 root@Knoppix:~# ping 192.168.0.1 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=64 time=0.578 ms 64 bytes from 192.168.0.1: icmp_seq=2 ttl=64 time=0.095 ms 64 bytes from 192.168.0.1: icmp_seq=3 ttl=64 time=0.093 ms 64 bytes from 192.168.0.1: icmp_seq=4 ttl=64 time=0.137 ms 64 bytes from 192.168.0.1: icmp_seq=5 ttl=64 time=0.106 ms _____________________________________ Andando su KNOPPIX: Programs and configurations specific to KNOPPIX --> Network/Internet --> ADSL/PPPOE configuration --> Interface eth0 has MTU of 64 -- should be 1500. You may have serious connection problems. Timeout waiting for PADO packets Interface eth0 has MTU of 64 -- should be 1500. You may have serious connection problems. Timeout waiting for PADO packets E alla fine --> Mi spiace ho controllato 1 interfaccia/e, ma il Concentratore d'Accesso del tuo provider non ha risposto. Per favore controlla la rete e i cavi del modem. Un'altra ragione per il fallimento del controllo potrebbe anche essere un'altra istanza di pppoe in esecuzione, che controlla il modem.
Sarei estremamente grato a chiunque possa darmi qualche dritta!!
Ciaoooo!