This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Sophos XG Home on Hyper-V with PPPoE

I just wanted to give some information on successfully setting up Sophos XG Home on Hyper-V with PPPoE.

 

Previously it was running fine on a HP Microserver but I wanted to retire that hardware.

 

First off, before even creating the virtual machine, I created a new vSwitch called WAN and dedicated a single physical NIC to it in the Hyper-V host. This NIC is wired directly into the vDSL PPPoE modem.

In Hyper-V I created a new vSwitch, also called WAN, and assigned the WAN NIC to it. I also enabled SR-IOV at this point as my NICs support it.

 

I found if you don't do dedicate a NIC and vSwitch to the WAN connection then in the XG the WAN port will bounce up and down every few minutes and the internet is then basically unusable.

 

I created a new virtual machine - it's important to create a Generation 1 machine as Generation 2 uses UEFI and the appliance won't boot.

 

I gave the VM 6GB RAM and 4 vCPU as this is the maximum XG Home can use.

 

I created a 20GB virtual IDE HDD

 

Note: Do NOT use legacy network adaptors. If a legacy adaptor is used for the WAN it gets throttled to 20Mbps.

 

Connect the first vNIC to the normal Hyper-V external vSwitch that is created during install and the second vNIC to the WAN vSwitch.

 

Install XG.

 

Ensure that the vNIC's are assigned correctly. Add your PPoE login details and it will connect. I found no need, like with the physical server, to alter the VLAN information here. Your mileage may vary depending on your choice of ISP.

 

It connects fine, max's out my 72Mbit line no problem and is rock solid.

 

Hopefully this'll help someone as I couldn't find any details on using Hyper-V as a host with PPPoE.



This thread was automatically locked due to age.
Parents
  • I did something similar with an Intel NUC for home use.

    Interface 1 (LAN) on the VM is bridged to the untagged VLAN

    Interface 2 (WAN) on the VM is bridged to VLAN 70, which is untagged on a physical port on the switch and has PPPoE modem plugged in.

    Originally I set it up with just one virtual NIC and the WAN on VLAN 70 directly, but virtual XG is a bit inflexible in this regard and I wasn't comfortable with the amount of hackery required.

    James

Reply
  • I did something similar with an Intel NUC for home use.

    Interface 1 (LAN) on the VM is bridged to the untagged VLAN

    Interface 2 (WAN) on the VM is bridged to VLAN 70, which is untagged on a physical port on the switch and has PPPoE modem plugged in.

    Originally I set it up with just one virtual NIC and the WAN on VLAN 70 directly, but virtual XG is a bit inflexible in this regard and I wasn't comfortable with the amount of hackery required.

    James

Children
No Data