Webserver with a aolynk DR814Q and smart

Treora

Has anyone been able to set up a webserver with aolynk DR814Q on smart's residential package.

I am using apache on a kubuntu machine and I can see my test page via http://localhost and http://192.168.1.3:80. So the service is running on the correct port. When I connect to http://IP I connect to my router with the prompt 'webuser at IP', login & password. It acts as though I have connected to 192.168.1.1. I cannot see anything from outside pointing to http://IP or http://IP:80

The firewall is enabled at default, IP interface is IPWAN and NAT is enabled, static NAT is blank, remote management is off and IDS is disabled. The portforwarding is setup correctly. No DMZ host. Everything else is setup as instructed and the BB works fine.

Smart support gave up nothing and their forums only suggested turning off the firewall, but it gave me the same problem.

Does anyone have a clue as to what is causing this?

cormon

you re apache is fine from the linux box itself .

1) When you are testing the ip in your browser are you doing so from another box or the linux box itself.

2) is this different box mentioned above on the same LAN ?

Looks like your problem is either on your arp entries or a possible misconfigured host table. What I'd try is just assigned a name to the .3 address in your host table and try the name in the browser and clear you arp cache. Maybe worth a try.

Treora

cormon wrote:

you re apache is fine from the linux box itself .

1) When you are testing the ip in your browser are you doing so from another box or the linux box itself.

2) is this different box mentioned above on the same LAN ?

Looks like your problem is either on your arp entries or a possible misconfigured host table. What I'd try is just assigned a name to the .3 address in your host table and try the name in the browser and clear you arp cache. Maybe worth a try.

1) Both - Initially: When I connect to http://IP I connect to my router with the prompt 'webuser at IP', login & password. It acts as though I have connected to 192.168.1.1. Later when I go to a machine outside of that lan (eg internet café) I cannot see anything (requests times out/page request fails) from outside pointing to http://IP or http://IP:80.
2) what different box?

I will look into the host table and the arp entries.

Tnx

cormon

local issue on the lan

This should be fixable with
1) a host file entry and then clearing the arp cache.
2) Sounds funny but after step 1 disable/enable the network card
3) There are a few "netsh" commands you can run to tweak ip/arp in Windows XP

remote issue from the outside world.

This looks like misconfigured port forwarding . Are you using port 80 ? can you use a different port number.... .where does the traceroute stop ?

Treora

Since I'm using linux is there an alternative to netsh?

I am using port forwarding to port 80. I'll check traceroute later.

cormon

LAN ISSUE
crap , you did say you're were running Linux . In relation to the (Lan) arp issue
the ARP command is the one you're after , its fairly small but powerful . You can even map an ip address to the ip address which i dont thing you can do in windows . Another great tool is TCPDUMP which will capture all packets going out you're interface . What I would do is to get the MAC address of .1 and .3 and then review the output of the TCPDUMP logs . you may have to enable this feature in TCPDUMP . Which ip traffic is going to which ip etc and then you can use the arp tool to nail it down .

Wan Issue

the port forwarding still sounds wonky to me http://www.canyouseeme.org/
use that in a browser on the linux box to see if the port is open or closed.

These issues could be over lapped but the linux tools should make things clearer .

Let me know how you get on

Treora

Cormon - I cleaned out arp table yesterday as you susggested. It did not appear to work initially, but I can access the server this morning . Funny thing is that I got a success on canyouseeme.org before flushing out the table. And smart had been onto my router again yesterday evening so maybe they fixed it then.

Thanks for the help.
(wow - googling arp can be scarily educational :eek:)

cormon

no probs , I f%^&kin hate dealing with Isp's as well.

ntlbell

if the routers gui interface is listening on port 80, change it to 8080 or disable it on the WAN interface.

Don't test it sitting on your local lan trying to hit the external IP

test it from the outside or ask someone else can see they see http://externalIP