Date: Tue, 16 Jun 1998 10:30:30 +0100 From: Richard Smith <richard@jezebel.demon.co.uk> To: Questions FreeBSD <freebsd-questions@FreeBSD.ORG> Subject: Re: amd & named Message-ID: <35863B36.A3C535DE@jezebel.demon.co.uk> References: <35851481.5B205E64@jezebel.demon.co.uk>
next in thread | previous in thread | raw e-mail | index | archive | help
I have solved the problem of 'amd' causing a 'dial-up' event. The problem was indeed a reverse look-up on my own IP address. I added a forward and reverse primary domain containing only my IP address to named.boot and the problem has gone away. Thanks for listening, Richard. Richard Smith wrote: > > I am having a problem with starting 'amd' at boot time on my home > machine. > > The machine is running FBSD 2.2.6R. It is not on a LAN. It starts > 'user-PPP' > at boot time (dial-on-demand) to access my ISP via a dial-up connection. > I start 'tcpdump' to a logfile at boot time also. 'named' is running > cache-only. > > I have been running the above configuration (less 'amd') for a few > months. > The dial-on-demand is well behaved and only brings up the telephone line > when I need it. > > After much hassle (and guidance from the freebsd-questions archive), I > finally > got 'amd' working, auto-mounting my local cdrom and floppy drive. > > The problem is that at boot time as 'amd' is starting, a dial-up event > occurs, and the boot process suspends (ie. 'amd' does not fork) until > what appears to be a DNS query has been completed (or times out). > > I do not recognise the tcpdump messages, other than that they are > directed > to my ISPs name servers. I suspected that they may be reverse look-ups, > so > I added the 'options fake_iquery' to named.boot. No change. > > Q. Does 'options fake_iquery' work with a 'cache only' name server, or > will > I need to make it a primary name server? > > The tcpdump messages are as follows... > -------- > 12:35:33.720239 158.152.38.143.1028 > 158.152.1.43.domain: 50384+ (45) > (ttl 64, id 6) > 12:35:36.730165 158.152.38.143.1029 > 158.152.1.58.domain: 50384+ (45) > (ttl 64, id 7) > 12:35:39.741371 158.152.38.143.domain > 158.152.1.43.domain: 57783+ (45) > (ttl 64, id 9) > 12:35:45.750137 158.152.38.143.domain > 158.152.1.58.domain: 57781+ (45) > (ttl 64, id 10) > 12:35:45.750305 158.152.38.143.iad2 > 158.152.1.43.domain: 50384+ (45) > (ttl 64, id 11) > 12:35:45.980194 158.152.1.58.domain > 158.152.38.143.domain: 57781 q: > 143.38.152.158.in-addr. 1/4/4 . (247) (ttl 61, id 52558) > 12:35:46.020212 158.152.1.43.domain > 158.152.38.143.iad2: 50384 q: > 143.38.152.158.in-addr. 1/4/4 (247) (ttl 61, id 9603) > 12:35:46.053867 158.152.38.143.1021 > 158.152.38.143.sunrpc: udp 56 (ttl > 64, id 14) > 12:35:46.054050 158.152.38.143.1021 > 158.152.38.143.sunrpc: udp 56 (ttl > 64, id 14) > 12:35:46.054865 158.152.38.143.sunrpc > 158.152.38.143.1021: udp 28 (ttl > 64, id 15) > 12:35:46.058949 158.152.38.143.iad3 > 158.152.38.143.1023: udp 92 (ttl > 64, id 16) > 12:35:46.059239 158.152.38.143.sunrpc > 158.152.38.143.1021: udp 28 (ttl > 64, id 15) > 12:35:46.060093 158.152.38.143.1020 > 158.152.38.143.sunrpc: udp 56 (ttl > 64, id 17) > 12:35:46.063463 158.152.38.143.iad3 > 158.152.38.143.1023: udp 92 (ttl > 64, id 16) > 12:35:46.063630 158.152.38.143.1020 > 158.152.38.143.sunrpc: udp 56 (ttl > 64, id 17) > 12:35:46.063870 158.152.38.143.sunrpc > 158.152.38.143.1020: udp 28 (ttl > 64, id 18) > 12:35:46.067975 158.152.38.143.sunrpc > 158.152.38.143.1020: udp 28 (ttl > 64, id 18) > 12:35:46.069124 158.152.38.143.1023 > 158.152.38.143.iad3: udp 96 (ttl > 64, id 19) > 12:35:46.070765 158.152.38.143.1023 > 158.152.38.143.iad3: udp 96 (ttl > 64, id 19) > -------- > 158.152.38.143 is my IP, and 158.152.1.43 & 158.152.1.58 are my ISPs > name servers. > > Please also note that I have NFS client and server enabled (I am not > sure if > this is necessary to make 'amd' work, I guess I need to go back and > disable > them once again). > > Also confusing is why 158.152.38.143 > 158.152.38.143 packets are > being detected by tcpdump at all. It's only supposed to be looking at > 'tun0' which should only see external traffic. Or am I missing > something. > > In rc.conf, I have the following settings (among others): > -------- > hostname="jezebel.demon.co.uk" # Set this! > nisdomainname="NO" # Set to NIS domain if using NIS (or NO). > ... > amd_flags="-a /a -c 1800 -k i386 -d demon.co.uk -l syslog /a > /etc/amd.map" > -------- > > Finally, if I let the dial-up event conplete, 'amd' works fine and only > reports the following warning: > -------- > Jun 14 12:35:46 jezebel amd[108]: NIS domain name is not set. NIS > ignored. > -------- > > However, if I pull the telephone plug, I get the following error: > -------- > Jun 13 21:35:47 jezebel amd[108]: unable to register (AMQ_PROGRAM, > AMQ_VERSION, tcp) > -------- > and the system is so unstable that a 'cd /a/cdrom' will hang all virtual > terminals indefinitely. > > Sorry for the length of the post. Keep up the sterling work. TIA. > -- > Richard Smith > Assistant Chief Engineer > TRL Technology Limited -- Richard Smith Assistant Chief Engineer TRL Technology Limited To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?35863B36.A3C535DE>