Hi folks,
for dummies, what is the purpose of net.inet.tcp.ecn=0?
Should I set it to 1 on a gateway?
Is there some way to support ecn for ip level?
I am running 6.1 stable (amd64) using the unmodified
GENERIC.MP.
Every helpful comment or recommendation is highly
appreciated
Harri
Oh. Yeah if there's no performance penalty on such a solution then
great. Could someone confirm that?
So this works for cabled ethernet, where NIC promiscuous mode due to the
bridge won't hurt.
Also it wouldn't work for wireless interfaces. Also to be robust it
presumes that NIC unplug impl
I don't know the bridge code in OpenBSD as well as I know it in Linux -
basic bridges don't add any appreciable overhead on that platform until you
start mucking around with bridge specific things.
It just means you maintain an arp table distinct from each sub-interface.
tl;dr - it's not going to
In the kernel however that implies an internal indirection/one or more
additional rounds copying of all traffic and passing around, right, so
even it works quite well, it's not optimal right?
Anyhow sure that is an effective workaround if needed.
On 2017-06-02 02:20, Joel Wirāmu Pauling wrote:
..I got the problem of USB3 devices not being recognized at boot, also
with "USB Legacy" enabled. Leading me to the question:
Did anyone else experience this?
Can I tweak anything in the OS/kernel to maximize the likelihood of USB3
device recognition success at boot?
This is also in a new c
References:
http://www.asix.com.tw/products.php?op=pItemdetail&PItemID=131;71;112&PLine=71
http://www.asix.com.tw/FrootAttach/brief/AX88179_Brief.pdf
http://www.asix.com.tw/FrootAttach/datasheet/AX88179_Product_Introduction_v101.pdf
The datasheet is there and at http://docdro.id/acgxAtj /
htt
Hi,
If anyone would like an UGreen CR111 (
http://www.ugreen.com.cn/product-697-en.html ) AXEN AX88179 gigabit USB
3 NIC from
https://www.aliexpress.com/item/Ugreen-USB-Ethernet-10-100-1000-Mbps-Rj45-Gigabit-Network-Card-Lan-Adapter-For-Mac-OS/32400737540.html
please
1) Send me the receipt
On 2017-06-02 00:45, Joe Gidi wrote:
Good news! You can have this already.
Yay!
Go run Linux.
Em -
Nay!
No yay. Hope to see a solid solution to this problem on a non-crappy OS
soon.
Good news! You can have this already. Go run Linux.
On June 1, 2017 8:42:45 PM EDT, Tinker wrote:
>Ah - having an interface name naming scheme that, instead of just being
>
>a counter, e.g. CDCE + 0 -> 1 -> ... = "cdce0", denoting the physical
>slot where the device is connected, e.g. CDCE + USB
Ah - having an interface name naming scheme that, instead of just being
a counter, e.g. CDCE + 0 -> 1 -> ... = "cdce0", denoting the physical
slot where the device is connected, e.g. CDCE + USB root-hub: 0 + slot:
17 + address: 4 = "cdceur0s17a4", would do the job too.
On 2017-06-02 00:24, Tin
Hi,
What I meant was, it's fairly easy for interface numbers (e.g. NIC A as
CDCE0 and NIC B as CDCE1) to become exchanged.
With lots of unluck, there could be mechanical stress on USB ports so
that they would rearrange spontaneously so NIC B would become CDCE0 and
NIC A would become CDCE1.
Hi misc@,
This is a weird issue. I resolved it for my usecase but just wanted to
report it and also ask if it's a bug or feature and if there's any right
or wrong way here.
So I have one AXEN and one RTL8153(CDCE) gigabit USB NIC plugged in to a
Xeon Asrock E3C226D2I motherboard.
It's 6.0
On 2017-06-01 08:10, Sebastien Marie wrote:
my guess would be IGMP uses IP-Options. and by default, pf doesn't
allow
them.
you should try using the following in pf.conf:
set skip lo
block log
pass allow-opts
That fixed the problem.
Thank you.
Inspired in the new utf8 man page (thanks tedu@) I think I found a
solution to the charset issue.
New version:
/*
* MIME encode mail header quoted-printable.
*
*/
#include
#define ASCII 0x7f
#define IN 1
#define OUT 0
#define MAX 1024
int
main()
{
int c, i, n, nl,
On Thu, Jun 01, 2017 at 07:42:51AM -0500, Michael Graves wrote:
> Hello
>
> [...]
>
> The problem that I cannot explain is when I ping from obsd01 vether0 to
> obsd02 vether0 and I do a tcpdump on rtbsd vio0 I never see any IGMP packets
> from the obsd01/02 system, but I do see VXLAN packets. Ho
Hello
I am attempting to configure VXLAN in dynamic mode on OpenBSD 6.1 and I
am running into problems. My setup is as follows...
I have two 6.1 virtuals setup running under QEMU. Each virtual has a
vether0 interface and a vxlan0 interface attached to a bridge0
interface. Each virtual has
On Thu, Jun 01, 2017 at 11:11:09AM +0200, David Skantz wrote:
> I have no chainloader but the same problem and solution.
Looks like a fix is already in the works:
http://marc.info/?l=openbsd-tech&m=149630569323456&w=2
http://marc.info/?l=openbsd-tech&m=149630653223750&w=2
On Thu, Jun 01, 2017 at 10:13:11AM +0200, Henrik Friedrichsen wrote:
> Hey,
>
> I just updated to the latest snapshot and can't run the EFI bootloader
> anymore.
>
> I used to chainload the bootx64.efi with GRUB2, which worked fine until
> today. Now it just reboots after chainloading the bootloa
Hey,
I just updated to the latest snapshot and can't run the EFI bootloader
anymore.
I used to chainload the bootx64.efi with GRUB2, which worked fine until
today. Now it just reboots after chainloading the bootloader. I don't
know if loading the OpenBSD bootx64.efi directly will solve this, but
19 matches
Mail list logo
