Redhat route InfiniBand problem
Clash Royale CLAN TAG#URR8PPP
I have a system (HPC) have
1 headnode (192.168.2.2)
10 node and (192.168.245-254)
1 NFS server (192.168.2.244).
My headnode can't ping to NFS server but from NFS server I can ping to headnode.
I already disable firewall in 2 PC but it still didn't work.
HeadNode
route -n (192.168.2.2)
[root@cluster ~]# route -n
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use Iface
172.16.39.0 0.0.0.0 255.255.255.0 U 0 0 0 vmnet1
192.168.2.0 0.0.0.0 255.255.255.0 U 0 0 0 ib0
192.168.2.0 0.0.0.0 255.255.255.0 U 0 0 0 em1
172.16.112.0 0.0.0.0 255.255.255.0 U 0 0 0 vmnet8
10.10.41.0 0.0.0.0 255.255.255.0 U 0 0 0 em2
192.168.122.0 0.0.0.0 255.255.255.0 U 0 0 0 virbr0
10.10.10.0 0.0.0.0 255.255.254.0 U 0 0 0 pem3
169.254.0.0 0.0.0.0 255.255.0.0 U 1006 0 0 ib0
169.254.0.0 0.0.0.0 255.255.0.0 U 1030 0 0 em1
0.0.0.0 10.10.10.1 0.0.0.0 UG 0 0 0 pem3
arp -a
[root@cluster ~]# arp -a
compute-0-5.local (192.168.2.249) at 48:00:00:80:fe:80:00:00:00 [infiniband] on ib0
? (10.10.41.1) at <incomplete> on em2
compute-0-0.local (192.168.2.254) at 48:00:00:80:fe:80:00:00:00 [infiniband] on ib0
compute-0-3.local (192.168.2.251) at 48:00:00:80:fe:80:00:00:00 [infiniband] on ib0
compute-0-4.local (192.168.2.250) at 48:00:00:80:fe:80:00:00:00 [infiniband] on ib0
compute-0-7.local (192.168.2.247) at 48:00:00:80:fe:80:00:00:00 [infiniband] on ib0
? (10.10.10.218) at f8:28:19:1f:22:33 [ether] on pem3
? (10.10.11.17) at 88:e9:fe:70:25:26 [ether] on pem3
compute-0-6.local (192.168.2.248) at 48:00:00:80:fe:80:00:00:00 [infiniband] on ib0
compute-0-1.local (192.168.2.253) at 48:00:00:80:fe:80:00:00:00 [infiniband] on ib0
? (10.10.10.47) at c0:cb:38:3e:72:6d [ether] on pem3
? (10.10.10.1) at 1c:df:0f:b7:11:3f [ether] on pem3
compute-0-2.local (192.168.2.252) at 48:00:00:80:fe:80:00:00:00 [infiniband] on ib0
rockscluster-nfs (192.168.2.244) at <incomplete> on ib0
It can't connect to IP 192.168.2.244
NFS server
route -n
[root@rockscluster-nfs ~]# route -n
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use Iface
0.0.0.0 10.10.40.1 0.0.0.0 UG 100 0 0 em1
10.10.40.1 0.0.0.0 255.255.255.255 UH 100 0 0 em1
10.10.41.0 0.0.0.0 255.255.255.0 U 100 0 0 em1
192.168.2.0 0.0.0.0 255.255.255.0 U 150 0 0 ib0
192.168.122.0 0.0.0.0 255.255.255.0 U 0 0 0 virbr0
arp -a
[root@rockscluster-nfs ~]# arp -a
? (192.168.2.250) at 48:00:00:80:fe:80:00:00:00 [infiniband] on ib0
gateway (10.10.40.1) at <incomplete> on em1
? (192.168.2.253) at 48:00:00:80:fe:80:00:00:00 [infiniband] on ib0
? (192.168.2.248) at 48:00:00:80:fe:80:00:00:00 [infiniband] on ib0
? (10.10.41.149) at <incomplete> on em1
? (192.168.2.251) at 48:00:00:80:fe:80:00:00:00 [infiniband] on ib0
? (10.10.41.223) at a0:48:1c:df:f8:86 [ether] on em1
? (10.10.41.119) at 80:18:44:e6:48:9d [ether] on em1
? (10.10.41.1) at <incomplete> on em1
? (192.168.2.254) at 48:00:00:80:fe:80:00:00:00 [infiniband] on ib0
? (10.10.11.209) at d8:9e:f3:18:39:26 [ether] on em1
? (192.168.2.249) at 48:00:00:80:fe:80:00:00:00 [infiniband] on ib0
? (192.168.2.252) at 48:00:00:80:fe:80:00:00:00 [infiniband] on ib0
? (192.168.2.247) at 48:00:00:80:fe:80:00:00:00 [infiniband] on ib0
? (192.168.2.2) at 48:00:00:80:fe:80:00:00:00 [infiniband] on ib0
linux rhel route
add a comment |
I have a system (HPC) have
1 headnode (192.168.2.2)
10 node and (192.168.245-254)
1 NFS server (192.168.2.244).
My headnode can't ping to NFS server but from NFS server I can ping to headnode.
I already disable firewall in 2 PC but it still didn't work.
HeadNode
route -n (192.168.2.2)
[root@cluster ~]# route -n
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use Iface
172.16.39.0 0.0.0.0 255.255.255.0 U 0 0 0 vmnet1
192.168.2.0 0.0.0.0 255.255.255.0 U 0 0 0 ib0
192.168.2.0 0.0.0.0 255.255.255.0 U 0 0 0 em1
172.16.112.0 0.0.0.0 255.255.255.0 U 0 0 0 vmnet8
10.10.41.0 0.0.0.0 255.255.255.0 U 0 0 0 em2
192.168.122.0 0.0.0.0 255.255.255.0 U 0 0 0 virbr0
10.10.10.0 0.0.0.0 255.255.254.0 U 0 0 0 pem3
169.254.0.0 0.0.0.0 255.255.0.0 U 1006 0 0 ib0
169.254.0.0 0.0.0.0 255.255.0.0 U 1030 0 0 em1
0.0.0.0 10.10.10.1 0.0.0.0 UG 0 0 0 pem3
arp -a
[root@cluster ~]# arp -a
compute-0-5.local (192.168.2.249) at 48:00:00:80:fe:80:00:00:00 [infiniband] on ib0
? (10.10.41.1) at <incomplete> on em2
compute-0-0.local (192.168.2.254) at 48:00:00:80:fe:80:00:00:00 [infiniband] on ib0
compute-0-3.local (192.168.2.251) at 48:00:00:80:fe:80:00:00:00 [infiniband] on ib0
compute-0-4.local (192.168.2.250) at 48:00:00:80:fe:80:00:00:00 [infiniband] on ib0
compute-0-7.local (192.168.2.247) at 48:00:00:80:fe:80:00:00:00 [infiniband] on ib0
? (10.10.10.218) at f8:28:19:1f:22:33 [ether] on pem3
? (10.10.11.17) at 88:e9:fe:70:25:26 [ether] on pem3
compute-0-6.local (192.168.2.248) at 48:00:00:80:fe:80:00:00:00 [infiniband] on ib0
compute-0-1.local (192.168.2.253) at 48:00:00:80:fe:80:00:00:00 [infiniband] on ib0
? (10.10.10.47) at c0:cb:38:3e:72:6d [ether] on pem3
? (10.10.10.1) at 1c:df:0f:b7:11:3f [ether] on pem3
compute-0-2.local (192.168.2.252) at 48:00:00:80:fe:80:00:00:00 [infiniband] on ib0
rockscluster-nfs (192.168.2.244) at <incomplete> on ib0
It can't connect to IP 192.168.2.244
NFS server
route -n
[root@rockscluster-nfs ~]# route -n
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use Iface
0.0.0.0 10.10.40.1 0.0.0.0 UG 100 0 0 em1
10.10.40.1 0.0.0.0 255.255.255.255 UH 100 0 0 em1
10.10.41.0 0.0.0.0 255.255.255.0 U 100 0 0 em1
192.168.2.0 0.0.0.0 255.255.255.0 U 150 0 0 ib0
192.168.122.0 0.0.0.0 255.255.255.0 U 0 0 0 virbr0
arp -a
[root@rockscluster-nfs ~]# arp -a
? (192.168.2.250) at 48:00:00:80:fe:80:00:00:00 [infiniband] on ib0
gateway (10.10.40.1) at <incomplete> on em1
? (192.168.2.253) at 48:00:00:80:fe:80:00:00:00 [infiniband] on ib0
? (192.168.2.248) at 48:00:00:80:fe:80:00:00:00 [infiniband] on ib0
? (10.10.41.149) at <incomplete> on em1
? (192.168.2.251) at 48:00:00:80:fe:80:00:00:00 [infiniband] on ib0
? (10.10.41.223) at a0:48:1c:df:f8:86 [ether] on em1
? (10.10.41.119) at 80:18:44:e6:48:9d [ether] on em1
? (10.10.41.1) at <incomplete> on em1
? (192.168.2.254) at 48:00:00:80:fe:80:00:00:00 [infiniband] on ib0
? (10.10.11.209) at d8:9e:f3:18:39:26 [ether] on em1
? (192.168.2.249) at 48:00:00:80:fe:80:00:00:00 [infiniband] on ib0
? (192.168.2.252) at 48:00:00:80:fe:80:00:00:00 [infiniband] on ib0
? (192.168.2.247) at 48:00:00:80:fe:80:00:00:00 [infiniband] on ib0
? (192.168.2.2) at 48:00:00:80:fe:80:00:00:00 [infiniband] on ib0
linux rhel route
2
I can see two network cards using the same IP LAN (ib0 and em1 on same 192.168.2.0/24). That's usually not done, because this can cause "arp flux" issues at best, or worse (if the cards aren't actually seing each others). Also, when a question is put on hold, that's to ask you yo clarify it. This question is probably related to unix.stackexchange.com/questions/490923/… , so answerers can get a better picture.
– A.B
Dec 27 '18 at 9:49
add a comment |
I have a system (HPC) have
1 headnode (192.168.2.2)
10 node and (192.168.245-254)
1 NFS server (192.168.2.244).
My headnode can't ping to NFS server but from NFS server I can ping to headnode.
I already disable firewall in 2 PC but it still didn't work.
HeadNode
route -n (192.168.2.2)
[root@cluster ~]# route -n
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use Iface
172.16.39.0 0.0.0.0 255.255.255.0 U 0 0 0 vmnet1
192.168.2.0 0.0.0.0 255.255.255.0 U 0 0 0 ib0
192.168.2.0 0.0.0.0 255.255.255.0 U 0 0 0 em1
172.16.112.0 0.0.0.0 255.255.255.0 U 0 0 0 vmnet8
10.10.41.0 0.0.0.0 255.255.255.0 U 0 0 0 em2
192.168.122.0 0.0.0.0 255.255.255.0 U 0 0 0 virbr0
10.10.10.0 0.0.0.0 255.255.254.0 U 0 0 0 pem3
169.254.0.0 0.0.0.0 255.255.0.0 U 1006 0 0 ib0
169.254.0.0 0.0.0.0 255.255.0.0 U 1030 0 0 em1
0.0.0.0 10.10.10.1 0.0.0.0 UG 0 0 0 pem3
arp -a
[root@cluster ~]# arp -a
compute-0-5.local (192.168.2.249) at 48:00:00:80:fe:80:00:00:00 [infiniband] on ib0
? (10.10.41.1) at <incomplete> on em2
compute-0-0.local (192.168.2.254) at 48:00:00:80:fe:80:00:00:00 [infiniband] on ib0
compute-0-3.local (192.168.2.251) at 48:00:00:80:fe:80:00:00:00 [infiniband] on ib0
compute-0-4.local (192.168.2.250) at 48:00:00:80:fe:80:00:00:00 [infiniband] on ib0
compute-0-7.local (192.168.2.247) at 48:00:00:80:fe:80:00:00:00 [infiniband] on ib0
? (10.10.10.218) at f8:28:19:1f:22:33 [ether] on pem3
? (10.10.11.17) at 88:e9:fe:70:25:26 [ether] on pem3
compute-0-6.local (192.168.2.248) at 48:00:00:80:fe:80:00:00:00 [infiniband] on ib0
compute-0-1.local (192.168.2.253) at 48:00:00:80:fe:80:00:00:00 [infiniband] on ib0
? (10.10.10.47) at c0:cb:38:3e:72:6d [ether] on pem3
? (10.10.10.1) at 1c:df:0f:b7:11:3f [ether] on pem3
compute-0-2.local (192.168.2.252) at 48:00:00:80:fe:80:00:00:00 [infiniband] on ib0
rockscluster-nfs (192.168.2.244) at <incomplete> on ib0
It can't connect to IP 192.168.2.244
NFS server
route -n
[root@rockscluster-nfs ~]# route -n
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use Iface
0.0.0.0 10.10.40.1 0.0.0.0 UG 100 0 0 em1
10.10.40.1 0.0.0.0 255.255.255.255 UH 100 0 0 em1
10.10.41.0 0.0.0.0 255.255.255.0 U 100 0 0 em1
192.168.2.0 0.0.0.0 255.255.255.0 U 150 0 0 ib0
192.168.122.0 0.0.0.0 255.255.255.0 U 0 0 0 virbr0
arp -a
[root@rockscluster-nfs ~]# arp -a
? (192.168.2.250) at 48:00:00:80:fe:80:00:00:00 [infiniband] on ib0
gateway (10.10.40.1) at <incomplete> on em1
? (192.168.2.253) at 48:00:00:80:fe:80:00:00:00 [infiniband] on ib0
? (192.168.2.248) at 48:00:00:80:fe:80:00:00:00 [infiniband] on ib0
? (10.10.41.149) at <incomplete> on em1
? (192.168.2.251) at 48:00:00:80:fe:80:00:00:00 [infiniband] on ib0
? (10.10.41.223) at a0:48:1c:df:f8:86 [ether] on em1
? (10.10.41.119) at 80:18:44:e6:48:9d [ether] on em1
? (10.10.41.1) at <incomplete> on em1
? (192.168.2.254) at 48:00:00:80:fe:80:00:00:00 [infiniband] on ib0
? (10.10.11.209) at d8:9e:f3:18:39:26 [ether] on em1
? (192.168.2.249) at 48:00:00:80:fe:80:00:00:00 [infiniband] on ib0
? (192.168.2.252) at 48:00:00:80:fe:80:00:00:00 [infiniband] on ib0
? (192.168.2.247) at 48:00:00:80:fe:80:00:00:00 [infiniband] on ib0
? (192.168.2.2) at 48:00:00:80:fe:80:00:00:00 [infiniband] on ib0
linux rhel route
I have a system (HPC) have
1 headnode (192.168.2.2)
10 node and (192.168.245-254)
1 NFS server (192.168.2.244).
My headnode can't ping to NFS server but from NFS server I can ping to headnode.
I already disable firewall in 2 PC but it still didn't work.
HeadNode
route -n (192.168.2.2)
[root@cluster ~]# route -n
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use Iface
172.16.39.0 0.0.0.0 255.255.255.0 U 0 0 0 vmnet1
192.168.2.0 0.0.0.0 255.255.255.0 U 0 0 0 ib0
192.168.2.0 0.0.0.0 255.255.255.0 U 0 0 0 em1
172.16.112.0 0.0.0.0 255.255.255.0 U 0 0 0 vmnet8
10.10.41.0 0.0.0.0 255.255.255.0 U 0 0 0 em2
192.168.122.0 0.0.0.0 255.255.255.0 U 0 0 0 virbr0
10.10.10.0 0.0.0.0 255.255.254.0 U 0 0 0 pem3
169.254.0.0 0.0.0.0 255.255.0.0 U 1006 0 0 ib0
169.254.0.0 0.0.0.0 255.255.0.0 U 1030 0 0 em1
0.0.0.0 10.10.10.1 0.0.0.0 UG 0 0 0 pem3
arp -a
[root@cluster ~]# arp -a
compute-0-5.local (192.168.2.249) at 48:00:00:80:fe:80:00:00:00 [infiniband] on ib0
? (10.10.41.1) at <incomplete> on em2
compute-0-0.local (192.168.2.254) at 48:00:00:80:fe:80:00:00:00 [infiniband] on ib0
compute-0-3.local (192.168.2.251) at 48:00:00:80:fe:80:00:00:00 [infiniband] on ib0
compute-0-4.local (192.168.2.250) at 48:00:00:80:fe:80:00:00:00 [infiniband] on ib0
compute-0-7.local (192.168.2.247) at 48:00:00:80:fe:80:00:00:00 [infiniband] on ib0
? (10.10.10.218) at f8:28:19:1f:22:33 [ether] on pem3
? (10.10.11.17) at 88:e9:fe:70:25:26 [ether] on pem3
compute-0-6.local (192.168.2.248) at 48:00:00:80:fe:80:00:00:00 [infiniband] on ib0
compute-0-1.local (192.168.2.253) at 48:00:00:80:fe:80:00:00:00 [infiniband] on ib0
? (10.10.10.47) at c0:cb:38:3e:72:6d [ether] on pem3
? (10.10.10.1) at 1c:df:0f:b7:11:3f [ether] on pem3
compute-0-2.local (192.168.2.252) at 48:00:00:80:fe:80:00:00:00 [infiniband] on ib0
rockscluster-nfs (192.168.2.244) at <incomplete> on ib0
It can't connect to IP 192.168.2.244
NFS server
route -n
[root@rockscluster-nfs ~]# route -n
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use Iface
0.0.0.0 10.10.40.1 0.0.0.0 UG 100 0 0 em1
10.10.40.1 0.0.0.0 255.255.255.255 UH 100 0 0 em1
10.10.41.0 0.0.0.0 255.255.255.0 U 100 0 0 em1
192.168.2.0 0.0.0.0 255.255.255.0 U 150 0 0 ib0
192.168.122.0 0.0.0.0 255.255.255.0 U 0 0 0 virbr0
arp -a
[root@rockscluster-nfs ~]# arp -a
? (192.168.2.250) at 48:00:00:80:fe:80:00:00:00 [infiniband] on ib0
gateway (10.10.40.1) at <incomplete> on em1
? (192.168.2.253) at 48:00:00:80:fe:80:00:00:00 [infiniband] on ib0
? (192.168.2.248) at 48:00:00:80:fe:80:00:00:00 [infiniband] on ib0
? (10.10.41.149) at <incomplete> on em1
? (192.168.2.251) at 48:00:00:80:fe:80:00:00:00 [infiniband] on ib0
? (10.10.41.223) at a0:48:1c:df:f8:86 [ether] on em1
? (10.10.41.119) at 80:18:44:e6:48:9d [ether] on em1
? (10.10.41.1) at <incomplete> on em1
? (192.168.2.254) at 48:00:00:80:fe:80:00:00:00 [infiniband] on ib0
? (10.10.11.209) at d8:9e:f3:18:39:26 [ether] on em1
? (192.168.2.249) at 48:00:00:80:fe:80:00:00:00 [infiniband] on ib0
? (192.168.2.252) at 48:00:00:80:fe:80:00:00:00 [infiniband] on ib0
? (192.168.2.247) at 48:00:00:80:fe:80:00:00:00 [infiniband] on ib0
? (192.168.2.2) at 48:00:00:80:fe:80:00:00:00 [infiniband] on ib0
linux rhel route
linux rhel route
edited Dec 27 '18 at 9:35
Rui F Ribeiro
39.3k1479131
39.3k1479131
asked Dec 27 '18 at 7:19
Le TrieuLe Trieu
62
62
2
I can see two network cards using the same IP LAN (ib0 and em1 on same 192.168.2.0/24). That's usually not done, because this can cause "arp flux" issues at best, or worse (if the cards aren't actually seing each others). Also, when a question is put on hold, that's to ask you yo clarify it. This question is probably related to unix.stackexchange.com/questions/490923/… , so answerers can get a better picture.
– A.B
Dec 27 '18 at 9:49
add a comment |
2
I can see two network cards using the same IP LAN (ib0 and em1 on same 192.168.2.0/24). That's usually not done, because this can cause "arp flux" issues at best, or worse (if the cards aren't actually seing each others). Also, when a question is put on hold, that's to ask you yo clarify it. This question is probably related to unix.stackexchange.com/questions/490923/… , so answerers can get a better picture.
– A.B
Dec 27 '18 at 9:49
2
2
I can see two network cards using the same IP LAN (ib0 and em1 on same 192.168.2.0/24). That's usually not done, because this can cause "arp flux" issues at best, or worse (if the cards aren't actually seing each others). Also, when a question is put on hold, that's to ask you yo clarify it. This question is probably related to unix.stackexchange.com/questions/490923/… , so answerers can get a better picture.
– A.B
Dec 27 '18 at 9:49
I can see two network cards using the same IP LAN (ib0 and em1 on same 192.168.2.0/24). That's usually not done, because this can cause "arp flux" issues at best, or worse (if the cards aren't actually seing each others). Also, when a question is put on hold, that's to ask you yo clarify it. This question is probably related to unix.stackexchange.com/questions/490923/… , so answerers can get a better picture.
– A.B
Dec 27 '18 at 9:49
add a comment |
0
active
oldest
votes
Your Answer
StackExchange.ready(function()
var channelOptions =
tags: "".split(" "),
id: "106"
;
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function()
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled)
StackExchange.using("snippets", function()
createEditor();
);
else
createEditor();
);
function createEditor()
StackExchange.prepareEditor(
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: false,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: null,
bindNavPrevention: true,
postfix: "",
imageUploader:
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
,
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
);
);
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f491084%2fredhat-route-infiniband-problem%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
0
active
oldest
votes
0
active
oldest
votes
active
oldest
votes
active
oldest
votes
Thanks for contributing an answer to Unix & Linux Stack Exchange!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Some of your past answers have not been well-received, and you're in danger of being blocked from answering.
Please pay close attention to the following guidance:
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f491084%2fredhat-route-infiniband-problem%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
2
I can see two network cards using the same IP LAN (ib0 and em1 on same 192.168.2.0/24). That's usually not done, because this can cause "arp flux" issues at best, or worse (if the cards aren't actually seing each others). Also, when a question is put on hold, that's to ask you yo clarify it. This question is probably related to unix.stackexchange.com/questions/490923/… , so answerers can get a better picture.
– A.B
Dec 27 '18 at 9:49