Re: [44net] Newbie issue

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Well maybe it's better to get things working step by step. First step I want to get to work is ping from Internet. As I do receive routing updates via RIPv2, the communication between the central amprgw and my gateway must work. However, ping and traceroute from Internet does not. Ping and traceroute from Internet must go via Brian's central amprgw, so if RIPv2 works I don't see why ping and traceroute shouldn't. This is what the traceroute looks: traceroute to 44.161.229.126 (44.161.229.126), 64 hops max, 52 byte packets 1 * * * 2 e0.vtt176-1.lux.lu.as51405.net (46.29.176.120) 98.936 ms 25.167 ms 76.600 ms 3 83.243.15.25 (83.243.15.25) 21.690 ms 40.556 ms 60.720 ms 4 llnw.dus.ecix.net (194.146.118.93) 34.630 ms 89.112 ms 33.067 ms 5 tge1-5.fr4.frf.llnw.net (69.28.189.161) 69.808 ms 46.594 ms 55.931 ms 6 tge1-2.fr4.ams.llnw.net (69.28.171.54) 102.495 ms 115.217 ms 94.458 ms 7 tge16-1.fr4.lga.llnw.net (69.28.189.49) 280.854 ms 213.193 ms 299.031 ms 8 tge1-2.fr4.ord.llnw.net (69.28.172.198) 307.245 ms 204.316 ms 249.123 ms 9 tge1-3.fr4.sjc.llnw.net (69.28.172.77) 200.818 ms 202.944 ms 199.952 ms 10 * * * 11 dc-oak-core1--paix-px1-ge.cenic.net (137.164.47.19) 232.588 ms 207.561 ms 205.932 ms 12 dc-tri-core1--oak-core1-10ge-4.cenic.net (137.164.46.43) 204.926 ms 204.194 ms 213.565 ms 13 dc-riv-core1--tri-core1-4.cenic.net (137.164.46.248) 195.708 ms 208.480 ms 209.391 ms 14 dc-sdg-agg1--riv-core1-10ge-2.cenic.net (137.164.47.15) 214.901 ms 215.563 ms 216.029 ms 15 dc-ucsd-1--sdg-agg1.cenic.net (137.164.23.54) 201.269 ms 213.264 ms 202.829 ms 16 nodem-core--mx0-30ge.ucsd.edu (132.239.254.163) 213.142 ms 200.361 ms 214.848 ms 17 ebu3b-6509-nodem-core-interconnect-vl910-bcast-255-131.ucsd.edu (132.239.255.131) 201.741 ms 204.033 ms 202.348 ms 18 amprgw.sysnet.ucsd.edu (169.228.66.251) 204.463 ms 201.769 ms 200.333 ms On the my 44net gateway no iptables rules have been defined: # iptables-save # Generated by iptables-save v1.4.8 on Thu Mar 28 22:59:30 2013 *filter :INPUT ACCEPT [31352:6172307] :FORWARD ACCEPT [0:0] :OUTPUT ACCEPT [27531:4868700] COMMIT # Completed on Thu Mar 28 22:59:30 2013 I'm pinging 44.161.229.126 and 176.9.140.87 from my Laptop at home. On my 44net gateway only the packets to 176.9.140.87 show up in a trace: # tshark -i any not port 22 Running as user "root" and group "root". This could be dangerous. Capturing on Pseudo-device that captures on all interfaces 0.000000 46.29.176.121 -> 176.9.140.87 ICMP Echo (ping) request 0.000023 176.9.140.87 -> 46.29.176.121 ICMP Echo (ping) reply 1.002346 46.29.176.121 -> 176.9.140.87 ICMP Echo (ping) request 1.002365 176.9.140.87 -> 46.29.176.121 ICMP Echo (ping) reply 2.002563 46.29.176.121 -> 176.9.140.87 ICMP Echo (ping) request 2.002593 176.9.140.87 -> 46.29.176.121 ICMP Echo (ping) reply 3.000364 46.29.176.121 -> 176.9.140.87 ICMP Echo (ping) request 3.000390 176.9.140.87 -> 46.29.176.121 ICMP Echo (ping) reply Brian can you see what happens with the ICMP ECHO REQUEST packets from 46.29.176.121 to 44.161.229.126? Regards, Marc On 27/03/2013 23:35, Marc STORCK wrote: