Kitz ADSL Broadband Information
adsl spacer  
Support this site
Home Broadband ISPs Tech Routers Wiki Forum
 
     
   Compare ISP   Rate your ISP
   Glossary   Glossary
 
Please login or register.

Login with username, password and session length
Advanced search  

News:

Pages: 1 [2] 3

Author Topic: Experiments With A BT HH5 (Type B)  (Read 16444 times)

burakkucat

  • Respected
  • Senior Kitizen
  • *
  • Posts: 38300
  • Over the Rainbow Bridge
    • The ELRepo Project
Re: Experiments With A BT HH5 (Type B)
« Reply #15 on: January 31, 2016, 05:12:59 PM »
I, too, was thinking that perhaps William could perform an nmap scan [1] (from the LAN side) to see what ports are visible.

Something like --

nmap -n -Pn -T4 -p0- 192.168.1.254

[1] https://nmap.org/
Logged
:cat:  100% Linux and, previously, Unix. Co-founder of the ELRepo Project.

Please consider making a donation to support the running of this site.

William Grimsley

  • Kitizen
  • ****
  • Posts: 1489
    • Newton Poppleford Weather
Re: Experiments With A BT HH5 (Type B)
« Reply #16 on: January 31, 2016, 05:26:18 PM »
Ok, this is the result I got:

« Last Edit: January 31, 2016, 05:33:58 PM by William Grimsley »
Logged

burakkucat

  • Respected
  • Senior Kitizen
  • *
  • Posts: 38300
  • Over the Rainbow Bridge
    • The ELRepo Project
Re: Experiments With A BT HH5 (Type B)
« Reply #17 on: January 31, 2016, 05:59:01 PM »
An interesting list of eleven ports that deserves systematic testing.  :)

Port 22, ssh, is the most interesting. It is just unfortunate that it shows as "filtered".
Logged
:cat:  100% Linux and, previously, Unix. Co-founder of the ELRepo Project.

Please consider making a donation to support the running of this site.

d2d4j

  • Kitizen
  • ****
  • Posts: 1103
Re: Experiments With A BT HH5 (Type B)
« Reply #18 on: January 31, 2016, 06:54:33 PM »
Hi

I would not bother testing 53, it's only DNS

Do you have ssh, if not, an easy ssh Windows program is putty (just google it), which you could try to see if you get response. The username maybe root but I suspect it might be tied down to keys for access, and not password

Just a thought

Many thanks

John
Logged

William Grimsley

  • Kitizen
  • ****
  • Posts: 1489
    • Newton Poppleford Weather
Re: Experiments With A BT HH5 (Type B)
« Reply #19 on: January 31, 2016, 07:35:02 PM »
I tried PuTTY on SSH and got "Network error: Connection timed out" and on Telnet I got "Network error: Connection refused".
« Last Edit: January 31, 2016, 07:38:00 PM by William Grimsley »
Logged

burakkucat

  • Respected
  • Senior Kitizen
  • *
  • Posts: 38300
  • Over the Rainbow Bridge
    • The ELRepo Project
Re: Experiments With A BT HH5 (Type B)
« Reply #20 on: January 31, 2016, 07:44:15 PM »
Your command line, if using telnet, would be --

telnet 192.168.1.254 22

I.e. the first argument is the IP address and the second argument is the port number.

Here is an example --

Code: [Select]
[Duo2 ~]$ nmap -n -Pn -p22 192.168.1.254

Starting Nmap 5.51 ( http://nmap.org ) at 2016-01-31 19:47 GMT
Nmap scan report for 192.168.1.254
Host is up (0.0032s latency).
PORT   STATE SERVICE
22/tcp open  ssh

Nmap done: 1 IP address (1 host up) scanned in 0.04 seconds
[Duo2 ~]$ telnet 192.168.1.254 22
Trying 192.168.1.254...
Connected to 192.168.1.254.
Escape character is '^]'.
SSH-2.0-dropbear_2012.55
^]

telnet> Connection closed.
[Duo2 ~]$
« Last Edit: January 31, 2016, 07:48:27 PM by burakkucat »
Logged
:cat:  100% Linux and, previously, Unix. Co-founder of the ELRepo Project.

Please consider making a donation to support the running of this site.

William Grimsley

  • Kitizen
  • ****
  • Posts: 1489
    • Newton Poppleford Weather
Re: Experiments With A BT HH5 (Type B)
« Reply #21 on: January 31, 2016, 07:47:01 PM »
Quote from: burakkucat on January 31, 2016, 07:44:15 PM
Your command line, if using telnet, would be --

telnet 192.168.1.254 22

