> There is a big battle over implicit vs expicit up. Especially since the
> way it is done is by hacking up every interface ioctl routine.
> So depending on which side did the driver it may do the up or not.
I noticed this in ifconfig(8):
up Mark an interface “up”. This may be
On Mon, Jun 03, 2024 at 11:35:16PM -0700, jrmu wrote:
> > This interface is not UP. Not sure why.
>
> Thank you! This was indeed the cause. I appended "up" to
> /etc/hostname.vport0 and everything works now.
>
> Most interfaces get turned on automatically, I wonder why vport(4) does
> not.
There
> This interface is not UP. Not sure why.
Thank you! This was indeed the cause. I appended "up" to
/etc/hostname.vport0 and everything works now.
Most interfaces get turned on automatically, I wonder why vport(4) does
not.
In any case, it's solved, thanks so much.
--
jrmu
IRCNow (https://ircno
On Mon, Jun 03, 2024 at 10:52:55PM -0700, jrmu wrote:
> Greetings,
>
> I am having a hard time figuring out how to bridge vport(4) and tap(4)
> interfaces.
>
> Previously, I had set up vmm with bridge(4) and vether(4), and all was
> working well. However, I recently heard that veb(4) has better
Greetings,
I am having a hard time figuring out how to bridge vport(4) and tap(4)
interfaces.
Previously, I had set up vmm with bridge(4) and vether(4), and all was
working well. However, I recently heard that veb(4) has better
performance, so I tried to replace my bridge0 and vether0 with veb0
5 matches
Mail list logo
