On 24/07/2011 00:25, Bruce Cran wrote:
On 23/07/2011 22:58, Chad Perrin wrote:
Do you realize that MS Windows has nothing equivalent to rc.conf or
/etc/network/interfaces?

It does: it's in the registry. HKLM\SYSTEM\CurrentControlSet\services\Tcpip\Parameters\Interfaces contains a list of interfaces and their settings.

Yeap, just a small detail, it doesn't bind the configuration to a device, but to a connection interface, which in turn is bound either to a control interface or to another service interface. Which in turns can be bound either to a final control interface, to another service interface or even to another connection interface.

All these bearing names in form of their class id + uid : {XXXXXXXX-XXXX-XXXX-XXXX-XXXXXXXXXXXX}\{XXXXXXXX-XXXX-XXXX-XXXX-XXXXXXXXXXXX} You basically turn around in circle for hours, looking for the next clue, if you do not use windows tools to do the job. Sure you can write WSH/WPS to do the mapping for you, but that is still using windows tools.

And I definitly would not edit those manually except for very simple changes, the imbrication of layers of control sets/interfaces/devices can result in unexpected results (for example in the likely case where you have a firewall, a tunnel, a VPN or anything at all also using the interface you are editing).

I remember crying tears of blood when I had to remove (not disable, destroy) from one tunnel connection all the 7 different version of IPv6 windows put on each and every network interface.


%SystemRoot%\System32\drivers\etc contains several BSD configuration files for DNS settings, protocols etc.


_______________________________________________
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"

Reply via email to