datadiffusion Posted April 24, 2014 Author Posted April 24, 2014 Surely if BT were blocking 9000 it would be well known? Tried external port scan, bt hh itself claims firewall automatically exempts port forwards... So, I've decided to take my work back underground.... to stop it falling into the wrong hands
matthew.brough Posted April 24, 2014 Posted April 24, 2014 I was trying to think of the word... Modem is not technically correct I think youll find... Whys that? www.securitywarehouse.co.uk/catalog/
datadiffusion Posted April 24, 2014 Author Posted April 24, 2014 Dont know just something someone told me once which Ive just realised probably isnt true... What's the IP on the WAN side of the HH? Not shared 86.184.25.46 So, I've decided to take my work back underground.... to stop it falling into the wrong hands
Adi Posted April 24, 2014 Posted April 24, 2014 That sounds like a crossword clue... I did read anout Nat loopback issues meaning that you couldnt uee a dyn address internally. Ffs how lame! But the issue remains even when I tried on 3G. Another site suggest a true static Ip outside the BT dhcp range... But not sure if the hub would allow forwarding to an arbitrary ip?? I only read that afterwards. At least the site is only 2 min away and im going back in a week anyway. Im on infinity but use a different router, same white infinity box though. Interestingly firmware on the hh is only a week old... Thought they were black Surely if BT were blocking 9000 it would be well known? Tried external port scan, bt hh itself claims firewall automatically exempts port forwards... Ah, gay port number, mines different so cant verify this works I really can't be ar**** with it anymore.
datadiffusion Posted April 24, 2014 Author Posted April 24, 2014 Hh is black, vdsl modem is white. As from hh5 the two are combined... (hh5 = hh4 with onboard vdsl) So, I've decided to take my work back underground.... to stop it falling into the wrong hands
Adi Posted April 24, 2014 Posted April 24, 2014 I'm out. The only only vd i know itches. I really can't be ar**** with it anymore.
Lwillis Posted April 25, 2014 Posted April 25, 2014 The BT hubs can be done. Took me a while the first time. Don't assign a local static IP to the DVR. Use DHCP so the DVR appears in the connected device list. Add it as a saved device and reserve its IP and Mac address. Create the port rules and then assign them to she DVR which is now in the list of connected devices . Test and done.
sixwheeledbeast Posted April 25, 2014 Posted April 25, 2014 86.184.25.46Well that should rule out a double-NAT issue. Did you test a DMZ?
datadiffusion Posted April 25, 2014 Author Posted April 25, 2014 The BT hubs can be done. Took me a while the first time. Don't assign a local static IP to the DVR. Use DHCP so the DVR appears in the connected device list. Add it as a saved device and reserve its IP and Mac address. Create the port rules and then assign them to she DVR which is now in the list of connected devices . Test and done. That's exactly what I did do though. This is my first with infinity AND HH - my other customers ditched the HH bit when they upgraded. Last two I did on VDSL were netgear and Fritzbox, no issues. Have done ADSL HHs before many a time... Other (BT BB) forum advice is NOT to use an address within DHCP scope, set it as actual static at the device. Oh dear... Just thinking, nothing to do with homeplugs messing about with the presented MAC is it.... So, I've decided to take my work back underground.... to stop it falling into the wrong hands
Recommended Posts
Archived
This topic is now archived and is closed to further replies.