bin/111354: Mountd replies using wrong source address
Tom Judge
tom at tomjudge.com
Sat Apr 7 12:00:13 UTC 2007
>Number: 111354
>Category: bin
>Synopsis: Mountd replies using wrong source address
>Confidential: no
>Severity: serious
>Priority: medium
>Responsible: freebsd-bugs
>State: open
>Quarter:
>Keywords:
>Date-Required:
>Class: sw-bug
>Submitter-Id: current-users
>Arrival-Date: Sat Apr 07 12:00:12 GMT 2007
>Closed-Date:
>Last-Modified:
>Originator: Tom Judge
>Release: 6.2-RELEASE
>Organization:
>Environment:
FreeBSD beaker.mintel.co.uk 6.2-RELEASE FreeBSD 6.2-RELEASE #2: Tue Mar 20 10:32:46 GMT 2007 root at bob.mintel.co.uk:/usr/obj/usr/src/sys/BUNSEN_BEAKER i386
>Description:
When using an IP alias to provide NFS services to a network mountd will reply to requests sent to the alias IP from the main IP on that network:
ifconfig em0
em0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> mtu 8192
options=b<RXCSUM,TXCSUM,VLAN_MTU>
inet 172.31.0.19 netmask 0xffffff00 broadcast 172.31.0.255
inet 172.31.0.200 netmask 0xffffffff broadcast 172.31.0.200
ether 00:13:72:5c:89:67
media: Ethernet autoselect (1000baseTX <full-duplex>)
status: active
Relevant line from client fstab:
172.31.0.200:/cfarm/ports /usr/ports nfs ro 0 0
When the client mounts the file system replies from mountd originate from 172.31.0.19 rather than from 172.31.0.200.
Could this be solved by adding the -h option mountd that is already present in nfsd and rpcbind, so that the bind address of mountd could be specified?
>How-To-Repeat:
>Fix:
>Release-Note:
>Audit-Trail:
>Unformatted:
More information about the freebsd-bugs
mailing list