[Bug 255054] jng fails to run ngctl msg vtnet0: setpromisc 1

[bugzilla-noreply at freebsd.org]

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=255054

            Bug ID: 255054
           Summary: jng fails to run ngctl msg vtnet0: setpromisc 1
           Product: Base System
           Version: 13.0-STABLE
          Hardware: Any
                OS: Any
            Status: New
          Severity: Affects Some People
          Priority: ---
         Component: misc
          Assignee: bugs at FreeBSD.org
          Reporter: timf at puroto.org

Having recently upgraded to 13.0-STABLE, I found that none of my jng-enabled
jails were coming up after boot.

root at puroto:/ # service jail start pupuru
Starting jails: cannot start jail  "pupuru":
ngctl: send msg: Operation not supported
jail: pupuru: jng bridge pupuru vtnet0: failed
.
root at puroto:/ #

In this case the jails.conf entry was:

pupuru {
  exec.prestart += "jng bridge pupuru vtnet0";
  exec.poststop += "jng shutdown pupuru";
}

Digging into what jng was doing, we were trying to switch the parent interface
to promiscuous mode, failing, and then bailing out:

# ngctl msg vtnet0: setpromisc 1
ngctl: send msg: Operation not supported

Just commenting out that line in jng seemed to be sufficient, though I don't
know
what side effects that might have. My jails all came up ok after that, and were
at least able to send/recv traffic, ping the jail host, etc.

    306                 # Set promiscuous mode and don't overwrite src addr
    307                 # ngctl msg $iface: setpromisc 1 || return
    308                 ngctl msg $iface: setautosrc 0 || return

I checked that my copy of /usr/sbin/jng wasn't significantly different to the
one being shipped in /usr/share/examles/jails.

-- 
You are receiving this mail because:
You are the assignee for the bug.