[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[riminilug-general] Problema di networking con Linux Fedora Core 4 e kernel 2.6.12
Salve a tutti, ho questo problema:
Nell'upgradare da Fedora Core 3 a Fedora Core 4, passando dal kernel
2.6.10 al kernel 2.6.12,
non riesco piu' ad utilizzare
il mio server che si collega a internet come Nat, oltre che non riesco
a
vedere direttamente altri client (come il mio portatile) senza passare
dichiaratamente in binding attraverso la scheda di rete con cui e'
collegata
direttamente la local network (eth2).
Per spiegarmi un po' meglio, faccio uno schemino (scusatemi la mia
mediocrita'
in "ascii-art" ):
Server "barton"
_______
| |
________ |=======| __________
| | | :: |-- eth0 ---------|modem eth |----...>
INTERNET
| | | |(192.168.1.18) |__________|
|________| | |-- eth1 (unused)
/:::::::::\ | |(192.168.1.19)
|_______|-- eth2-----\ (192.168.1.16)
__|__
| hub |
|_____|
| | |
_______________________/ | \_______ ... etc.
/ \_____
| eth0
eth0 ____|___
____|___ | | Client 2
| | Client 1 | | "athlon"
| | "gabolaptop" |________| 192.168.1.11
|________| 192.168.1.74 /:::::::::\
/:::::::::\
Ora, come si puo' osservare dallo schema, il server "barton" ha
3 Nic, e' dhcp server, e quello che fa la connessione ad internet
tramite
il modem collegato alla eth0.
Il dhcp sembra che funzioni correttamente, in quanto a "gabolaptop"
viene assegnato
sempre l'IP giusto (74), in quanto dal dhcp server e' stato assegnato
un'ip fisso
collegato al MAC.
Questo e' il dhcp.conf su barton :
=== /etc/dhcp.conf =============================
subnet 192.168.1.0 netmask 255.255.255.0 {
range 192.168.1.200 192.168.1.240;
option subnet-mask 255.255.255.0;
option domain-name "virgilio.it";
option routers 192.168.1.16;
option domain-name-servers 62.211.69.150,212.48.4.15;
default-lease-time 3600;
max-lease-time 7200;
}
ddns-update-style ad-hoc;
host gabolaptop {
# filename "/tftpboot/vmlinuz.xterm";
hardware ethernet 00:50:ba:7f:a0:0e;
fixed-address 192.168.1.74;
option host-name "gabolaptop";
}
===============================================
Il problema e' che, non solo "gabolaptop" non riesce a raggiungere il
Web, ma non
riesce neanche a 'pingare' correttamente "barton", ma neanche viceversa.
Mi spiego meglio.
Se da "barton" do "ping gabolaptop", ottengo
PING gabolaptop (192.168.1.74) 56(84) bytes of data.
>From 192.168.1.18 icmp_seq=1 Destination Host Unreachable
>From 192.168.1.18 icmp_seq=2 Destination Host Unreachable
>From 192.168.1.18 icmp_seq=3 Destination Host Unreachable
.....
--- gabolaptop ping statistics ---
5 packets transmitted, 0 received, +3 errors, 100% packet loss, time
4000ms
, pipe 4
Se invece specifico l'interfaccia collegata alla rete interna (nel mio
caso eth2)
dando il comando "ping gabolaptop -I eth2", allora pinga correttamente.
PING gabolaptop (192.168.1.74) from 192.168.1.16 eth2: 56(84) bytes of
data.
64 bytes from gabolaptop (192.168.1.74): icmp_seq=0 ttl=64 time=0.453 ms
64 bytes from gabolaptop (192.168.1.74): icmp_seq=1 ttl=64 time=0.445 ms
--- gabolaptop ping statistics ---
2 packets transmitted, 2 received, 0% packet loss, time 1000ms
rtt min/avg/max/mdev = 0.445/0.449/0.453/0.004 ms, pipe 2
Per contro, se da "gabolaptop" faccio un "ping barton" ottengo un
risultato negativo ugualmente
PING barton (192.168.1.16) 56(84) bytes of data.
(nessuna risposta)
Ho provato a dare diverse impostazioni nel netfilter, ma senza
risultato.
Se qualcuno riesce a darmi una dritta, intanto lascio un po' di
impostazioni del sistema "barton"
Da Barton:
========= output del comando "ifconfig" =======
eth0 Link encap:Ethernet HWaddr 00:05:1C:0B:62:DE
inet addr:192.168.1.18 Bcast:192.168.1.255
Mask:255.255.255.0
inet6 addr: fe80::205:1cff:fe0b:62de/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:1393 errors:0 dropped:0 overruns:0 frame:0
TX packets:1324 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:282873 (276.2 KiB) TX bytes:138897 (135.6 KiB)
Interrupt:5 Base address:0x9c00
eth1 Link encap:Ethernet HWaddr 00:0E:A6:4C:5D:F4
inet addr:192.168.1.19 Bcast:192.168.1.255
Mask:255.255.255.0
inet6 addr: fe80::20e:a6ff:fe4c:5df4/64 Scope:Link
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:1000
RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)
Interrupt:5 Memory:df000000-0
eth2 Link encap:Ethernet HWaddr 00:0E:A6:46:98:35
inet addr:192.168.1.16 Bcast:192.168.1.255
Mask:255.255.255.0
inet6 addr: fe80::20e:a6ff:fe46:9835/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:2073 errors:0 dropped:0 overruns:0 frame:0
TX packets:37 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:160711 (156.9 KiB) TX bytes:2920 (2.8 KiB)
Interrupt:9 Base address:0xe000
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:806 errors:0 dropped:0 overruns:0 frame:0
TX packets:806 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:66013 (64.4 KiB) TX bytes:66013 (64.4 KiB)
ppp0 Link encap:Point-to-Point Protocol
inet addr:82.57.177.138 P-t-P:192.168.100.1
Mask:255.255.255.255
UP POINTOPOINT RUNNING NOARP MULTICAST MTU:1492 Metric:1
RX packets:1299 errors:0 dropped:0 overruns:0 frame:0
TX packets:1066 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:3
RX bytes:247935 (242.1 KiB) TX bytes:98937 (96.6 KiB)
=================================================================================
========= output del comando "route" =======
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use
Iface
192.168.100.1 * 255.255.255.255 UH 0 0 0
ppp0
192.168.1.0 * 255.255.255.0 U 0 0 0
eth0
192.168.1.0 * 255.255.255.0 U 0 0 0
eth1
192.168.1.0 * 255.255.255.0 U 0 0 0
eth2
169.254.0.0 * 255.255.0.0 U 0 0 0
eth2
default 192.168.100.1 0.0.0.0 UG 0 0 0
ppp0
========= output del comando "arp -v" =======
Address HWtype HWaddress Flags Mask
Iface
gabolaptop ether 00:50:BA:7F:A0:0E C
eth2
gabolaptop (incomplete)
eth0
Entries: 2 Skipped: 0 Found: 2
========= output del comando "iptables -L" =======
Chain FORWARD (policy DROP)
target prot opt source destination
Chain INPUT (policy ACCEPT)
target prot opt source destination
DROP tcp -- anywhere anywhere tcp
dpts:0:1023
DROP udp -- anywhere anywhere udp
dpts:0:1023
DROP tcp -- anywhere anywhere tcp
flags:SYN,RST,ACK/SYN
DROP icmp -- anywhere anywhere icmp
echo-request
ACCEPT tcp -- isiway anywhere state NEW
tcp dpt:ssh
Chain OUTPUT (policy ACCEPT)
target prot opt source destination
Chain RH-Firewall-1-INPUT (0 references)
target prot opt source destination
ACCEPT all -- anywhere anywhere
ACCEPT icmp -- anywhere anywhere icmp any
ACCEPT ipv6-crypt-- anywhere anywhere
ACCEPT ipv6-auth-- anywhere anywhere
ACCEPT udp -- anywhere 224.0.0.251 udp
dpt:5353
ACCEPT udp -- anywhere anywhere udp dpt:ipp
ACCEPT all -- anywhere anywhere state
RELATED,ESTABLISHED
ACCEPT tcp -- anywhere anywhere state NEW
tcp dpt:ssh
ACCEPT tcp -- anywhere anywhere state NEW
tcp dpt:http
ACCEPT tcp -- anywhere anywhere state NEW
tcp dpt:ftp
REJECT all -- anywhere anywhere reject-with
icmp-host-prohibited
========= output del comando "cat /proc/sys/net/ipv4/ip_forward" ======
1
E' il routing table che scazza ? o cosa ?
Vi puo' servire vedere qualche altro output o qualche altra
configurazione?
Grazie anticipatamente per ogni suggerimento?