https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=248172
Eugene Grosbein changed:
What|Removed |Added
CC||eu...@freebsd.org
--- Comment #2
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=247647
Kubilay Kocak changed:
What|Removed |Added
Keywords|needs-qa|
Assignee|n...@freebsd.o
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=247647
--- Comment #12 from Zhenlei Huang ---
(In reply to Vincenzo Maffione from comment #11)
Thx :)
--
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-net@freebsd.o
Kristof Provost wrote this message on Thu, Jul 23, 2020 at 11:02 +0200:
> On 23 Jul 2020, at 11:00, Bjoern A. Zeeb wrote:
> > On 23 Jul 2020, at 8:09, Kristof Provost wrote:
> >
> >> On 23 Jul 2020, at 9:19, Kristof Provost wrote:
> >>> On 23 Jul 2020, at 0:15, John-Mark Gurney wrote:
> So, it
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=248213
Michael Tuexen changed:
What|Removed |Added
Assignee|n...@freebsd.org |tue...@freebsd.org
--
You are r
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=248213
Mark Linimon changed:
What|Removed |Added
Assignee|b...@freebsd.org|n...@freebsd.org
--
You are receiv
On 23 Jul 2020, at 9:02, Kristof Provost wrote:
On 23 Jul 2020, at 11:00, Bjoern A. Zeeb wrote:
On 23 Jul 2020, at 8:09, Kristof Provost wrote:
On 23 Jul 2020, at 9:19, Kristof Provost wrote:
On 23 Jul 2020, at 0:15, John-Mark Gurney wrote:
So, it's pretty easy to trigger, just attach a cou
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=247647
--- Comment #11 from Vincenzo Maffione ---
Once a commit hits master, we wait for a settling period (e.g. 2 weeks) to give
other developers and users the chance to hit possible regressions and problems.
If nothing shows up, the commit can b
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=248046
Mark Johnston changed:
What|Removed |Added
Flags|mfc-stable12? |mfc-stable12+
Assignee|n
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=242406
Mark Johnston changed:
What|Removed |Added
Assignee|n...@freebsd.org |ma...@freebsd.org
--
You are rec
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=242406
Mark Johnston changed:
What|Removed |Added
Status|Open|In Progress
--- Comment #13 from M
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=242406
--- Comment #12 from Mark Johnston ---
(In reply to Michael Muenz from comment #11)
Thanks. Do you happen to use VNET jails at all? If so it would be useful to
know that ng_tty still works as expected if you pass the associated interface
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=248172
--- Comment #20 from Gert Doering ---
Just for the record: if I insert a "sleep(1)" in the tester.c between the
open() call to /dev/tun0 and the ifconfig statement, *and* insert a "sleep 1"
in pccard_ether between "`ifconfig -ul` and if [ "
On Thu, Jul 23, 2020 at 3:38 AM Hans Petter Selasky wrote:
>
> On 2020-07-23 05:45, Kyle Evans wrote:
> > abandoning because the review process for this area is simply not
>
> Are you looking for this:
>
> https://reviews.freebsd.org/D24914
>
No, not at all. The race I was reliably hitting is mor
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=248172
--- Comment #19 from Gert Doering ---
(In reply to Andrey V. Elsukov from comment #17)
Thanks for the explanation.
I wonder if there is an easy way to trace these scripts, to see when exactly
something was ifconfig'ed?
I've sprinkled the
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=248172
--- Comment #18 from Eugene Grosbein ---
This depends on devd(8) daemon being enabled/running or not running at the
moment of creation of network interface.
If devd is running (and modern FreeBSD tends to require this), it is notified
by t
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=248172
--- Comment #17 from Andrey V. Elsukov ---
When you create tun/tap interface, the kernel generates LINK_UP event, then
devd handles this event and invokes /etc/pccard_ether script, that uses
routines from network.subr script. You may have s
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=248172
--- Comment #16 from Gert Doering ---
(In reply to Andrey V. Elsukov from comment #15)
This is still missing the point. If having ipv6_activate_all_interfaces="YES"
is a hard requirement now, the interface should *always* come up with
IFD
On Thu, 23 Jul 2020 11:02:01 +0200
"Kristof Provost" wrote:
> Yeah, agreed. I think hselasky has a better fix:
> https://reviews.freebsd.org/D24914
Yup, that should be it.
>
> I just saw his e-mail in a different thread.
>
> Best regards,
> Kristof
> _
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=248172
--- Comment #15 from Andrey V. Elsukov ---
(In reply to Gert Doering from comment #14)
Presence of this flag is under control of /etc/network.subr script. And this
always worked via rc.conf.
--
You are receiving this mail because:
You ar
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=248172
--- Comment #14 from Gert Doering ---
(In reply to Andrey V. Elsukov from comment #12)
rc.conf settings can not be the correct answer for spurious and
timing-dependent differences in behaviour.
Also, I can not control what our users will
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=248172
--- Comment #13 from Gert Doering ---
New test program coming, so please ignore this one.
There is something else needed to make this trigger more often, like "packets
in queue for this interface" or an actual reader on the tunfd.
(OpenVP
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=248172
Andrey V. Elsukov changed:
What|Removed |Added
CC||a...@freebsd.org
--- Comment #
On 23 Jul 2020, at 11:00, Bjoern A. Zeeb wrote:
On 23 Jul 2020, at 8:09, Kristof Provost wrote:
On 23 Jul 2020, at 9:19, Kristof Provost wrote:
On 23 Jul 2020, at 0:15, John-Mark Gurney wrote:
So, it's pretty easy to trigger, just attach a couple USB ethernet
adapters, in my case, they were u
On 23 Jul 2020, at 8:09, Kristof Provost wrote:
On 23 Jul 2020, at 9:19, Kristof Provost wrote:
On 23 Jul 2020, at 0:15, John-Mark Gurney wrote:
So, it's pretty easy to trigger, just attach a couple USB ethernet
adapters, in my case, they were ure, but likely any two spare
ethernet
interface
On 2020-07-23 05:45, Kyle Evans wrote:
abandoning because the review process for this area is simply not
Are you looking for this:
https://reviews.freebsd.org/D24914
--HPS
___
freebsd-net@freebsd.org mailing list
https://lists.freebsd.org/mailman/li
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=248172
--- Comment #11 from Gert Doering ---
This is driving me totally insane.
The first 4 times I ran the tester, it had IFDISABLED.
The next like 50 times, nothing... not sure what else is need to trigger it -
I ran a few openvpn instances i
On 23 Jul 2020, at 9:19, Kristof Provost wrote:
On 23 Jul 2020, at 0:15, John-Mark Gurney wrote:
So, it's pretty easy to trigger, just attach a couple USB ethernet
adapters, in my case, they were ure, but likely any two spare
ethernet
interfaces will work, and wire them back to back..
I’ve b
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=248172
--- Comment #10 from Gert Doering ---
Created attachment 216689
--> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=216689&action=edit
test program to reproduce behaviour
--
You are receiving this mail because:
You are on the CC lis
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=248172
--- Comment #9 from Gert Doering ---
So. I have a nice test program now which can be run in a loop and then looked
at later.
As I said it's somewhat spurious on my system - sometimes it triggers 10 times
in a row, then 20 times not at all
On 23 Jul 2020, at 0:15, John-Mark Gurney wrote:
> So, it's pretty easy to trigger, just attach a couple USB ethernet
> adapters, in my case, they were ure, but likely any two spare ethernet
> interfaces will work, and wire them back to back..
>
I’ve been able to trigger it using epair as well:
`s
31 matches
Mail list logo
