BT Home Hub, port forwarding
[This is not strictly Linux, but I guess it's the sort of thing a number of people on -list may have played with] I was playing with the port forwarding on my BTHH the other day, and noticed something odd. If I forward port 80 from the internet to my Linux box running Apache, when I visit whatever non-RIPE address the HH has at that time (from inside the NAT range), it still presents the HH admin interface, not the Apache files - i.e. the calls aren't being forwarded. Is there a way around this other than running on a port other than 80? Anyone know if it works from the internet proper (still waiting for my BT FON to be enabled)? TIA, Greg
On Mon, 2007-11-19 at 19:02 +0000, Greg Thomas wrote:
I was playing with the port forwarding on my BTHH the other day, and noticed something odd. If I forward port 80 from the internet to my Linux box running Apache, when I visit whatever non-RIPE address the HH has at that time (from inside the NAT range), it still presents the HH admin interface, not the Apache files - i.e. the calls aren't being forwarded.
Erm no generally the NAT will only work from the outside in..so hitting your routers internal interface on port 80 will not redirect you to the server you forwarded that port to. I dunno how the BT routers behave if the administration interface is on the same port as you have forwarded..I presume that the port forwarding rule wins. If in doubt there should be an option somewhere to tell the router to not accept connections to the admin interface from the outside facing interface..whether you are forwarding port 80 or not you would be well advised to turn this off.
Greg, Ill have a look when I get home, but Ive done exactly the same thing as you and I can access my apache webserver ok. The only slight difference is that I use dydns name instead of IP address but this is the same. Also I had no idea it was possible to access the BT home hub management interface from the internet. That is rather worrying considering how often it resets itself and port forwarding rules disappear, On Nov 19, 2007 7:47 PM, Wayne Stallwood <ALUGlist@digimatic.co.uk> wrote:
On Mon, 2007-11-19 at 19:02 +0000, Greg Thomas wrote:
I was playing with the port forwarding on my BTHH the other day, and noticed something odd. If I forward port 80 from the internet to my Linux box running Apache, when I visit whatever non-RIPE address the HH has at that time (from inside the NAT range), it still presents the HH admin interface, not the Apache files - i.e. the calls aren't being forwarded.
Erm no generally the NAT will only work from the outside in..so hitting your routers internal interface on port 80 will not redirect you to the server you forwarded that port to.
I dunno how the BT routers behave if the administration interface is on the same port as you have forwarded..I presume that the port forwarding rule wins. If in doubt there should be an option somewhere to tell the router to not accept connections to the admin interface from the outside facing interface..whether you are forwarding port 80 or not you would be well advised to turn this off.
_______________________________________________ main@lists.alug.org.uk http://www.alug.org.uk/ http://lists.alug.org.uk/mailman/listinfo/main Unsubscribe? See message headers or the web site above!
Greg, I also don't see this behaviour on my HomeHub running firmware release 6.2.6.C.
From the internal network, if I type the WAN address I get the web server and if I type the LAN address of the router, I get the HomeHub admin pages.
You can also check what you would see from the Internet by using an anonymiser service such as: http://anonymouse.org/anonwww.html HTH, Peter.
On 24/11/2007, samwise <samwise@bagshot-row.org> wrote:
Greg,
I also don't see this behaviour on my HomeHub running firmware release 6.2.6.C.
From the internal network, if I type the WAN address I get the web server and if I type the LAN address of the router, I get the HomeHub admin pages.
Well, armed with the knowledge that it can work, I unconfigured the existing set up, and then reconfigured it again.This time, it worked! Go figure; probably finger trouble with the set up in the first place. FWIW, I've had no issues with the HH since one of the early software updates; it's stable, reliable, gives me a good enough connection speed, and (generally) required very little thought from me. Greg
participants (4)
-
Greg Thomas -
samwise -
Venura Mendis -
Wayne Stallwood