Problems with NAT
Hello, Debian Users!
I have odd problem with NAT.
My desktop PC has permanent access to the internet and static IP adress.
I went to the internet from laptop via wi-fi (simple wi-fi cards in laptop and
desktop computers). Everything was fine. But last week something broke.
My desktop:
/etc/network/interfaces
auto lo
iface lo inet loopback
address 127.0.0.1
netmask 255.0.0.0
# The primary network interface
allow-hotplug eth1
allow-hotplug wlan0
iface eth1 inet static
address 10.22.13.19
netmask 255.255.255.0
broadcast 10.22.13.255
gateway 10.22.13.1
# dns-* options are implemented by the resolvconf package, if installed
#dns-nameservers 195.189.80.66
dns-nameservers 10.10.0.2
domain gnu
iface wlan0 inet static
address 10.22.99.1
netmask 255.255.255.0
wireless-mode ad-hoc
wireless-channel 1
wireless-rate auto
wireless-essid first
/etc/dhcp3/dhcpd
default-lease-time 600;
max-lease-time 7200;
subnet 10.22.99.0 netmask 255.255.255.0 {
range 10.22.99.2 10.22.99.2;
option domain-name-servers 10.10.0.2;
option domain-name "gnu";
option routers 10.22.99.1;
option broadcast-address 10.22.99.255;
default-lease-time 600;
max-lease-time 7200;
}
IP forward enabled:
cat /proc/sys/net/ipv4/ip_forward
1
NAT:
iptables -t nat -A POSTROUTING -s 10.22.99.0/24 -o eth1 -j MASQUERADE
My laptop:
I use network-manager for this connection. I also trying
use /etc/network/interfaces, but result the same.
SSH laptop <--> desktop work, but provider's local network and internet
doesn't work on laptop.
ping google.com
ping: unknown host google.com
ping 10.10.0.2
PING 10.10.0.2 (10.10.0.2) 56(84) bytes of data.
^C
--- 10.10.0.2 ping statistics ---
89 packets transmitted, 0 received, 100% packet loss, time 88015ms
Also i can ping neighboring IP (For example 10.22.13.20).
tcpdump shows strange results.
When i ping google.com on laptop
tcpdump on desktop pc show:
tcpdump: verbose output suppressed, use -v or -vv for full protocol decode
listening on wlan0, link-type EN10MB (Ethernet), capture size 96 bytes
02:11:57.439537 IP 10.22.99.2.42378 > lbox.local.domain: 42125+ A? google.com.
(28)
02:11:57.443082 IP lbox.local.domain > 10.22.99.2.42378: 42125 3/4/1 A
yx-in-f100.google.com,[|domain]
02:12:02.443047 arp who-has 10.22.99.2 tell 10.22.99.1
02:12:02.509911 arp who-has 10.22.99.1 tell 10.22.99.2
02:12:02.509935 arp reply 10.22.99.1 is-at 00:18:f3:95:e2:0e (oui Unknown)
02:12:02.510935 IP 10.22.99.2.42378 > lbox.local.domain: 42125+ A? google.com.
(28)
02:12:02.514138 IP lbox.local.domain > 10.22.99.2.42378: 42125 3/4/1 A
qb-in-f100.google.com,[|domain]
02:12:07.445705 IP 10.22.99.2.39232 > lbox.local.domain: 54184+ A?
google.com.gnu. (32)
02:12:07.448773 IP lbox.local.domain > 10.22.99.2.39232: 54184 NXDomain* 0/1/0
(107)
02:12:07.511042 arp who-has 10.22.99.2 tell 10.22.99.1
02:12:07.512570 arp reply 10.22.99.2 is-at 00:19:7e:c8:51:b3 (oui Unknown)
tcpdump on laptop show:
tcpdump: verbose output suppressed, use -v or -vv for full protocol decode
listening on wlan0, link-type EN10MB (Ethernet), capture size 96 bytes
02:11:34.588196 IP 10.22.99.2.34800 > 10.10.0.2.domain: 14288+ A? google.com.
(28)
02:11:34.589244 IP 10.22.99.2.59108 > 10.10.0.2.domain: 62690+ PTR?
2.0.10.10.in-addr.arpa. (40)
02:11:34.591819 vlan 0, p 5, IP 10.10.0.2.domain > 10.22.99.2.34800: 14288
3/4/1 A 74.125.45.100,[|domain]
02:11:34.592598 vlan 0, p 5, IP 10.10.0.2.domain > 10.22.99.2.59108: 62690*
1/1/1 (94)
02:11:39.585643 arp who-has 10.22.99.1 tell 10.22.99.2
02:11:39.586609 arp reply 10.22.99.1 is-at 00:18:f3:95:e2:0e (oui Unknown)
02:11:39.589675 IP 10.22.99.2.34800 > 10.10.0.2.domain: 14288+ A? google.com.
(28)
02:11:39.589703 IP 10.22.99.2.59108 > 10.10.0.2.domain: 62690+ PTR?
2.0.10.10.in-addr.arpa. (40)
02:11:39.593712 vlan 0, p 5, IP 10.10.0.2.domain > 10.22.99.2.34800: 14288
3/4/1 A 72.14.205.100,[|domain]
02:11:39.594026 vlan 0, p 5, IP 10.10.0.2.domain > 10.22.99.2.59108: 62690*
1/1/1 (94)
02:11:44.591333 arp who-has 10.22.99.2 tell 10.22.99.1
02:11:44.591367 arp reply 10.22.99.2 is-at 00:19:7e:c8:51:b3 (oui Unknown)
02:11:44.593942 IP 10.22.99.2.60554 > 10.10.0.2.domain: 14338+ PTR?
2.99.22.10.in-addr.arpa. (41)
02:11:44.594077 IP 10.22.99.2.45630 > 10.10.0.2.domain: 31749+ A?
google.com.gnu. (32)
02:11:44.598038 vlan 0, p 5, IP 10.10.0.2.domain > 10.22.99.2.60554: 14338
NXDomain* 0/1/0 (104)
02:11:44.598355 vlan 0, p 5, IP 10.10.0.2.domain > 10.22.99.2.45630: 31749
NXDomain* 0/1/0 (107)
02:11:49.597561 IP 10.22.99.2.45630 > 10.10.0.2.domain: 31749+ A?
google.com.gnu. (32)
02:11:49.597659 IP 10.22.99.2.60554 > 10.10.0.2.domain: 14338+ PTR?
2.99.22.10.in-addr.arpa. (41)
02:11:49.601062 vlan 0, p 5, IP 10.10.0.2.domain > 10.22.99.2.45630: 31749
NXDomain* 0/1/0 (107)
02:11:49.603170 vlan 0, p 5, IP 10.10.0.2.domain > 10.22.99.2.60554: 14338
NXDomain* 0/1/0 (104)
02:11:54.601986 IP 10.22.99.2.56986 > 10.10.0.2.domain: 3541+ PTR?
100.45.125.74.in-addr.arpa. (44)
02:11:54.607125 vlan 0, p 5, IP 10.10.0.2.domain > 10.22.99.2.56986: 3541
1/4/1 (167)
02:11:59.605434 IP 10.22.99.2.56986 > 10.10.0.2.domain: 3541+ PTR?
100.45.125.74.in-addr.arpa. (44)
02:11:59.608508 vlan 0, p 5, IP 10.10.0.2.domain > 10.22.99.2.56986: 3541
1/4/1 (167)
02:12:04.609772 IP 10.22.99.2.37703 > 10.10.0.2.domain: 22071+ PTR?
1.99.22.10.in-addr.arpa. (41)
02:12:04.612831 vlan 0, p 5, IP 10.10.0.2.domain > 10.22.99.2.37703: 22071
NXDomain* 0/1/0 (104)
02:12:07.001796 IP 10.22.99.2.55775 > 10.10.0.2.domain: 6135+ A? google.com.
(28)
02:12:07.005903 vlan 0, p 5, IP 10.10.0.2.domain > 10.22.99.2.55775: 6135
3/4/1 A 72.14.205.100,[|domain]
02:12:09.613307 IP 10.22.99.2.37703 > 10.10.0.2.domain: 22071+ PTR?
1.99.22.10.in-addr.arpa. (41)
02:12:09.617453 vlan 0, p 5, IP 10.10.0.2.domain > 10.22.99.2.37703: 22071
NXDomain* 0/1/0 (104)
02:12:12.005279 IP 10.22.99.2.55775 > 10.10.0.2.domain: 6135+ A? google.com.
(28)
02:12:12.008939 vlan 0, p 5, IP 10.10.0.2.domain > 10.22.99.2.55775: 6135
3/4/1 A 74.125.45.100,[|domain]
02:12:14.613209 arp who-has 10.22.99.1 tell 10.22.99.2
02:12:14.614140 arp reply 10.22.99.1 is-at 00:18:f3:95:e2:0e (oui Unknown)
But i don't use VLAN.
--
Александр Владимирович Екимов
Reply to: