# [OmniOS-discuss] FW: Tun/Tap device installed but not showing up on OmniOS

Andries Annema an3s.annema at gmail.com
Mon Oct 31 19:32:23 UTC 2016

- Previous message: [OmniOS-discuss] Tun/Tap device installed but not showing up on OmniOS
- Next message: [OmniOS-discuss] OmniOS (Joined Active Directory & KRB5.Conf + NFS = NFS Disconnects in ESXI on DC Reboot)
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

    (Forgot the include the discuss list. Sorry)

    -----Original Message-----
    From: Andries Annema [mailto:an3s.annema at gmail.com]
    Sent: maandag 31 oktober 2016 20:30
    To: 'Thomas Wagner'
    Subject: RE: [OmniOS-discuss] Tun/Tap device installed but not showing up on
    OmniOS

    Thomas, thanks!
    Your suggestion to include the lines:
    driver name=tap
    driver name=tun
    in the manifest solved it for me! Wow.

    Although the build process with "pkgtool"/"pkgbuild" and the script as shown
    by your first link seem old, and even though they probably might still work,
    I used the build process as documented by Solaris here:
    http://www.oracle.com/technetwork/articles/servers-storage-admin/o11-097-cre
    ate-pkg-ips-524496.html
    Combined this with the two "driver name"-lines and bingo!

    Your second link - of the OpenCSW project - got me a nice manifest to
    compare to and with it polish some other settings. Nice.

    I am not sure however on how to participate in a public repository or share
    my recipes any other way; I'm still learning and am not sure, security wise,
    on how to allow access to my personal repository and maintain it on a public
    level. Suggestions are always welcome though.

    Thanks again!
    Greetings,
    Andries

    -----Original Message-----
    From: Thomas Wagner [mailto:tom-omnios-discuss at tom.bn-ulm.de]
    Sent: dinsdag 25 oktober 2016 14:41
    To: Andries Annema
    Cc: omnios-discuss
    Subject: Re: [OmniOS-discuss] Tun/Tap device installed but not showing up on
    OmniOS

    Hi Andries,

    does your IPS manifest have an "action" to add the driver entries "tun" and
    "tap"?

    If you scroll down here to the %action section:
    https://sourceforge.net/p/pkgbuild/code/HEAD/tree/spec-files-extra/trunk/SFE
    tun.spec
    This results if built with "pkgtool"/"pkbbuild" to an entry in the manifest
    file like this:
    driver name=tap
    driver name=tun

    A ready-made package is available here:
    http://sfe.opencsw.org/quickrepolinks
    (fully independent of OpenCSW project, but kindly hosted by them)

    Btw, it would be cool if you could share your build recipes and / or
    participate in one of the public repositories for build recipes.

    Regards,
    Thomas

- Previous message: [OmniOS-discuss] Tun/Tap device installed but not showing up on OmniOS
- Next message: [OmniOS-discuss] OmniOS (Joined Active Directory & KRB5.Conf + NFS = NFS Disconnects in ESXI on DC Reboot)
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

More information about the OmniOS-discuss mailing list