[debian-lan-devel] More networking Q's

[Andreas B. Mundt]

On Sat, Feb 21, 2015 at 12:46:00AM +0000, Boylan, Ross wrote:
> Regarding 1) below, the mainserver logs show the client requesting
> 10.0.1.100 and the dhcp server acknowledging it.  /etc/dhcp/dhcpd.conf
> shows the range for unknown clients is 10.0.1.100 to 10.0.1.199, so
> everything seems OK there.

Yes, that looks fine.

> There are a lot of messages from named like
> validating @0x7f5d...: com SOA: no valid signature found
> or net SOA: verify failed due to bad signature
> dumping master file /etc/bind/tmp-xxxx: open: permission denied

These messages usually are not fatal -- I have them here too, but
never figured out how to fix them properly.  IIRC, some are IPv6
related.

> I'm growing more suspicious that my virtual lan may be using
> 10.0.0.1 for some purpose conflicting with the mainserver VM that I
> think is running at 10.0.0.1

Attach a VM (need not to have a disk at all) to the 10.0.0.1 local
network and try to boot using PXE -- this should give you a boot menu
from the mainserver (with diskless debian-lan live system).  Of course
you need to have installed the chroots properly.  If that does not
work check the mainserver's log for suspicious messages when booting
the diskless client.

> Summary:
> Should a VM attached to the same 10.xxx network is mainserver, but not created by FAI,
> 1) get an IP from mainserver?
> 2) be able to ssh to mainserver?
> 3) be able to view a web page at mainserver?
> 4) be able get the IP for mainserver?
>
> Currently, none of the operations work, even when using the IP for 2 + 3.
> The VM did get an IP from somewhere, though it's not in the expected range.

I guess 1) is solved now.  All the other issues should work too, first
try without DNS.  Check /etc/resolv.conf on the client if name
resolution fails.  Try 'host mainserver', 'host workstation00' etc.

Best regards,

     Andi