Linux does not reply to ARP request

The name of the pictureThe name of the pictureThe name of the pictureClash Royale CLAN TAG#URR8PPP





.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty margin-bottom:0;







up vote
-1
down vote

favorite












I have 3 interfaces on my Ubuntu 12.04 machine with 3.10.101-1 kernel. Two of the three interfaces are responsive (ping data) and one interface does not response to ARP request (when I ping to it).



I thought maybe it's a matter of rules, but the table seems OK (after I checked this answer):



# ip route show table local
local 10.206.182.140 dev eth2 proto kernel scope host src 10.206.182.140
broadcast 127.255.255.255 dev lo proto kernel scope link src 127.0.0.1
broadcast 10.206.0.0 dev eth0 proto kernel scope link src 10.206.182.138
broadcast 10.206.0.0 dev eth2 proto kernel scope link src 10.206.182.140
broadcast 10.206.0.0 dev eth1 proto kernel scope link src 10.206.182.139
local 10.206.182.139 dev eth1 proto kernel scope host src 10.206.182.139
local 10.206.182.138 dev eth0 proto kernel scope host src 10.206.182.138
broadcast 10.206.255.255 dev eth0 proto kernel scope link src 10.206.182.138
broadcast 10.206.255.255 dev eth2 proto kernel scope link src 10.206.182.140
broadcast 10.206.255.255 dev eth1 proto kernel scope link src 10.206.182.139
broadcast 127.0.0.0 dev lo proto kernel scope link src 127.0.0.1


# ip route show
10.206.0.0/16 dev eth2 proto kernel scope link src 10.206.182.140
10.206.0.0/16 dev eth1 proto kernel scope link src 10.206.182.139
default via 10.206.1.1 dev eth2


When I run tcpdump on eth1, I can see only the ARP requests with no response, but eth0 and eth2 works fine.



This is the tcpdump:



# tcpdump -n -i any host 10.206.182.138 and arp
tcpdump: verbose output suppressed, use -v or -vv for full protocol decode
listening on any, link-type LINUX_SLL (Linux cooked), capture size 65535 bytes
13:36:03.003660 ARP, Request who-has 10.206.182.149 tell 10.206.182.138, length 46
13:36:03.003660 ARP, Request who-has 10.206.182.149 tell 10.206.182.138, length 46
13:36:03.003679 ARP, Request who-has 10.206.182.149 tell 10.206.182.138, length 46
13:36:05.007450 ARP, Request who-has 10.206.182.149 tell 10.206.182.138, length 46
13:36:05.007451 ARP, Request who-has 10.206.182.149 tell 10.206.182.138, length 46
13:36:05.007464 ARP, Request who-has 10.206.182.149 tell 10.206.182.138, length 46
13:36:06.007431 ARP, Request who-has 10.206.182.149 tell 10.206.182.138, length 46
13:36:06.007431 ARP, Request who-has 10.206.182.149 tell 10.206.182.138, length 46
13:36:06.007444 ARP, Request who-has 10.206.182.149 tell 10.206.182.138, length 46
13:36:07.007466 ARP, Request who-has 10.206.182.149 tell 10.206.182.138, length 46
13:36:07.007466 ARP, Request who-has 10.206.182.149 tell 10.206.182.138, length 46
13:36:07.007486 ARP, Request who-has 10.206.182.149 tell 10.206.182.138, length 46
13:36:09.011350 ARP, Request who-has 10.206.182.149 tell 10.206.182.138, length 46
13:36:09.011352 ARP, Request who-has 10.206.182.149 tell 10.206.182.138, length 46
13:36:09.011360 ARP, Request who-has 10.206.182.149 tell 10.206.182.138, length 46
13:36:10.011464 ARP, Request who-has 10.206.182.149 tell 10.206.182.138, length 46
13:36:10.011462 ARP, Request who-has 10.206.182.149 tell 10.206.182.138, length 46
13:36:10.011480 ARP, Request who-has 10.206.182.149 tell 10.206.182.138, length 46
13:36:11.011444 ARP, Request who-has 10.206.182.149 tell 10.206.182.138, length 46
13:36:11.011483 ARP, Request who-has 10.206.182.149 tell 10.206.182.138, length 46
13:36:11.011494 ARP, Request who-has 10.206.182.149 tell 10.206.182.138, length 46


What can cause that kind of problem?




