Re: Web server access SOLVED
On 02/04/2025 11:49 am, Van Snyder wrote:
> I disabled firewalld because I have no idea how to configure it, but
> my Linksys router is running a firewall that's really easy to configure.
For next time you get a connectivity issue like this.. If you are sure
the linksys router box is passing the external requests (DNAT) to the
web server, then you will see a client connection within a packet
capture on the destination web server. Typically the webserver won't
log anything before a 3-way handshake is completed and it receives a
http request.
Install tcpdump on your web server (apt install tcpdump) and run a
simple traffic capture from your home directory:
tcpdump port 80 or 443 -s 65535 -w web-server-cap01.pcap (that will
run continuously until you end it, CNTL-C)
You can then scp the capture file (*.pcap) into wireshark and see if
your actual inbound request packet is reaching the web server at all
(you're looking for a SYN packet to start the connection). In your
case, you would have not seen this traffic at all from the external
client, so then you would have considered what was blocking it.
Additionally, you could mirror the switch port that connects to your web
server and confirm it was passing the initial connection frames (after
the linksys DNAT). If Linksys doesn't offer that capture facility you
can easily use another switch in between your router & web server that does.
Reply to: