MDNS across two interfaces WITHOUT Avahi - help !
-
Yep - Different MACs but asking for the same name on the network.
-
Yep - Different MACs but asking for the same name on the network.
Cool - yeah I think thats thee conclusion I came to last time I looked at this ! It was a naming issues which lent itself to being an Avahi 'thing'Maybe not… :(
This is what I see in the DHCP reservation table now and Avahi isn't running:
10.0.101.101 a8:88:08:69:c5:5c BW-iPhone-361 2013/09/17 22:50:33 2013/09/18 22:50:33 online active
My iphone has been renamed 361 times ! Why does this not happen on any other F/W device I have ever had at home ? I have been running Asus RTN66U with no such shenanigans !
-
I do not know. Perhaps it is an avahi issue then?
Try this with your apple device and see if it gets fixed.
Give it a 1 single name using a static DHCP assignment on wired based on MAC.
Then give it a slightly different name in DHCP on the interface wireless is on based on MAC.(You know how to go into DHCP leases and do that right?)
(You may be able to give the same name on both interfaces for the 2 MACs, but I wouldn't think so. Never tried)
One would think this would put an end to all the renaming.
-
It's an Avahi issue.
Your device will attach itself to your network and Avahi then announces the mDNS name to the local subnet and then routes it to the next subnet. I believe it also cache's the name in its own database.
The next time you attach the same devices to the network, the announcement goes out and Avahi thinks there's a duplicate. The Mac responds to the duplication message by renaming itself. All of my machines do this to a certain extent and then by the second or third iteration it stops.
Removing Avahi and renaming your devices solves the issue.
-
Well - yeah… But wouldn't a static map and name also do it? (just guessing here)
-
Unfortunately, it doesn't.
I have a static IP for my Mac server (10.0.1.240). On occasion when I reboot the machine and Avahi is running, it renames the box's mDNS name because it thinks there's a conflict.
I also have another machine with two NICs and two static IPs. It's on both my 10.0.1.0/24 and 10.0.2.0/24 networks. The same thing will happen to that machine because it's on both networks with the same mDNS name.
I don't know exactly how Avahi works, but it seems to be caching the names and may not be associating them with a MAC address or some other voodoo.
-
BUT YOU NEED IT! What will you do without iStuff? ;D
OK - Lets hope you guys can make IGMP proxy work for you then.
(Did I use up all the possible wrong answers yet?)
-
I think we're going to see the proliferation of more mDNS traffic over time, especially in SOHO and home networks. Nearly all of Apple's devices communicate over mDNS to make networking and resource sharing easier by declaring the device and its available services on the network. Google TV and other streaming TV implementations rely on mDNS, and I'll assume that Google will be using mDNS as a standard in all of their mobile devices for the same reason Apple did–to make device and service availability simple for folks.
So I can see mDNS support becoming more of a requirement than a nice to have in the future. So breathing life back into the Avahi project or something similar to it would be a good thing. Either that or someone smarter than me could tell me how to correctly set up IGMP for two LANs and make mDNS route properly.
-
Well - I'm either not smarter than you or I'm just hoarding my arcane wisdom. You decide :P
-
Well - I'm either not smarter than you or I'm just hoarding my arcane wisdom. You decide :P
:|