linux networking linux-kernel arp




share|improve this question

















  • 1




    This is most definitely a issue w/ the rules, since you've followed the packet to the point of the request, but not seeing the response packet. Are you running tcpdump listening to all interfaces or just the one you expect to see the response on? If so I'd listen on all of them to see if your rules are sending the packet to the wrong interface.
    – slm♦
    Jul 19 at 13:25










  • e.g. use tdpdump -n -i any inside the server. If you are talking in questions about such things as tcpdump or whatever, please do not turn them into magical dark boxes, but add them to the questions before people ask you too.
    – Rui F Ribeiro
    Jul 19 at 13:26











  • thanks , I added the tcpdump command to the question. as you can see, no interface returns ARP reply..
    – user1673206
    Jul 19 at 13:34










  • Why is the route for eth0 missing?
    – Isaac
    Jul 19 at 13:45










  • Its on different route table
    – user1673206
    Jul 19 at 13:49
















up vote
-1
down vote

favorite












I have 3 interfaces on my Ubuntu 12.04 machine with 3.10.101-1 kernel. Two of the three interfaces are responsive (ping data) and one interface does not response to ARP request (when I ping to it).



I thought maybe it's a matter of rules, but the table seems OK (after I checked this answer):



# ip route show table local
local 10.206.182.140 dev eth2 proto kernel scope host src 10.206.182.140
broadcast 127.255.255.255 dev lo proto kernel scope link src 127.0.0.1
broadcast 10.206.0.0 dev eth0 proto kernel scope link src 10.206.182.138
broadcast 10.206.0.0 dev eth2 proto kernel scope link src 10.206.182.140
broadcast 10.206.0.0 dev eth1 proto kernel scope link src 10.206.182.139
local 10.206.182.139 dev eth1 proto kernel scope host src 10.206.182.139
local 10.206.182.138 dev eth0 proto kernel scope host src 10.206.182.138
broadcast 10.206.255.255 dev eth0 proto kernel scope link src 10.206.182.138
broadcast 10.206.255.255 dev eth2 proto kernel scope link src 10.206.182.140
broadcast 10.206.255.255 dev eth1 proto kernel scope link src 10.206.182.139
broadcast 127.0.0.0 dev lo proto kernel scope link src 127.0.0.1


# ip route show
10.206.0.0/16 dev eth2 proto kernel scope link src 10.206.182.140
10.206.0.0/16 dev eth1 proto kernel scope link src 10.206.182.139
default via 10.206.1.1 dev eth2


When I run tcpdump on eth1, I can see only the ARP requests with no response, but eth0 and eth2 works fine.



This is the tcpdump:



# tcpdump -n -i any host 10.206.182.138 and arp
tcpdump: verbose output suppressed, use -v or -vv for full protocol decode
listening on any, link-type LINUX_SLL (Linux cooked), capture size 65535 bytes
13:36:03.003660 ARP, Request who-has 10.206.182.149 tell 10.206.182.138, length 46
13:36:03.003660 ARP, Request who-has 10.206.182.149 tell 10.206.182.138, length 46
13:36:03.003679 ARP, Request who-has 10.206.182.149 tell 10.206.182.138, length 46
13:36:05.007450 ARP, Request who-has 10.206.182.149 tell 10.206.182.138, length 46
13:36:05.007451 ARP, Request who-has 10.206.182.149 tell 10.206.182.138, length 46
13:36:05.007464 ARP, Request who-has 10.206.182.149 tell 10.206.182.138, length 46
13:36:06.007431 ARP, Request who-has 10.206.182.149 tell 10.206.182.138, length 46
13:36:06.007431 ARP, Request who-has 10.206.182.149 tell 10.206.182.138, length 46
13:36:06.007444 ARP, Request who-has 10.206.182.149 tell 10.206.182.138, length 46
13:36:07.007466 ARP, Request who-has 10.206.182.149 tell 10.206.182.138, length 46
13:36:07.007466 ARP, Request who-has 10.206.182.149 tell 10.206.182.138, length 46
13:36:07.007486 ARP, Request who-has 10.206.182.149 tell 10.206.182.138, length 46
13:36:09.011350 ARP, Request who-has 10.206.182.149 tell 10.206.182.138, length 46
13:36:09.011352 ARP, Request who-has 10.206.182.149 tell 10.206.182.138, length 46
13:36:09.011360 ARP, Request who-has 10.206.182.149 tell 10.206.182.138, length 46
13:36:10.011464 ARP, Request who-has 10.206.182.149 tell 10.206.182.138, length 46
13:36:10.011462 ARP, Request who-has 10.206.182.149 tell 10.206.182.138, length 46
13:36:10.011480 ARP, Request who-has 10.206.182.149 tell 10.206.182.138, length 46
13:36:11.011444 ARP, Request who-has 10.206.182.149 tell 10.206.182.138, length 46
13:36:11.011483 ARP, Request who-has 10.206.182.149 tell 10.206.182.138, length 46
13:36:11.011494 ARP, Request who-has 10.206.182.149 tell 10.206.182.138, length 46


