Superhub FTP Problem

Mike UK · 22 Jul 2012 at 11:47

Could someone using a superhub tell me if f6.sensr.net is ping able? I can ping it on another connection but not through the superhub.

NZB · 22 Jul 2012 at 11:53

I can ping it fine using a superhub, quite high at 169ms. I have it in modem mode though, not router mode.

Mike UK · 22 Jul 2012 at 11:55

Probably should have specified that it needs to be done when the superhub is used in Router mode.

Thanks though

NZB · 22 Jul 2012 at 11:58

Just switched to router mode and same deal, pings fine. All settings are default on it.

Mike UK · 22 Jul 2012 at 12:14

Annoyingly I get this

ping f6.sensr.net
Pinging f6.sensr.net [50.116.0.73] with 32 bytes of data:
Request timed out.
Request timed out.
Request timed out.
Request timed out.

Are you running R36 with the firewall on?

NZB · 22 Jul 2012 at 12:35

Mike UK said:
Are you running R36 with the firewall on?

Yeah mate.

KIA · 22 Jul 2012 at 12:39

Mike UK said:
Could someone using a superhub tell me if f6.sensr.net is ping able? I can ping it on another connection but not through the superhub.

Post a traceroute to the IP address in question.

Mike UK · 22 Jul 2012 at 12:50

Just done a bit of testing it looks like its blocked unless the Superhub firewall is on low.

Would be nice if it gave more info than high medium or low.

KIA · 22 Jul 2012 at 12:54

Why would it block outbound traffic?

Post a traceroute...

Mike UK · 22 Jul 2012 at 13:27

KIA said:
Why would it block outbound traffic?

Post a traceroute...

Unfortunatley with the host not being pingable it offers little of interest.

ping f6.sensr.net

Pinging f6.sensr.net [50.116.0.73] with 32 bytes of data:
Request timed out.
Request timed out.
Request timed out.
Request timed out.

Ping statistics for 50.116.0.73:
Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),

tracert f6.sensr.net

Tracing route to f6.sensr.net [74.207.247.217]
over a maximum of 30 hops:

1 * * * Request timed out.
2 * * * Request timed out.
3 * * * Request timed out.
4 * * * Request timed out.
5 * * * Request timed out.
6 * * * Request timed out.
7 * * * Request timed out.
8 * * * Request timed out.
9 * * * Request timed out.
10 * * * Request timed out.
11 * * * Request timed out.
12 * * * Request timed out.
13 * * * Request timed out.
14 * * * Request timed out.
15 * * * Request timed out.
16 * * * Request timed out.
17 * * * Request timed out.
18 * * * Request timed out.
19 * * * Request timed out.
20 * * * Request timed out.
21 * * * Request timed out.
22 * * * Request timed out.
23 * * * Request timed out.
24 * * * Request timed out.
25 * * * Request timed out.
26 * * * Request timed out.
27 * * * Request timed out.
28 * * * Request timed out.
29 * * * Request timed out.
30 * * * Request timed out.

Trace complete.

This is with the Firewall being on Medium or High.

Mike UK · 22 Jul 2012 at 13:40

Just for further info heres a traceroute on low.

Tracing route to f6.sensr.net [50.116.0.73]
over a maximum of 30 hops:

1 12 ms 7 ms 7 ms 10.41.40.1
2 8 ms 9 ms 8 ms hudd-core-1b-ae1-2485.network.virginmedia.net [8
0.7.153.197]
3 15 ms 17 ms 14 ms leed-bb-1b-xe-602-0.network.virginmedia.net [212
.43.162.121]
4 9 ms 11 ms 10 ms leed-bb-1a-ae0-0.network.virginmedia.net [62.253
.187.185]
5 31 ms 14 ms 18 ms tcl3-ic-1-ae0-0.network.virginmedia.net [212.43.
163.198]
6 39 ms 18 ms 25 ms 10gigabitethernet1-1.core1.lon1.he.net [195.66.2
24.21]
7 96 ms 91 ms 98 ms 10gigabitethernet7-4.core1.nyc4.he.net [72.52.92
.241]
8 186 ms 175 ms 176 ms 10gigabitethernet10-1.core1.sjc2.he.net [184.105
.213.173]
9 184 ms 178 ms 176 ms 10gigabitethernet1-1.core1.fmt1.he.net [72.52.92
.109]
10 173 ms 159 ms 159 ms router1-fmt.linode.com [64.62.250.6]
11 164 ms 160 ms 161 ms li391-73.members.linode.com [50.116.0.73]

Trace complete.

Also theres nothing in the Firewall log to say anythings been blocked.