Smart WiFi plugs

Strider590

AndyPix wrote: »

Total rubbish

For example .. My BT HH2 has 17 devices connected to it right now

Static IPs?

But don't forget, they do firmware updates too.

I happened to get sick of it and bought my own router.

I don't care what the website says, it doesn't mentioned the IP loopback problem OR the issue with blocking FTP traffic OR the crashing when Torrenting OR the ports that are permanently open (security risk).

In fact, the only place you find reference to these issues, is NOT on the BT website.

Strider590

kwikbreaks wrote: »

I've never come across that but I don't use ISP routers so maybe that's why.

Luckily though as I mentioned earlier there is no need at all for any port forwarding or fixed IPs either on the LAN or WAN with the ones linked to as they are cloud devices and use an intermediate server for both communication and security.

So they're not internet connected then?

AndyPix

Strider590 wrote: »

Static IPs?

But don't forget, they do firmware updates too.

I happened to get sick of it and bought my own router.

I don't care what the website says, it doesn't mentioned the IP loopback problem OR the issue with blocking FTP traffic OR the crashing when Torrenting OR the ports that are permanently open (security risk).

In fact, the only place you find reference to these issues, is NOT on the BT website.

Yes - but we weren't talking about all that other stuff were we ?
You are providing wrong information

I think you have the problem "a little knowledge is a dangerous thing"

You are saying the right words, but don't quite know what you are talking about.

Andy

kwikbreaks

Strider590 wrote: »

So they're not internet connected then?

AndyPix wrote: »

Do you mean they use their own 3g connection and not the home wifi ?

No. They communicate with the manufacturers server and that leaves an open connection which the server can respond to. The mobile app communicates with the same server to communicate commands to the device. There are web cameras that work the same way.

Think of services such as Teamviewer - no need to open ports for that either - the client PC communicates with the central server and so does the control PC. Home firewalls don't normally block outgoing data just unsolicited incoming.

AndyPix

Strider590 wrote: »

Static IPs?

But don't forget, they do firmware updates too.

I happened to get sick of it and bought my own router.

I don't care what the website says, it doesn't mentioned the IP loopback problem OR the issue with blocking FTP traffic OR the crashing when Torrenting OR the ports that are permanently open (security risk).

In fact, the only place you find reference to these issues, is NOT on the BT website.

No not static . DHCP
They don't block FTP traffic and can torrent fine.
No ports are open.

You obviously have issues

kwikbreaks

The usual reason routers hang when using torrents is because their internal connection table isn't big enough to handle the large number of connections badly configured torrent clients can use. Sometimes it's just cost cutting by the manufacturer in not providing enough ram for even a moderately large number of connections.

AndyPix

kwikbreaks wrote: »

No. They communicate with the manufacturers server and that leaves an open connection which the server can respond to. The mobile app communicates with the same server to communicate commands to the device. There are web cameras that work the same way.

Think of services such as Teamviewer - no need to open ports for that either - the client PC communicates with the central server and so does the control PC. Home firewalls don't normally block outgoing data just unsolicited incoming.

They communicate with the manufacturers servers how ?

Black magic ?

They have to have some kind of connection.

Again, you half sound like you know what your talking about but I can tell you don't fully understand it.
Teamviewer etc communicate over port 80 (HTTP) or port 443 (HTTPS) .
Both these ports are open by default on any router so that you can browse the internet.
These devices work in the same way

That is what you are trying to say

AndyPix

kwikbreaks wrote: »

The usual reason routers hang when using torrents is because their internal connection table isn't big enough to handle the large number of connections badly configured torrent clients can use. Sometimes it's just cost cutting by the manufacturer in not providing enough ram for even a moderately large number of connections.

What the hell does that mean ?
All the router will see is traffic going over the dedicated port for that app.
What on earth is an internal connection table ?

jesus

bod1467

Andy - it seems to me that it is you who is struggling to digest what others have written.

Taking the HH2 (routers) issues ... my interpretation of what Strider was saying is that the HH2 struggled with a maximum number of devices assigned with a static IP address. (As well as the other issues mentioned, to which kwikbreaks has addressed why torrenting could be an issue).

Taking the wifi plug issue ... the plug is essentially a mini-PC with a wifi network adapter, which is configured and connected to the local wifi network. This then opens its own port in the router to a remote (internet-connected) server machine which authenticates users and devices (i.e. cloud-based). A user connects to the server using their phone (from wherever and however - could be another wifi, local wifi, or mobile data) to see their device and control it.

Nothing difficult to understand at all from where I'm sitting.

What was that jibe you made before? Oh yes ...

AndyPix wrote: »

I think you have the problem "a little knowledge is a dangerous thing"

Strider590

AndyPix wrote: »

No not static . DHCP
They don't block FTP traffic and can torrent fine.
No ports are open.

You obviously have issues

Ok not static, can they be set as static? or was that bug patched out?

FTP was being blocked some years back, I had to use non-standard ports to access my home FTP, by forwarding something like 62326 to port 21, a PITA.
There might still be a forum post about this on their support forum, where I went to vent my frustration at the fact id been pushed into use a new hub and this had broken half the things I need the internet for.

There are open ports (port 161 for a start), look this up, it's well known, they're the ports BT use to force firmware updates. But it's a security concern, because anyone can determine your on BT and then they'll know which ports to attack without even running a port scan.

NAT Loopback was a big issue for me, it prevented me being able to test my own website from within the LAN, using my domain name.

And I was giving examples of flaws in the homehub firmware, all perfectly relevant, but you seem to think it's flawless.