What can cause that kind of problem?




linux networking linux-kernel arp




share|improve this question

















  • 1




    This is most definitely a issue w/ the rules, since you've followed the packet to the point of the request, but not seeing the response packet. Are you running tcpdump listening to all interfaces or just the one you expect to see the response on? If so I'd listen on all of them to see if your rules are sending the packet to the wrong interface.
    – slm♦
    Jul 19 at 13:25










  • e.g. use tdpdump -n -i any inside the server. If you are talking in questions about such things as tcpdump or whatever, please do not turn them into magical dark boxes, but add them to the questions before people ask you too.
    – Rui F Ribeiro
    Jul 19 at 13:26











  • thanks , I added the tcpdump command to the question. as you can see, no interface returns ARP reply..
    – user1673206
    Jul 19 at 13:34










  • Why is the route for eth0 missing?
    – Isaac
    Jul 19 at 13:45










  • Its on different route table
    – user1673206
    Jul 19 at 13:49












up vote
-1
down vote

favorite









up vote
-1
down vote

favorite











I have 3 interfaces on my Ubuntu 12.04 machine with 3.10.101-1 kernel. Two of the three interfaces are responsive (ping data) and one interface does not response to ARP request (when I ping to it).



I thought maybe it's a matter of rules, but the table seems OK (after I checked this answer):



# ip route show table local
local 10.206.182.140 dev eth2 proto kernel scope host src 10.206.182.140
broadcast 127.255.255.255 dev lo proto kernel scope link src 127.0.0.1
broadcast 10.206.0.0 dev eth0 proto kernel scope link src 10.206.182.138
broadcast 10.206.0.0 dev eth2 proto kernel scope link src 10.206.182.140
broadcast 10.206.0.0 dev eth1 proto kernel scope link src 10.206.182.139
local 10.206.182.139 dev eth1 proto kernel scope host src 10.206.182.139
local 10.206.182.138 dev eth0 proto kernel scope host src 10.206.182.138
broadcast 10.206.255.255 dev eth0 proto kernel scope link src 10.206.182.138
broadcast 10.206.255.255 dev eth2 proto kernel scope link src 10.206.182.140
broadcast 10.206.255.255 dev eth1 proto kernel scope link src 10.206.182.139
broadcast 127.0.0.0 dev lo proto kernel scope link src 127.0.0.1


# ip route show
10.206.0.0/16 dev eth2 proto kernel scope link src 10.206.182.140
10.206.0.0/16 dev eth1 proto kernel scope link src 10.206.182.139
default via 10.206.1.1 dev eth2


When I run tcpdump on eth1, I can see only the ARP requests with no response, but eth0 and eth2 works fine.



This is the tcpdump:



