As a follow up to the bridge talk from yesterday: dladm create-bridge -l igb0 -l igb1 ... <bridgename> actually creates a 'dumb' switch for what I can tell.

I succeeded in giving my machine it's own IPv4 by just picking one of my physical NICs and ipadm create-if and create-addr for that link.

Creating a vnic or a vlan device on top of the bridge did not work for me and fails with this message: VLAN over '<bridgename>0' may not use default_tag ID.

By the way: You _can_ create an etherstub and add it as bridge member. I'm not sure if that is in any way helpful or interesting.

Just wanted to let you know that I'm still on it but it seems to be quite janky to me, so no garantees. I need time to learn about all this.

jacuzzibob: The default_tag error is interesting. What were the exact arguments to "dladm create-vnic"?

I tried "dladm create-vnic -l test0 mynic0" and "dladm create-vnic -l test0 -v 3000 mynic0" and "dladm create-vnic -l test0 -v 3000 -p default_tag=0 mynic0"

My bridge is named "test". The corressponding link name was "test0".

I was justing goofing to be honest. Not really understanding what I'm doing '=D

*goofing around

jacuzzibob: I believe the message is actually referring to the default_tag link property on the underlying NICs or the bridge. You can see the property with, say, dladm show-linkprop | awk 'NR == 1 || /default_tag/'

In general unless you've modified it, it will be "1"; i.e., VLAN 1, the "default" or "management" VLAN on most switches

as per dladm(8), it's the VLAN ID that we assume for untagged frames sent or received on the link

I think you are probably correct that you need to: [1] create an etherstub (which is, itself, a bit like an isolated virtual switch), [2] add that etherstub to the bridge like you did with the physical links, [3] create a VNIC on top of the etherstub

dladm(8) does say, for "dladm create-vnic", that the "-l" option accepts either a physical link or an etherstub

So I think that all makes sense. You'd have all your physical links, and your etherstub, on the bridge, and then you'd have a VNIC on the etherstub that you could give an IP to

Sweet! Thank you jclulow for your support and for elaborating. I will try it out soon.

You're welcome!

I'll also have a look at this tomorrow. Transform omnios as a router is easy.. but as a switch, it is more complicated. I use etherstubs and vnic for VM with bhyve, but never tried for a switch. I had written a howto for a router : buttondown.email/majekla/archive/tr…an-omnios-server-into-a-router-with

This is perfect majekla ! My end goal is turning this machine into a router. So your article will be of great benefit

you're welcome ! It is more easy as a router... But anyway, if someone has already succeeding in configuring omnios (or opendiana/tribblix) with vrrp, I take !! I never succeeded, it seems to me that vrrp version on illumos is too old. I did it on solaris, but never succeeded on illumos

what does the "m" mean in the images in downloads.omnios.org/media/stable ? is r151048m a patch version over r151048 or something? I see it's a later release...

It's the update version, there's basically one update a week incrementing the letter of the alphabet

Not every update gets new media, though

Release notes for interesting updates omnios.org/rn/r48

jclulow : It took me a few minutes to test out your suggestions. This is my progress so far:

After creating the etherstub I had to set the MTU from 9000 to 1500 to equal the MTU of the physical links on the bridge. This was just to make sure that there is not yet another thing that might go badly. Then I created the VNIC on top of that and gave it a IPv4 for my LAN.

I tried pinging my router. Using snoop I can see, that the response only reaches the bridge but never enters the etherstub or the vnic, so something is still not working for me right now. Sadly I have leave for today. I will keep trying tomorrow

thanks; so if I'm writing something that downloads OmniOS images... I should pick the last image listed alphabetically in downloads.omnios.org/media/stable , right?

Better to grab downloads.omnios.org/media/img.json and parse that to get the list of available images

oh, nice, I'll add an issue to switch to that, thanks!

As for vrrp, it's unfortunate that we don't have a man page, but I would expect that the instructions for the original Solaris 11 (not current, as it's changed over time) ought to work)

unfortunately, the creation of the router with 'vrrpadm create-router ...' linked to the dedicated vNIC is impossible because a lot of options are missing in the command.

On Solaris it is working

Yes, the commands used on Solaris 11.3 or 11.4 won't work here, but maybe the Solaris documentation from sufficiently far back won't have diverged.

This is also what I thought, even before Solaris 10, the documentation doesn't work. I spent several days on it :-S...