Thread Info
  • State Suggested Answer
  • Locked Locked
  • Replies 12 replies
  • Answers 1 answer
  • Subscribers 5 subscribers
  • Views 16966 views
  • Users 0 members are here
Options
Suggested
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

Two internal interfaces bridge with same dhcp and subnet

Joosep1

Hi!

I have a Server 2016 Hyper-V host.

Right now Sophos UTM9 VM, has three virtual NICS.

1) WAN - External Hyper-V virtual switch, dedicated physical nic

2) LAN - Internal Hyper-V virtual switch

3) LAN2 - External Hyper-V virtual switch, dedicated physical nic

UTM works great with NIC1 and 2, i have internet and lan connection for all the virtual machines.

Now i am not sure, that i can do it, but this is why i started this question topic.

 

Can i get the NIC3, that is actually bounded to physical nic, to extend the same internal lan to external switch so i can extend my virtual network to other physical devices.

I tried to configure second nic, at sophos it is Internal interface as bridge with the additonal nic three.

All my virtual machines have internet and lan connection, but for the third nic, there is no connection at all.



This thread was automatically locked due to age.
  • 0 in reply to DouglasFoster

    If you really want to clean up the unused NICs, the following sequence will probably work.   It is not something that I have tried because I am not running in a VM.

    After the bridge is built and there is no configuration remaining on the old interface  (A1 and A2 in my example):

    • Delete A1 and A2 to make ETH1 and ETH2 unused.   
    • Add ETH1 and ETH2 into the bridge.
    • Shutdown and reconfigure VMWare so that ETH1 and ETH2 are mapped to the desired switch connections, while ETH4 and ETH5 become inactive.
    • Boot UTM.   
    • Delete ETH4 and ETH5 from the bridge.
    • Shutdown UTM.   
    • Remove NIC4 and NIC5 from the guest environment.

    By extension, to discard ETH3:

    • Remove the IP configuration from A3.
    • Delete UTM interface A3 to make ETH3 unused.
    • Shut down UTM.
    • Remove the NIC for ETH3 from the guest environment.
    • Reboot UTM.
  • 0 in reply to Ol Deda

    In interfaces Edit "Internal Network".
    Under "Type" Dropdown to Ethernet Bridge. Than "Bridge selected NICs" check the desired NIC's. And you should get a picture like the attachment.
    No further configuration is needed 

     

    As user oldeda wrote, i added the second, nic, edited the existing lan interface and changed it to bridge, also adding the second nic to the bridge and i got the same configuration as on the picture.

    But, i forget, that missing key component for making it work with Hyper-V, i need to switch on "Enable mac address spoofing" for BOTH virtual lan network adapter, that are used in the bridge!

    Also, Realtek NIC is junk, throw it away :) First i was able to get a connection for a test virtual machine with the second lan interface and additional Hyper-V virtual switch.

    Configuring the second lan interface for a Hyper-V external network (selecting physical nic), at first, i could not get connection for physical netowork.

    Changing from Realtek nic to a USB one and it works!!! My virtual UTM VM serves now both, virtual VMs and hyper-v host network plus all physical devices connected with a switch

Unfiltered HTML