FireBall
asked on
Emergency & Advanced Multihomed CentOs routing issue
Hello ,
I have a problem with interfaces on a multihomed topology. My interfaces can not ping each other and can not ping theirselves too
sysctl as given below.
But it is able to ping the interface ip when i directly write ping 37.123.98.142 , if the both interface are not able to ping this interface's ip how does it ping it or from where ?
I have to let them have access each other how shoud i do it ?
Note: loopback interface activated
Note2: em interfaces are all down
I have a problem with interfaces on a multihomed topology. My interfaces can not ping each other and can not ping theirselves too
sysctl as given below.
But it is able to ping the interface ip when i directly write ping 37.123.98.142 , if the both interface are not able to ping this interface's ip how does it ping it or from where ?
I have to let them have access each other how shoud i do it ?
Note: loopback interface activated
Note2: em interfaces are all down
[root@spd network-scripts]# sysctl -p
net.ipv4.ip_forward = 1
net.ipv4.conf.p1p1.rp_filter = 2
net.ipv4.conf.p1p2.rp_filter = 2
net.ipv4.conf.all.rp_filter = 2
net.ipv4.conf.default.rp_filter = 2
net.ipv4.conf.lo.rp_filter = 2
net.ipv4.conf.p1p1.accept_local = 1
net.ipv4.conf.p1p2.accept_local = 1
net.ipv4.conf.all.accept_local = 1
net.ipv4.conf.default.accept_local = 1
net.ipv4.conf.lo.accept_local = 1
net.ipv4.conf.default.arp_filter = 0
net.ipv4.conf.all.arp_filter = 0
net.ipv4.conf.p1p2.arp_filter = 0
net.ipv4.conf.p1p1.arp_filter = 0
net.ipv4.conf.lo.arp_announce = 2
net.ipv4.conf.all.arp_announce = 2
net.ipv4.conf.default.arp_announce = 2
net.ipv4.conf.p1p1.arp_announce = 2
net.ipv4.conf.p1p2.arp_announce = 2
PING 37.123.98.142 (37.123.98.142) from 37.123.98.142 p1p1: 56(84) bytes of data.
^C
--- 37.123.98.142 ping statistics ---
3 packets transmitted, 0 received, 100% packet loss, time 2055ms
[root@spd network-scripts]# ping -I p1p1 37.123.98.138
PING 37.123.98.138 (37.123.98.138) from 37.123.98.142 p1p1: 56(84) bytes of data.
^C
--- 37.123.98.138 ping statistics ---
4 packets transmitted, 0 received, 100% packet loss, time 3064ms
[root@spd network-scripts]# ping -I p1p2 37.123.98.138
PING 37.123.98.138 (37.123.98.138) from 37.123.98.138 p1p2: 56(84) bytes of data.
^C
--- 37.123.98.138 ping statistics ---
2 packets transmitted, 0 received, 100% packet loss, time 1038ms
[root@spd network-scripts]# ping -I p1p2 37.123.98.142
PING 37.123.98.142 (37.123.98.142) from 37.123.98.138 p1p2: 56(84) bytes of data.
^C
--- 37.123.98.142 ping statistics ---
3 packets transmitted, 0 received, 100% packet loss, time 2060ms
[root@spd network-scripts]# ping 37.123.98.142
PING 37.123.98.142 (37.123.98.142) 56(84) bytes of data.
64 bytes from 37.123.98.142: icmp_seq=1 ttl=64 time=0.019 ms
64 bytes from 37.123.98.142: icmp_seq=2 ttl=64 time=0.022 ms
64 bytes from 37.123.98.142: icmp_seq=3 ttl=64 time=0.017 ms
64 bytes from 37.123.98.142: icmp_seq=4 ttl=64 time=0.015 ms
[root@spd network-scripts]# ifconfig
em1: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
inet 178.20.231.230 netmask 255.255.255.0 broadcast 178.20.231.255
inet6 fe80::15aa:336c:10f4:ac25 prefixlen 64 scopeid 0x20<link>
ether d4:be:d9:f3:a9:7c txqueuelen 1000 (Ethernet)
RX packets 318680 bytes 20750645 (19.7 MiB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 4971 bytes 586494 (572.7 KiB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
em2: flags=4099<UP,BROADCAST,MULTICAST> mtu 1500
ether d4:be:d9:f3:a9:7e txqueuelen 1000 (Ethernet)
RX packets 0 bytes 0 (0.0 B)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 0 bytes 0 (0.0 B)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
em3: flags=4099<UP,BROADCAST,MULTICAST> mtu 1500
ether d4:be:d9:f3:a9:80 txqueuelen 1000 (Ethernet)
RX packets 0 bytes 0 (0.0 B)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 0 bytes 0 (0.0 B)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
em4: flags=4099<UP,BROADCAST,MULTICAST> mtu 1500
ether d4:be:d9:f3:a9:82 txqueuelen 1000 (Ethernet)
RX packets 0 bytes 0 (0.0 B)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 0 bytes 0 (0.0 B)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
lo: flags=73<UP,LOOPBACK,RUNNING> mtu 65536
inet 127.0.0.1 netmask 255.0.0.0
inet6 ::1 prefixlen 128 scopeid 0x10<host>
loop txqueuelen 1000 (Local Loopback)
RX packets 297 bytes 25497 (24.8 KiB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 297 bytes 25497 (24.8 KiB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
p1p1: flags=4419<UP,BROADCAST,RUNNING,PROMISC,MULTICAST> mtu 1500
inet 37.123.98.142 netmask 255.255.255.252 broadcast 37.123.98.143
inet6 fe80::19fe:896:2a58:f807 prefixlen 64 scopeid 0x20<link>
ether a0:36:9f:55:7c:a8 txqueuelen 10000 (Ethernet)
RX packets 2715 bytes 251618 (245.7 KiB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 846 bytes 109138 (106.5 KiB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
p1p2: flags=4419<UP,BROADCAST,RUNNING,PROMISC,MULTICAST> mtu 1500
inet 37.123.98.138 netmask 255.255.255.252 broadcast 37.123.98.139
inet6 fe80::9e35:d5c8:4334:52e3 prefixlen 64 scopeid 0x20<link>
ether a0:36:9f:55:7c:aa txqueuelen 10000 (Ethernet)
RX packets 5309 bytes 480270 (469.0 KiB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 3348 bytes 479429 (468.1 KiB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
ASKER
Dear david,
Network is completely mine here is my building. I just get the connectivity from Seabone & cogent . And they do not build any setup in my building
https://www.flickr.com/photos/spdnet/
Also i have removed the cables from server still can not ping each other
Network is completely mine here is my building. I just get the connectivity from Seabone & cogent . And they do not build any setup in my building
https://www.flickr.com/photos/spdnet/
Also i have removed the cables from server still can not ping each other
This question needs an answer!
Become an EE member today
7 DAY FREE TRIALMembers can start a 7-Day Free trial then enjoy unlimited access to the platform.
View membership options
or
Learn why we charge membership fees
We get it - no one likes a content blocker. Take one extra minute and find out why we block content.
If I were in this situation, I'd open a ticket with my provisioning company + ask them to get networking running correctly on all my boxes.
Some hosting/provisioning companies have very odd network setups, so sometimes getting the simplest networking running can require subtle, situation specific configs.