This problem for your IP ( 44.60.44.13 ) is again - link http://44.60.44.13/startampr if ip is from tuneled 44 network is not open.
If pinging or open from not tunelled (not 44) network is all ok ping and open your ip, if pinging from tuneled network is not response or ping .
Testing from Germany, Bulgarian and Romania ampr (44) network - from all those places the result is the same.
Yesterday, about 30 minutes after my first post things were fine and everything was normal, but now again the problem is the same. Analogous problem with n1uro.ampr.org [44.88.0.9] .
73, Miro LZ4NY
----- Цитат от lleachii@aol.com, на 02.08.2013 в 22:25 ----- (Please trim inclusions from previous messages) _______________________________________________ Marius,
172.31.255.254 is merely my tunl0 IP address, it's a Private IP in the Class B range, using a /32 (a single host on the network), nothing works using that IP address but ping from my 44LAN.
44.60.44.1 is the IP of my eth1 interface, everything is handled on my device via IP forwarding.
I have my tunnel isolated from my 44LAN and Local/WAN network for testing and troubleshooting purposes. This ensures that I'm in fact routing if a packet moves from one network to another. My eth0 is my public facing LAN - which has a 192.168 IP scheme, IP-in-IP is passed to that network from my Public IP address by my Router. eth1 is my 44LAN with the IP address of 44.60.44.1/24.
my setup script can be seen at http://44.60.44.13/startampr
73,
Lynwood KB3VWG