> On 7/09/2016, at 4:07 pm, Kevin Whelan <
kwhel...@gmail.com> wrote:
>
> is this supposed to work or is it our firewall
If you're using the N4L firewall service, it's probably that.
Below are two examples. The first is from a school where the N4L (Cisco) box acts as a firewall. The second is from a school where the N4L (Cisco) box acts as a router only (ie they use an N4L connection, but with their own firewall).
Is the problem you're experiencing manifesting itself in a similar fashion to the first example?
Pete
ladmin@fpl-rpi17:~$ traceroute -n 8.8.8.8
traceroute to 8.8.8.8 (8.8.8.8), 30 hops max, 60 byte packets
1 10.250.232.1 1.036 ms 0.824 ms 0.729 ms
2 * * *
3 * * *
4 * * *
5 * * *
6 * * *
7 * * *
8 * * *
9 * * *
10 * * *
11 * * *
12 * * *
13 * * *
14 * * *
15 * * *
16 * * *
17 * * *
18 * * *
19 * * *
20 * * *
21 * * *
22 * * *
23 * * *
24 * * *
25 * * *
26 * * *
27 * * *
28 * * *
29 * * *
30 * * *
ladmin@fpl-rpi24:~$ traceroute -n 8.8.8.8
traceroute to 8.8.8.8 (8.8.8.8), 30 hops max, 60 byte packets
1 10.1.50.254 0.792 ms 1.186 ms 1.247 ms
2 122.56.63.122 3.697 ms 3.705 ms 3.870 ms
3 122.56.78.208 12.355 ms 12.558 ms 12.472 ms
4 122.56.99.250 12.861 ms 12.776 ms 12.695 ms
5 122.56.99.253 12.242 ms 12.161 ms 12.336 ms
6 * * *
7 122.56.116.5 22.151 ms 20.278 ms 20.295 ms
8 122.56.119.53 19.411 ms 210.55.202.213 19.344 ms 20.029 ms
9 202.50.232.110 43.035 ms 202.50.232.10 43.396 ms 202.50.232.110 43.010 ms
10 202.50.232.246 42.982 ms 44.463 ms 44.067 ms
11 202.50.237.198 45.202 ms 44.294 ms 51.429 ms
12 216.239.41.31 45.179 ms 216.239.41.51 44.867 ms 216.239.41.31 44.615 ms
13 216.239.41.1 42.809 ms 209.85.244.15 43.767 ms 216.239.40.255 42.898 ms
14 8.8.8.8 44.541 ms 44.789 ms 44.438 ms