Subject: Re: Setting up ipnat with NetBSD and OSX[almost]
To: Andrew Gillham <firstname.lastname@example.org>
From: Ian P. Thomas <email@example.com>
Date: 12/29/2001 10:58:20
On Saturday 29 December 2001 01:26 am, you wrote:
> On Fri, Dec 28, 2001 at 11:26:09PM -0500, Ian P. Thomas wrote:
> > I added my DNS server IP's to the space listed as Domain Names and
> > found that it created a file /var/run/resolv.conf that has a
> > symlink /etc/resolv.conf.
> > ipnat -l
> > MAP 192.168.3.2 49185 <- -> 220.127.116.11 40045 [18.104.22.168
> > 53] MAP 192.168.3.2 49185 <- -> 22.214.171.124 40044
> > [126.96.36.199 53] MAP 192.168.3.2 49184 <- -> 188.8.131.52
> > 40039 [184.108.40.206 53] MAP 192.168.3.2 49183 <- ->
> > 220.127.116.11 40038 [18.104.22.168 53]
> > This is what I got after trying to look up a site, www.apple.com
> > from the Mac. The connection are being built, but somehow this
> > info is not making its way back to the Mac. Its mapping the Mac's
> > IP to the IP given to me by my ISP.
> Yes, those entries look ok. Try querying some other server besides
> those two. With tcpdump you can see if the server is responding to
> the request or not.
> > I just checked my rc.conf and found that rpcbind was not enabled.
> > I enabled it and added logging. This may be why the Mac wasn't
> > getting any packets back. I'm going to reboot after Koffice
> > finished building.
> You shouldn't need rpcbind. Worst case you should be able to run a
> caching only DNS server on your NetBSD box. It doesn't make sense
> why this is not working, but I think only a tcpdump will tell us
> more. Also, you might want to install 'ethereal' on your NetBSD box,
> it is a nice GUI packet capture utility.
> This command should do what you want:
> tcpdump -nvvi fxp0 -x -X -s 1500 udp port 53
> Basically it should dump the full packet in hex and ascii, and
> provide a verbose decode of the packets as well.
> If you want to save the tcpdump info to a file, just add '-w
> filename' to the options.
> Anyway, start tcpdump, then do "nslookup www.netbsd.org." on the Mac
> and you should get a couple screensful of output.
I did as asked and got a file full of output. I opened up the file
with ethereal (I've used it before to pin down a problem connecting
with broadband). I'm not sure what I'm looking for. I have 12 packets
that originate from the Mac, but never seem to get back there. It
looks as if these packets are going out onto the net with an internal
I turned off rpcbind. You're right, it didn't help. I thought it
might be needed because of the call to portmap made by ipnat.
I've included the file as an attachment.
Of Course it Runs NetBSD
Content-Description: tcpdump output
Content-Disposition: attachment; filename="dumpfile"
Do You Yahoo!?
Get your free @yahoo.com address at http://mail.yahoo.com