Hi,
It's not supported yet.
But I think it is reasonably feasible to add jumbo frames support on head
and stable/12, by improving iflib netmap support.
I hope to find the time to do this soon.
Cheers,
Vincenzo
Il giorno lun 18 mar 2019 alle ore 02:52 Andrew Vylegzhanin <
avv...@gmail.com> ha
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=236383
--- Comment #5 from Sergey Anokhin ---
Part of etc.conf
ifconfig_sk0="inet 10.0.0.1 netmask 255.255.255.0"
cloned_interfaces="bridge0"
ifconfig_rl0="inet 192.168.1.1 netmask 255.255.255.0"
ifconfig_bridge0="addm rl0 addm wlan0 up"
ifconfig
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=236383
--- Comment #4 from Sergey Anokhin ---
(In reply to Eugene Grosbein from comment #3)
Will it enough? Please let me know if you want to see additional info
~# pciconf -lvvv
hostb0@pci0:0:0:0: class=0x06 card=0x820b1043 chip=0x29a0
On 19.03.19 14:47, Sami Halabi wrote:
> Hi everyone,
>
> All buzz around Software-Defined Wan.. I wonder what is in the base of its
> fundamentals and what does FreeBSD has to offer in the subject.
You can always build solutions using normal open source components.
FreeBSD itself can do some net
Hi everyone,
All buzz around Software-Defined Wan.. I wonder what is in the base of its
fundamentals and what does FreeBSD has to offer in the subject.
Sami
___
freebsd-net@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-net
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=236383
--- Comment #3 from Eugene Grosbein ---
The panic is in ral(4) driver for wireless NIC. Please describe your hardware
including output of dmesg and pciconf -lvvv and show your wifi configuration.
--
You are receiving this mail because:
Yo
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=236383
Eugene Grosbein changed:
What|Removed |Added
Summary|Kernel panic|[ral] Kernel panic in
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=236383
Eugene Grosbein changed:
What|Removed |Added
Summary|[netgraph] Kernel panic |Kernel panic
|
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=236383
Eugene Grosbein changed:
What|Removed |Added
Attachment #202920|0 |1
is obsolete|
Hi Patrick.
I get that point, but then I have two options only: I somehow convince the BIOS
to do a network boot over a VLAN for installation - not a capability this BIOS
appears to have, or I end up creating a whole new VLAN that's either routed or
has YP, DNS, time and installation servers
Hi!
> Am 18.03.2019 um 22:12 schrieb Eric Bautsch :
> I now have a bridge0 on re0.33 which works, great.
> I now configure a bridge1 which contains re0 and put an IP on that bridge,
> and hey presto, that IP pings, but the IP on bridge0 on VLAN 33 stops pinging.
IMHO you should not be mixing VLA
11 matches
Mail list logo