On Wed, Apr 2, 2025 at 1:37 AM Van Snyder wrote:
> I discovered that although I haven't even installed iptables, my server
> was running firewalld. I wasn't even aware it existed. I stopped it, and
> now I can access my web vandyke.mynetgear.com through my router on port
> 80 or 443.
>
> I disabl
On Wed, Apr 2, 2025 at 1:50 AM Timothy M Butterworth <
timothy.m.butterwo...@gmail.com> wrote:
>
>
> On Wed, Apr 2, 2025 at 1:37 AM Van Snyder
> wrote:
>
>> I discovered that although I haven't even installed iptables, my server
>> was running firewalld. I wasn't even aware it existed. I stopped
On Tue, 01 Apr 2025 18:19:55 -0700
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.
firewall-config for GUI operation. firewalld comes with a command line
(and scriptable) tool ca
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 t
I discovered that although I haven't even installed iptables, my server
was running firewalld. I wasn't even aware it existed. I stopped it,
and now I can access my web vandyke.mynetgear.com through my router on
port 80 or 443.
I disabled firewalld because I have no idea how to configure it, but m
5 matches
Mail list logo
