39Sam
April 7th, 2018, 12:19
Hello all,
I'm having a hell of a time understanding why my GM session is unreachable since I changed the host on my internal network. I changed my FW rules *and* resetted it (damn ARP tables). Still it does not work.
The logs on the firewall are mostly useless so I'm down to Wireshark to try to understand what's going on:
1) The "Run Test" feature on the FG program reach first to 104.20.131.20 over http:80, likely to initiate the test on FG server.
2) Now the FG server *I suppose* is trying to open the TCP:1802 on the source address that initiated step 1)
However I am not certain that the FG crew implemented it this way. Can someone confirm that the server trying to initiate the TCP:1802 connection for the test sequence is really 104.20.131.20 and not some other source ?
My network has a lot of IoTs and other computers so I need to filter out as much as I can to diagnose my syslog and wireshark logs to understand what's going wrong. Thanks for your help.
I'm having a hell of a time understanding why my GM session is unreachable since I changed the host on my internal network. I changed my FW rules *and* resetted it (damn ARP tables). Still it does not work.
The logs on the firewall are mostly useless so I'm down to Wireshark to try to understand what's going on:
1) The "Run Test" feature on the FG program reach first to 104.20.131.20 over http:80, likely to initiate the test on FG server.
2) Now the FG server *I suppose* is trying to open the TCP:1802 on the source address that initiated step 1)
However I am not certain that the FG crew implemented it this way. Can someone confirm that the server trying to initiate the TCP:1802 connection for the test sequence is really 104.20.131.20 and not some other source ?
My network has a lot of IoTs and other computers so I need to filter out as much as I can to diagnose my syslog and wireshark logs to understand what's going wrong. Thanks for your help.