27 Mar
2013
27 Mar
'13
3:40 p.m.
# tshark -i eth0 not port 22
Running as user "root" and group "root". This could be dangerous.
Capturing on eth0
3.659640 76.114.216.250 -> 169.228.66.251 IP Fragmented IP protocol
(proto=IPIP 0x04, off=512, ID=0000)
4.670065 76.114.216.250 -> 169.228.66.251 IP
Fragmented IP protocol
(proto=IPIP 0x04, off=512, ID=0000)
5.675693 76.114.216.250 -> 169.228.66.251 IP
Fragmented IP protocol
(proto=IPIP 0x04, off=512, ID=0000)
6.683756 76.114.216.250 -> 169.228.66.251 IP
Fragmented IP protocol
(proto=IPIP 0x04, off=512, ID=0000)
This traces are correct Marc, they are IPIP encapsulated frames (protocol
0x04) as it should be.
Surfing from my office network to
http://44.60.44.10/tools/ping/php-ping.php works fine.
Here you use the public internet, so all traffic goes via 44.0.0.1 and is
sent to the needed tunnel.
Surfing to http://44.161.229.126 gives a timeout on my
browser and not a
single tcp packet towards port 80 on my gateway.
You mean that when surfing to your gw from the office?
If all is set up correctly, you should get incoming packets proto 4 from
169.228.66.251 to your public IP (I assume 76.114.216.250).
Check that your firewall settings allow incoming IP proto 4 on your
interface.
Marius, YO2LOJ