[Bug 199478] tools/regression/sockets/unix_cmsg fails on 10.1-STABLE/11-CURRENT
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=199478 Garrett Cooper,425-314-3911 changed: What|Removed |Added Assignee|freebsd-test...@freebsd.org |n...@freebsd.org -- You are receiving this mail because: You are on the CC list for the bug. ___ freebsd-net@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-net To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org"
[Bug 199478] tools/regression/sockets/unix_cmsg fails on 10.1-STABLE/11-CURRENT
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=199478 --- Comment #2 from Garrett Cooper,425-314-3911 --- Works fine on my r275110 (5 month old) i386 build. I suspect it's a test issue with amd64 vs i386... -- You are receiving this mail because: You are on the CC list for the bug. ___ freebsd-net@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-net To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org"
[Bug 199136] [if_tap] Added down_on_close sysctl variable to tap(4)
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=199136 Gleb Smirnoff changed: What|Removed |Added Status|New |Open CC||gleb...@freebsd.org --- Comment #7 from Gleb Smirnoff --- I'm strongly against the sysctl, and reasons are same as before. Sysctl knob is global. You can make it per-vnet, but your patch lacks that. You could even make it per-interface, but that would require quite a lot of extra code. The IFF_LINK flag is a lesser patch, and immediately gives you a per-interface configuration granularity, which of course implies per-vnet. Setting flag in rc.conf requires same efforts as putting a line in sysctl.conf. Changing the default is different question, and should be discussed separately. -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-net@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-net To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org"
[Bug 177184] [bge] [patch] enable wake on lan
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=177184 Cy Schubert changed: What|Removed |Added CC||c...@freebsd.org, ||hi...@freebsd.org --- Comment #5 from Cy Schubert --- I'm willing to take this on if someone can donate a high end controller to -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-net@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-net To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org"
[Bug 177184] [bge] [patch] enable wake on lan
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=177184 --- Comment #6 from Cy Schubert --- Let's try this again... I'm willing to take this on if someone can donate an appropriate controller to me. So far a modified (for a recent CURRENT) version of the patch works. -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-net@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-net To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org"
[Bug 185996] [ip6] For IPv6, ipsec_address returns pointer to corrupted data
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=185996 Andrey V. Elsukov changed: What|Removed |Added CC||a...@freebsd.org Assignee|freebsd-net@FreeBSD.org |a...@freebsd.org -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-net@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-net To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org"
[Bug 199136] [if_tap] Added down_on_close sysctl variable to tap(4)
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=199136 eu...@grosbein.net changed: What|Removed |Added CC||eu...@grosbein.net --- Comment #8 from eu...@grosbein.net --- There is three years old PR containing per-interface patch for the problem: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=165174 -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-net@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-net To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org"
[Differential] [Changed Subscribers] D1438: FreeBSD callout rewrite and cleanup
jch added a subscriber: jch. REVISION DETAIL https://reviews.freebsd.org/D1438 To: hselasky, jhb, adrian, markj, emaste, sbruno, imp, lstewart, rwatson, gnn, rrs, kostikbel, delphij, neel, erj, mat, remkolodder, bcr, brueffer, brd, allanjude, wblock Cc: jch, wblock, freebsd-net ___ freebsd-net@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-net To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org"
[Bug 199478] tools/regression/sockets/unix_cmsg fails on 9.3-STABLE/10.1-STABLE/11-CURRENT (but only on amd64..?)
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=199478 Garrett Cooper,425-314-3911 changed: What|Removed |Added Summary|tools/regression/sockets/un |tools/regression/sockets/un |ix_cmsg fails on|ix_cmsg fails on |10.1-STABLE/11-CURRENT |9.3-STABLE/10.1-STABLE/11-C ||URRENT (but only on ||amd64..?) -- You are receiving this mail because: You are on the CC list for the bug. ___ freebsd-net@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-net To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org"
[Bug 199136] [if_tap] Added down_on_close sysctl variable to tap(4)
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=199136 --- Comment #9 from y...@rawbw.com --- > I'm strongly against the sysctl, and reasons are same as before. Sysctl knob > is global. You can make it per-vnet, but your patch lacks that. You could > even make it per-interface, but that would require quite a lot of extra code. Gleb, Default in this case is unreasonable. Consider this situation: admin makes tapN interface to initialize tap0 in /etc/rc.conf: cloned_interfaces="tap0; ifconfig_tap0="inet 192.168.2.1 up" tap0 is in "up" and initialized state from the system start. Now imagine virtual machine (say VirtualBox) is using tap0. This VM goes up, works, then shuts down. Now tap0 interface is "down", and has lost its IP address. The second and all subsequent run-cycles of VM will not be able to connect to the same network again, unless admin does 'ifconfig tap0 up; ifconfig tap0 inet ...' every time. This behavior is unreasonable in general, because *tapN driver has overridden the default tap0 state set by admin*, and decided that this interface should now be "down". VM run alters the system state in unintended fashion. > The IFF_LINK flag is a lesser patch, and immediately gives you a > per-interface configuration granularity, which of course implies per-vnet. > Setting flag in rc.conf requires same efforts as putting a line in > sysctl.conf. Besides that IFF_LINK flags are generally cryptic in their nature, there is really no need to be able to fine-tune this on per-net or per-interface basis. > Changing the default is different question, and should be discussed > separately. Yes, changing the default is what seems to be the most reasonable solution here. Please note that all users of tapN are more or less the same: they are the processes that need to connect to the network from the process side through the device /dev/tapN. They aren't aware of the network side of it, tapN interfaces. This side should behave reasonably as a system default behavior. My patch (the proposed new default) essentially *prevents any temporary tapN user from altering the system state defined by admin*. And with this new default tapN driver would bring the state back to what it was before tapN device was opened. I believe people who introduced vmnetN interfaces were solving the same exact problem. But vmnetN solution (morphing of tapN) seems to be an overkill. Because all users of tapN expect the same behavior. If you still disagree with the suggested new default, please describe the situation when tap0 is initialized before the use, and has to be reasonably expected to be "down" and lose its IP address after it is closed by the user. I propose to keep the old behavior net.link.tap.down_on_close=1 just in case for the off-chance that somebody actually depends on this behavior. But I don't think anybody should. -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-net@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-net To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org"
Multipoint GRE
Is it possible to create a point to multipoint GRE network on FreeBSD? On Linux I would do this by creating the GRE interface without a defined tunnel endpoint. Then by adding psudo-arp entries which map addresses on the GRE subnet with a tunnel endpoint address I can have multiple GRE tunnel destinations. Based on my testing so far, it looks like GRE on FreeBSD requires a single tunnel endpoint address. Is there any way around this? ___ freebsd-net@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-net To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org"
[Bug 199136] [if_tap] Added down_on_close sysctl variable to tap(4)
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=199136 Kubilay Kocak changed: What|Removed |Added See Also||https://bugs.freebsd.org/bu ||gzilla/show_bug.cgi?id=1651 ||74 -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-net@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-net To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org"
[Bug 165174] [patch] [tap] allow tap(4) to keep its address on close
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=165174 Kubilay Kocak changed: What|Removed |Added See Also||https://bugs.freebsd.org/bu ||gzilla/show_bug.cgi?id=1991 ||36 -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-net@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-net To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org"
[Bug 199478] tools/regression/sockets/unix_cmsg fails on 9.3-STABLE/10.1-STABLE/11-CURRENT (but only on amd64..?)
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=199478 Kubilay Kocak changed: What|Removed |Added Hardware|Any |amd64 -- You are receiving this mail because: You are on the CC list for the bug. ___ freebsd-net@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-net To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org"
[Bug 177184] [bge] Enable wake on lan (WoL)
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=177184 Kubilay Kocak changed: What|Removed |Added Keywords||feature, patch Summary|[bge] [patch] enable wake |[bge] Enable wake on lan |on lan |(WoL) -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-net@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-net To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org"
