|
2013-04-20
, 05:11
|
Posts: 262 |
Thanked: 315 times |
Joined on Jun 2010
|
#12
|
|
2013-04-20
, 07:52
|
Posts: 2,154 |
Thanked: 8,464 times |
Joined on May 2010
|
#13
|
sudo iptables -A INPUT -p udp -d 224.0.0.251 --dport 5353 -j ACCEPT
sudo iptables -A INPUT -p udp -d ff02::fb --dport 5353 -j ACCEPT
|
2013-04-22
, 01:43
|
Posts: 262 |
Thanked: 315 times |
Joined on Jun 2010
|
#14
|
# iptables -L Chain INPUT (policy ACCEPT) target prot opt source destination Chain FORWARD (policy ACCEPT) target prot opt source destination Chain OUTPUT (policy ACCEPT) target prot opt source destination
|
2013-08-08
, 08:49
|
Posts: 2,154 |
Thanked: 8,464 times |
Joined on May 2010
|
#15
|
Tags |
avahi, avahi-daemon, zeroconf |
|
I then installed the Debian avahi/mdns packages on my laptop.
Neither is able to ping the .local address of its counterpart.
Running avahi-discover on my laptop, I can see only the laptop itself.
On the n900, 'ps -ef | grep avahi' shows two processes running okay. And the changes to the /etc/nsswitch.conf file look correct (same as the laptop).
Do you have any idea why it might not be working? I guess I can run tcpdump for multicast packets next, if need be.