Ticket #297 (closed defect: invalid)
Can't resolve names via ipv4
| Reported by: | cortana | Owned by: | lennart |
|---|---|---|---|
| Milestone: | Component: | avahi-daemon | |
| Keywords: | Cc: |
Description
For some reason that's beyond me, I can't get avahi on this particular system (thoth) to work with ipv4.
$ uname -r 2.6.30-bpo.2-amd64
$ lspci -v -s 06:00 06:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168B PCI Express Gigabit Ethernet controller (rev 02)
Subsystem: ASUSTeK Computer Inc. Device 82c6 Flags: bus master, fast devsel, latency 0, IRQ 55 I/O ports at d800 [size=256] Memory at fbdff000 (64-bit, non-prefetchable) [size=4K] Memory at faef0000 (64-bit, prefetchable) [size=64K] Expansion ROM at fbdc0000 [disabled] [size=128K] Capabilities: [40] Power Management version 3 Capabilities: [50] Message Signalled Interrupts: Mask- 64bit+ Queue=0/0 Enable+ Capabilities: [70] Express Endpoint, MSI 01 Capabilities: [b0] MSI-X: Enable- Mask- TabSize?=2 Capabilities: [d0] Vital Product Data <?> Capabilities: [100] Advanced Error Reporting <?> Capabilities: [140] Virtual Channel <?> Capabilities: [160] Device Serial Number 00-e0-4c-68-00-00-00-03 Kernel driver in use: r8169 Kernel modules: r8169
$ ip addr show dev eth0 2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP qlen 1000
link/ether 00:24:8c:71:4d:1d brd ff:ff:ff:ff:ff:ff inet 10.0.0.1/16 brd 10.0.255.255 scope global eth0 inet6 fe80::224:8cff:fe71:4d1d/64 scope link
valid_lft forever preferred_lft forever
$ ip route 81.110.188.0/22 dev eth1 proto kernel scope link src 81.110.190.38 10.0.0.0/16 dev eth0 proto kernel scope link src 10.0.0.1 default via 81.110.188.1 dev eth1
The system can resolve its own name fine, but anything else just doesn't show up.
$ avahi-browse -avt Server version: avahi 0.6.23; Host name: thoth.local E Ifce Prot Name Type Domain + eth0 IPv6 HP OfficeJet? 4215 @ thoth Internet Printer local + eth0 IPv6 Xerox Phaser 6100 @ thoth Internet Printer local + eth0 IPv4 HP OfficeJet? 4215 @ thoth Internet Printer local + eth0 IPv4 Xerox Phaser 6100 @ thoth Internet Printer local + eth0 IPv6 saned _sane-port._tcp local + eth0 IPv4 saned _sane-port._tcp local + eth0 IPv6 Sam Morris's encryption keys GnuPG/PGP HKP Key Server local + eth0 IPv6 durandal.local Web Site local + eth0 IPv6 Sam Morris on durandal Web Site local + eth0 IPv6 thoth [00:24:8c:71:4d:1d] Workstation local + eth0 IPv6 durandal [00:1c:bf:9c:77:6c] Workstation local + eth0 IPv6 durandal [00:13:77:60:aa:1d] Workstation local + eth0 IPv4 thoth [00:24:8c:71:4d:1d] Workstation local : Cache exhausted : All for now
$ avahi-resolve-host-name durandal.local durandal.local fe80::21c:bfff:fe9c:776c
$ avahi-resolve-host-name -4 durandal.local Failed to resolve host name 'durandal.local': Timeout reached
Unfortunately I don't see anything suspicious in the system logs.
Other systems are similarly unable to resolve this system's host name via ipv4, but ipv6 works fine.
Here's what happens when I run 'avahi-resolve-host-name -4 thoth.local' on another host on the network. The result is 'timeout reached'.
Packet trace on the other host: $ tshark -pn -i eth0 -R dns Capturing on eth0
0.000000 fe80::213:77ff:fe60:aa1d -> ff02::fb MDNS Standard query A thoth.local, "QM" question 0.000071 10.0.1.1 -> 224.0.0.251 MDNS Standard query A thoth.local, "QM" question 1.001460 fe80::213:77ff:fe60:aa1d -> ff02::fb MDNS Standard query A thoth.local, "QM" question 1.001527 10.0.1.1 -> 224.0.0.251 MDNS Standard query A thoth.local, "QM" question 3.003879 fe80::213:77ff:fe60:aa1d -> ff02::fb MDNS Standard query A thoth.local, "QM" question 3.003942 10.0.1.1 -> 224.0.0.251 MDNS Standard query A thoth.local, "QM" question
Packet trace on thoth: $ tshark -pn -i eth0 -R dns Capturing on eth0
1.755521 fe80::213:77ff:fe60:aa1d -> ff02::fb MDNS Standard query A thoth.local, "QM" question 2.757001 fe80::213:77ff:fe60:aa1d -> ff02::fb MDNS Standard query A thoth.local, "QM" question 4.759471 fe80::213:77ff:fe60:aa1d -> ff02::fb MDNS Standard query A thoth.local, "QM" question
So it appears that the IPv4 packets from the other host are disappearing. Maybe this isn't an avahi problem after all, but I'd appreciate a second opinion (and, if you have them, any suggestions for other things to try). :)
