How to unblock service discovery for IPv4 via Avahi?Can't connect to MySql server on remote serverCan't...
What to wear for invited talk in Canada
How to create a consistent feel for character names in a fantasy setting?
Why is my log file so massive? 22gb. I am running log backups
What do the Banks children have against barley water?
Crop image to path created in TikZ?
Why did the Germans forbid the possession of pet pigeons in Rostov-on-Don in 1941?
extract characters between two commas?
Can produce flame be used to grapple, or as an unarmed strike, in the right circumstances?
I see my dog run
Are cabin dividers used to "hide" the flex of the airplane?
Why do UK politicians seemingly ignore opinion polls on Brexit?
What does 'script /dev/null' do?
Was there ever an axiom rendered a theorem?
Extreme, but not acceptable situation and I can't start the work tomorrow morning
Information to fellow intern about hiring?
Piano - What is the notation for a double stop where both notes in the double stop are different lengths?
Email Account under attack (really) - anything I can do?
How to move the player while also allowing forces to affect it
What is the offset in a seaplane's hull?
Shall I use personal or official e-mail account when registering to external websites for work purpose?
Lied on resume at previous job
Copycat chess is back
Is Social Media Science Fiction?
What do you call something that goes against the spirit of the law, but is legal when interpreting the law to the letter?
How to unblock service discovery for IPv4 via Avahi?
Can't connect to MySql server on remote serverCan't access oracle(@1521) and http(8080) even with firewall stoppedFirewall still blocking port 53 despite listing otherwise?Trying to make iptables stateless is causing unforeseen filteringResolve avahi hostnames via DNSHow to establish firewall rules that accepting 11211 port in intranet for memcached ( Fedora)?Can't discover a IPv4 link-local address when having an static IP configuredNetfilter - LAN -> VPN Clientsnslookup, host, ssh connection works but ping notICMPv6 restrictive firewall: losing connectivity over time
.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty{ height:90px;width:728px;box-sizing:border-box;
}
On a Debian 6.0.6 system (squeeze) I am having trouble resolving a host using Avahi and IPv4. Here is a sample output:
: nr@homedog 10102 ; avahi-browse -a
+ eth0 IPv6 yorkie [00:1f:3b:d8:67:1d] Workstation local
+ eth0 IPv6 homedog [bc:5f:f4:5a:b1:73] Workstation local
+ eth0 IPv4 homedog [bc:5f:f4:5a:b1:73] Workstation local
Notice that homedog, the local machine, is visible both on IPv6 and IPv4. But yorkie, the remote machine, is visible only on IPv4. And avahi-resolve-host-name -4 yorkie.local hangs with no result.
EDIT: The situation is symmetric: yorkie sees itself on IPv4 and IPv6, but it sees homedog on IPv6 only.
On yorkie, the output from iptables -vnL is
Chain INPUT (policy ACCEPT 109K packets, 98M bytes)
pkts bytes target prot opt in out source destination
Chain FORWARD (policy ACCEPT 0 packets, 0 bytes)
pkts bytes target prot opt in out source destination
Chain OUTPUT (policy ACCEPT 108K packets, 94M bytes)
pkts bytes target prot opt in out source destination
(To make the display fit StackExchange without wrapping, I have taken a couple of liberties with horizontal space.) The display on homedog is identical except for the numbers: for all three, it displays 0 packets and 0 bytes.
(I have no clue how to interpret these outputs, but it may be informative that yorkie's current uptime is 41 days and homedog's current uptime is 6 hours.)
I found a closed ticket at http://avahi.org/ticket/297, which suggests that the problem is some sort of firewall configuration. I am a complete novice in this area, and through web search I have been unable to inform myself about how to use the iptables command to diagnose or repair the problem. I found another ticket as Debian bug 547974, but this bug was closed without explaining how to fix the problem.
The hypothesis is that somehow the service-discovery packet is being blocked—I don't know on which machine. Can anyone say how to discover which machine is blocking the packet and how to reconfigure it so Avahi discovers the IPv4 address?
firewall avahi
asked Feb 8 '13 at 23:12
Norman RamseyNorman Ramsey
3652623
bumped to the homepage by Community♦ 1 hour ago
This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.
|
show 1 more comment
On a Debian 6.0.6 system (squeeze) I am having trouble resolving a host using Avahi and IPv4. Here is a sample output:
: nr@homedog 10102 ; avahi-browse -a
+ eth0 IPv6 yorkie [00:1f:3b:d8:67:1d] Workstation local
+ eth0 IPv6 homedog [bc:5f:f4:5a:b1:73] Workstation local
+ eth0 IPv4 homedog [bc:5f:f4:5a:b1:73] Workstation local
Notice that homedog, the local machine, is visible both on IPv6 and IPv4. But yorkie, the remote machine, is visible only on IPv4. And avahi-resolve-host-name -4 yorkie.local hangs with no result.
EDIT: The situation is symmetric: yorkie sees itself on IPv4 and IPv6, but it sees homedog on IPv6 only.
On yorkie, the output from iptables -vnL is
Chain INPUT (policy ACCEPT 109K packets, 98M bytes)
pkts bytes target prot opt in out source destination
Chain FORWARD (policy ACCEPT 0 packets, 0 bytes)
pkts bytes target prot opt in out source destination
Chain OUTPUT (policy ACCEPT 108K packets, 94M bytes)
pkts bytes target prot opt in out source destination
(To make the display fit StackExchange without wrapping, I have taken a couple of liberties with horizontal space.) The display on homedog is identical except for the numbers: for all three, it displays 0 packets and 0 bytes.
(I have no clue how to interpret these outputs, but it may be informative that yorkie's current uptime is 41 days and homedog's current uptime is 6 hours.)
I found a closed ticket at http://avahi.org/ticket/297, which suggests that the problem is some sort of firewall configuration. I am a complete novice in this area, and through web search I have been unable to inform myself about how to use the iptables command to diagnose or repair the problem. I found another ticket as Debian bug 547974, but this bug was closed without explaining how to fix the problem.
The hypothesis is that somehow the service-discovery packet is being blocked—I don't know on which machine. Can anyone say how to discover which machine is blocking the packet and how to reconfigure it so Avahi discovers the IPv4 address?
firewall avahi
asked Feb 8 '13 at 23:12
Norman RamseyNorman Ramsey
3652623
bumped to the homepage by Community♦ 1 hour ago
This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.
iptables -vnLis a good start at dumping everything in there for IPv4 rules (ip6tablesis used for IPv6 rules). Ifhomedogcan see itself on both IPv4 and IPv6, the obvious next step to see where it's broken is to see ifyorkiecan see itself on both IPv4 and IPv6
– DerfK
Feb 8 '13 at 23:26
@DerfK thanks for helping me improve my question. Visibility is symmetric, butiptablesshows many more bytes and packets on yorkie.
– Norman Ramsey
Feb 9 '13 at 1:16
Do you actually need IPv4 here?
– Michael Hampton♦
Feb 9 '13 at 1:25
@Michael, I don't know. I have no particular brief for one or the other, but I can't figure out how to getsshto work with IPv6. I have my/etc/nsswitch.confconfigured to work with mdns4, but doingssh -6 yorkie.localresults in a failure to resolve the hostname.
– Norman Ramsey
Feb 9 '13 at 2:36
If avahi is actually running,ssh yorkieshould be sufficient.
– Michael Hampton♦
Feb 9 '13 at 2:38
|
show 1 more comment
On a Debian 6.0.6 system (squeeze) I am having trouble resolving a host using Avahi and IPv4. Here is a sample output:
: nr@homedog 10102 ; avahi-browse -a
+ eth0 IPv6 yorkie [00:1f:3b:d8:67:1d] Workstation local
+ eth0 IPv6 homedog [bc:5f:f4:5a:b1:73] Workstation local
+ eth0 IPv4 homedog [bc:5f:f4:5a:b1:73] Workstation local
Notice that homedog, the local machine, is visible both on IPv6 and IPv4. But yorkie, the remote machine, is visible only on IPv4. And avahi-resolve-host-name -4 yorkie.local hangs with no result.
EDIT: The situation is symmetric: yorkie sees itself on IPv4 and IPv6, but it sees homedog on IPv6 only.
On yorkie, the output from iptables -vnL is
Chain INPUT (policy ACCEPT 109K packets, 98M bytes)
pkts bytes target prot opt in out source destination
Chain FORWARD (policy ACCEPT 0 packets, 0 bytes)
pkts bytes target prot opt in out source destination
Chain OUTPUT (policy ACCEPT 108K packets, 94M bytes)
pkts bytes target prot opt in out source destination
(To make the display fit StackExchange without wrapping, I have taken a couple of liberties with horizontal space.) The display on homedog is identical except for the numbers: for all three, it displays 0 packets and 0 bytes.
(I have no clue how to interpret these outputs, but it may be informative that yorkie's current uptime is 41 days and homedog's current uptime is 6 hours.)
I found a closed ticket at http://avahi.org/ticket/297, which suggests that the problem is some sort of firewall configuration. I am a complete novice in this area, and through web search I have been unable to inform myself about how to use the iptables command to diagnose or repair the problem. I found another ticket as Debian bug 547974, but this bug was closed without explaining how to fix the problem.
The hypothesis is that somehow the service-discovery packet is being blocked—I don't know on which machine. Can anyone say how to discover which machine is blocking the packet and how to reconfigure it so Avahi discovers the IPv4 address?
firewall avahi
asked Feb 8 '13 at 23:12
Norman RamseyNorman Ramsey
3652623
On a Debian 6.0.6 system (squeeze) I am having trouble resolving a host using Avahi and IPv4. Here is a sample output:
: nr@homedog 10102 ; avahi-browse -a
+ eth0 IPv6 yorkie [00:1f:3b:d8:67:1d] Workstation local
+ eth0 IPv6 homedog [bc:5f:f4:5a:b1:73] Workstation local
+ eth0 IPv4 homedog [bc:5f:f4:5a:b1:73] Workstation local
Notice that homedog, the local machine, is visible both on IPv6 and IPv4. But yorkie, the remote machine, is visible only on IPv4. And avahi-resolve-host-name -4 yorkie.local hangs with no result.
EDIT: The situation is symmetric: yorkie sees itself on IPv4 and IPv6, but it sees homedog on IPv6 only.
On yorkie, the output from iptables -vnL is
Chain INPUT (policy ACCEPT 109K packets, 98M bytes)
pkts bytes target prot opt in out source destination
Chain FORWARD (policy ACCEPT 0 packets, 0 bytes)
pkts bytes target prot opt in out source destination
Chain OUTPUT (policy ACCEPT 108K packets, 94M bytes)
pkts bytes target prot opt in out source destination
(To make the display fit StackExchange without wrapping, I have taken a couple of liberties with horizontal space.) The display on homedog is identical except for the numbers: for all three, it displays 0 packets and 0 bytes.
(I have no clue how to interpret these outputs, but it may be informative that yorkie's current uptime is 41 days and homedog's current uptime is 6 hours.)
I found a closed ticket at http://avahi.org/ticket/297, which suggests that the problem is some sort of firewall configuration. I am a complete novice in this area, and through web search I have been unable to inform myself about how to use the iptables command to diagnose or repair the problem. I found another ticket as Debian bug 547974, but this bug was closed without explaining how to fix the problem.
The hypothesis is that somehow the service-discovery packet is being blocked—I don't know on which machine. Can anyone say how to discover which machine is blocking the packet and how to reconfigure it so Avahi discovers the IPv4 address?
firewall avahi
firewall avahi
asked Feb 8 '13 at 23:12
Norman RamseyNorman Ramsey
3652623
asked Feb 8 '13 at 23:12
Norman RamseyNorman Ramsey
3652623
edited Feb 9 '13 at 1:17
Norman Ramsey
asked Feb 8 '13 at 23:12
Norman RamseyNorman Ramsey
3652623
asked Feb 8 '13 at 23:12
Norman RamseyNorman Ramsey
3652623
asked Feb 8 '13 at 23:12
Norman RamseyNorman Ramsey
3652623
3652623
bumped to the homepage by Community♦ 1 hour ago
This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.
bumped to the homepage by Community♦ 1 hour ago
This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.
iptables -vnLis a good start at dumping everything in there for IPv4 rules (ip6tablesis used for IPv6 rules). Ifhomedogcan see itself on both IPv4 and IPv6, the obvious next step to see where it's broken is to see ifyorkiecan see itself on both IPv4 and IPv6
– DerfK
Feb 8 '13 at 23:26
@DerfK thanks for helping me improve my question. Visibility is symmetric, butiptablesshows many more bytes and packets on yorkie.
– Norman Ramsey
Feb 9 '13 at 1:16
Do you actually need IPv4 here?
– Michael Hampton♦
Feb 9 '13 at 1:25
@Michael, I don't know. I have no particular brief for one or the other, but I can't figure out how to getsshto work with IPv6. I have my/etc/nsswitch.confconfigured to work with mdns4, but doingssh -6 yorkie.localresults in a failure to resolve the hostname.
– Norman Ramsey
Feb 9 '13 at 2:36
If avahi is actually running,ssh yorkieshould be sufficient.
– Michael Hampton♦
Feb 9 '13 at 2:38
|
show 1 more comment
iptables -vnLis a good start at dumping everything in there for IPv4 rules (ip6tablesis used for IPv6 rules). Ifhomedogcan see itself on both IPv4 and IPv6, the obvious next step to see where it's broken is to see ifyorkiecan see itself on both IPv4 and IPv6
– DerfK
Feb 8 '13 at 23:26
@DerfK thanks for helping me improve my question. Visibility is symmetric, butiptablesshows many more bytes and packets on yorkie.
– Norman Ramsey
Feb 9 '13 at 1:16
Do you actually need IPv4 here?
– Michael Hampton♦
Feb 9 '13 at 1:25
@Michael, I don't know. I have no particular brief for one or the other, but I can't figure out how to getsshto work with IPv6. I have my/etc/nsswitch.confconfigured to work with mdns4, but doingssh -6 yorkie.localresults in a failure to resolve the hostname.
– Norman Ramsey
Feb 9 '13 at 2:36
If avahi is actually running,ssh yorkieshould be sufficient.
– Michael Hampton♦
Feb 9 '13 at 2:38
iptables -vnL is a good start at dumping everything in there for IPv4 rules (ip6tables is used for IPv6 rules). If homedog can see itself on both IPv4 and IPv6, the obvious next step to see where it's broken is to see if yorkie can see itself on both IPv4 and IPv6– DerfK
Feb 8 '13 at 23:26
iptables -vnL is a good start at dumping everything in there for IPv4 rules (ip6tables is used for IPv6 rules). If homedog can see itself on both IPv4 and IPv6, the obvious next step to see where it's broken is to see if yorkie can see itself on both IPv4 and IPv6– DerfK
Feb 8 '13 at 23:26
@DerfK thanks for helping me improve my question. Visibility is symmetric, but
iptables shows many more bytes and packets on yorkie.– Norman Ramsey
Feb 9 '13 at 1:16
@DerfK thanks for helping me improve my question. Visibility is symmetric, but
iptables shows many more bytes and packets on yorkie.– Norman Ramsey
Feb 9 '13 at 1:16
Do you actually need IPv4 here?
– Michael Hampton♦
Feb 9 '13 at 1:25
Do you actually need IPv4 here?
– Michael Hampton♦
Feb 9 '13 at 1:25
@Michael, I don't know. I have no particular brief for one or the other, but I can't figure out how to get
ssh to work with IPv6. I have my /etc/nsswitch.conf configured to work with mdns4, but doing ssh -6 yorkie.local results in a failure to resolve the hostname.– Norman Ramsey
Feb 9 '13 at 2:36
@Michael, I don't know. I have no particular brief for one or the other, but I can't figure out how to get
ssh to work with IPv6. I have my /etc/nsswitch.conf configured to work with mdns4, but doing ssh -6 yorkie.local results in a failure to resolve the hostname.– Norman Ramsey
Feb 9 '13 at 2:36
If avahi is actually running,
ssh yorkie should be sufficient.– Michael Hampton♦
Feb 9 '13 at 2:38
If avahi is actually running,
ssh yorkie should be sufficient.– Michael Hampton♦
Feb 9 '13 at 2:38
|
show 1 more comment
1 Answer
1
active
oldest
votes
This one isn't still fully diagnosed, but it was a combination of two problems:
On host
yorkie, some unknown daemon keeps installingiptablesrules. I remove the rules, but eventually they reappear.The more pernicious part:
yorkieis connected wirelessly, and **my Verizon ActionTec router was blocking mDNS packets.
With both problems resolved, avahi-browse -a works as expected.
answered Feb 16 '13 at 3:54
Norman RamseyNorman Ramsey
3652623
add a comment |
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "2"
};
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: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
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%2fserverfault.com%2fquestions%2f477068%2fhow-to-unblock-service-discovery-for-ipv4-via-avahi%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
This one isn't still fully diagnosed, but it was a combination of two problems:
On host
yorkie, some unknown daemon keeps installingiptablesrules. I remove the rules, but eventually they reappear.The more pernicious part:
yorkieis connected wirelessly, and **my Verizon ActionTec router was blocking mDNS packets.
With both problems resolved, avahi-browse -a works as expected.
answered Feb 16 '13 at 3:54
Norman RamseyNorman Ramsey
3652623
add a comment |
This one isn't still fully diagnosed, but it was a combination of two problems:
On host
yorkie, some unknown daemon keeps installingiptablesrules. I remove the rules, but eventually they reappear.The more pernicious part:
yorkieis connected wirelessly, and **my Verizon ActionTec router was blocking mDNS packets.
With both problems resolved, avahi-browse -a works as expected.
answered Feb 16 '13 at 3:54
Norman RamseyNorman Ramsey
3652623
add a comment |
This one isn't still fully diagnosed, but it was a combination of two problems:
On host
yorkie, some unknown daemon keeps installingiptablesrules. I remove the rules, but eventually they reappear.The more pernicious part:
yorkieis connected wirelessly, and **my Verizon ActionTec router was blocking mDNS packets.
With both problems resolved, avahi-browse -a works as expected.
answered Feb 16 '13 at 3:54
Norman RamseyNorman Ramsey
3652623
This one isn't still fully diagnosed, but it was a combination of two problems:
On host
yorkie, some unknown daemon keeps installingiptablesrules. I remove the rules, but eventually they reappear.The more pernicious part:
yorkieis connected wirelessly, and **my Verizon ActionTec router was blocking mDNS packets.
With both problems resolved, avahi-browse -a works as expected.
answered Feb 16 '13 at 3:54
Norman RamseyNorman Ramsey
3652623
answered Feb 16 '13 at 3:54
Norman RamseyNorman Ramsey
3652623
answered Feb 16 '13 at 3:54
Norman RamseyNorman Ramsey
3652623
answered Feb 16 '13 at 3:54
Norman RamseyNorman Ramsey
3652623
3652623
add a comment |
add a comment |
Thanks for contributing an answer to Server Fault!
- 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%2fserverfault.com%2fquestions%2f477068%2fhow-to-unblock-service-discovery-for-ipv4-via-avahi%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
iptables -vnLis a good start at dumping everything in there for IPv4 rules (ip6tablesis used for IPv6 rules). Ifhomedogcan see itself on both IPv4 and IPv6, the obvious next step to see where it's broken is to see ifyorkiecan see itself on both IPv4 and IPv6– DerfK
Feb 8 '13 at 23:26
@DerfK thanks for helping me improve my question. Visibility is symmetric, but
iptablesshows many more bytes and packets on yorkie.– Norman Ramsey
Feb 9 '13 at 1:16
Do you actually need IPv4 here?
– Michael Hampton♦
Feb 9 '13 at 1:25
@Michael, I don't know. I have no particular brief for one or the other, but I can't figure out how to get
sshto work with IPv6. I have my/etc/nsswitch.confconfigured to work with mdns4, but doingssh -6 yorkie.localresults in a failure to resolve the hostname.– Norman Ramsey
Feb 9 '13 at 2:36
If avahi is actually running,
ssh yorkieshould be sufficient.– Michael Hampton♦
Feb 9 '13 at 2:38