Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

[roseway]

I'm intending to add a simple embedded webserver to DSLstats, so that users can view their stats and graphs remotely. I've got it working to the point where users on the LAN can view the pages it serves, but now I have to make it available to remote connections, and I'm outside my comfort zone here. As I see it, there are three possibilities:

- put the PC running DSLstats in a DMZ
- use an unallocated port chosen by the user, and the user forwards that port in their firewall
- use uPnP

The first option is probably a non-starter, except for a small minority.
The second is easy to implement, but I'm unsure about the security implications.
I know next to nothing about uPnP.

Any advice would be welcome.

[ryant704]

DMZ wouldn't be an option for me as it's already in use.

Security port would be most favorable depending upon the security issues it could raise.

Not too sure on uPnP but I've assumed it to be rather vulnerable unless it's been fixed in the last year or so.

I think this is a very good idea overall!

[roseway]

Thanks for that.

[burakkucat]

Of your three options, I would not be happy using either the first or third (DMZ or UPnP). 

The second, however, is reasonable and I would be prepared to configure my firewall appropriately -- if I ever require remote access to the statistics. 

[roseway]

Thanks, that ties up with a couple of opinions I've received privately.

[broadstairs]

I'd go for option 2 as well if I ever needed it. I'm sure that you have considered making the embedded web server an option as I probably would not use it anyway.

Stuart

[roseway]

Thanks Stuart, yes it will be optional. There will be another tab under 'Configuration', where you can enable/disable it and set parameters such as the port number.

[broadstairs]

One thought about this which has just struck me. What happens if someone already runs an Apache (other web servers are available  ) on the same PC? Could there be a problem with which port(s) this DSLStats server listens on?

Stuart

[roseway]

I guess the answer to that is that it's up to the user to choose a port which isn't currently in use on their system. I'm intending to stick to the officially unassigned ports (49152 - 65535) because the port authority says: "Assigned ports both System and User ports SHOULD NOT be used without or prior to IANA registration."

http://www.iana.org/assignments/service-names-port-numbers/service-names-port-numbers.xhtml

[Ronski]

@broadstairs You just configure it to use a different port.

You'll also need to open the relevant port  in your pc's firewall.

[broadstairs]

@broadstairs You just configure it to use a different port.

You'll also need to open the relevant port  in your pc's firewall.

Yes I know but since you can re-direct ports as well in most routers I just wanted to make sure that the server itself was not limited to port 80 or 8080 and relied on redirection.

Stuart

[roseway]

Just to be clear, DSLstats will use the port chosen by the user. To access the webserver remotely, you'll point your browser at <IP address>:<Port number>/<Page name> (e.g. 50.60.70.80:55555/snrm.html).

[burakkucat]

Excellent. That is just what I would have expected.