# tcpdump -n -i any host 10.206.182.138 and arp
tcpdump: verbose output suppressed, use -v or -vv for full protocol decode
listening on any, link-type LINUX_SLL (Linux cooked), capture size 65535 bytes
13:36:03.003660 ARP, Request who-has 10.206.182.149 tell 10.206.182.138, length 46
13:36:03.003660 ARP, Request who-has 10.206.182.149 tell 10.206.182.138, length 46
13:36:03.003679 ARP, Request who-has 10.206.182.149 tell 10.206.182.138, length 46
13:36:05.007450 ARP, Request who-has 10.206.182.149 tell 10.206.182.138, length 46
13:36:05.007451 ARP, Request who-has 10.206.182.149 tell 10.206.182.138, length 46
13:36:05.007464 ARP, Request who-has 10.206.182.149 tell 10.206.182.138, length 46
13:36:06.007431 ARP, Request who-has 10.206.182.149 tell 10.206.182.138, length 46
13:36:06.007431 ARP, Request who-has 10.206.182.149 tell 10.206.182.138, length 46
13:36:06.007444 ARP, Request who-has 10.206.182.149 tell 10.206.182.138, length 46
13:36:07.007466 ARP, Request who-has 10.206.182.149 tell 10.206.182.138, length 46
13:36:07.007466 ARP, Request who-has 10.206.182.149 tell 10.206.182.138, length 46
13:36:07.007486 ARP, Request who-has 10.206.182.149 tell 10.206.182.138, length 46
13:36:09.011350 ARP, Request who-has 10.206.182.149 tell 10.206.182.138, length 46
13:36:09.011352 ARP, Request who-has 10.206.182.149 tell 10.206.182.138, length 46
13:36:09.011360 ARP, Request who-has 10.206.182.149 tell 10.206.182.138, length 46
13:36:10.011464 ARP, Request who-has 10.206.182.149 tell 10.206.182.138, length 46
13:36:10.011462 ARP, Request who-has 10.206.182.149 tell 10.206.182.138, length 46
13:36:10.011480 ARP, Request who-has 10.206.182.149 tell 10.206.182.138, length 46
13:36:11.011444 ARP, Request who-has 10.206.182.149 tell 10.206.182.138, length 46
13:36:11.011483 ARP, Request who-has 10.206.182.149 tell 10.206.182.138, length 46
13:36:11.011494 ARP, Request who-has 10.206.182.149 tell 10.206.182.138, length 46


What can cause that kind of problem?




linux networking linux-kernel arp




share|improve this question













I have 3 interfaces on my Ubuntu 12.04 machine with 3.10.101-1 kernel. Two of the three interfaces are responsive (ping data) and one interface does not response to ARP request (when I ping to it).



I thought maybe it's a matter of rules, but the table seems OK (after I checked this answer):



# ip route show table local
local 10.206.182.140 dev eth2 proto kernel scope host src 10.206.182.140
broadcast 127.255.255.255 dev lo proto kernel scope link src 127.0.0.1
broadcast 10.206.0.0 dev eth0 proto kernel scope link src 10.206.182.138
broadcast 10.206.0.0 dev eth2 proto kernel scope link src 10.206.182.140
broadcast 10.206.0.0 dev eth1 proto kernel scope link src 10.206.182.139
local 10.206.182.139 dev eth1 proto kernel scope host src 10.206.182.139
local 10.206.182.138 dev eth0 proto kernel scope host src 10.206.182.138
broadcast 10.206.255.255 dev eth0 proto kernel scope link src 10.206.182.138
broadcast 10.206.255.255 dev eth2 proto kernel scope link src 10.206.182.140
broadcast 10.206.255.255 dev eth1 proto kernel scope link src 10.206.182.139
broadcast 127.0.0.0 dev lo proto kernel scope link src 127.0.0.1


# ip route show
10.206.0.0/16 dev eth2 proto kernel scope link src 10.206.182.140
10.206.0.0/16 dev eth1 proto kernel scope link src 10.206.182.139
default via 10.206.1.1 dev eth2


When I run tcpdump on eth1, I can see only the ARP requests with no response, but eth0 and eth2 works fine.



This is the tcpdump:



