Tiny Core Base > CorePlus

DNS Not working after TC_Install to USB

<< < (2/2)

curaga:
Multiple network interfaces are always a special configuration and need your attention. Use the bootcode nodhcp and configure your networks in bootlocal.sh.

drendar:

--- Quote from: gerald_clark on August 31, 2015, 03:12:08 PM ---Why would you configure 2 virtual network interfaces in a VM?

--- End quote ---

Because the system I'm simulating is dual homed.  One NIC facing the corporate network and the other an isolated, unrouted VLAN.

There are (or rather, will be) other VMs that exist only on the Host-Only Network, and the hosts "host-only" interface is usually shutdown, enabled only for troubleshooting (Which is why it's host-only and not 'Internal network'


--- Quote from: curaga on September 01, 2015, 05:34:05 AM ---Multiple network interfaces are always a special configuration and need your attention. Use the bootcode nodhcp and configure your networks in bootlocal.sh.

--- End quote ---

Forgive my ignorance, but is it possible to still leave DHCP enabled on one interface?


All this though doesn't explain why the system works *perfectly* when booting from CorePlus CD, and only fails once installed.

curaga:
Yes, you just specify DHCP for this interface, static for that. The default is DHCP for all found interfaces, under the assumption only one is usually operable.
Look in dhcp.sh for an example, or use the control panel network applet.

The result of which interface is first is random, and the CD loads more extensions, which affects other processes at boot.

drendar:
Righto, Thanks!

Navigation

[0] Message Index

[*] Previous page