Project

General

Profile

Bug #27780

Network Interface configuration seems to be broken when using VM's and iocage

Added by Mark Watling almost 2 years ago. Updated over 1 year ago.

Status:
Closed
Priority:
No priority
Assignee:
Marcelo Araujo
Category:
Middleware
Target version:
Seen in:
Severity:
New
Reason for Closing:
Reason for Blocked:
Needs QA:
Yes
Needs Doc:
Yes
Needs Merging:
Yes
Needs Automation:
No
Support Suite Ticket:
n/a
Hardware Configuration:

HP Gen 8 Microserver, 16GB ECC RAM, Xeon e3-1265, 3x3TB WD RED, 1x2TB Barracuda

ChangeLog Required:
No

Description

Very new to networking so I might be doing something wrong here..... I'm on FreeNAS 11.1-Release

Anyway setup 2 VM's and using iocage for plex and a basic FreeBSD.

When setting up, FreeNAS creates two bridges one for iocage (includes vnets) and one for the VM's (includes tap0, tap1).

Problem is that my physical ethernet adapter can only be assigned to one bridge (which FreeNAS assigns to the VM bridge), and this means that my jails cannot access the internet.

The only solution I have found is once FreeNAS has booted, destroy the bridge containing tap0, tap1, bge1(ethernet adapter), and then assign them to bridge0 which is where my vnets are.

Question is - is this normal, or am I missing something here - appreciate any help please? Thank you!

I've attached to ifconfig output files :-
ifconfig.20180106.after.boot is the configuration just after boot
ifconfig.20180106.working is my modified network configuration.

ifconfig.20180106.after.boot (3.25 KB) ifconfig.20180106.after.boot network configuration after boot Mark Watling, 01/12/2018 12:32 PM
ifconfig.20180106.working (2.93 KB) ifconfig.20180106.working network configuration modified and working Mark Watling, 01/12/2018 12:32 PM

Related issues

Related to FreeNAS - Bug #27122: Add overhauled bridge support to APIDone

History

#1 Updated by Dru Lavigne almost 2 years ago

  • Assignee changed from Release Council to Marcelo Araujo
  • Target version set to 11.2-BETA1

#2 Updated by Marcelo Araujo almost 2 years ago

  • Status changed from Unscreened to Closed

Hi,

Unfortunately it is a know issue and the way how you are doing is the right way!
We plan to have a standalone tool to manage VMs and I will work hard to solve this issue.

But for now, there is no other way.

Best,

#3 Updated by Dru Lavigne almost 2 years ago

  • Target version changed from 11.2-BETA1 to N/A

#4 Updated by Stephen Cunningham over 1 year ago

Is there another issue # to follow when this will be resolved?

#5 Updated by Dru Lavigne over 1 year ago

  • Related to Bug #27122: Add overhauled bridge support to API added

Also available in: Atom PDF