Can't access SmartHub 2 from different local subnet

[ptrduffy]

I can ping any device connected via the SH2 in AP mode from a different subnet, just not the SH2 itself (unless I am in the same subnet).

Which strongly suggests to me that the SH2 is dropping requests for admin access from outside its own subnet - is there anything in the logs to that effect?

@TimCurtismentioned he was able to connect via an Asus to the SH2, but he didn't mention what the subnet mask was on the SH2, so they could have been on the same subnet.

[TimCurtis]

@ptrduffy 

I think I used the same mask as in the Asus of 255.255.252.0 .

[WSH]

@ptrduffy  However, I can both ping and access my SH2 on 192.168.1.254/24 from my network on 192.168.144.0/24 without issue.

Edit: And that's with my Draytek inbetween doing the routing.

[licquorice]

Correction to my post earlier, the hub responds to pings on the LAN interface but not the WAN.

The problem does appear to be a strange quirk of the BT hub as everything else works as expected.

[WSH]

yes, that would make sense as a default setting today.

[jamespavett]

@licquorice but just as it blocks on the WAN interface that shouldn’t  me directly should it here? As these requests are being routed from another internal LAN.

I wasn’t sure if it could be rejecting requests outside of the 192.168.x.x range. Both of your subnets still following this convention @WSH. Especially seeing as the SH2 doesn’t let you set a static IP in the 10.x.x.x range. But my lack of networking understanding might mean this isn’t relevant.

So to summarise so far:

- Can’t ping 192.168.1.6 or access admin panel off any other subnet other than the one the SH2 is on. Atleast in the 10.44.x.x range 

- Can ping / reach any other device on the 192.168.1.0/24 subnet, including any devices connected via the SH2, from other subnets.

- Can ping and access admin panel from other devices on the 192.168.1.0/24 subnet.

I’m now questioning myself though and wondering if I can actually access / ping the SH2 on any other device on the 192.168.1.0/24 subnet, or only those that are connected via the AP on the SH2, need to give that a test later.  

[licquorice]

---

@jamespavett wrote:

I’m now questioning myself though and wondering if I can actually access / ping the SH2 on any other device on the 192.168.1.0/24 subnet, or only those that are connected via the AP on the SH2, need to give that a test later.  

---

Yes, that will be an interesting test.

[WSH]

@jamespavett  The 10.44.x.x range?  The 10 private range is usually /8.  What are you using then?

I suspect anything starting with 10 will be treated as private today, (although I've not checked), but perhaps the SH2 is looking for a private address as /8.

[jamespavett]

@WSH I have a few subnets:

192.168.1.0/24

10.44.2.0/24

10.44.3.0/24

10.44.4.0/24

These should should be valid tough, are they regularly /8, as these subnets exist within the /space anyway? Anything in the 10.0.0.0–10.255.255.255 range should be valid.

[WSH]

@jamespavett  Yes, true enough.  Just a thought.