Installing IPCOP as a Hyper-V Guest – Part 3
December 21, 2010 6 Comments
You will now have the chance to configure your keyboard mapping, time zone, passwords, and additional interfaces.
Select your keyboard layout using the TAB key, and again, TAB down to OK.
Repeat for your Time Zone
Next enter the hostname you would like, and TAB down to OK.
Choose an internal domain name, and TAB down to OK. I am leaving mine on the defaults. IPCOP.localdomain
Now you can configure your ISDN interfaces… what? you don’t have a brook trout ISDN card? Oh, well if your like me, and you DON’T need to use ISDN, i would choose to disable it.
TAB across to DISABLE ISDN and hit SPACE to accept.
Next we need to choose our NETWORK CONFIGURATION TYPE.
If you have followed the above advice you will need to choose GREEN + RED then TAB down to OK.
You will see a screen showing ‘pushing non local network down’
You’re then returned to the Network Configuration Menu.
Select Drivers and Card Assignments.
You will see your TULIP card is assigned to the GREEN NIC, but RED shows as UNKNOWN (UNSET)
We do wish to change these settings, so select OK.
Again you will see a screen showing ‘pushing non local network down’
You will now see a message about an unclaimed NIC, you can assign this NIC to RED, select OK.
All cards are now successfully allocated.
You can now set your address settings for your NICs.
We have already configured the GREEN NIC, so select RED and select OK.
This section will vary dependant on your own lab setup. I have my RED NIC set to use DHCP, and i have a DHCP server on the LAB network handing out an IP to it. Make sure you have a valid address to hand if you want to statically assign this.
I’m setting mine to DHCP.
When you’re ready, select DONE.
If you have selected to use a STATIC configuration on the RED NIC, you will then need to go ahead and enter DNS and GATEWAY information on the next menu.
You can also configure IPCOP to be a DHCP server,but we do not need to do that for this setup. You will be prompted to do this after selecting DONE on the network configuration menu.
When you’re happy with you configuration, select DONE.
On the DHCP Server Configuration menu, leave the defaults and select OK.
Make sure you don’t hit CANCEL at this point like i just did, if you do, i can’t say what your results will be like, so probably best to start over!
If your smart, and you don’t hit cancel, you can now enter your ‘root’ password. This is just used for console access.
As this is a lab system i am going to enter ‘password’ you won’t actually see the characters as you type them, TAB down to confirm, and TAB down to select OK.
Next is the ‘admin’ password – this is used when accessing the web console.
Now enter a password to be used when doing an export of your backup key.
Setup is now complete.
Your IPCOP VM will now reboot, and you will be able to access the web console of your system from a locally connected VM.
Your system will boot and you will see an ‘ipcop login:’ prompt when it has booted up.
The console is not something i have used to configure IPCOP so i will refer you to their documentation for configuration tips.
Update – 10/02/2016 Please see below comments re updated port numbers for IPCOP Login
If you logon to a locally connected VM you can access the console at: http://192.168.16.254:81
You will get redirected to an HTTPS site – so don’t be alarmed if you get a certificate warning.
If you want to get really clever with it, you can then start to use the firewall on the IPCOP to publish services on the ‘internal’ / ‘GREEN’ network, which you can then access from your physical network.
And there you have it, an operational NAT device to separate your Hyper-V guest machines.