NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
mdns
3 Topics
Multicast requests blocked ?
We have this WNR614 router being setup to connect few HP wireless printers for printing from Mobiles .But non of the HP printers would list in mobile . The same scenario worked with other brand routers. Interesting point is that canon wireless printers does get listed. When checked with Wireshark for monitoring traffic it was found that MDNS traffic (Multicast) was getting blocked. Is there a way to enable Multicast traffic in this router or is it some sort of a bug ? There are not much options in the advanced page too. The router is running the latest firmware . Any suggestions would be greatly appreciated . Thanks in Advance CinjuSolved5.6KViews0likes6CommentsReadyNas 202 - Withdrawing mDNS address records / Withdrawing LLMNR address records etc...
Hi, I've noticed recently my ReadyNas 202 has been "playing up". Normally I'd expect the activity light to blink away if its carrying out a back up or in use. However just recently, I've seen the activity light continually flashing at quite a rapid rate. The device is accessible via both the web interface as well as the shares through my laptop. I looked in the basic log and couldn't find anything, but I had installed the loganalyzer app and noticed the following entries continually appearing each second: Apr 21 23:42:26 Batman avahi-daemon[1615]: Withdrawing mDNS address records for 2a02:c7d:5bcc:2e00:a263:91ff:fe65:4abd on eth1. Apr 21 23:42:26 Batman avahi-daemon[1615]: Withdrawing mDNS address records for fdbd:33c0:f95c:0:a263:91ff:fe65:4abd on eth1. Apr 21 23:42:26 Batman avahi-daemon[1615]: Withdrawing LLMNR address records for fdbd:33c0:f95c:0:a263:91ff:fe65:4abd on eth1. Apr 21 23:42:26 Batman avahi-daemon[1615]: Withdrawing mDNS address records for 192.168.0.3 on eth1. Apr 21 23:42:26 Batman avahi-daemon[1615]: Withdrawing LLMNR address records for 192.168.0.3 on eth1. Apr 21 23:42:26 Batman avahi-daemon[1615]: Withdrawing mDNS address records for 2a02:c7d:5bcc:2e00:a263:91ff:fe65:4abc on eth0. Apr 21 23:42:26 Batman avahi-daemon[1615]: Withdrawing LLMNR address records for 2a02:c7d:5bcc:2e00:a263:91ff:fe65:4abc on eth0. Apr 21 23:42:26 Batman avahi-daemon[1615]: Withdrawing mDNS address records for fdbd:33c0:f95c:0:a263:91ff:fe65:4abc on eth0. Apr 21 23:42:26 Batman avahi-daemon[1615]: Withdrawing LLMNR address records for fdbd:33c0:f95c:0:a263:91ff:fe65:4abc on eth0. Apr 21 23:42:26 Batman avahi-daemon[1615]: Withdrawing mDNS address records for 192.168.0.2 on eth0. Apr 21 23:42:26 Batman avahi-daemon[1615]: Withdrawing LLMNR address records for 192.168.0.2 on eth0. Apr 21 23:42:26 Batman avahi-daemon[1615]: Host name conflict, retrying with Batman-278 Apr 21 23:42:26 Batman avahi-daemon[1615]: Registering new mDNS address record for 2a02:c7d:5bcc:2e00:a263:91ff:fe65:4abd on eth1.*. Apr 21 23:42:26 Batman avahi-daemon[1615]: Registering new LLMNR address record for 2a02:c7d:5bcc:2e00:a263:91ff:fe65:4abd on eth1.*. Apr 21 23:42:26 Batman avahi-daemon[1615]: Registering new mDNS address record for fdbd:33c0:f95c:0:a263:91ff:fe65:4abd on eth1.*. Apr 21 23:42:26 Batman avahi-daemon[1615]: Registering new LLMNR address record for fdbd:33c0:f95c:0:a263:91ff:fe65:4abd on eth1.*. Apr 21 23:42:26 Batman avahi-daemon[1615]: Registering new mDNS address record for 192.168.0.3 on eth1.IPv4. Apr 21 23:42:26 Batman avahi-daemon[1615]: Registering new LLMNR address record for 192.168.0.3 on eth1.IPv4. Apr 21 23:42:26 Batman avahi-daemon[1615]: Registering new mDNS address record for 2a02:c7d:5bcc:2e00:a263:91ff:fe65:4abc on eth0.*. Apr 21 23:42:26 Batman avahi-daemon[1615]: Registering new LLMNR address record for 2a02:c7d:5bcc:2e00:a263:91ff:fe65:4abc on eth0.*. Apr 21 23:42:26 Batman avahi-daemon[1615]: Registering new mDNS address record for fdbd:33c0:f95c:0:a263:91ff:fe65:4abc on eth0.*. Apr 21 23:42:26 Batman avahi-daemon[1615]: Registering new LLMNR address record for fdbd:33c0:f95c:0:a263:91ff:fe65:4abc on eth0.*. Apr 21 23:42:26 Batman avahi-daemon[1615]: Registering new mDNS address record for 192.168.0.2 on eth0.IPv4. Apr 21 23:42:26 Batman avahi-daemon[1615]: Registering new LLMNR address record for 192.168.0.2 on eth0.IPv4. I noticed it stated there is a conflict but I have no other devices with the same name on the network. Its only recently I've started to get these messages. I've reset the box as well as router hoping it may clear any cached entries in their memory but no luck. Can anyone shed any light on this. System is running: Firmware:6.4.2SolvedAirPrint and ReadyNASOS6
Hey, I've been trying to get my ReadyNAS to operate as a 'print server' for my local network, including with AirPrint functionallity. I have a Brother wifi printer (so it's not connected via USB) and have sucessfully installed the required CUPS and foomatic filter packages, and have the printer shared with my network without issue. The next issue was AirPrint. I've read all the posts in this forun where people have sucessfully got it working with pre-iOS6 clients; but have had no success with the post-6 devices. I believe I have figured out why.... The issue is Avahi, and the advertising of the printer as an AirPrint printer. Previous to iOS6, the Avahi .service file did not make use of the <subtype> directive; but since iOS6, a specific <subtype> setting is required in order for iOS to 'see' the printer. Unforunately, it is the use of the <subtype> directive in the .service file which is causing Avahi to crash on the ReadyNAS - and thus prevent the NAS from advertising the AirPrint printers to the local network. The Avahi .service file for my Brother wifi printer was created with this script: https://raw.github.com/tjfontaine/airprint-generate/master/airprint-generate.py The script spits out a valid .service file which contains everything which SHOULD be required in order to advertise the printer via mDNS/Bonjour for the iOS devices to pick up. The problem is that Avahi crashes while it is parsing any .service file which contains a <subtype> option. This can easily be reproduced if you upload a .service file created using the above script (or any other example you find with google) and run Avahi from a terminal as root. The .service file for my Brother wifi printer is: <?xml version="1.0" ?><!DOCTYPE service-group SYSTEM 'avahi-service.dtd'> <service-group> <name replace-wildcards="yes">AirPrint Brother_DCP-1610W @ %h</name> <service> <type>_ipp._tcp</type> <subtype>_universal._sub._ipp._tcp</subtype> <port>631</port> <txt-record>txtvers=1</txt-record> <txt-record>qtotal=1</txt-record> <txt-record>Transparent=T</txt-record> <txt-record>URF=none</txt-record> <txt-record>rp=printers/Brother_DCP-1610W</txt-record> <txt-record>note=Brother DCP-1610W</txt-record> <txt-record>product=(GPL Ghostscript)</txt-record> <txt-record>printer-state=3</txt-record> <txt-record>printer-type=0x80b004</txt-record> <txt-record>pdl=application/octet-stream,application/pdf,application/postscript,image/gif,image/jpeg,image/png,image/tiff,image/urf,text/html,text/plain,application/vnd.adobe-reader-postscript,application/vnd.cups-command,application/vnd.cups-pdf</txt-record> </service> </service-group> (different printers will obviously have different output from the script... but the key point of note here is the inclusion of the <subtype> directive) If the <subtype> directive is commented out, Avahi on the ReadyNAS will parse and load the file without issue (but the printer is not picked up by iOS due to the missing directive): Found user 'avahi' (UID 84) and group 'avahi' (GID 84). Successfully dropped root privileges. avahi-daemon 0.6.31 starting up. Successfully called chroot(). Successfully dropped remaining capabilities. Loading service file /services/AirPrint-Brother_DCP-1610W.service. Loading service file /services/frontview.service. Loading service file /services/nut.service. Joining mDNS multicast group on interface bond0.IPv4 with address 192.168.67.248. New relevant interface bond0.IPv4 for mDNS. Joining LLMNR multicast group on interface bond0.IPv4 with address 192.168.67.248. New relevant interface bond0.IPv4 for LLMNR. Network interface enumeration completed. Registering new mDNS address record for 192.168.67.248 on bond0.IPv4. Registering new LLMNR address record for 192.168.67.248 on bond0.IPv4. Server startup complete. Host name is NAS.local. Local service cookie is 2760298420. All host RR's have been announced/verified : SERVER RUNNING Service "NAS" (/services/nut.service) successfully established. Service "ReadyNAS Administration on NAS" (/services/frontview.service) successfully established. Service "AirPrint Brother_DCP-1610W @ NAS" (/services/AirPrint-Brother_DCP-1610W.service) successfully established. However, with the <subtype> option present, Avahi crashed out at startup: Found user 'avahi' (UID 84) and group 'avahi' (GID 84). Successfully dropped root privileges. avahi-daemon 0.6.31 starting up. Successfully called chroot(). Successfully dropped remaining capabilities. Loading service file /services/AirPrint-Brother_DCP-1610W.service. Loading service file /services/frontview.service. Loading service file /services/nut.service. Joining mDNS multicast group on interface bond0.IPv4 with address 192.168.67.248. New relevant interface bond0.IPv4 for mDNS. Joining LLMNR multicast group on interface bond0.IPv4 with address 192.168.67.248. New relevant interface bond0.IPv4 for LLMNR. Network interface enumeration completed. Registering new mDNS address record for 192.168.67.248 on bond0.IPv4. Registering new LLMNR address record for 192.168.67.248 on bond0.IPv4. Server startup complete. Host name is NAS.local. Local service cookie is 1803852026. avahi-daemon: running [NAS.local]: entry.c:1080: avahi_server_add_service_subtype: Assertion `flags & AVAHI_PUBLISH_USE_MULTICAST || flags & AVAHI_PUBLISH_USE_WIDE_AREA' failed. I believe this is an issue related to the version of Avahi present on the ReadyNAS. Is there any chance of Netgear upgrading the version to one which doesn't contain this bug, or at the very least patch something which will cause Avahi to crash at start? I'd appreciate if anyone else can test their system to see if they get a similar problem with Avahi - just to make sure i'm not doing something completely brain-dead :) If we can get this crashing issue resolved, i'm pretty sure we can get AirPrint working again in ReadyNASOS6. Cheers.5.9KViews0likes6Comments
