Bug 250875 - net/vether-kmod fails to load
Summary: net/vether-kmod fails to load
Status: New
Alias: None
Product: Ports & Packages
Classification: Unclassified
Component: Individual Port(s) (show other bugs)
Version: Latest
Hardware: Any Any
: --- Affects Many People
Assignee: Kyle Evans
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2020-11-05 08:11 UTC by Alex Povolotsky
Modified: 2020-11-15 19:35 UTC (History)
5 users (show)

See Also:
bugzilla: maintainer-feedback? (henning.matyschok)


Attachments
Update, g20201111 (1.35 KB, patch)
2020-11-12 14:18 UTC, Henning Matyschok
no flags Details | Diff

Note You need to log in before you can comment on or make changes to this bug.
Description Alex Povolotsky 2020-11-05 08:11:03 UTC
I've tried to install net/vether-kmod, both from ports and from packages. It fails to load
Code:
link_elf_obj: symbol ifnet undefined
linker_load_file: /boot/modules/if_vether.ko - unsupported file type

I'm running 12.1-RELEASE-p10, with fresh sources.
Comment 1 Kurt Jaeger freebsd_committer 2020-11-08 12:33:44 UTC
tested on 12.2 with a port build on 12.2 has the same problem:

link_elf_obj: symbol ifnet undefined
Comment 2 Kurt Jaeger freebsd_committer 2020-11-08 13:00:56 UTC
The source seems to be for 11.x, and probably needs updates to work for 12.x
Comment 3 Henning Matyschok 2020-11-11 14:56:33 UTC
(In reply to Kurt Jaeger from comment #2)

Thank you for the advice.

Try to use this version, please: https://reviews.freebsd.org/D20468
Comment 4 olevole 2020-11-11 16:42:20 UTC
remark: this port works fine with FreeBSD-13 (CURRENT) ( unfortunately i don't have FreeBSD 12x )
Comment 5 Alex Povolotsky 2020-11-11 19:32:37 UTC
(In reply to Henning Matyschok from comment #3)
Nov 11 22:30:58 bipgame kernel: link_elf_obj: symbol ifnet undefined
Nov 11 22:30:58 bipgame kernel: linker_load_file: /boot/modules/if_vether.ko - unsupported file type

Nothing changes.
Comment 6 Henning Matyschok 2020-11-12 14:18:53 UTC
Created attachment 219600 [details]
Update, g20201111

Update, g20201111
Comment 7 Kurt Jaeger freebsd_committer 2020-11-12 15:05:02 UTC
testbuilds are fine. testload ok on 12.2
Comment 8 olevole 2020-11-12 15:38:56 UTC
test (build/load/work) ok on FreeBSD 13.0-CURRENT r367494
Comment 9 Alex Povolotsky 2020-11-13 19:01:57 UTC
(In reply to Kurt Jaeger from comment #7)
But does it works? In conjunction of if_bridge and several vnets (and jails), it caused strange ARP resolution bugs, with random connection failures between jails. I'll have to investigate it yet, but the problem is surely vether-related.
Comment 10 Kurt Jaeger freebsd_committer 2020-11-13 19:31:37 UTC
(In reply to Alex Povolotsky from comment #9)
I can't tell you if it works, as I have no test-case at hand.

Adding usage examples to the man page would definitly help.
Comment 11 olevole 2020-11-14 09:49:12 UTC
I suspect the ARP issue may not be related to the vether(4) module/interface ( and goes beyond this PR )

My use case for vether is routing from VALE/netmap switch to external network (stack) for bhyve VMs: https://www.bsdstore.ru/en/12.1.x/wf_bhyvenetwork_ssi.html#bhyvenetwork_opt4_sample

This is a more efficient network compared to bridge+tap.
Also use case relevant to jail + VALE/netmap.

g20201111 work fine for me with FreeBSD 13-CURRENT
Comment 12 Alex Povolotsky 2020-11-15 19:35:13 UTC
(In reply to Kurt Jaeger from comment #10)

I'll do the test case, I just need some free time...