# tcpdump -n -i any host 10.206.182.138 and arp
tcpdump: verbose output suppressed, use -v or -vv for full protocol decode
listening on any, link-type LINUX_SLL (Linux cooked), capture size 65535 bytes
13:36:03.003660 ARP, Request who-has 10.206.182.149 tell 10.206.182.138, length 46
13:36:03.003660 ARP, Request who-has 10.206.182.149 tell 10.206.182.138, length 46
13:36:03.003679 ARP, Request who-has 10.206.182.149 tell 10.206.182.138, length 46
13:36:05.007450 ARP, Request who-has 10.206.182.149 tell 10.206.182.138, length 46
13:36:05.007451 ARP, Request who-has 10.206.182.149 tell 10.206.182.138, length 46
13:36:05.007464 ARP, Request who-has 10.206.182.149 tell 10.206.182.138, length 46
13:36:06.007431 ARP, Request who-has 10.206.182.149 tell 10.206.182.138, length 46
13:36:06.007431 ARP, Request who-has 10.206.182.149 tell 10.206.182.138, length 46
13:36:06.007444 ARP, Request who-has 10.206.182.149 tell 10.206.182.138, length 46
13:36:07.007466 ARP, Request who-has 10.206.182.149 tell 10.206.182.138, length 46
13:36:07.007466 ARP, Request who-has 10.206.182.149 tell 10.206.182.138, length 46
13:36:07.007486 ARP, Request who-has 10.206.182.149 tell 10.206.182.138, length 46
13:36:09.011350 ARP, Request who-has 10.206.182.149 tell 10.206.182.138, length 46
13:36:09.011352 ARP, Request who-has 10.206.182.149 tell 10.206.182.138, length 46
13:36:09.011360 ARP, Request who-has 10.206.182.149 tell 10.206.182.138, length 46
13:36:10.011464 ARP, Request who-has 10.206.182.149 tell 10.206.182.138, length 46
13:36:10.011462 ARP, Request who-has 10.206.182.149 tell 10.206.182.138, length 46
13:36:10.011480 ARP, Request who-has 10.206.182.149 tell 10.206.182.138, length 46
13:36:11.011444 ARP, Request who-has 10.206.182.149 tell 10.206.182.138, length 46
13:36:11.011483 ARP, Request who-has 10.206.182.149 tell 10.206.182.138, length 46
13:36:11.011494 ARP, Request who-has 10.206.182.149 tell 10.206.182.138, length 46


What can cause that kind of problem?





linux networking linux-kernel arp





share|improve this question












share|improve this question




share|improve this question








edited Jul 19 at 13:33
























asked Jul 19 at 13:09









user1673206

1021




1021







  • 1




    This is most definitely a issue w/ the rules, since you've followed the packet to the point of the request, but not seeing the response packet. Are you running tcpdump listening to all interfaces or just the one you expect to see the response on? If so I'd listen on all of them to see if your rules are sending the packet to the wrong interface.
    – slm♦
    Jul 19 at 13:25










  • e.g. use tdpdump -n -i any inside the server. If you are talking in questions about such things as tcpdump or whatever, please do not turn them into magical dark boxes, but add them to the questions before people ask you too.
    – Rui F Ribeiro
    Jul 19 at 13:26











  • thanks , I added the tcpdump command to the question. as you can see, no interface returns ARP reply..
    – user1673206
    Jul 19 at 13:34










  • Why is the route for eth0 missing?
    – Isaac
    Jul 19 at 13:45










  • Its on different route table
    – user1673206
    Jul 19 at 13:49












  • 1




    This is most definitely a issue w/ the rules, since you've followed the packet to the point of the request, but not seeing the response packet. Are you running tcpdump listening to all interfaces or just the one you expect to see the response on? If so I'd listen on all of them to see if your rules are sending the packet to the wrong interface.
    – slm♦
    Jul 19 at 13:25










  • e.g. use tdpdump -n -i any inside the server. If you are talking in questions about such things as tcpdump or whatever, please do not turn them into magical dark boxes, but add them to the questions before people ask you too.
    – Rui F Ribeiro
    Jul 19 at 13:26











  • thanks , I added the tcpdump command to the question. as you can see, no interface returns ARP reply..
    – user1673206
    Jul 19 at 13:34










  • Why is the route for eth0 missing?
    – Isaac
    Jul 19 at 13:45










  • Its on different route table
    – user1673206
    Jul 19 at 13:49







1




1




This is most definitely a issue w/ the rules, since you've followed the packet to the point of the request, but not seeing the response packet. Are you running tcpdump listening to all interfaces or just the one you expect to see the response on? If so I'd listen on all of them to see if your rules are sending the packet to the wrong interface.
– slm♦
Jul 19 at 13:25




This is most definitely a issue w/ the rules, since you've followed the packet to the point of the request, but not seeing the response packet. Are you running tcpdump listening to all interfaces or just the one you expect to see the response on? If so I'd listen on all of them to see if your rules are sending the packet to the wrong interface.
– slm♦
Jul 19 at 13:25












e.g. use tdpdump -n -i any inside the server. If you are talking in questions about such things as tcpdump or whatever, please do not turn them into magical dark boxes, but add them to the questions before people ask you too.
– Rui F Ribeiro
Jul 19 at 13:26





e.g. use tdpdump -n -i any inside the server. If you are talking in questions about such things as tcpdump or whatever, please do not turn them into magical dark boxes, but add them to the questions before people ask you too.
– Rui F Ribeiro
Jul 19 at 13:26













