| Age | Commit message (Collapse) | Author | Files | Lines |
|---|
|
The changes here start our own copy of BIND, listening on a new
interface that we create at the start of the script. The user must
specify the IP address etc that this interface will have, and BIND and
Samba will bind to that interface only.
This means that we won't conflict with an existing BIND on the system,
so long as it isn't configured to listen on all interfaces.
We also auto-create the /etc/resolv.conf and restore it at the end of
the script, using the existing server value from the script as a
forwarder.
Andrew Bartlett
Autobuild-User: Andrew Bartlett <abartlet@samba.org>
Autobuild-Date: Tue Nov 23 08:30:34 CET 2010 on sn-devel-104
|
|
- Don't change the IP address if DHCP is not in use
The main reason to 'fix' the IP is to get around Dynamic DNS issues caused
by the DHCP server, if the VM is already on a fixed IP, it does not matter.
- Set the maximum telnet connection limit to 1024
This ensures that we can always make a new connection, regardless
of the existing configuration. We also catch more conditions when
the server has restricted the number of connections, and try again.
- Set the route after the connection drops out
My WinXP box always wants to drop the default route
- Set the DNS as a distinct step
My WinXP box drops the connection when we set DNS servers
Andrew Bartlett
|
|
The idea here is that the virtual machine stays on the address
allocated by DHCP, but is configured statically. This avoids the need
to manually set the address on the host, but avoids the host being
instructed by DHCP not to do Dynamic DNS.
Andrew Bartlett
|
|
This avoids needing to set the krb5.conf for the whole host to match
the test environment.
Andrew Bartlett
|
|
|
|
ready for test-s3.py
|
