named X route monitor problem
Hi, I am running OpenBSD 4.1 on a firewall/router. For some unknown reason (to me), whenever I start the command nice route monitor after a little while, I begin to get an enormous quantity of messages like: got message of size 104 on ... RTM_MISS: Lookup failed on this address: len 104, table 0, pid: 0, seq o, errno 0m flags:DONE locks: inits: sockaddrs: DST 2001:503:a83e::2:31 When it happens, I notice that named begins to take over the CPU, holding more than 70% of it. Even if I flush PF with pfctl -F all, the problem continues to happen. My question are: 1. Is this address an IPv6 one? Can I find out who is asking for it and why? 2. How can I tell named not to deal with IPv6? Thanks Regards, Jeff. -- Get a Free E-mail Account at Mail.com! Choose From 100+ Personalized Domains Visit http://www.mail.com today
Re: named X route monitor problem
On 6/21/07, Jeff Santos [EMAIL PROTECTED] wrote: 1. Is this address an IPv6 one? Can I find out who is asking for it and why? ugghh, named log? tcpdump? 2. How can I tell named not to deal with IPv6? an ugly workaround would be to block all ipv6 traffic on named port. -- almir
Re: named X route monitor problem
On 6/21/07, Jeff Santos [EMAIL PROTECTED] wrote: ... sockaddrs: DST 2001:503:a83e::2:31 ... My question are: 1. Is this address an IPv6 one? Can I find out who is asking for it and why? Yes, it's an IPv6 address. It's almost certainly being asked for by named in the course of trying to resolve some name: that address is of a DNS server. 2. How can I tell named not to deal with IPv6? If you don't have real IPv6 connectivity, you should probably add -4 to the value of named_flags you set in your /etc/rc.conf.local, so that named won't try to query nameservers with IPv6 address. Indeed, that may completely solve your issue. Oh, and you should consider passing 'route monitor' the -n option to suppress address-name lookups. When you're looking at local routing info, the numbers usually are more helpful, in my experience. Philip Guenther