I.e. the first argument is the IP address and the second argument is the port number.

Nope, same error as before. :(



I have changed the Telnet port in the port forwarding part to 22.
« Last Edit: January 31, 2016, 07:54:19 PM by William Grimsley »
Logged

burakkucat

  • Respected
  • Senior Kitizen
  • *
  • Posts: 38300
  • Over the Rainbow Bridge
    • The ELRepo Project
Re: Experiments With A BT HH5 (Type B)
« Reply #22 on: January 31, 2016, 07:50:21 PM »
Whilst you were replying, I was making an edit to my previous post to provide an example of what can be expected from a device with port 22 fully open.
Logged
:cat:  100% Linux and, previously, Unix. Co-founder of the ELRepo Project.

Please consider making a donation to support the running of this site.

William Grimsley

  • Kitizen
  • ****
  • Posts: 1489
    • Newton Poppleford Weather
Re: Experiments With A BT HH5 (Type B)
« Reply #23 on: January 31, 2016, 07:58:30 PM »
Quote from: burakkucat on January 31, 2016, 07:50:21 PM
Whilst you were replying, I was making an edit to my previous post to provide an example of what can be expected from a device with port 22 fully open.

Ok, thanks. But, this seems like this isn't get anywhere. I got this result when completing the steps in your previous screenshot:



How would I get the port to be fully open?

Can I just get one thing straight here, would doing any of this mean I can monitor my router line stats as it seems a hell of a lot of work?
« Last Edit: January 31, 2016, 08:12:12 PM by William Grimsley »
Logged

ejs

  • Kitizen
  • ****
  • Posts: 2078
Re: Experiments With A BT HH5 (Type B)
« Reply #24 on: January 31, 2016, 08:44:41 PM »
"filtered" in the nmap results isn't necessarily hopeful, it means nmap did not receive any response to its probe at all.
For all the closed ports not shown, "closed" means nmap did receive a response, but it was just a standard response to indicate there is no program listening on that port.

Quote from: William Grimsley on January 31, 2016, 07:58:30 PM
Can I just get one thing straight here, would doing any of this mean I can monitor my router line stats as it seems a hell of a lot of work?

If you eventually succeed in finding some way to access the shell of the router, then yes, you could monitor the line stats. It could take a lot of work, with no guarantee or even expectation of success though.
Logged

William Grimsley

  • Kitizen
  • ****
  • Posts: 1489
    • Newton Poppleford Weather
Re: Experiments With A BT HH5 (Type B)
« Reply #25 on: January 31, 2016, 08:48:32 PM »
Ok, well thanks everyone for the help, if anyone has any other thoughts then please post as I don't have a clue from here.
Logged

Dray

  • Kitizen
  • ****
  • Posts: 2361
Re: Experiments With A BT HH5 (Type B)
« Reply #26 on: January 31, 2016, 09:01:44 PM »
Did you factory reset the HH5 after the firmware upgrade as it sounds like it's unstable right now?
Logged

licquorice

  • Reg Member
  • ***
  • Posts: 977
Re: Experiments With A BT HH5 (Type B)
« Reply #27 on: January 31, 2016, 09:02:03 PM »
As far as I'm aware the HH is completely locked down and has no SSH or Telnet access readily available.
Logged

kitz

  • Administrator
  • Senior Kitizen
  • *
  • Posts: 33883
  • Trinity: Most guys do.
    • http://www.kitz.co.uk
Re: Experiments With A BT HH5 (Type B)
« Reply #28 on: January 31, 2016, 09:24:44 PM »
It is totally locked down :(

Unfortunately none of the logging apps work with the 5B - even routerstats.
Logged
Please do not PM me with queries for broadband help as I may not be able to respond.
-----
How to get your router line stats :: ADSL Exchange Checker

William Grimsley

  • Kitizen
  • ****
  • Posts: 1489
    • Newton Poppleford Weather
Re: Experiments With A BT HH5 (Type B)
« Reply #29 on: January 31, 2016, 09:38:37 PM »
Quote from: Dray on January 31, 2016, 09:01:44 PM
Did you factory reset the HH5 after the firmware upgrade as it sounds like it's unstable right now?

I have factory reset it since the firmware upgrade but not for that reason, it's perfectly stable.

Quote from: licquorice on January 31, 2016, 09:02:03 PM
As far as I'm aware the HH is completely locked down and has no SSH or Telnet access readily available.

That's a shame. It's a bit odd that BT included a "Telnet" entry in the Port Forwarding section of the Hub interface.
Logged
Pages: 1 [2] 3
« previous next »
 

anything