The issue is that you must allow the traffic from ethernet address. If you accept only connections from your http proxy, you use the address from your interface (i.e. 172.16.1.1). I hope it helps.
I'm allowing traffic from "any" to access the webadmin. Do I have to add something somewhere else? I don't see any packet filter log events, which leads me to believe that the issue lies with webadmin rejecting the connection. I'm not using a proxy to connect, but I could if there is a way for that to work. Where would I enter address of my interface?
I'm allowing traffic from "any" to access the webadmin. Do I have to add something somewhere else? I don't see any packet filter log events, which leads me to believe that the issue lies with webadmin rejecting the connection. I'm not using a proxy to connect, but I could if there is a way for that to work. Where would I enter address of my interface?
1st I would test if you can access your webmin from your internal network (I think you can). 2nd I would test if you can access your webmin from your external interface. You can do it for connecting directly your PC at you home hub/switch/router at the external interface.
Please control your local logs from "packet rules". You can allow ssh connect with your asl under "System - Webadmin settings". If you have any error messages from your log or with ssh, please post it here. If you get the connection with this "internal" connect, you must test to enable a port forwarding rule at your router to webmin.
Hi AFH, thanks for the help. 1. Internal access works to internal address (no proxy involved). 2. External access works to external address. 3. SSH works from internal and external.
When I try to connect, nothing is logged in the packet filter event log. However, this shows up in the webadmin log: 2004:11:01-10:15:22 (none) webadmin[1310]: U:admin ID:0121
My guess is that somewhere in the http server configuration localhost access is blocked. I have no idea where to look though. Any other thoughts?