tor 2006-01-19 klockan 04:11 +1100 skrev Anand Kumria:
> Hi Mikael,
>
> On Wed, Jan 18, 2006 at 03:09:07PM +0100, Mikael Nilsson wrote:
> > Package: zeroconf
> > Version: 0.6.1-1
> > Severity: critical
> > Justification: breaks unrelated software
>
> I'll leave these as is, though I suspect these are inflated.
I'll let you be the judge on that, even though I don't consider my setup
as particularly peculiar. And it made me spend some time with the
support at my ISP :-).
> > # ip addr show dev eth0
> > 2: eth0: <BROADCAST,MULTICAST,NOTRAILERS,UP> mtu 1500 qdisc pfifo_fast qlen
> > 1000
> > link/ether 00:0d:56:ec:09:3c brd ff:ff:ff:ff:ff:ff
> > inet 192.168.0.1/24 brd 192.168.0.255 scope global eth0
> > inet6 fe80::20d:56ff:feec:93c/64 scope link
> > valid_lft forever preferred_lft forever
>
> Could you also show me what 'ip addr route' has before and after
> zeroconf is involved?
You mean 'ip route' I assume?
Without zeroconf:
192.168.0.0/24 dev eth0 scope link
default via 192.168.0.254 dev eth0
/etc/resolv.conf:
----------------------
# Dynamic resolv.conf(5) file for glibc resolver(3) generated by resolvconf(8)
# DO NOT EDIT THIS FILE BY HAND -- YOUR CHANGES WILL BE OVERWRITTEN
nameserver 192.168.0.254
search nada.kth.se lan
----------------------
nada.kth.se is my own addition in /etc/resolvconf/resolv.conf.d/base
lan is configured on my router, which calls itself SpeedTouch.lan.
/etc/nsswitch.conf
---------------------
# /etc/nsswitch.conf
#
# Example configuration of GNU Name Service Switch functionality.
# If you have the `glibc-doc' and `info' packages installed, try:
# `info libc "Name Service Switch"' for information about this file.
passwd: compat
group: compat
shadow: compat
hosts: files dns mdns
networks: files
protocols: db files
services: db files
ethers: db files
rpc: db files
netgroup: nis
----------------------
With zeroconf:
Oh, I should add that DHCP works very randomly when zeroconf is
installed. I have to kill dhcpcd-bin several times and retry before I
get an IP. This does not happen without zeroconf.
ip route:
192.168.0.0/24 dev eth0 scope link
169.254.0.0/16 dev eth0 proto kernel scope link src 169.254.253.111
default via 192.168.0.254 dev eth0
/etc/resolv.conf
----------------------
# Dynamic resolv.conf(5) file for glibc resolver(3) generated by resolvconf(8)
# DO NOT EDIT THIS FILE BY HAND -- YOUR CHANGES WILL BE OVERWRITTEN
nameserver 192.168.0.254
search nada.kth.se lan
-----------------------
/etc/nsswitch.conf
-------------------------
# /etc/nsswitch.conf
#
# Example configuration of GNU Name Service Switch functionality.
# If you have the `glibc-doc' and `info' packages installed, try:
# `info libc "Name Service Switch"' for information about this file.
passwd: compat
group: compat
shadow: compat
hosts: files dns mdns
networks: files
protocols: db files
services: db files
ethers: db files
rpc: db files
netgroup: nis
-------------------------
Thus, no difference to resolv.conf or nsswitch.conf. The only difference
is this route line:
169.254.0.0/16 dev eth0 proto kernel scope link src 169.254.253.111
>
> From what you have given me, what I think is happening is that your ADSL
> router also has link-local multicast name resolution available. And
> that for some reason the link-local address nameserver address is being
> placed into /etc/resolv.conf
Hmm, trying to help, I telnetted to the router. Here's the command set for ip:
apadd : Assigns an IP address to an IP interface.
apdelete : Removes an IP address from an IP interface.
aplist : Shows all configured IP addresses.
ping : Sends ICMP ECHO_REQUEST packets.
traceroute : Sends ICMP/UDP packets to trace the ip path.
sendto : Sends UDP packets.
iflist : Shows all IP interfaces.
ifconfig : Configures IP interface parameters.
ifwait : Wait for a status change of an IP interface.
rtadd : Adds a route to the routing table.
rtdelete : Deletes a route from the routing table.
rtlist : Shows the routing table.
arpadd : Adds an entry to the ARP cache of a broadcast IP interface.
arpdelete : Deletes an ARP entry.
arplist : Shows the ARP cache.
mcadd : Adds a MC address to a MC capable interface.
mcdelete : Deletes a MC address to a MC capable interface.
mclist : List all MC addresses.
config : Gets/Sets global IP stack configuration options.
flush : Flushes all static IP parameters. Dynamic info (e.g. from
PPP links) remains.
Trying mclist I get nothing. aplist gives me:
3 PPPoE Type:SERIAL
ip-addr:84.217.29.123 point-to-point:195.58.100.215
UP RUNNING pat MTU:1452 Group:0
IPRX bytes:204264443 unicastpkts:200576 brcastpkts:0
IPTX bytes:11802086 unicastpkts:143993 brcastpkts:0 droppkts:0
1 eth0 Type:Ethernet HWaddr 00:0e:50:79:b2:cc BRHWaddr
ff:ff:ff:ff:ff:ff
ip-addr:169.254.141.11 mask:255.255.0.0
UP RUNNING MTU:1500 Group:2
IPRX bytes:12215980 unicastpkts:147522 brcastpkts:116
IPTX bytes:204452159 unicastpkts:202018 brcastpkts:0 droppkts:0
1 eth0 Type:Ethernet HWaddr 00:0e:50:79:b2:cc BRHWaddr
ff:ff:ff:ff:ff:ff
ip-addr:192.168.0.254 mask:255.255.255.0
UP RUNNING MTU:1500 Group:2
IPRX bytes:12215980 unicastpkts:147522 brcastpkts:116
IPTX bytes:204452159 unicastpkts:202018 brcastpkts:0 droppkts:0
0 loop Type:0
ip-addr:127.0.0.1 mask:255.0.0.0
UP RUNNING MTU:1500 Group:1
IPRX bytes:0 unicastpkts:0 brcastpkts:0
IPTX bytes:0 unicastpkts:0 brcastpkts:0 droppkts:0
arplist:
Intf IP-address HW-address Type
eth0 192.168.0.1 00:0d:56:ec:09:3c STATIC
eth0 169.254.141.11 00:00:00:00:00:00 STATIC
eth0 169.254.253.111 00:0d:56:ec:09:3c DYNAMIC
eth0 239.255.255.250 01:00:5e:7f:ff:fa DYNAMIC
Anything else that might help? In any case, the link local address does
*not* end up in resolv.conf.
Actually, putting it there manually makes address lookup work again :-)
>
> host, should never be querying a link-local address, only looks in
> /etc/resolv.conf -- so if there is a link-local address there, how did
> it get there? Was it already there? Was it provided?
It is not there, but the answer still comes from the link-local address
of the router... the question is why it does *not* come from that
address when zeroconf is not installed?
>
> If there isn't a link-local address there, then perhaps the ADSL modem
> is generating packets with an incorrect source address? I'll need the
> information about your resolv.conf and nsswitch file (with before/after)
> to determine what next.
Should I try to do packet capture somehow? Let me know what to try.
/Mikael
--
Plus ça change, plus c'est la même chose
