News: This forum is now permanently frozen.
Pages: [1]
Topic: new M0N0WALL and Hyper-V  (Read 2015 times)
« on: June 07, 2013, 10:58:49 »
mrcola *
Posts: 7

Hi, is it possible to run the new beta m0n0wall 1.8 in Hyper-V

Or any plan to support Hyper-V in the future

Thanks

Regards RW
« Reply #1 on: June 10, 2013, 16:53:25 »
Lee Sharp *****
Posts: 517

It should, but we do not support it.  You will need an environment with two nics on different networks...  What problem are you having?
« Reply #2 on: June 12, 2013, 14:47:35 »
mrcola *
Posts: 7

Hi

Thanks. Basically it is the same issue as described in this post http://forum.m0n0.ch/index.php?topic=4547.0.

The NICs are playing up and it is unusable. I know pfsense is having similar issue, however, there is a solution

http://www.ern.nu/blog/2013/01/pfsense-and-hyper-v/

I tried to run the command ifconfig de0 down and ifconfig de0 up in the shellcmd session in the configuration file, but it does not help

Thanks

RW
« Reply #3 on: June 12, 2013, 22:25:50 »
brushedmoss ****
Posts: 446

I assume you are using 1.8.1b540 ?  once m0n0wall is booted, in hyper-v, with the guest still powered on, set the network as 'not connected' , apply, and set back to connected.  This will be required on every restart of the VM.


FreeBSD isn't supported on hyper-v yet .....
« Reply #4 on: June 13, 2013, 22:03:26 »
mrcola *
Posts: 7

Hi To answer my own question, add <shellcmd>ping x.x.x.x (One of your LAN ip)</shellcmd> and it can be running under Hyper-v

BTW, brushedmoss, I'm afraid your solution is not working. However, the NIC will respond when I run ping command (option 6).

So I added a shellcmd in the config section and it works perfectly.

However the ping time is not great, up (30ms) and down (3ms) from the same network

But it can be automated up and running, even after rebooting
 
Pages: [1]
 
 
Powered by SMF 1.1.20 | SMF © 2013, Simple Machines