Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > comp.os.linux.networking > #5230 > unrolled thread
| Started by | Bit Twister <BitTwister@mouse-potato.com> |
|---|---|
| First post | 2022-12-19 04:08 -0600 |
| Last post | 2022-12-20 22:19 +0000 |
| Articles | 20 on this page of 51 — 6 participants |
Back to article view | Back to comp.os.linux.networking
ping failure, what do I check? Bit Twister <BitTwister@mouse-potato.com> - 2022-12-19 04:08 -0600
Re: ping failure, what do I check? Marco Moock <nn263@uni-heidelberg.de> - 2022-12-19 13:04 +0100
Re: ping failure, what do I check? Bit Twister <BitTwister@mouse-potato.com> - 2022-12-19 06:57 -0600
Re: ping failure, what do I check? Bit Twister <BitTwister@mouse-potato.com> - 2022-12-19 07:37 -0600
Re: ping failure, what do I check? Marco Moock <nn263@uni-heidelberg.de> - 2022-12-19 14:45 +0100
Re: ping failure, what do I check? Bit Twister <BitTwister@mouse-potato.com> - 2022-12-19 08:11 -0600
Re: ping failure, what do I check? Marco Moock <nn263@uni-heidelberg.de> - 2022-12-19 16:14 +0100
Re: ping failure, what do I check? "David W. Hodgins" <dwhodgins@nomail.afraid.org> - 2022-12-19 15:53 -0500
Re: ping failure, what do I check? Bit Twister <BitTwister@mouse-potato.com> - 2022-12-19 20:29 -0600
Re: ping failure, what do I check? "David W. Hodgins" <dwhodgins@nomail.afraid.org> - 2022-12-19 21:46 -0500
Re: ping failure, what do I check? Bit Twister <BitTwister@mouse-potato.com> - 2022-12-19 21:54 -0600
Re: ping failure, what do I check? "Carlos E. R." <robin_listas@es.invalid> - 2022-12-19 22:20 +0100
Re: ping failure, what do I check? Bit Twister <BitTwister@mouse-potato.com> - 2022-12-19 19:54 -0600
Re: ping failure, what do I check? "David W. Hodgins" <dwhodgins@nomail.afraid.org> - 2022-12-19 21:35 -0500
Re: ping failure, what do I check? Bit Twister <BitTwister@mouse-potato.com> - 2022-12-19 23:53 -0600
Re: ping failure, what do I check? "David W. Hodgins" <dwhodgins@nomail.afraid.org> - 2022-12-20 02:06 -0500
Re: ping failure, what do I check? Bit Twister <BitTwister@mouse-potato.com> - 2022-12-20 01:34 -0600
Re: ping failure, what do I check? "David W. Hodgins" <dwhodgins@nomail.afraid.org> - 2022-12-20 03:36 -0500
[solved] Re: ping failure, what do I check? Bit Twister <BitTwister@mouse-potato.com> - 2022-12-20 04:33 -0600
Re: [solved] Re: ping failure, what do I check? Marco Moock <nn263@uni-heidelberg.de> - 2022-12-20 11:40 +0100
Re: ping failure, what do I check? Bit Twister <BitTwister@mouse-potato.com> - 2022-12-20 05:19 -0600
Re: ping failure, what do I check? Bit Twister <BitTwister@mouse-potato.com> - 2022-12-20 06:20 -0600
Re: ping failure, what do I check? Marco Moock <nn263@uni-heidelberg.de> - 2022-12-20 13:33 +0100
Re: ping failure, what do I check? Bit Twister <BitTwister@mouse-potato.com> - 2022-12-20 11:22 -0600
Re: ping failure, what do I check? Marco Moock <mo01@posteo.de> - 2022-12-20 21:30 +0100
Re: ping failure, what do I check? Bit Twister <BitTwister@mouse-potato.com> - 2022-12-20 06:28 -0600
Re: ping failure, what do I check? "David W. Hodgins" <dwhodgins@nomail.afraid.org> - 2022-12-20 13:40 -0500
Re: ping failure, what do I check? "David W. Hodgins" <dwhodgins@nomail.afraid.org> - 2022-12-20 15:08 -0500
Re: ping failure, what do I check? Bit Twister <BitTwister@mouse-potato.com> - 2022-12-20 14:51 -0600
Re: ping failure, what do I check? Marco Moock <mo01@posteo.de> - 2022-12-20 21:51 +0100
Re: ping failure, what do I check? Bit Twister <BitTwister@mouse-potato.com> - 2022-12-20 15:08 -0600
Re: ping failure, what do I check? "David W. Hodgins" <dwhodgins@nomail.afraid.org> - 2022-12-20 16:31 -0500
Re: [solved] ping failure, what do I check? Bit Twister <BitTwister@mouse-potato.com> - 2022-12-20 15:54 -0600
Re: [solved] ping failure, what do I check? "David W. Hodgins" <dwhodgins@nomail.afraid.org> - 2022-12-20 17:56 -0500
Re: [solved] ping failure, what do I check? Bit Twister <BitTwister@mouse-potato.com> - 2022-12-20 18:41 -0600
Re: [solved] ping failure, what do I check? "David W. Hodgins" <dwhodgins@nomail.afraid.org> - 2022-12-20 22:39 -0500
Re: [solved] ping failure, what do I check? "David W. Hodgins" <dwhodgins@nomail.afraid.org> - 2022-12-20 18:03 -0500
Re: [solved] ping failure, what do I check? Bit Twister <BitTwister@mouse-potato.com> - 2022-12-20 18:56 -0600
Re: [solved] ping failure, what do I check? "David W. Hodgins" <dwhodgins@nomail.afraid.org> - 2022-12-20 22:52 -0500
Re: [solved] ping failure, what do I check? Bit Twister <BitTwister@mouse-potato.com> - 2022-12-20 22:23 -0600
Re: [solved] ping failure, what do I check? "David W. Hodgins" <dwhodgins@nomail.afraid.org> - 2022-12-20 23:44 -0500
Re: [solved] ping failure, what do I check? Bit Twister <BitTwister@mouse-potato.com> - 2022-12-20 23:42 -0600
Re: [solved] ping failure, what do I check? "David W. Hodgins" <dwhodgins@nomail.afraid.org> - 2022-12-21 03:07 -0500
Re: [solved] ping failure, what do I check? Bit Twister <BitTwister@mouse-potato.com> - 2022-12-21 06:28 -0600
Re: ping failure, what do I check? Marco Moock <mo01@posteo.de> - 2022-12-21 09:16 +0100
Re: ping failure, what do I check? Bit Twister <BitTwister@mouse-potato.com> - 2022-12-21 05:41 -0600
Re: ping failure, what do I check? Bit Twister <BitTwister@mouse-potato.com> - 2022-12-20 14:26 -0600
Re: ping failure, what do I check? "David W. Hodgins" <dwhodgins@nomail.afraid.org> - 2022-12-20 17:23 -0500
Re: ping failure, what do I check? Bit Twister <BitTwister@mouse-potato.com> - 2022-12-20 20:42 -0600
Re: ping failure, what do I check? "David W. Hodgins" <dwhodgins@nomail.afraid.org> - 2022-12-20 22:48 -0500
Re: ping failure, what do I check? Ted Heise <theise@panix.com> - 2022-12-20 22:19 +0000
Page 1 of 3 [1] 2 3 Next page →
| From | Bit Twister <BitTwister@mouse-potato.com> |
|---|---|
| Date | 2022-12-19 04:08 -0600 |
| Subject | ping failure, what do I check? |
| Message-ID | <slrntq0e11.k3b.BitTwister@wb.home.test> |
ping failure, what do I check? I have three nodes on the lan. wb, mtv, and tb. I have install_scripts to do system configurations so all node setups should be pretty much the same +/- network ip addresses and network cards. Firewall is shorewall and are pretty much the same. tb can ping mtv and wb. wb and mtv can not ping each other. Setting at wb terminal I have root xterms open on all three nodes via ssh. I had to ssh tb, then from tb, ssh mtv. I opened terminals on wb and mtv to constantly watch/display the system log (jpournalctl). No drop lines show up on either wb or mtv during ping failures. [root@mtv ~]# host mtv mtv.home.test has address 192.168.50.200 [root@mtv ~]# host wb wb.home.test has address 192.168.50.132 keep an eye on root prompts on the following: [root@tb ~]# ping -4c1 -w1 192.168.50.200 PING 192.168.50.200 (192.168.50.200) 56(84) bytes of data. 64 bytes from 192.168.50.200: icmp_seq=1 ttl=64 time=0.249 ms --- 192.168.50.200 ping statistics --- 1 packets transmitted, 1 received, 0% packet loss, time 0ms rtt min/avg/max/mdev = 0.249/0.249/0.249/0.000 ms [root@tb ~]# ping -4c1 -w1 192.168.50.132 PING 192.168.50.132 (192.168.50.132) 56(84) bytes of data. 64 bytes from 192.168.50.132: icmp_seq=1 ttl=64 time=0.208 ms --- 192.168.50.132 ping statistics --- 1 packets transmitted, 1 received, 0% packet loss, time 0ms rtt min/avg/max/mdev = 0.208/0.208/0.208/0.000 ms [root@mtv ~]# ping -4c1 -w1 192.168.50.132 PING 192.168.50.132 (192.168.50.132) 56(84) bytes of data. --- 192.168.50.132 ping statistics --- 1 packets transmitted, 0 received, 100% packet loss, time 0ms [root@wb ~]# ping -4c1 -w1 192.168.50.200 PING 192.168.50.200 (192.168.50.200) 56(84) bytes of data. --- 192.168.50.200 ping statistics --- 1 packets transmitted, 0 received, 100% packet loss, time 0ms I have no idea where to look to see what is causing the problem. Any suggestions? Thanks in advance for any replies. [root@mtv ~]# route -n Kernel IP routing table Destination Gateway Genmask Flags Metric Ref Use Iface 0.0.0.0 192.168.50.1 0.0.0.0 UG 1024 0 0 enp4s0 169.254.1.0 0.0.0.0 255.255.255.0 U 0 0 0 enp3s0 192.168.50.0 0.0.0.0 255.255.255.0 U 0 0 0 enp4s0 192.168.50.1 0.0.0.0 255.255.255.255 UH 1024 0 0 enp4s0 [root@wb ~]# route -n Kernel IP routing table Destination Gateway Genmask Flags Metric Ref Use Iface 0.0.0.0 192.168.50.1 0.0.0.0 UG 10 0 0 enp15s0 192.168.50.0 0.0.0.0 255.255.255.0 U 0 0 0 enp15s0
[toc] | [next] | [standalone]
| From | Marco Moock <nn263@uni-heidelberg.de> |
|---|---|
| Date | 2022-12-19 13:04 +0100 |
| Message-ID | <tnpk0a$82vd$2@dont-email.me> |
| In reply to | #5230 |
Am 19.12.2022 schrieb Bit Twister <BitTwister@mouse-potato.com>: > --- 192.168.50.200 ping statistics --- > 1 packets transmitted, 0 received, 100% packet loss, time 0ms > > > I have no idea where to look to see what is causing the problem. Check your firewalls. You can also use ARP/NDP to find out if they are online because the have to reply to these messages instead of ICMP echo request.
[toc] | [prev] | [next] | [standalone]
| From | Bit Twister <BitTwister@mouse-potato.com> |
|---|---|
| Date | 2022-12-19 06:57 -0600 |
| Message-ID | <slrntq0nte.a0hl.BitTwister@wb.home.test> |
| In reply to | #5232 |
On Mon, 19 Dec 2022 13:04:25 +0100, Marco Moock wrote: > Am 19.12.2022 schrieb Bit Twister <BitTwister@mouse-potato.com>: > >> --- 192.168.50.200 ping statistics --- >> 1 packets transmitted, 0 received, 100% packet loss, time 0ms >> >> >> I have no idea where to look to see what is causing the problem. > > Check your firewalls. Check the original post, I have opened a system log tool journalctl to display the log continusily looking for shorewall drops. I do see drops for rules to reject some packets. > You can also use ARP/NDP to find out if they are > online because the have to reply to these messages instead of ICMP echo > request. Looking like arp is working. No idea how to do something for NDP [root@wb ~]# arp | sort Address HWtype HWaddress Flags Mask Iface mtv.home.test ether 08:60:6e:44:25:56 C enp15s0 myrtr.home.test ether a4:2b:8c:09:90:f9 C enp15s0 tb.home.test ether d8:5e:d3:e4:b7:d0 C enp15s0 [root@wb ~]# arp --numeric | sort --version-sort --key=1 192.168.50.1 ether a4:2b:8c:09:90:f9 C enp15s0 192.168.50.100 ether d8:5e:d3:e4:b7:d0 C enp15s0 192.168.50.200 ether 08:60:6e:44:25:56 C enp15s0 Address HWtype HWaddress Flags Mask Iface
[toc] | [prev] | [next] | [standalone]
| From | Bit Twister <BitTwister@mouse-potato.com> |
|---|---|
| Date | 2022-12-19 07:37 -0600 |
| Message-ID | <slrntq0q9n.a5fe.BitTwister@wb.home.test> |
| In reply to | #5232 |
On Mon, 19 Dec 2022 13:04:25 +0100, Marco Moock wrote:
> Am 19.12.2022 schrieb Bit Twister <BitTwister@mouse-potato.com>:
>
>> --- 192.168.50.200 ping statistics ---
>> 1 packets transmitted, 0 received, 100% packet loss, time 0ms
>>
>>
>> I have no idea where to look to see what is causing the problem.
>
> Check your firewalls.
Did a shorewall clear on mtv and wb and still ping fails from/to either nodes.
man shorewall snippet
Clear will remove all rules and chains installed by Shorewall. The
firewall is then wide open and unprotected. Existing connections
are untouched. Clear is often used to see if the firewall is
causing connection problems.
[toc] | [prev] | [next] | [standalone]
| From | Marco Moock <nn263@uni-heidelberg.de> |
|---|---|
| Date | 2022-12-19 14:45 +0100 |
| Message-ID | <tnppt1$82vd$7@dont-email.me> |
| In reply to | #5235 |
Am 19.12.2022 schrieb Bit Twister <BitTwister@mouse-potato.com>: > Did a shorewall clear on mtv and wb and still ping fails from/to > either nodes. > > man shorewall snippet > Clear will remove all rules and chains installed by Shorewall. > The firewall is then wide open and unprotected. Existing connections > are untouched. Clear is often used to see if the firewall > is causing connection problems. Then use Wireshark/other package capture an check if the ICMP echo request packages reached the computer. Maybe it is configured to not answer the ICMP echo request.
[toc] | [prev] | [next] | [standalone]
| From | Bit Twister <BitTwister@mouse-potato.com> |
|---|---|
| Date | 2022-12-19 08:11 -0600 |
| Message-ID | <slrntq0s8g.a8b1.BitTwister@wb.home.test> |
| In reply to | #5236 |
On Mon, 19 Dec 2022 14:45:05 +0100, Marco Moock wrote: > Am 19.12.2022 schrieb Bit Twister <BitTwister@mouse-potato.com>: > >> Did a shorewall clear on mtv and wb and still ping fails from/to >> either nodes. >> >> man shorewall snippet >> Clear will remove all rules and chains installed by Shorewall. >> The firewall is then wide open and unprotected. Existing connections >> are untouched. Clear is often used to see if the firewall >> is causing connection problems. > > Then use Wireshark/other package capture an check if the ICMP echo > request packages reached the computer. Why tb can ping mtv which works. $ type uping uping is aliased to `ping -4c1 -w1' [root@tb ~]# uping mtv PING mtv.home.test (192.168.50.200) 56(84) bytes of data. 64 bytes from mtv.home.test (192.168.50.200): icmp_seq=1 ttl=64 time=0.207 ms --- mtv.home.test ping statistics --- 1 packets transmitted, 1 received, 0% packet loss, time 0ms rtt min/avg/max/mdev = 0.207/0.207/0.207/0.000 ms [root@wb ~]# uping mtv PING mtv.home.test (192.168.50.200) 56(84) bytes of data. --- mtv.home.test ping statistics --- 1 packets transmitted, 0 received, 100% packet loss, time 0ms > Maybe it is configured to not answer the ICMP echo request. No idea where that can be done other than the firewall.
[toc] | [prev] | [next] | [standalone]
| From | Marco Moock <nn263@uni-heidelberg.de> |
|---|---|
| Date | 2022-12-19 16:14 +0100 |
| Message-ID | <tnpv3s$82vd$10@dont-email.me> |
| In reply to | #5237 |
Am 19.12.2022 schrieb Bit Twister <BitTwister@mouse-potato.com>: > No idea where that can be done other than the firewall. Is there another one active? Maybe ufw or iptables?
[toc] | [prev] | [next] | [standalone]
| From | "David W. Hodgins" <dwhodgins@nomail.afraid.org> |
|---|---|
| Date | 2022-12-19 15:53 -0500 |
| Message-ID | <op.1xfyzqsca3w0dxdave@hodgins.homeip.net> |
| In reply to | #5237 |
On Mon, 19 Dec 2022 09:11:27 -0500, Bit Twister <BitTwister@mouse-potato.com> wrote: > No idea where that can be done other than the firewall. Let's look at just tb and mtv for now. On each system, what's the output of ... # ip addr |grep -e default -e 'inet ' # grep -v ^'#' /etc/shorewall/interfaces # cat /etc/shorewall/rules.drakx Regards, Dave Hodgins
[toc] | [prev] | [next] | [standalone]
| From | Bit Twister <BitTwister@mouse-potato.com> |
|---|---|
| Date | 2022-12-19 20:29 -0600 |
| Message-ID | <slrntq27gk.b5fn.BitTwister@wb.home.test> |
| In reply to | #5239 |
On Mon, 19 Dec 2022 15:53:40 -0500, David W. Hodgins wrote:
> On Mon, 19 Dec 2022 09:11:27 -0500, Bit Twister <BitTwister@mouse-potato.com> wrote:
>> No idea where that can be done other than the firewall.
>
> Let's look at just tb and mtv for now.
> On each system, what's the output of ...
> # ip addr |grep -e default -e 'inet '
> # grep -v ^'#' /etc/shorewall/interfaces
> # cat /etc/shorewall/rules.drakx
That is odd, I have guessed that with shorewall clear,
nothing in /etc/shorewall would apply, rule wise.
[root@wb ~]# ssh tb
Last login: Mon Dec 19 19:51:43 2022 from wb.home.test
ssh DISPLAY=localhost:11.0
Mageia release 8 (Official) for x86_64
FYI: Above custom message via ~/.bash_profile
===================== tb ==========================
[root@tb ~]# ip addr |grep -e default -e 'inet '
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
inet 127.0.0.1/8 scope host lo
2: enp15s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UP group default qlen 1000
inet 192.168.50.100/24 brd 192.168.50.255 scope global enp15s0
3: enp20s0u3: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UP group default qlen 1000
FYI: I make extensive use of /etc/shorewall/params so that
all shorewall settings are consistent but have any specific node changes
since my install scripts have to support my neighbor and my setup.
]# grep -v ^'#' /etc/shorewall/interfaces
net enp15s0 $NET_OPTIONS
loc enp22s0f4u1 $NET_OPTIONS
# grep NET_OPTIONS /etc/shorewall/params | grep -v ^'#'
NET_OPTIONS="" # used in /interfaces
root@tb ~]# cat /etc/shorewall/rules.drakx
[root@tb ~]# dir /etc/shorewall/rules.drakx
-rw------- 1 root root 0 Nov 4 06:55 /etc/shorewall/rules.drakx
[root@tb ~]# ssh mtv
===================== mtv ==========================
Last login: Mon Dec 19 07:28:42 2022 from tb.home.test
ssh DISPLAY=localhost:10.0
Mageia release 8 (Official) for x86_64
# ip addr |grep -e default -e 'inet '
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
inet 127.0.0.1/8 scope host lo
2: enp3s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UP group default qlen 1000
inet 169.254.1.200/24 brd 169.254.1.255 scope global enp3s0
3: enp4s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UP group default qlen 1000
inet 192.168.50.200/24 brd 192.168.50.255 scope global dynamic enp4s0
# grep -v ^'#' /etc/shorewall/interfaces
net enp4s0 $NET_OPTIONS
loc enp3s0 $NET_OPTIONS
# grep NET_OPTIONS /etc/shorewall/params | grep -v ^'#'
NET_OPTIONS="" # used in /interfaces
# cat /etc/shorewall/rules.drakx
[root@mtv ~]#
[toc] | [prev] | [next] | [standalone]
| From | "David W. Hodgins" <dwhodgins@nomail.afraid.org> |
|---|---|
| Date | 2022-12-19 21:46 -0500 |
| Message-ID | <op.1xgfbhjxa3w0dxdave@hodgins.homeip.net> |
| In reply to | #5242 |
On Mon, 19 Dec 2022 21:29:27 -0500, Bit Twister <BitTwister@mouse-potato.com> wrote: > On Mon, 19 Dec 2022 15:53:40 -0500, David W. Hodgins wrote: >> On Mon, 19 Dec 2022 09:11:27 -0500, Bit Twister <BitTwister@mouse-potato.com> wrote: >>> No idea where that can be done other than the firewall. >> >> Let's look at just tb and mtv for now. >> On each system, what's the output of ... >> # ip addr |grep -e default -e 'inet ' >> # grep -v ^'#' /etc/shorewall/interfaces >> # cat /etc/shorewall/rules.drakx > > That is odd, I have guessed that with shorewall clear, > nothing in /etc/shorewall would apply, rule wise. > > [root@wb ~]# ssh tb > Last login: Mon Dec 19 19:51:43 2022 from wb.home.test > ssh DISPLAY=localhost:11.0 > Mageia release 8 (Official) for x86_64 > > FYI: Above custom message via ~/.bash_profile > > ===================== tb ========================== > > [root@tb ~]# ip addr |grep -e default -e 'inet ' > 1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000 > inet 127.0.0.1/8 scope host lo > 2: enp15s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UP group default qlen 1000 > inet 192.168.50.100/24 brd 192.168.50.255 scope global enp15s0 > 3: enp20s0u3: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UP group default qlen 1000 > > FYI: I make extensive use of /etc/shorewall/params so that > all shorewall settings are consistent but have any specific node changes > since my install scripts have to support my neighbor and my setup. > > > ]# grep -v ^'#' /etc/shorewall/interfaces > net enp15s0 $NET_OPTIONS > loc enp22s0f4u1 $NET_OPTIONS NOTE: enp22s0f4u1 should be enp20s0u3 based on the ip addr output. > # grep NET_OPTIONS /etc/shorewall/params | grep -v ^'#' > NET_OPTIONS="" # used in /interfaces > > root@tb ~]# cat /etc/shorewall/rules.drakx > [root@tb ~]# dir /etc/shorewall/rules.drakx > -rw------- 1 root root 0 Nov 4 06:55 /etc/shorewall/rules.drakx The dir command is not cat. :-) > [root@tb ~]# ssh mtv > > ===================== mtv ========================== > > Last login: Mon Dec 19 07:28:42 2022 from tb.home.test > ssh DISPLAY=localhost:10.0 > Mageia release 8 (Official) for x86_64 > > # ip addr |grep -e default -e 'inet ' > 1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000 > inet 127.0.0.1/8 scope host lo > 2: enp3s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UP group default qlen 1000 > inet 169.254.1.200/24 brd 169.254.1.255 scope global enp3s0 > 3: enp4s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UP group default qlen 1000 > inet 192.168.50.200/24 brd 192.168.50.255 scope global dynamic enp4s0 > > # grep -v ^'#' /etc/shorewall/interfaces > net enp4s0 $NET_OPTIONS > loc enp3s0 $NET_OPTIONS > > # grep NET_OPTIONS /etc/shorewall/params | grep -v ^'#' > NET_OPTIONS="" # used in /interfaces > > > # cat /etc/shorewall/rules.drakx > [root@mtv ~]# So mtv does not have shorewall configured? Regards, Dave Hodgins
[toc] | [prev] | [next] | [standalone]
| From | Bit Twister <BitTwister@mouse-potato.com> |
|---|---|
| Date | 2022-12-19 21:54 -0600 |
| Message-ID | <slrntq2cgs.b5fn.BitTwister@wb.home.test> |
| In reply to | #5244 |
On Mon, 19 Dec 2022 21:46:19 -0500, David W. Hodgins wrote:
> On Mon, 19 Dec 2022 21:29:27 -0500, Bit Twister <BitTwister@mouse-potato.com> wrote:
>
>> [root@tb ~]# ip addr |grep -e default -e 'inet '
>> 1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
>> inet 127.0.0.1/8 scope host lo
>> 2: enp15s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UP group default qlen 1000
>> inet 192.168.50.100/24 brd 192.168.50.255 scope global enp15s0
>> 3: enp20s0u3: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UP group default qlen 1000
>>
>> FYI: I make extensive use of /etc/shorewall/params so that
>> all shorewall settings are consistent but have any specific node changes
>> since my install scripts have to support my neighbor and my setup.
>>
>>
>> ]# grep -v ^'#' /etc/shorewall/interfaces
>> net enp15s0 $NET_OPTIONS
>> loc enp22s0f4u1 $NET_OPTIONS
>
> NOTE: enp22s0f4u1 should be enp20s0u3 based on the ip addr output.
Nice catch, got a new computer last week to replace mtv.
tb is the new system. Still working out changes needed for install scripts.
That is going to save me a bunch of time trying to figure out why mythtv
is not recording shows on tb. :)
# ip addr |grep -e default -e 'inet ' snippet
3: enp20s0u3: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UP group default qlen 1000
inet 169.254.1.100/16 brd 169.254.255.255 scope global enp20s0u3
>> # grep NET_OPTIONS /etc/shorewall/params | grep -v ^'#'
>> NET_OPTIONS="" # used in /interfaces
>>
>> root@tb ~]# cat /etc/shorewall/rules.drakx
>> [root@tb ~]# dir /etc/shorewall/rules.drakx
>> -rw------- 1 root root 0 Nov 4 06:55 /etc/shorewall/rules.drakx
>
> The dir command is not cat. :-)
Yep, but I was anticipating a reply to the null output from the cat command. :-D
>> [root@tb ~]# ssh mtv
>>
>> ===================== mtv ==========================
>>
>> Last login: Mon Dec 19 07:28:42 2022 from tb.home.test
>> ssh DISPLAY=localhost:10.0
>> Mageia release 8 (Official) for x86_64
>>
>> # ip addr |grep -e default -e 'inet '
>> 1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
>> inet 127.0.0.1/8 scope host lo
>> 2: enp3s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UP group default qlen 1000
>> inet 169.254.1.200/24 brd 169.254.1.255 scope global enp3s0
>> 3: enp4s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UP group default qlen 1000
>> inet 192.168.50.200/24 brd 192.168.50.255 scope global dynamic enp4s0
>>
>> # grep -v ^'#' /etc/shorewall/interfaces
>> net enp4s0 $NET_OPTIONS
>> loc enp3s0 $NET_OPTIONS
>>
>> # grep NET_OPTIONS /etc/shorewall/params | grep -v ^'#'
>> NET_OPTIONS="" # used in /interfaces
>>
>>
>> # cat /etc/shorewall/rules.drakx
>> [root@mtv ~]#
>
> So mtv does not have shorewall configured?
Bad assumption. /etc/shorewall/rules.drakx is empty because I made no
selections during install setup.
No, same shorewall install scripts configured all nodes.
I your ""enp22s0f4u1 should be enp20s0u3" catch made me fix the
base hardware information file for tb used by install/change scripts.
[root@mtv ~]# dir /etc/shorewall/rules.drakx
-rw------- 1 root root 0 Apr 8 2021 /etc/shorewall/rules.drakx
[toc] | [prev] | [next] | [standalone]
| From | "Carlos E. R." <robin_listas@es.invalid> |
|---|---|
| Date | 2022-12-19 22:20 +0100 |
| Message-ID | <k0c2saFt2nqU4@mid.individual.net> |
| In reply to | #5230 |
On 19/12/2022 11.08, Bit Twister wrote:
> ping failure, what do I check?
>
> I have three nodes on the lan. wb, mtv, and tb.
...
> mtv.home.test has address 192.168.50.200
> wb.home.test has address 192.168.50.132
> Any suggestions?
>
> Thanks in advance for any replies.
> [root@mtv ~]# route -n
> Kernel IP routing table
> Destination Gateway Genmask Flags Metric Ref Use Iface
> 0.0.0.0 192.168.50.1 0.0.0.0 UG 1024 0 0 enp4s0
> 169.254.1.0 0.0.0.0 255.255.255.0 U 0 0 0 enp3s0
> 192.168.50.0 0.0.0.0 255.255.255.0 U 0 0 0 enp4s0
> 192.168.50.1 0.0.0.0 255.255.255.255 UH 1024 0 0 enp4s0
Why does this machine has a separate route to the gateway?
> [root@wb ~]# route -n
> Kernel IP routing table
> Destination Gateway Genmask Flags Metric Ref Use Iface
> 0.0.0.0 192.168.50.1 0.0.0.0 UG 10 0 0 enp15s0
> 192.168.50.0 0.0.0.0 255.255.255.0 U 0 0 0 enp15s0
>
--
Cheers,
Carlos E.R.
[toc] | [prev] | [next] | [standalone]
| From | Bit Twister <BitTwister@mouse-potato.com> |
|---|---|
| Date | 2022-12-19 19:54 -0600 |
| Message-ID | <slrntq25fb.b5fn.BitTwister@wb.home.test> |
| In reply to | #5240 |
On Mon, 19 Dec 2022 22:20:10 +0100, Carlos E. R. wrote: > On 19/12/2022 11.08, Bit Twister wrote: >> ping failure, what do I check? >> >> I have three nodes on the lan. wb, mtv, and tb. > > ... > >> mtv.home.test has address 192.168.50.200 >> wb.home.test has address 192.168.50.132 > > >> Any suggestions? >> >> Thanks in advance for any replies. >> [root@mtv ~]# route -n >> Kernel IP routing table >> Destination Gateway Genmask Flags Metric Ref Use Iface >> 0.0.0.0 192.168.50.1 0.0.0.0 UG 1024 0 0 enp4s0 >> 169.254.1.0 0.0.0.0 255.255.255.0 U 0 0 0 enp3s0 >> 192.168.50.0 0.0.0.0 255.255.255.0 U 0 0 0 enp4s0 >> 192.168.50.1 0.0.0.0 255.255.255.255 UH 1024 0 0 enp4s0 > > Why does this machine has a separate route to the gateway? > You ask me like I know what I am doing. :) mtv is my mythtv node where I record all my tv shows. Saves me 20+ minutes per hour of viewing because I can fast forward through commercials. The 169.254.1 range is the second nic to my other network switch where all the Over The Air Silicondust TV tuners are connected. Routing is automagically built by the nic configuration files which are used by systemd networking modules. I amazes me that I have a complex setup and know so little about what I am doing. Which reminds me to say nics on all systems are connected to network switches with the Internet nic switch hooked to my lan router. That is what stumps me logic wise. If ssh tb with ssh mtv works from wb and tb can ping mtv that tells me I do not have physical connectivity problems, and with shorewall firewall wide open/off ping should work. root@wb ~]# host tb tb.home.test has address 192.168.50.100 root@wb ~]# host mtv mtv.home.test has address 192.168.50.200 root@wb ~]# host wb wb.home.test has address 192.168.50.132 >> [root@wb ~]# route -n >> Kernel IP routing table >> Destination Gateway Genmask Flags Metric Ref Use Iface >> 0.0.0.0 192.168.50.1 0.0.0.0 UG 10 0 0 enp15s0 >> 192.168.50.0 0.0.0.0 255.255.255.0 U 0 0 0 enp15s0 >> > -- The warranty and liability expired as you read this message. If the above breaks your system, it's yours and you keep both pieces. Practice safe computing. Backup the file before you change it. Do a, man command_here or cat command_here, before using it.
[toc] | [prev] | [next] | [standalone]
| From | "David W. Hodgins" <dwhodgins@nomail.afraid.org> |
|---|---|
| Date | 2022-12-19 21:35 -0500 |
| Message-ID | <op.1xges9x1a3w0dxdave@hodgins.homeip.net> |
| In reply to | #5241 |
On Mon, 19 Dec 2022 20:54:39 -0500, Bit Twister <BitTwister@mouse-potato.com> wrote: > On Mon, 19 Dec 2022 22:20:10 +0100, Carlos E. R. wrote: >> On 19/12/2022 11.08, Bit Twister wrote: >>> ping failure, what do I check? >>> >>> I have three nodes on the lan. wb, mtv, and tb. >> >> ... >> >>> mtv.home.test has address 192.168.50.200 >>> wb.home.test has address 192.168.50.132 >> >> >>> Any suggestions? >>> >>> Thanks in advance for any replies. >>> [root@mtv ~]# route -n >>> Kernel IP routing table >>> Destination Gateway Genmask Flags Metric Ref Use Iface >>> 0.0.0.0 192.168.50.1 0.0.0.0 UG 1024 0 0 enp4s0 >>> 169.254.1.0 0.0.0.0 255.255.255.0 U 0 0 0 enp3s0 >>> 192.168.50.0 0.0.0.0 255.255.255.0 U 0 0 0 enp4s0 >>> 192.168.50.1 0.0.0.0 255.255.255.255 UH 1024 0 0 enp4s0 >> >> Why does this machine has a separate route to the gateway? >> > > You ask me like I know what I am doing. :) > > mtv is my mythtv node where I record all my tv shows. Saves me 20+ minutes per > hour of viewing because I can fast forward through commercials. > > The 169.254.1 range is the second nic to my other network switch where all > the Over The Air Silicondust TV tuners are connected. > > Routing is automagically built by the nic configuration files which are > used by systemd networking modules. I amazes me that I have a complex setup > and know so little about what I am doing. > > Which reminds me to say nics on all systems are connected to network switches > with the Internet nic switch hooked to my lan router. > > That is what stumps me logic wise. If ssh tb with ssh mtv works from wb > and tb can ping mtv that tells me I do not have physical connectivity problems, > and with shorewall firewall wide open/off ping should work. > > root@wb ~]# host tb > tb.home.test has address 192.168.50.100 > > root@wb ~]# host mtv > mtv.home.test has address 192.168.50.200 > > root@wb ~]# host wb > wb.home.test has address 192.168.50.132 > >>> [root@wb ~]# route -n >>> Kernel IP routing table >>> Destination Gateway Genmask Flags Metric Ref Use Iface >>> 0.0.0.0 192.168.50.1 0.0.0.0 UG 10 0 0 enp15s0 >>> 192.168.50.0 0.0.0.0 255.255.255.0 U 0 0 0 enp15s0 Please post the results of cat /etc/sysconfig/network-scripts/ifcfg-e* for each system. Regards, Dave Hodgins
[toc] | [prev] | [next] | [standalone]
| From | Bit Twister <BitTwister@mouse-potato.com> |
|---|---|
| Date | 2022-12-19 23:53 -0600 |
| Message-ID | <slrntq2jeu.b5fn.BitTwister@wb.home.test> |
| In reply to | #5243 |
On Mon, 19 Dec 2022 21:35:23 -0500, David W. Hodgins wrote: > Please post the results of > cat /etc/sysconfig/network-scripts/ifcfg-e* > for each system. [root@wb ~]# ssh tb Last login: Mon Dec 19 23:07:26 2022 from wb.home.test ssh DISPLAY=localhost:11.0 Mageia release 8 (Official) for x86_64 [root@tb ~]# # cat /etc/sysconfig/network-scripts/ifcfg-e* DEVICE=enp15s0 BOOTPROTO=static IPADDR=192.168.50.100 NETMASK=255.255.255.0 GATEWAY=192.168.50.1 ONBOOT=yes METRIC=10 MII_NOT_SUPPORTED=no USERCTL=no RESOLV_MODS=no LINK_DETECTION_DELAY=6 IPV6INIT=yes IPV6TO4INIT=no ACCOUNTING=no NM_CONTROLLED=no DNS1=127.0.0.1 DNS2=8.8.8.8 DOMAIN=home.test DEVICE=enp20s0u3 BOOTPROTO=static IPADDR=169.254.1.100 NETMASK=255.255.0.0 ONBOOT=yes MII_NOT_SUPPORTED=no USERCTL=no DOMAIN="home.test tuner.test" RESOLV_MODS=no IPV6INIT=yes IPV6TO4INIT=no ACCOUNTING=no NM_CONTROLLED=no ]# ssh mtv Last login: Mon Dec 19 22:09:28 2022 from tb.home.test ssh DISPLAY=localhost:10.0 Mageia release 8 (Official) for x86_64 [root@mtv ~]# # cat /etc/sysconfig/network-scripts/ifcfg-e* DEVICE=enp3s0 BOOTPROTO=static IPADDR=169.254.1.200 NETMASK=255.255.0.0 ONBOOT=yes METRIC=5 MII_NOT_SUPPORTED=no USERCTL=no NEEDHOSTNAME=no PEERDNS=no PEERYP=no PEERNTPD=no RESOLV_MODS=no LINK_DETECTION_DELAY=10 IPV6INIT=no IPV6TO4INIT=no ACCOUNTING=no NM_CONTROLLED=no DOMAIN="home.test tuner.test" DEVICE=enp4s0 BOOTPROTO=static IPADDR=192.168.11.200 NETMASK=255.255.255.0 GATEWAY=192.168.50.1 ONBOOT=yes METRIC=10 MII_NOT_SUPPORTED=no USERCTL=no DNS1=127.0.0.1 DOMAIN=google RESOLV_MODS=no LINK_DETECTION_DELAY=6 IPV6INIT=yes IPV6TO4INIT=no ACCOUNTING=no NM_CONTROLLED=no DNS2=8.8.8.8 Can only guess you will need systemd network files since that is what I use. [root@mtv ~]# cat /usr/lib/systemd/network/*__e* | grep -v "#" [Match] Name=enp4s0 [Network] Description=LAN_NIC DHCP=ipv4 DNS=127.0.0.1 Domains=home.test IPv6AcceptRouterAdvertisements=false [Address] Address=192.168.50.200/24 [Route] Gateway=192.168.11.1 [Match] Name=enp3s0 [Network] Description=TUNER_NIC IPv6AcceptRouterAdvertisements=false [Address] Address=169.254.1.200/24 [root@tb ~]# ssh mtv Last login: Mon Dec 19 21:03:48 2022 from tb.home.test ssh DISPLAY=localhost:10.0 Mageia release 8 (Official) for x86_64 [root@mtv ~] # cat /usr/lib/systemd/network/*__e* | grep -v "#" [Match] Name=enp4s0 [Network] Description=LAN_NIC DHCP=ipv4 DNS=127.0.0.1 Domains=home.test IPv6AcceptRouterAdvertisements=false [Address] Address=192.168.50.200/24 [Route] Gateway=192.168.11.1 [Match] Name=enp3s0 [Network] Description=TUNER_NIC IPv6AcceptRouterAdvertisements=false [Address] Address=169.254.1.200/24 I have found ip route to provide more significant information. my wb1 node is getting two ip addresses one of which is wb. :( Still trying to work that out. [root@mtv ~]# ip route default via 192.168.50.1 dev enp4s0 proto dhcp src 192.168.50.200 metric 1024 169.254.1.0/24 dev enp3s0 proto kernel scope link src 169.254.1.200 192.168.50.0/24 dev enp4s0 proto kernel scope link src 192.168.50.200 192.168.50.1 dev enp4s0 proto dhcp scope link src 192.168.50.200 metric 1024 [root@mtv ~]# route -n Kernel IP routing table Destination Gateway Genmask Flags Metric Ref Use Iface 169.254.1.0 0.0.0.0 255.255.255.0 U 0 0 0 enp3s0 192.168.50.0 0.0.0.0 255.255.255.0 U 0 0 0 enp4s0 Damn, confused myself as to which nic was LAN. added a GATEWAY=192.168.50.1 to /etc/sysconfig/network-scripts/ifcfg-enp4s0 and removed it from /etc/sysconfig/network-scripts/ifcfg-enp3s0 After systemctl restart network mtv can ping wb and vice versa. Off to reboot mtv and verify it still works. Nope, back to no ping and according to route -n there is no gateway route on mtv. Above file dumps are after reboot. [root@tb ~]# ip route default via 192.168.50.1 dev enp15s0 metric 10 169.254.0.0/16 dev enp20s0u3 proto kernel scope link src 169.254.1.100 192.168.50.0/24 dev enp15s0 proto kernel scope link src 192.168.50.100 # route -n Kernel IP routing table Destination Gateway Genmask Flags Metric Ref Use Iface 0.0.0.0 192.168.50.1 0.0.0.0 UG 10 0 0 enp15s0 169.254.0.0 0.0.0.0 255.255.0.0 U 0 0 enp20s0u3 192.168.50.0 0.0.0.0 255.255.255.0 U 0 0 0 enp15s0
[toc] | [prev] | [next] | [standalone]
| From | "David W. Hodgins" <dwhodgins@nomail.afraid.org> |
|---|---|
| Date | 2022-12-20 02:06 -0500 |
| Message-ID | <op.1xgrcwzja3w0dxdave@hodgins.homeip.net> |
| In reply to | #5246 |
On Tue, 20 Dec 2022 00:53:32 -0500, Bit Twister <BitTwister@mouse-potato.com> wrote: > On Mon, 19 Dec 2022 21:35:23 -0500, David W. Hodgins wrote: > >> Please post the results of >> cat /etc/sysconfig/network-scripts/ifcfg-e* >> for each system. > > [root@wb ~]# ssh tb > Last login: Mon Dec 19 23:07:26 2022 from wb.home.test > ssh DISPLAY=localhost:11.0 > Mageia release 8 (Official) for x86_64 > [root@tb ~]# > > # cat /etc/sysconfig/network-scripts/ifcfg-e* > DEVICE=enp15s0 > BOOTPROTO=static > IPADDR=192.168.50.100 > NETMASK=255.255.255.0 > GATEWAY=192.168.50.1 > ONBOOT=yes > METRIC=10 > MII_NOT_SUPPORTED=no > USERCTL=no > RESOLV_MODS=no > LINK_DETECTION_DELAY=6 > IPV6INIT=yes > IPV6TO4INIT=no > ACCOUNTING=no > NM_CONTROLLED=no > DNS1=127.0.0.1 > DNS2=8.8.8.8 > DOMAIN=home.test > > DEVICE=enp20s0u3 > BOOTPROTO=static > IPADDR=169.254.1.100 > NETMASK=255.255.0.0 > ONBOOT=yes > MII_NOT_SUPPORTED=no > USERCTL=no > DOMAIN="home.test tuner.test" > RESOLV_MODS=no > IPV6INIT=yes > IPV6TO4INIT=no > ACCOUNTING=no > NM_CONTROLLED=no > > ]# ssh mtv > Last login: Mon Dec 19 22:09:28 2022 from tb.home.test > ssh DISPLAY=localhost:10.0 > Mageia release 8 (Official) for x86_64 > > [root@mtv ~]# > # cat /etc/sysconfig/network-scripts/ifcfg-e* > > DEVICE=enp3s0 > BOOTPROTO=static > IPADDR=169.254.1.200 > NETMASK=255.255.0.0 > ONBOOT=yes > METRIC=5 > MII_NOT_SUPPORTED=no > USERCTL=no > NEEDHOSTNAME=no > PEERDNS=no > PEERYP=no > PEERNTPD=no > RESOLV_MODS=no > LINK_DETECTION_DELAY=10 > IPV6INIT=no > IPV6TO4INIT=no > ACCOUNTING=no > NM_CONTROLLED=no > DOMAIN="home.test tuner.test" > > DEVICE=enp4s0 > BOOTPROTO=static > IPADDR=192.168.11.200 > NETMASK=255.255.255.0 > GATEWAY=192.168.50.1 > ONBOOT=yes > METRIC=10 > MII_NOT_SUPPORTED=no > USERCTL=no > DNS1=127.0.0.1 > DOMAIN=google > RESOLV_MODS=no > LINK_DETECTION_DELAY=6 > IPV6INIT=yes > IPV6TO4INIT=no > ACCOUNTING=no > NM_CONTROLLED=no > DNS2=8.8.8.8 > > Can only guess you will need systemd network files since that is what > I use. > [root@mtv ~]# cat /usr/lib/systemd/network/*__e* | grep -v "#" > > [Match] > Name=enp4s0 > > [Network] > Description=LAN_NIC > DHCP=ipv4 > DNS=127.0.0.1 > Domains=home.test > IPv6AcceptRouterAdvertisements=false > > [Address] > Address=192.168.50.200/24 > > [Route] > Gateway=192.168.11.1 > > > [Match] > Name=enp3s0 > > [Network] > Description=TUNER_NIC > IPv6AcceptRouterAdvertisements=false > > [Address] > Address=169.254.1.200/24 > > > > > > [root@tb ~]# ssh mtv > Last login: Mon Dec 19 21:03:48 2022 from tb.home.test > ssh DISPLAY=localhost:10.0 > Mageia release 8 (Official) for x86_64 > [root@mtv ~] > > # cat /usr/lib/systemd/network/*__e* | grep -v "#" > > [Match] > Name=enp4s0 > > [Network] > Description=LAN_NIC > DHCP=ipv4 > DNS=127.0.0.1 > Domains=home.test > IPv6AcceptRouterAdvertisements=false > > [Address] > Address=192.168.50.200/24 > > [Route] > Gateway=192.168.11.1 > > > [Match] > Name=enp3s0 > > [Network] > Description=TUNER_NIC > IPv6AcceptRouterAdvertisements=false > > [Address] > Address=169.254.1.200/24 > > > > > I have found ip route to provide more significant information. > my wb1 node is getting two ip addresses one of which is wb. :( > Still trying to work that out. > > [root@mtv ~]# ip route > default via 192.168.50.1 dev enp4s0 proto dhcp src 192.168.50.200 metric 1024 > 169.254.1.0/24 dev enp3s0 proto kernel scope link src 169.254.1.200 > 192.168.50.0/24 dev enp4s0 proto kernel scope link src 192.168.50.200 > 192.168.50.1 dev enp4s0 proto dhcp scope link src 192.168.50.200 metric 1024 > > [root@mtv ~]# route -n > Kernel IP routing table > Destination Gateway Genmask Flags Metric Ref Use Iface > 169.254.1.0 0.0.0.0 255.255.255.0 U 0 0 0 enp3s0 > 192.168.50.0 0.0.0.0 255.255.255.0 U 0 0 0 enp4s0 > > Damn, confused myself as to which nic was LAN. > > added a GATEWAY=192.168.50.1 to /etc/sysconfig/network-scripts/ifcfg-enp4s0 > and removed it from /etc/sysconfig/network-scripts/ifcfg-enp3s0 > > After systemctl restart network mtv can ping wb and vice versa. > Off to reboot mtv and verify it still works. > > Nope, back to no ping and according to route -n there is no gateway route > on mtv. Above file dumps are after reboot. > > [root@tb ~]# ip route > default via 192.168.50.1 dev enp15s0 metric 10 > 169.254.0.0/16 dev enp20s0u3 proto kernel scope link src 169.254.1.100 > 192.168.50.0/24 dev enp15s0 proto kernel scope link src 192.168.50.100 > > # route -n > Kernel IP routing table > Destination Gateway Genmask Flags Metric Ref Use Iface > 0.0.0.0 192.168.50.1 0.0.0.0 UG 10 0 0 enp15s0 > 169.254.0.0 0.0.0.0 255.255.0.0 U 0 0 enp20s0u3 > 192.168.50.0 0.0.0.0 255.255.255.0 U 0 0 0 enp15s0 For 169.254 there's a mixing of /16 and /24 being specified. Is that intentional? If you want the lan to be totally open, you might want to consider adding ACCEPT net:10.0.0.0/8 fw ACCEPT net:169.254.0.0/16 fw ACCEPT net:172.16.0.0/12 fw ACCEPT net:192.168.0.0/16 fw for shorewall on all systems. That ensures that all posssible rfc1918 addresses are allowed full access. Not great from a security point of view, but much more convenient. Regards, Dave Hodgins
[toc] | [prev] | [next] | [standalone]
| From | Bit Twister <BitTwister@mouse-potato.com> |
|---|---|
| Date | 2022-12-20 01:34 -0600 |
| Message-ID | <slrntq2pbd.7hv.BitTwister@wb.home.test> |
| In reply to | #5247 |
On Tue, 20 Dec 2022 02:06:22 -0500, David W. Hodgins wrote: > On Tue, 20 Dec 2022 00:53:32 -0500, Bit Twister <BitTwister@mouse-potato.com> wrote: > >> On Mon, 19 Dec 2022 21:35:23 -0500, David W. Hodgins wrote: >> >>> Please post the results of >>> cat /etc/sysconfig/network-scripts/ifcfg-e* >>> for each system. >> >> [root@wb ~]# ssh tb >> Last login: Mon Dec 19 23:07:26 2022 from wb.home.test >> ssh DISPLAY=localhost:11.0 >> Mageia release 8 (Official) for x86_64 >> [root@tb ~]# >> >> # cat /etc/sysconfig/network-scripts/ifcfg-e* >> DEVICE=enp15s0 >> BOOTPROTO=static >> IPADDR=192.168.50.100 >> NETMASK=255.255.255.0 >> GATEWAY=192.168.50.1 >> ONBOOT=yes >> METRIC=10 >> MII_NOT_SUPPORTED=no >> USERCTL=no >> RESOLV_MODS=no >> LINK_DETECTION_DELAY=6 >> IPV6INIT=yes >> IPV6TO4INIT=no >> ACCOUNTING=no >> NM_CONTROLLED=no >> DNS1=127.0.0.1 >> DNS2=8.8.8.8 >> DOMAIN=home.test >> >> DEVICE=enp20s0u3 >> BOOTPROTO=static >> IPADDR=169.254.1.100 >> NETMASK=255.255.0.0 >> ONBOOT=yes >> MII_NOT_SUPPORTED=no >> USERCTL=no >> DOMAIN="home.test tuner.test" >> RESOLV_MODS=no >> IPV6INIT=yes >> IPV6TO4INIT=no >> ACCOUNTING=no >> NM_CONTROLLED=no >> >> ]# ssh mtv >> Last login: Mon Dec 19 22:09:28 2022 from tb.home.test >> ssh DISPLAY=localhost:10.0 >> Mageia release 8 (Official) for x86_64 >> >> [root@mtv ~]# >> # cat /etc/sysconfig/network-scripts/ifcfg-e* >> >> DEVICE=enp3s0 >> BOOTPROTO=static >> IPADDR=169.254.1.200 >> NETMASK=255.255.0.0 >> ONBOOT=yes >> METRIC=5 >> MII_NOT_SUPPORTED=no >> USERCTL=no >> NEEDHOSTNAME=no >> PEERDNS=no >> PEERYP=no >> PEERNTPD=no >> RESOLV_MODS=no >> LINK_DETECTION_DELAY=10 >> IPV6INIT=no >> IPV6TO4INIT=no >> ACCOUNTING=no >> NM_CONTROLLED=no >> DOMAIN="home.test tuner.test" >> >> DEVICE=enp4s0 >> BOOTPROTO=static >> IPADDR=192.168.11.200 >> NETMASK=255.255.255.0 >> GATEWAY=192.168.50.1 >> ONBOOT=yes >> METRIC=10 >> MII_NOT_SUPPORTED=no >> USERCTL=no >> DNS1=127.0.0.1 >> DOMAIN=google >> RESOLV_MODS=no >> LINK_DETECTION_DELAY=6 >> IPV6INIT=yes >> IPV6TO4INIT=no >> ACCOUNTING=no >> NM_CONTROLLED=no >> DNS2=8.8.8.8 >> >> Can only guess you will need systemd network files since that is what >> I use. >> [root@mtv ~]# cat /usr/lib/systemd/network/*__e* | grep -v "#" >> >> [Match] >> Name=enp4s0 >> >> [Network] >> Description=LAN_NIC >> DHCP=ipv4 >> DNS=127.0.0.1 >> Domains=home.test >> IPv6AcceptRouterAdvertisements=false >> >> [Address] >> Address=192.168.50.200/24 >> >> [Route] >> Gateway=192.168.11.1 >> >> >> [Match] >> Name=enp3s0 >> >> [Network] >> Description=TUNER_NIC >> IPv6AcceptRouterAdvertisements=false >> >> [Address] >> Address=169.254.1.200/24 >> >> >> >> >> >> [root@tb ~]# ssh mtv >> Last login: Mon Dec 19 21:03:48 2022 from tb.home.test >> ssh DISPLAY=localhost:10.0 >> Mageia release 8 (Official) for x86_64 >> [root@mtv ~] >> >> # cat /usr/lib/systemd/network/*__e* | grep -v "#" >> >> [Match] >> Name=enp4s0 >> >> [Network] >> Description=LAN_NIC >> DHCP=ipv4 >> DNS=127.0.0.1 >> Domains=home.test >> IPv6AcceptRouterAdvertisements=false >> >> [Address] >> Address=192.168.50.200/24 >> >> [Route] >> Gateway=192.168.11.1 >> >> >> [Match] >> Name=enp3s0 >> >> [Network] >> Description=TUNER_NIC >> IPv6AcceptRouterAdvertisements=false >> >> [Address] >> Address=169.254.1.200/24 >> >> >> >> >> I have found ip route to provide more significant information. >> my wb1 node is getting two ip addresses one of which is wb. :( >> Still trying to work that out. >> >> [root@mtv ~]# ip route >> default via 192.168.50.1 dev enp4s0 proto dhcp src 192.168.50.200 metric 1024 >> 169.254.1.0/24 dev enp3s0 proto kernel scope link src 169.254.1.200 >> 192.168.50.0/24 dev enp4s0 proto kernel scope link src 192.168.50.200 >> 192.168.50.1 dev enp4s0 proto dhcp scope link src 192.168.50.200 metric 1024 >> >> [root@mtv ~]# route -n >> Kernel IP routing table >> Destination Gateway Genmask Flags Metric Ref Use Iface >> 169.254.1.0 0.0.0.0 255.255.255.0 U 0 0 0 enp3s0 >> 192.168.50.0 0.0.0.0 255.255.255.0 U 0 0 0 enp4s0 >> >> Damn, confused myself as to which nic was LAN. >> >> added a GATEWAY=192.168.50.1 to /etc/sysconfig/network-scripts/ifcfg-enp4s0 >> and removed it from /etc/sysconfig/network-scripts/ifcfg-enp3s0 >> >> After systemctl restart network mtv can ping wb and vice versa. >> Off to reboot mtv and verify it still works. >> >> Nope, back to no ping and according to route -n there is no gateway route >> on mtv. Above file dumps are after reboot. >> >> [root@tb ~]# ip route >> default via 192.168.50.1 dev enp15s0 metric 10 >> 169.254.0.0/16 dev enp20s0u3 proto kernel scope link src 169.254.1.100 >> 192.168.50.0/24 dev enp15s0 proto kernel scope link src 192.168.50.100 >> >> # route -n >> Kernel IP routing table >> Destination Gateway Genmask Flags Metric Ref Use Iface >> 0.0.0.0 192.168.50.1 0.0.0.0 UG 10 0 0 enp15s0 >> 169.254.0.0 0.0.0.0 255.255.0.0 U 0 0 0 enp20s0u3 >> 192.168.50.0 0.0.0.0 255.255.255.0 U 0 0 0 enp15s0 > > For 169.254 there's a mixing of /16 and /24 being specified. Is that intentional? Not on my part and that is on tb. Just a result of some setting in some file by some app. Since I have very little idea about who is doing what from where, it is pretty hard fix it except play around with network and systemd config files. I can not even get a gateway (UG) set correctly on mtv. mtv ~]$ route -n Kernel IP routing table Destination Gateway Genmask Flags Metric Ref Use Iface 169.254.1.0 0.0.0.0 255.255.255.0 U 0 0 0 enp3s0 192.168.50.0 0.0.0.0 255.255.255.0 U 0 0 0 enp4s0 mtv txt]$ grep gate /etc/sysconfig/network-scripts/ifcfg-e* /etc/sysconfig/network-scripts/ifcfg-enp4s0:GATEWAY=192.168.50.1 mtv txt]$ grep gate /usr/lib/systemd/network/*__e* /usr/lib/systemd/network/10_xx__enp4s0.network: Gateway=192.168.11.1
[toc] | [prev] | [next] | [standalone]
| From | "David W. Hodgins" <dwhodgins@nomail.afraid.org> |
|---|---|
| Date | 2022-12-20 03:36 -0500 |
| Message-ID | <op.1xgvivl3a3w0dxdave@hodgins.homeip.net> |
| In reply to | #5248 |
On Tue, 20 Dec 2022 02:34:02 -0500, Bit Twister <BitTwister@mouse-potato.com> wrote: > Not on my part and that is on tb. Just a result of some setting in some > file by some app. > > Since I have very little idea about who is doing what from where, it is > pretty hard fix it except play around with network and systemd config files. There are four ways normal networking can be configured in Mageia. First was drakx-net. Second, avahi which handles zeroconf network configuration, typically used by smartphones and apple computers. That's the 169.254.0.0/16 addresses. https://en.wikipedia.org/wiki/Zero-configuration_networking Third, networkmanager was added. Fourth, systemd-networkd.service. The installer only handles drakx-net or networkmanager. They cannot both be used on a given install. The drakx-net method is being deprecated and will likely be removed in Mageia 10 as it doesn't seem to work well with ipv6, and networkmanager will likely become the only choice in the installer. While the installer doesn't handle configuring it (no config needed), avahi is installed and activated too. systemd-networkd can be used by itself, but that causes problems with applications that expect either drakx-net or networkmanager. It can be used in at the same time as drakx-net, if done correctly. I do that on some of my installs to get ipv6 working without using networkmanager. For avahi, I've never bothered looking into it's configuration files. I just disable it. # grep MII /etc/sysconfig/network-scripts/ifcfg-e* MII_NOT_SUPPORTED=yes The MII stands for Media Independent Interface, which is another name for zeroconf. Most likely one of the avahi configuration files on tb has been altered to restrict it to a /24 instead of it's default of using /16. Don't do that. If the alteration wasn't intention you may want to remove avahi using "rpm -e --nodeps avahi" and then reinstall avahi. The old config files will be kept with the .rpmsave suffix. I'll review the rest of the article tomorrow. Regards, Dave Hodgins
[toc] | [prev] | [next] | [standalone]
| From | Bit Twister <BitTwister@mouse-potato.com> |
|---|---|
| Date | 2022-12-20 04:33 -0600 |
| Subject | [solved] Re: ping failure, what do I check? |
| Message-ID | <slrntq33rg.i3m.BitTwister@wb.home.test> |
| In reply to | #5249 |
On Tue, 20 Dec 2022 03:36:21 -0500, David W. Hodgins wrote: > On Tue, 20 Dec 2022 02:34:02 -0500, Bit Twister <BitTwister@mouse-potato.com> wrote: >> Not on my part and that is on tb. Just a result of some setting in some >> file by some app. >> >> Since I have very little idea about who is doing what from where, it is >> pretty hard fix it except play around with network and systemd config files. > > There are four ways normal networking can be configured in Mageia. Yeah, but I configured/enabled systemd-netwoked and thought it was in control. Starting to look like I missed something. The SOLUTION to the ping problem was no gateway (UG) line seen in route -n $ route -n Kernel IP routing table Destination Gateway Genmask Flags Metric Ref Use Iface 0.0.0.0 192.168.50.1 0.0.0.0 UG 10 0 0 enp4s0 169.254.1.0 0.0.0.0 255.255.255.0 U 0 0 0 enp3s0 192.168.50.0 0.0.0.0 255.255.255.0 U 0 0 0 enp4s0 Once I got a gateway defined, doing a systemd restart network, ping started working. > > For avahi, I've never bothered looking into it's configuration files. I just > disable it. > # grep MII /etc/sysconfig/network-scripts/ifcfg-e* > MII_NOT_SUPPORTED=yes > The MII stands for Media Independent Interface, which is another name for > zeroconf. Thanks changed scripts to set MII_NOT_SUPPORTED=yes I thought I had disabled it by getting rid of mdms stuff in /etc/nsswitch.conf $ grep hosts: /etc/nsswitch.conf # hosts: mdns4_minimal files nis dns mdns4 myhostname hosts: files dns myhostname > > Most likely one of the avahi configuration files on tb has been altered to > restrict it to a /24 instead of it's default of using /16. Don't do that. I THINK it was a NETMASK setting in one of the /etc/sysconfig/network-scripts/ifcfg-e* set NETMASK=255.255.0.0 which I changed to NETMASK=255.255.255.0 See above route dump.
[toc] | [prev] | [next] | [standalone]
| From | Marco Moock <nn263@uni-heidelberg.de> |
|---|---|
| Date | 2022-12-20 11:40 +0100 |
| Subject | Re: [solved] Re: ping failure, what do I check? |
| Message-ID | <tns3fk$kojb$6@dont-email.me> |
| In reply to | #5250 |
Am 20.12.2022 schrieb Bit Twister <BitTwister@mouse-potato.com>: > The SOLUTION to the ping problem was no gateway (UG) line seen in > route -n > $ route -n > Kernel IP routing table > Destination Gateway Genmask Flags Metric Ref > Use Iface 0.0.0.0 192.168.50.1 0.0.0.0 UG 10 > 0 0 enp4s0 169.254.1.0 0.0.0.0 255.255.255.0 U > 0 0 0 enp3s0 192.168.50.0 0.0.0.0 > 255.255.255.0 U 0 0 0 enp4s0 The line "destination 0.0.0.0/0" is the equivalent to the IPv4 default gateway. > Once I got a gateway defined, doing a systemd restart network, ping > started working. How does your routing table now look like? If no route exists, there should be an ICMP message.
[toc] | [prev] | [next] | [standalone]
Page 1 of 3 [1] 2 3 Next page →
Back to top | Article view | comp.os.linux.networking
csiph-web