NFS server replies on wrong IP

[Daniel O'Connor]

Hi,
I recently upgraded a system from 7.x to 8.0-RC1 (well, got new guts for 
it and copied the data over..) and I am having trouble getting NFS to 
work.

I have re0 like so
re0: flags=8943<UP,BROADCAST,RUNNING,PROMISC,SIMPLEX,MULTICAST> metric 0 
mtu 1500
        
options=389b<RXCSUM,TXCSUM,VLAN_MTU,VLAN_HWTAGGING,VLAN_HWCSUM,WOL_UCAST,WOL_MCAST,WOL_MAGIC>
        ether 00:24:1d:d1:92:cc
        inet 10.0.2.1 netmask 0xffffff00 broadcast 10.0.2.255
        inet 10.0.2.3 netmask 0xffffffff broadcast 10.0.2.3
        inet 10.0.2.4 netmask 0xffffffff broadcast 10.0.2.4
        inet 10.0.2.7 netmask 0xffffffff broadcast 10.0.2.7
        media: Ethernet autoselect (1000baseT <full-duplex>)
        status: active

and when I try and NFS mount something on 10.0.2.7 I see that the reply 
comes from the wrong address (10.0.2.1). ie from wireshark..
7	0.801704	10.0.2.1	10.0.2.103	NFS	V3 NULL Reply (Call In 6)
8	0.802742	10.0.2.103	10.0.2.1	ICMP	Destination unreachable (Port 
unreachable)

Interestingly Linux works OK, but perhaps it specifically allows it some 
how?

I can work around this by using -h to bind to 10.0.2.7 though, which is 
what I did on 7.x. I was wondering if there was a "correct" solution 
though.

-- 
Daniel O'Connor software and network engineer
for Genesis Software - http://www.gsoft.com.au
"The nice thing about standards is that there
are so many of them to choose from."
  -- Andrew Tanenbaum
GPG Fingerprint - 5596 B766 97C0 0E94 4347 295E E593 DC20 7B3F CE8C
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 188 bytes
Desc: This is a digitally signed message part.
Url : http://lists.freebsd.org/pipermail/freebsd-stable/attachments/20090927/bd6bbc70/attachment.pgp