Thread Info
  • State Suggested Answer
  • Locked Locked
  • Replies 12 replies
  • Answers 1 answer
  • Subscribers 5 subscribers
  • Views 17645 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.
Parents
  • 0

    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 

     

     

  • 0 in reply to Ol Deda

    Hi

    Thank for the reply, but i have done this already, but i do not get any network connection from the third nic.

  • 0 in reply to Joosep1

    To form a bridge, both NICs need to be unused.   To deal with the loss of connectivity during the transition, I also needed to create a management access port, for a total of three new ports.  Do you really have a BR0 or BR1 interface created, one that looks like the picture?   You never mentioned creating any unused interfaces, so I wonder if it ever happened.   

    After the bridge is created, it defaults to only forwarding IPv4 packets.  You need to use the "Advanced Bridge" section of the interface properties window to specify the Etherypes that are forwarded.   Do a Google search for "Ethertype List" and follow the links for IANA.ORG.  You probably want to add at least ARP and Reverse ARP.   This is the second possible explanation for your symptoms.   You did not specify the exact traffic that was failing.

    I don't know that UTM implements Spanning Tree Protocol.   I would not recommend using a wiring configuration that makes STP necessary.

    There may be an issue with UTM providing DHCP services for both sides of a bridge.   This is based on my recollection of an earlier discussion in this forum, not based on experience.  Search the forum to investigate.

  • 0 in reply to DouglasFoster

    I think it is a HyperV  misconfiguration. What I see he is trying to do the bridge in Wan designed interface (if im not wrong)

    Consider implementing VLAN

  • 0 in reply to DouglasFoster

    I tried to add additionl entries to Ethertype List, but it didnt help.

     

    To form a bridge, both NICs need to be unused.   To deal with the loss of connectivity during the transition, I also needed to create a management access port, for a total of three new ports.  Do you really have a BR0 or BR1 interface created, one that looks like the picture?   You never mentioned creating any unused interfaces, so I wonder if it ever happened.  

    Could You point me to any guide for this, as previous post by a user told, that there should not be any other configuration needed.

  • 0 in reply to Ol Deda

    I think it is a HyperV  misconfiguration. What I see he is trying to do the bridge in Wan designed interface (if im not wrong)

    Consider implementing VLAN

    And how is this a misconfiguration? I am trying to bridge two lan interfaces, one is virtual switch for VM´s, but the second one would be physical network connection to a switch, to extend the same lan.

    I even tried for the third nic (LAN2) to change Hyper-V virtual switch setting from External to Private and added it to a virtual machine on the same Hyper-V host.

    Same problem, no network connection for the VM.

  • 0 in reply to Joosep1

    Now lets get things right. How you reach the UTM from PC with physical Lan or virtual switch. Can you write a schema topology?

  • 0 in reply to Ol Deda

    I have three virtual switches on the Hyper-V host:

    1) WAN - External network Hyper-V virtual switch, using dedicated physical nic and not sharing with the management op.system

    2) LAN - Internal netowrk Hyper-V virtual switch

    3) LAN2 - External Hyper-V virtual switch, dedicated physical nic - right now testing as a private switch setting with another vm, using the same switch.

     

    I can reach UTM from the Hyper-V host, because it has the same lan connection from Internal virtual switch. Also i can access UTM from some VM on the same virtual switch - the second LAN.

    LAN and LAN2 are bridged in UTM.

    I am not sure, that if this is possible, but i would like the same virtual Sophos UTM to provide internet connection and DHCP for some physical devices, like PC, printer and so.

    I thought maybe adding third lan interface as External network hyper-v swithc, with a additonal nic provide the connection to other physical devices.

  • 0 in reply to Joosep1

    Maybe by mistake you configured IP on virtual interfaces? I am newbie to virtual switches. As you can see from my picture I can extend network with USB Ethernet, so it is not the fault of UTM

Reply Children
No Data
Unfiltered HTML