Newsgroup: it.comp.os.linux.sys
Titolo: Ping non funzionante

Ho una novità.
arp -a
impiega una vita a mostrare le tabelle ed una volta terminata 
l'elaborazione mostra queste 2 righe.
? (192.168.0.254) at <incomplete> on eth0
? (192.168.0.253) at <incomplete> on eth0
.254 è il router
.253 è un serverino interno con fax ed altre cagate.
però non becca i mac address.

 ? (192.168.0.253) at <incomplete> on eth0
Caro alessandro,
se vuoi metterci in grado di darti una mano dovresti inviarci i seguenti
output:
1) dmesg | grep eth
2) lsmod 
3) ifconfig
4) route -n
5) iptables -L
6) cat /var/log/syslog | grep eth | tail -n 20
o in alternativa
cat /var/log/messages | grep eth | tail -n 20


E' solo perche' non riceve le risposte alle richieste arp che ha
inviato. Ci mette tanto perche tenta di risolvere gli ip, se fai
arp -an ci mette... subito.
Fabio

 
Eccoli.
Bisogna fare una precisazione.
In alcuni log viene riportato "no link" o qualcosa di simile.
Be, al momento della generazione dei report effettivamente non era 
collegato il cavo di rete. Ma il risultato non cambia. Anche 
collegandolo, dmesg si accorge del cavo, le lucine della scheda si 
accendono (quando faccio un ping, la lucina dell'attività inizia a 
lavorare) ma non riesco ad ottenere risposte.
########################################################################
[uname -a]
Linux mediacenter 2.6.17.8 #17 SMP PREEMPT Wed Sep 6 05:29:38 CEST 2006 
i686 unknown unknown GNU/Linux
########################################################################
[dmesg | grep eth]
forcedeth.c: Reverse Engineered nForce ethernet driver. Version 0.54.
forcedeth: using HIGHDMA
eth0: forcedeth.c: subsystem: 01043:816a bound to 0000:00:14.0
eth0: no link during initialization.
########################################################################
[lsmod]
Module                  Size  Used by
saa7134_alsa           11488  0
saa7134_dvb            12036  0
mt352                   6532  1 saa7134_dvb
video_buf_dvb           5380  1 saa7134_dvb
nxt200x                12932  1 saa7134_dvb
tda1004x               13700  1 saa7134_dvb
tuner                  49452  0
saa7134               102880  2 saa7134_alsa,saa7134_dvb
ir_kbd_i2c              7312  1 saa7134
psmouse                34312  0
shpchp                 33960  0
forcedeth              24076  0
ohci1394               29872  0
video_buf              20100  4 
saa7134_alsa,saa7134_dvb,video_buf_dvb,saa7134
ir_common              24452  2 saa7134,ir_kbd_i2c
########################################################################
[ifconfig]
eth0      Link encap:Ethernet  HWaddr 00:17:31:A4:79:DE
           inet addr:192.168.0.25  Bcast:192.168.0.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:16 Base address:0xa000
lo        Link encap:Local Loopback
           inet addr:127.0.0.1  Mask:255.0.0.0
           UP LOOPBACK RUNNING  MTU:16436  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)
