Strange behaviour sending IGMP on multi IP address for interface
I'd be glad to have some info/clue on the behavior in the followings situation:
There are eth0 with IP address 10.10.10.10 and eth0:1 with IP address 20.20.20.20.
IGMP join and leave shall be send from 20.20.20.20 IP.
Initially, there was no IGMP join at all. Checking the IP tables, it was found that:
Chain INPUT (policy ACCEPT)
target prot opt source destination
DROP igmp -- anywhere anywhere
DROP igmp -- anywhere anywhere
Chain FORWARD (policy ACCEPT)
target prot opt source destination
Chain OUTPUT (policy ACCEPT)
target prot opt source destination
DROP igmp -- anywhere anywhere
DROP igmp -- anywhere anywhere
After flushing the the OUTPUT chain, IGMP join/leave is sent from the 10.10.10.10 IP.
After flushing the INPUT chain, the join is sent from the wanted 20.20.20.20 IP (the leave is still sent from the 10.10.10.10 IP, but this is less important for us right now).
It seems to be very strange for me and for the SW eng.
Any idea on this behaviour
multicast
add a comment |
I'd be glad to have some info/clue on the behavior in the followings situation:
There are eth0 with IP address 10.10.10.10 and eth0:1 with IP address 20.20.20.20.
IGMP join and leave shall be send from 20.20.20.20 IP.
Initially, there was no IGMP join at all. Checking the IP tables, it was found that:
Chain INPUT (policy ACCEPT)
target prot opt source destination
DROP igmp -- anywhere anywhere
DROP igmp -- anywhere anywhere
Chain FORWARD (policy ACCEPT)
target prot opt source destination
Chain OUTPUT (policy ACCEPT)
target prot opt source destination
DROP igmp -- anywhere anywhere
DROP igmp -- anywhere anywhere
After flushing the the OUTPUT chain, IGMP join/leave is sent from the 10.10.10.10 IP.
After flushing the INPUT chain, the join is sent from the wanted 20.20.20.20 IP (the leave is still sent from the 10.10.10.10 IP, but this is less important for us right now).
It seems to be very strange for me and for the SW eng.
Any idea on this behaviour
multicast
add a comment |
I'd be glad to have some info/clue on the behavior in the followings situation:
There are eth0 with IP address 10.10.10.10 and eth0:1 with IP address 20.20.20.20.
IGMP join and leave shall be send from 20.20.20.20 IP.
Initially, there was no IGMP join at all. Checking the IP tables, it was found that:
Chain INPUT (policy ACCEPT)
target prot opt source destination
DROP igmp -- anywhere anywhere
DROP igmp -- anywhere anywhere
Chain FORWARD (policy ACCEPT)
target prot opt source destination
Chain OUTPUT (policy ACCEPT)
target prot opt source destination
DROP igmp -- anywhere anywhere
DROP igmp -- anywhere anywhere
After flushing the the OUTPUT chain, IGMP join/leave is sent from the 10.10.10.10 IP.
After flushing the INPUT chain, the join is sent from the wanted 20.20.20.20 IP (the leave is still sent from the 10.10.10.10 IP, but this is less important for us right now).
It seems to be very strange for me and for the SW eng.
Any idea on this behaviour
multicast
I'd be glad to have some info/clue on the behavior in the followings situation:
There are eth0 with IP address 10.10.10.10 and eth0:1 with IP address 20.20.20.20.
IGMP join and leave shall be send from 20.20.20.20 IP.
Initially, there was no IGMP join at all. Checking the IP tables, it was found that:
Chain INPUT (policy ACCEPT)
target prot opt source destination
DROP igmp -- anywhere anywhere
DROP igmp -- anywhere anywhere
Chain FORWARD (policy ACCEPT)
target prot opt source destination
Chain OUTPUT (policy ACCEPT)
target prot opt source destination
DROP igmp -- anywhere anywhere
DROP igmp -- anywhere anywhere
After flushing the the OUTPUT chain, IGMP join/leave is sent from the 10.10.10.10 IP.
After flushing the INPUT chain, the join is sent from the wanted 20.20.20.20 IP (the leave is still sent from the 10.10.10.10 IP, but this is less important for us right now).
It seems to be very strange for me and for the SW eng.
Any idea on this behaviour
multicast
multicast
asked 13 mins ago
user1977050
139315
139315
add a comment |
add a comment |
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%2f490932%2fstrange-behaviour-sending-igmp-on-multi-ip-address-for-interface%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
active
oldest
votes
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%2f490932%2fstrange-behaviour-sending-igmp-on-multi-ip-address-for-interface%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