I've recently moved into a new place and transferred my existing Sky account over. This included TV and Fibre Unlimited. The old setup was a SR101 and an OpenReach modem (Huawei). The Home Move team sent out an SR102 to be used after the line was setup.
The SR102 worked ok and eventually the connection sped up to 38/9. However, it would constantly drop active connections. Not the DSL connection, but at the IP level. Large uploads would bail out after 30-50meg or so.
This, and that the WiFi on the SR102 was 2.4Ghz only, lead me to get an Airport Extreme. I had an OpenReach modem from the previous installation. I read the guide, sniffed the username/password combo for the DHCP Client identifier and setup the Airport Extreme by manually editing the configuration XML.
The connection worked - however ping times were a bit longer than previously and the connection was only running at 11/1. I plugged the SR102 in instead of the Airport extreme (so still using the OpenReach Modem) and the speed was back at 38/9. I set up the Airport Extreme again to see what was going on.
A traceroute to 184.108.40.206 was far longer than it should have been and seemed to be going through BT Internet's network. How bizarre.
The Airport extreme was reporting an external Sky IP, but when I typed 'what is my ip' into google, I got a BT Internet IP address. Puzzled, I port mapped the IP, which reveal a HTTP port.
Browsing to this IP (which I had just one hop to on mtr) revealed a Netgear router login… I have no Netgear kit. I used the default password for that brand of router and was greater with… the configuration page for my neighbour's router. I noticed the SSID as their's. At this point I was wired into the Airport Extreme and had WiFi off on my laptop. I don't know their wireless password so there was no way I was connected via Wifi.
Somehow, the airport express was routing through the Netgear router via the cabinet! This was also somehow exposing the Netgear router to me - I could connect on 192.168.0.1 also.
I changed the subnet on the Airport Extreme to something other than 192.168.0.x and rebooted. The connection is now at full speed and reporting a Sky IP address.
I think as the Airport Extreme was also setting itself up on 192.168.0.1 and setting it's DHCP clients router addresses as 192.168.0.1, there was some funky ARP going on which lead to the clients routing via the Netgear router (hitting the Airport Extreme and OpenReach box along the way). I'm also wondering if this issue was leading to connections dropping.
Is there anything I can do to stop the Netgear router 'leaking' via the cabinet? Quite friendly with the neighbour but probably a bit complicated to explain what's going on! Any advice or better explanation appreciated.
Edited by cooberto (Fri 15-Aug-14 12:43:51)