Samsung Galaxy Y wifi hotspot webserver

Forums › Spark New Zealand (including Skinny and BigPipe) › Samsung Galaxy Y wifi hotspot webserver

davef2

12 posts

Geek

#140582 13-Feb-2014 16:20

I recently bought a Samsung Galaxy Y, mainly to use as a WiFi hot spot, so that I can remotely access a home automation web server.

I installed DynDNS client and using Port Scanner worked out that the only open port is 53. So, I "rooted" the phone in order to use ports <1024. Then used Port Forwarder to pass port 53 to my Linux box on port 80.

I can ping [link removed] from the device running the web server, so the "uplink" appears to be working.

The DynDNS client does have a message, "You are connected to the internet through a proxy. This probably means that internet users can NOT connect to your device".

I can see my IP being updated on DynDNS but I can not access my web server remotely. So, maybe that message is a clue but I don't know how to fix it!

I am on prepay, if that makes any difference. I have an incident filed with Telecom, but no answer after 3 days.

Thanks for any tips.

gundar

488 posts

Ultimate Geek

Trusted

#986833 13-Feb-2014 16:31

I don;t know anything about Galaxy Y's, but, I'm sure DNS uses 53 to send AND receive so maybe using 53 for anything, on any device that expects to be part of a network, is a bad idea.

You should be able to check this on your Linux box, if it is receiving DNS traffic of any sort in it's webservice, that will prove my theory.

davef2

12 posts

Geek

#986883 13-Feb-2014 17:07

The sequence of events in my posting was incorrect. I determined that port 53 was open when WIFI hotspot is enabled before running the DynDNS client. I understand your comment about port 53.

I never changed anything to port 53, so I need to determine if that is normal behaviour for enabling the WiFi hotspot or ?

Cheers,
Dave

openmedia

3324 posts

Uber Geek

Trusted

#987076 13-Feb-2014 23:52

davef2: I recently bought a Samsung Galaxy Y, mainly to use as a WiFi hot spot, so that I can remotely access a home automation web server.

I installed DynDNS client and using Port Scanner worked out that the only open port is 53. So, I "rooted" the phone in order to use ports <1024. Then used Port Forwarder to pass port 53 to my Linux box on port 80.

I can ping [link removed] from the device running the web server, so the "uplink" appears to be working.

The DynDNS client does have a message, "You are connected to the internet through a proxy. This probably means that internet users can NOT connect to your device".

I can see my IP being updated on DynDNS but I can not access my web server remotely. So, maybe that message is a clue but I don't know how to fix it!

I am on prepay, if that makes any difference. I have an incident filed with Telecom, but no answer after 3 days.

Thanks for any tips.

Afraid I don't understand your network

Is the Galaxy Y for remote access to home for being used at Home.

Why are you trying to port forward port 53?

If the galaxy Y is acting as a wifi hotspot on Telecom's network you should be able to reach any address on the internet? Can you browse other websites via that hotspot.

Steve

Generally known online as OpenMedia, now working for Red Hat APAC as a Technology Evangelist and Portfolio Architect. Still playing with MythTV and digital media on the side.

davef2

12 posts

Geek

#987102 14-Feb-2014 07:31

Steve,

Yes, I want to put the Galaxy Y at the bach and access it from home. At the bach I have a web server running on a Linux platform that I want to "attach" to the Galaxy Y running as a Wifi hotspot. I currently have the system running on ADSL, using a wireless router. In that system I needed to forward port 80.

Because I really don't know a lot about setting these systems up I thought I needed to find out which ports were open on the Galaxy Y as a WiFi hotspot and forward one of those. The only port that is open is 53.

Should I be trying to get the Galaxy Y to open port 80 and then forward that one?

Yes, I can browse to websites from the bach.

Thanks for taking the time to answer.

Cheers,
Dave

Mattmannz

471 posts

Ultimate Geek

#987131 14-Feb-2014 08:57

Port 53 is open because that's the DNS port that the handset needs to have open to use DNS. You can't use port 53.

The only ports that should be open are ones that are already configured for services. Once you select a port and forward that port from your handset to the web server then when you rescan you should be able to see that new port open.

From a design perspective you shouldn't use any common ports, use a high number port and forward that to port 80 on your webserver using NAT.

Cheers
Matt.

davef2

12 posts

Geek

#987157 14-Feb-2014 09:50

Matt,

Right! Now, after a rescan I have port 8080 open. Thanks that was the clue I needed.

Dave

davef2

12 posts

Geek

#999082 4-Mar-2014 21:10

Conclusion: Telecom, due to network management design constraints do not permit individuals to operate a web server on the mobile network.

It was suggested to approach a web hosting provider.

Equinox IT

Cloud spending continues to surge globally, but most organisations haven’t made the changes necessary to maximise the value and cost-efficiency benefits of their cloud investments. Download the whitepaper From Overspend to Advantage now.

openmedia

3324 posts

Uber Geek

Trusted

#999170 4-Mar-2014 22:41

Get the server in the batch to open a VPN connection to your home, for example with OpenVPN?

Generally known online as OpenMedia, now working for Red Hat APAC as a Technology Evangelist and Portfolio Architect. Still playing with MythTV and digital media on the side.

davef2

12 posts

Geek

#999285 5-Mar-2014 10:13

Thank you I'll check it out.