thanks , I added the tcpdump command to the question. as you can see, no interface returns ARP reply..
– user1673206
Jul 19 at 13:34




thanks , I added the tcpdump command to the question. as you can see, no interface returns ARP reply..
– user1673206
Jul 19 at 13:34












Why is the route for eth0 missing?
– Isaac
Jul 19 at 13:45




Why is the route for eth0 missing?
– Isaac
Jul 19 at 13:45












Its on different route table
– user1673206
Jul 19 at 13:49




Its on different route table
– user1673206
Jul 19 at 13:49















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',
convertImagesToLinks: false,
noModals: false,
showLowRepImageUploadWarning: true,
reputationToPostImages: null,
bindNavPrevention: true,
postfix: "",
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
);



);








 

draft saved


draft discarded


















StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f457215%2flinux-does-not-reply-to-arp-request%23new-answer', 'question_page');

);

Post as a guest






















active

oldest

votes













active

oldest

votes









active

oldest

votes






active

oldest

votes










 

draft saved


draft discarded


























 


draft saved


draft discarded














StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f457215%2flinux-does-not-reply-to-arp-request%23new-answer', 'question_page');

);

Post as a guest
































































-

Popular posts from this blog

How to check contact read email or not when send email to Individual?

Image
Clash Royale CLAN TAG #URR8PPP up vote 1 down vote favorite I'm using WordPress 4.9.8, CiviCRM to 5.5.1, I usually send email to contact by Search> Find contacts View contact details Action> Send email Send email ok, Contact received mail ok like picture But status only Email sent though contact read email or not. So, can CiviCRM can change status to Email read when contact read email? wordpress email share | improve this question asked Sep 26 at 0:12 ToanLuong 49 9 add a comment  |  up vote 1 down vote favorite I'm using WordPress 4.9.8, CiviCRM to 5.5.1, I usually send email to contact by Search> Find contacts View contact details Action> Send email Send email ok, Contact received mail ok like picture But status only Email sent though contact read email or not. So, can CiviCRM can change status to Email read when contact read email? wordpress email share | improve this question asked Se
Read more

Bahrain

Image
For other uses, see Bahrain (disambiguation). Sovereign island state in the Persian Gulf Kingdom of Bahrain مملكة البحرين   (Arabic) Mamlakat al-Baḥrayn Flag Coat of arms Anthem:  نشيد البحرين الوطني Bahrainona Our Bahrain Location of   Bahrain    (circled in red) Capital and largest city Manama 26°13′N 50°35′E  /  26.217°N 50.583°E  / 26.217; 50.583 Official languages Arabic Ethnic groups (2010 [1] ) 50.7% Arab (46% Bahrani, 4.7% other Arabs) 45.5% Asian 1% European 1.2% Others Religion Islam Demonym(s) Bahraini Government Unitary constitutional monarchy • King Hamad bin Isa Al Khalifa • Crown Prince Salman bin Hamad bin Isa Al Khalifa • Prime Minister Khalifa bin Salman Al Khalifa Legislature National Assembly • Upper house Consultative Council • Lower house Council of Representatives Independence • Declared Independence [2] 14 August 1971 • from United Kingdom [1] 15 August 1971 • Admitted to the United Nations 21 September 1971 • Kingdom of Bahrain 14 February 2002
Read more

Postfix configuration issue with fips on centos 7; mailgun relay

Image
Clash Royale CLAN TAG #URR8PPP up vote 0 down vote favorite I am trying to setup postfix to relay all mail generated on the local machine via SMTP to a mailgun relay. I have used the mailgun relay before with success on an ubuntu server, but I am migrating to a Centos 7 server which I will be running in FIPS mode. There error log is below, slightly sanitized. I have a small enough network that I choose to have each machine reach out to mailgun individually (this the loopback-only, 127.0.0.0/8 restrictions) and no firewall open port allowing smtp in to the machine. I assume the FIPS mode (and with it disabling of MD5) is causing problems, but I don't know how to overcome it or if it is even possible for tls_fprint to use some supported hash such as sha256 or sha512. However, the relay=none is slightly concerning since I have relayhost set, but perhaps that is because the smtp process is failing? Any help would be appreciated! postconf -n: alias_database = hash:/etc/alia
Read more