Re: firewalld help

Ok. I see the problem now. Default routes have always been a bit of a mystery to me. Based on your reply, I manually deleted the default route for enp3s0 to confirm it works. Then, I edited the connection with nmcli to remove the default permanently across reboots. For everyone's benefit,

Re: firewalld help

> On 10 Nov 2016, at 15:41, Ken Teh wrote: > > Default routes on the failing system. > >> [root@saudade ~]# ip --details route >> unicast default via 192.168.203.1 dev enp3s0 proto static scope global >> metric 100 >> unicast default via 146.139.198.1 dev enp4s0 proto static

Re: firewalld help

Default routes on the failing system. [root@saudade ~]# ip --details route unicast default via 192.168.203.1 dev enp3s0 proto static scope global metric 100 unicast default via 146.139.198.1 dev enp4s0 proto static scope global metric 101 unicast 146.139.198.0/23 dev enp4s0 proto

Re: firewalld help

Hi Ken, I have been recently learning about firewalld. Please run the commands below on your hosts to see whether they look the same or not. I hope it helps. Best regards, Sebastian * General: firewall-cmd --state # Sometimes you need to reload the firewall to get the configuration actually

Re: firewalld help

> On 10 Nov 2016, at 15:09, Ken Teh wrote: > > I'm trying to isolate a network problem and I need some debugging help. > Frustrating when I am not fluent in the new sys admin tools. > > Symptom is as follows: I have a machine running Fedora 24 with its firewall > zone set to

firewalld help

I'm trying to isolate a network problem and I need some debugging help. Frustrating when I am not fluent in the new sys admin tools. Symptom is as follows: I have a machine running Fedora 24 with its firewall zone set to work. I cannot ping the machine except from the same subnet. I don't