Leif Neland wrote:
> Bug or pilot error?
> My network is 192.168.5.0
> I used to have im my /etc/exports:
> /var -alldirs -maproot=root: -network 192.168.5 -mask 255.255.255.0
> But after the portmapper change, I couldn't mount, was getting permission
> showmount -e showed 192.168.5 was being interpreted as 192.168.0.5
> Changing -network to 192.168.5.0 fixed it, naturally, but the 192.168.5
> used to work.
> Is this change intentional, or is 192.168.5 supposed to work?
My buest guess is that this is because it is now using something like
inet_addr() for decoding the address instead of some roll-your-own code.
FWIW, this zero fill is a standard part of the system:
peter@daintree[11:24pm]~src/sys/pci-142> ping 192.168.5
PING 192.168.5 (192.168.0.5): 56 data bytes
peter@daintree[12:13am]~src/sys/pci-143> ping 127.1
PING 127.1 (127.0.0.1): 56 data bytes
64 bytes from 127.0.0.1: icmp_seq=0 ttl=64 time=0.068 ms
This is far more prolific in IPv6. Eg: "ping ::1" is localhost.
Peter Wemm - [EMAIL PROTECTED]; [EMAIL PROTECTED]; [EMAIL PROTECTED]
"All of this is for nothing if we don't go to the stars" - JMS/B5
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message