[Xorp-users] XORP on Windows

[Ray Soucy]

I suspect it will use the internal ID which would look like
"{EB736B76-9090-4C28-8FC5-42118B4328EF}"

To find it, you'll need to go into the registry and navigate to:
"HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Network\"
Then expand each key in the tree and look for a "Connection\Name"
entry that is the name of the interface you want.

For me the full key was:

"HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Network\{4D36E972-E325-11CE-BFC1-08002BE10318}\{EB736B76-9090-4C28-8FC5-42118B4328EF}\Connection\Name"
= "Local Area Connection".

That might not be the case, but other *nix ports for Windows seem to
work like this.

Might be worth writing a VB script or something to list interface IDs
and include it with the Windows copy of XORP, assuming it even runs at
all.

I think it's time you embrace Linux ;-)

On Mon, Feb 14, 2011 at 12:45 PM, Sharma2, Sandeep
<sandeep.sharma2 at iqor.com> wrote:
>
>
> Hi,
>
>
>
> I am trying to run XORP 1.6 on multiple platforms. I was able to get it to
> run quite easily on Centos Linux 2.6.18 but ran into difficulties on Windows
> Server 2008. I could not figure out the correct way to name the network
> interfaces in the boot config file. Unfortunately I could not get
> show_interfaces to run either.
>
>
>
> Unsuccessfully tried:
>
> Unix style interface names e.g. eth0 and ge0
>
> Windows ipconfig syle interface names e.g. “Local Area Connection 2”
>
>
>
> Can anyone point out the correct naming scheme for network interfaces on
> Windows ?
>
>
>
> Thanks,
>
> Sandeep
>
>
>
>
>
>
>
>
>
> _______________________________________________
> Xorp-users mailing list
> Xorp-users at xorp.org
> http://mailman.ICSI.Berkeley.EDU/mailman/listinfo/xorp-users
>
>



-- 
Ray Soucy

Epic Communications Specialist

Phone: +1 (207) 561-3526

Networkmaine, a Unit of the University of Maine System
http://www.networkmaine.net/