Reply
Thread Tools
Posts: 220 | Thanked: 178 times | Joined on Jun 2010
#11
@pali, I've installed this on my n900 from the repos (-maemo5 package version) and rebooted my phone.

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.
 
Posts: 220 | Thanked: 178 times | Joined on Jun 2010
#12
It actually worked, just once, from my laptop to the n900. Then it stopped working some minutes later, while I was testing from the other end.

Running 'tcpdump -i wlan0 -n multicast' on both ends shows requests being sent, but neither end receives the requests from the other.

I am beginning to suspect the router (which has really b0rked firmware, e.g. local dns lookups return the router's IP, even for non-existent addresses!).

Or possibly the radio in my n900 is dying, because it kept not being able to see the wlan.
 
Posts: 1,930 | Thanked: 7,381 times | Joined on May 2010
#13
check also firewall. mDNS using udp multicast port 5353.

iptables for ipv4:
Code:
sudo iptables -A INPUT -p udp -d 224.0.0.251 --dport 5353 -j ACCEPT
iptables for ipv6:
Code:
sudo iptables -A INPUT -p udp -d ff02::fb --dport 5353 -j ACCEPT
By default n900 does not use firewall, but all (desktop) linux distribution yes.
 

The Following 2 Users Say Thank You to pali For This Useful Post:
Posts: 220 | Thanked: 178 times | Joined on Jun 2010
#14
Thanks pali. I'm running a server install of Debian Wheezy. My iptables look like this :

Code:
# 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


So it would seem this piece of junk Huawei HG556a router is to blame, even with the most recent firmware. I can't believe hw manufacturers can release such broken pieces of junk!
 
Posts: 1,930 | Thanked: 7,381 times | Joined on May 2010
#15
 
Reply

Tags
avahi, avahi-daemon, zeroconf

Thread Tools

 
Forum Jump


All times are GMT -4. The time now is 05:58 PM.