Can't Access Webserver in Wireless Segment

[Rick Curtis]

Fresh firmware upgrade to Merlin 380.70. I have an Apache webserver that lives in my wireless segment (personal use only...not open to WAN.) I can access any/all web content on the server itself but not from any other device, either wired OR wireless. AP isolation is NOT enabled.

The webserver is a new install...there's a possibility that it is simply not configured properly to respond to outside traffic, but from everything I have researched it should be good (to be determined, I guess.)

I CAN ping the server from both wired side and another wireless client. The webserver is Ubuntu 18.04, both other clients used for testing are Windows, one is Windows 10 and the other Windows 7.

My main concern is that there is something set in the router that is causing this...but have not been able to find anything other than AP Isolation that even comes close to sounding like it might be the culprit.

Anybody got any ideas for what I can check?

 

[ColinTaylor]

I also have the default Apache server running on Ubuntu 18.04 and it works out-of-the box for HTTP access.

Unless your server is attached to a guest WiFi SSID there is nothing on the router that should block access to it. Assuming you're using the server's LAN IP address and not the router's WAN address.

 

[Rick Curtis]

Yes, but is *your* server on the wireless segment?

Clarification: Mine is not on the guest wireless. Also, if I connect the server to the wired segment all is good from other clients. That's why I'm questioning the router.

 

[dosborne]

Most likely this is an Apache configuration issue.

The first things you should verify are the basic config options such as the virtual host, port binding etc as listed in this web link
https://www.ntu.edu.sg/home/ehchua/programming/howto/Apache_HowToConfigure.html

Also, the next most obvious thing to do is check the Apache logs for errors or restrictions to see if the network traffic is getting that far.

Next thing would be the firewall on the Ubuntu box.

 

[ColinTaylor]

No it's not using a wireless interface.

I'd check the server's firewall, Apache's ports.conf and do a netstat to confirm which interfaces Apache is binding to.

 

[Rick Curtis]

OK...thanks all! I needed a sanity check before I went off on a wild goose chase *away* from the Apache configuration. I suspect that it *is* the Apache...