########################################################################
[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 eth0
127.0.0.0       0.0.0.0         255.0.0.0       U     0      0        0 lo
0.0.0.0         192.168.0.254   0.0.0.0         UG    1      0        0 eth0
########################################################################
[iptables -L]
Chain INPUT (policy ACCEPT)
target     prot opt source               destination
Chain FORWARD (policy ACCEPT)
target     prot opt source               destination
Chain OUTPUT (policy ACCEPT)
target     prot opt source               destination
########################################################################
[SYSLOG]
Aug 17 06:40:22 mediacenter kernel: eth0: no link during initialization.
Aug 17 08:37:47 mediacenter kernel: eth0: no link during initialization.
Aug 17 08:41:11 mediacenter kernel: hda-intel: Invalid position buffer, 
using LPIB read method instead.
Aug 17 09:10:29 mediacenter kernel: eth0: no link during initialization.
Aug 17 09:20:55 mediacenter kernel: hda-intel: Invalid position buffer, 
using LPIB read method instead.
Aug 17 14:19:02 mediacenter kernel: eth0: no link during initialization.
Aug 17 14:23:20 mediacenter kernel: eth0: no link during initialization.
Aug 17 15:01:58 mediacenter kernel: eth0: no link during initialization.
Aug 17 15:23:23 mediacenter kernel: eth0: no link during initialization.
Aug 17 15:38:08 mediacenter kernel: eth0: no link during initialization.
Aug 17 15:48:26 mediacenter kernel: eth0: no link during initialization.
Aug 17 15:49:35 mediacenter kernel: hda-intel: Invalid position buffer, 
using LPIB read method instead.
Aug 17 16:31:24 mediacenter kernel: eth0: no link during initialization.
Sep  3 04:16:00 mediacenter kernel: eth0: no link during initialization.
Sep  3 04:26:29 mediacenter kernel: eth0: no link during initialization.
Sep  3 08:32:07 mediacenter kernel: eth0: no link during initialization.
Sep  5 07:09:46 mediacenter kernel: eth0: no link during initialization.
Sep  6 03:38:07 mediacenter kernel: eth0: no link during initialization.
Sep  6 05:25:16 mediacenter kernel: eth0: no link during initialization.
Sep  6 05:31:08 mediacenter kernel: eth0: no link during initialization.
########################################################################
[MESSAGES]
Sep  5 07:09:46 mediacenter logger: /etc/rc.d/rc.inet1:  /sbin/ifconfig 
eth0 192.168.0.25 broadcast 192.168.0.255 netmask 255.255.255.0
Sep  5 07:09:48 mediacenter kernel: eth0: link up.
Sep  5 21:37:10 mediacenter kernel: eth0: link down.
Sep  5 21:37:12 mediacenter kernel: eth0: link up.
Sep  6 03:20:35 mediacenter logger: /etc/rc.d/rc.inet1:  /sbin/ifconfig 
eth0 down
Sep  6 03:38:07 mediacenter kernel: forcedeth.c: Reverse Engineered 
nForce ethernet driver. Version 0.54.
Sep  6 03:38:07 mediacenter kernel: forcedeth: using HIGHDMA
Sep  6 03:38:07 mediacenter kernel: eth0: forcedeth.c: subsystem: 
01043:816a bound to 0000:00:14.0
Sep  6 03:38:07 mediacenter logger: /etc/rc.d/rc.inet1:  /sbin/ifconfig 
eth0 192.168.0.25 broadcast 192.168.0.255 netmask 255.255.255.0
Sep  6 03:38:10 mediacenter kernel: eth0: link up.
Sep  6 03:38:37 mediacenter logger: /etc/rc.d/rc.inet1:  /sbin/ifconfig 
eth0 down
Sep  6 05:25:15 mediacenter kernel: forcedeth.c: Reverse Engineered 
nForce ethernet driver. Version 0.54.
Sep  6 05:25:15 mediacenter kernel: forcedeth: using HIGHDMA
Sep  6 05:25:15 mediacenter kernel: eth0: forcedeth.c: subsystem: 
01043:816a bound to 0000:00:14.0
Sep  6 05:25:16 mediacenter logger: /etc/rc.d/rc.inet1:  /sbin/ifconfig 
eth0 192.168.0.25 broadcast 192.168.0.255 netmask 255.255.255.0
Sep  6 05:30:05 mediacenter logger: /etc/rc.d/rc.inet1:  /sbin/ifconfig 
eth0 down
Sep  6 05:31:08 mediacenter kernel: forcedeth.c: Reverse Engineered 
nForce ethernet driver. Version 0.54.
Sep  6 05:31:08 mediacenter kernel: forcedeth: using HIGHDMA
Sep  6 05:31:08 mediacenter kernel: eth0: forcedeth.c: subsystem: 
01043:816a bound to 0000:00:14.0
Sep  6 05:31:08 mediacenter logger: /etc/rc.d/rc.inet1:  /sbin/ifconfig 
eth0 192.168.0.25 broadcast 192.168.0.255 netmask 255.255.255.0

 [MESSAGES]

-- 
questo articolo e` stato inviato via web dal servizio gratuito 
http://www.newsland.it/news
 segnala gli abusi ad 
ab...@newsland.it

 Scusa, forse ti era già stato detto, ethtool che dice?
azz....
proprio ora che ho staccato il computer.
Comunque, a memoria ethtool dice che è tutto ok.
autonegoziazione fatta ok, cavo collegato, etc etc
apparentemente, tutto funziona..eppure non si pinga nulla.
Guarda i sintomi sono proprio quelli di un classico firewall..
Scheda perfettamente ok ma non si pinga nulla.
Il problema è che non ho alcun firewall.
La scheda è isolata dal mondo. non escono nemmeno le arp (ho provato a 
vedere tramite sniffer)