what is the secret behind 192.168.0.121

[Erich Dollansky]

Hi,

I found the cause of the problem. After fixing this problem
in /etc/hosts:

192.168.0.127	raspberry8.alogt.com		Raspberry8
192.168.0.128	raspberry8.alogt.com		Raspberry9

After fixing the second line to

192.168.0.127	raspberry8.alogt.com		Raspberry8
192.168.0.128	raspberry9.alogt.com		Raspberry9

and adjusting the names in the respective /etc/rc.conf files,
everything started to work. Before, I left then names as they have been
but changed the IP addresses of the clients to run some tests. I do not
know why is affected IPs above 120 but not the IPs from 116 to 120.

Erich

On Wed, 16 Dec 2015 21:50:47 +0800
Erich Dollansky <erich at alogt.com> wrote:

> Hi,
> 
> I have a very weird problem with my testing LAN. Only FreeBSD machines
> are on the network. It all works as expected until I give the address
> 192.168.0.121 to a client machine. This machine is not able to mount
> remote file systems via NFS despite this IP address is specifically
> mentioned in /etc/exports.
> 
> I know that some routers/switches use this address as the default. But
> I run into this problem even when I connect the NFS server and the
> client directly.
> 
> I do not need to use this address but I would like to know why it does
> not work.
> 
> Showmount for the specific NFS mount point shows this:
> 
> /usr/home                          192.168.0.121 192.168.0.122
> 192.168.0.99 192.168.0.112 192.168.0.116 192.168.0.117 192.168.0.118
> 192.168.0.119 192.168.0.120 192.168.0.123 192.168.0.124 192.168.0.125
> 192.168.0.126 192.168.0.127 192.168.0.128 192.168.0.129 
> 
> /etc/hosts.allow says this as the first effective line:
> 
> ALL : ALL : allow
> 
> Does anybody has an idea what could cause this?
> 
> Erich
> _______________________________________________
> freebsd-net at freebsd.org mailing list
> https://lists.freebsd.org/mailman/listinfo/freebsd-net
> To unsubscribe, send any mail to "freebsd-net-unsubscribe at freebsd.org"