Re: netlink socket does not accept SOCK_DGRAM

> On 16 Jan 2023, at 15:13, Alexander V. Chernikov wrote: > > > >> On 15 Jan 2023, at 13:09, Alexander V. Chernikov wrote: >> >>> >>> On 15 Jan 2023, at 02:26, User Ngor wrote: >>> >>> man 4 rtnetlink says:

Re: netlink socket does not accept SOCK_DGRAM

> On 16 Jan 2023, at 18:00, User Ngor wrote: > > > On 1/15/23 12:43, Alexander V. Chernikov wrote: >> The snl(3) manpage itself includes some examples, including the complete >> working program in the end >> > man snl > No manual entry for

Re: netlink socket does not accept SOCK_DGRAM

> On 15 Jan 2023, at 13:09, Alexander V. Chernikov wrote: > >> >> On 15 Jan 2023, at 02:26, User Ngor wrote: >> >> man 4 rtnetlink says: >> >>int socket(AF_NETLINK, SOCK_DGRAM, NETLINK_ROUTE); >> >> >> >> The follo

Re: close(2) on a PF_ROUTE socket returns -1 and sets errno to EOPNOTSUPP

> On 15 Jan 2023, at 13:50, Alexander V. Chernikov wrote: > > > >> On 14 Jan 2023, at 20:46, Guy Yur wrote: >> >> Hi, >> >> close(2) on a PF_ROUTE socket returns -1 and sets errno to EOPNOTSUPP. >> I am testing 14.0-CURRENT (main branch) bu

Re: netlink socket does not accept SOCK_DGRAM

The snl(3) manpage itself includes some examples, including the complete working program in the end/Alexander15.01.2023, 16:55, "User Ngor" : It’s a bug. The manage should state SOCK_RAW, but both options should be supported, which is not the case ATM. I’ll fix it in a couple of days. Meanwhile it

Re: close(2) on a PF_ROUTE socket returns -1 and sets errno to EOPNOTSUPP

> On 14 Jan 2023, at 20:46, Guy Yur wrote: > > Hi, > > close(2) on a PF_ROUTE socket returns -1 and sets errno to EOPNOTSUPP. > I am testing 14.0-CURRENT (main branch) built today. > On 13.1-RELEASE-p5 close returns 0. > > The problem looks to be related to

Re: netlink socket does not accept SOCK_DGRAM

> On 15 Jan 2023, at 02:26, User Ngor wrote: > > man 4 rtnetlink says: > > int socket(AF_NETLINK, SOCK_DGRAM, NETLINK_ROUTE); > > > > The following snippet fails > >int fd = socket(AF_NETLINK, SOCK_DGRAM, NETLINK_ROUTE); >if (fd < 0) { >perror("Failed to open netlink

Re: mention AF_NETLINK in man 2 socket

Committed in b0286ee504c6. > On 12 Jan 2023, at 17:23, Alexander V. Chernikov wrote: > > Ack, thanks for pointing that out. > I’ll update the manage when I have time. > > /Alexander > >> On 12 Jan 2023, at 03:18, User Ngor wrote: >> >> Looks like the

Re: mention AF_NETLINK in man 2 socket

Ack, thanks for pointing that out. I’ll update the manage when I have time. /Alexander > On 12 Jan 2023, at 03:18, User Ngor wrote: > > Looks like there are no references to {PF|AF}_NETLINK in the socket manpage. > > -- > Ihor Antonov > >

Re: Build Break?

02.10.2022, 17:18, "Larry Rosenman" :On 10/02/2022 8:12 am, Alexander V. Chernikov wrote: On 1 Oct 2022, at 22:57, Larry Rosenman <l...@lerctr.org> wrote:  --- all_subdir_nfscommon --- Building  /usr/obj/usr/src/amd64.amd64/sys/LER-MINIMAL/modules/usr/src/sys/modules/nfscommon/

Re: Build Break?

> On 1 Oct 2022, at 22:57, Larry Rosenman wrote: > > --- all_subdir_nfscommon --- > Building > /usr/obj/usr/src/amd64.amd64/sys/LER-MINIMAL/modules/usr/src/sys/modules/nfscommon/nfs_commonkrpc.o > --- all_subdir_netgraph --- > --- all_subdir_netgraph/deflate --- > Building >

Re: ipfw: setsockopt(IP_FW_NAT44_XCONFIG): Invalid argument

> On 12 Sep 2021, at 11:51, Yuri Tcherkasov wrote: > > ipfw nat 1 config ip XXX.XXX.XXX.xx reset unreg_only same_ports Looks pretty close to https://reviews.freebsd.org/D23450 I guess rebuilding the ipfw(8) binary should help.

Re: ipfw: setsockopt(IP_FW_NAT44_XCONFIG): Invalid argument

> On 12 Sep 2021, at 06:52, Yuri Tcherkasov wrote: > > Hi > > I'm binary upgrade FreeBSD from 10.2 to 13.0 > > After upgrate all workin well, but I need add one more routing table. So add > to > GENERIC kernel You can add 'net.fibs=2' in the loader.conf, there is no need to recompile the

Re: ifa leak on VNET teardown

> On 6 Mar 2021, at 09:26, Kristof Provost wrote: > > On 13 Feb 2021, at 21:58, Alexander V. Chernikov wrote: >> It turns out we're leaking some ifas for loopback interfaces on VNET >> teardown: >> > There’s a recent bug about this as well: 253998. > The prob

ifa leak on VNET teardown

___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: panic rtentry / hashdestroy /in6_purgeaddr related?

21.01.2021, 18:10, "Alexander Leidinger" : > Hi, > > -current at d7fc908cffa as of 2021-01-20-154143. > > I've seen several failures to free an rtentry on the console shortly > before the panic. May or may not be related..._ Sorry for the breakage, should be fixed by 130aebbab0d3. > ---snip--- >

Re: jail fib no longer works after net.add_addr_allfibs=0

11.01.2021, 14:59, "qroxana" : > On Mon, 11 Jan 2021 13:25:51 +0000, Alexander V. Chernikov > wrote: > >>  Could you please consider clarifying the end result you want to achieve? >>  If you could include some more details of how it was configured earlier, it &

Re: jail fib no longer works after net.add_addr_allfibs=0

11.01.2021, 12:39, "qroxana" : > I have exec.fib = 2 in /etc/jail.conf, but it seems the address of > the jail is not inserted into this fib. What's the best practice > for using jail with fib when net.add_addr_allfibs=0? Could you please consider clarifying the end result you want to achieve? If

Re: linker_load_file: /boot/kernel/ipfw.ko - unsupported file type

15.12.2020, 15:17, "Oleg V. Nauman" : >  Hello, > > kernel: link_elf_obj: symbol fib6_lookup_rt undefined > kernel: linker_load_file: /boot/kernel/ipfw.ko - unsupported file type > > It seems ipf.ko unconditionally perform IPV6 lookup even on system built with > WITHOUT_INET6=YES defined Should be

Re: adding existing ipv6 network route returns ENOMEM instead of EEXIST if loopback route also exists

21.11.2020, 22:48, "Guy Yur" : > Hi, > > When adding a route with a netmask, add_route() in route_ctl.c > adds the route with destination address masked. > If the add failed (for example, the route exists) it calls > lookup_prefix() with the original unmasked destination. Thank you for the report!

Re: FreeBSD CI Weekly Report 2020-04-12

___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: net.add_addr_allfibs=1 behaviour deprecation

18.07.2020, 14:22, "Alexander V. Chernikov" : > Dear FreeBSD users, > > I would like to make net.add_addr_allfibs=0 as the default system behaviour > and remove net.add_addr_allfibs. > To do so, I would like to collect use cases with net.add_addr_allfibs=1 and > multi

net.add_addr_allfibs=1 behaviour deprecation

Dear FreeBSD users, I would like to make net.add_addr_allfibs=0 as the default system behaviour and remove net.add_addr_allfibs. To do so, I would like to collect use cases with net.add_addr_allfibs=1 and multiple fibs, to ensure they can still be supported after removal. Background:

Re: routed && route6d removal proposal

22.06.2020, 14:54, "Hiroki Sato" : > "Alexander V. Chernikov" wrote >   in <273191592779...@mail.yandex.ru>: > > me> Hey, > me> > me> I would like to propose removal of sbin/routed and usr.sbin/route6d. > >  I am still using both o

Re: routed && route6d removal proposal

22.06.2020, 13:50, "Rodney W. Grimes" : >>  Hey, Hi Rodney, >> >>  I would like to propose removal of sbin/routed and usr.sbin/route6d. > > I disagree with removal, as your analysis is flawed. Thank you for the feedback! > >>  routed(8) is the daemon implementing RIPv2 routing protocol. >>  

routed && route6d removal proposal

Hey, I would like to propose removal of sbin/routed and usr.sbin/route6d. routed(8) is the daemon implementing RIPv2 routing protocol. route6d(8) is the daemon implementing RIPng routing protocol for IPv6. RIP [1] was one of the first protocols used in the networking. The first version was

Re: net.inet6.ip6.deembed_scopeid removal

[re-sending email with as non-html] Hey, I would like to deprecate net.inet6.ip6.deembed_scopeid sysctl while leaving the current default behaviour. This sysctl controls whether IPv6 scope is embedded in the IPv6 address or not when reading or writing route/interface/ifaddr data via

net.inet6.ip6.deembed_scopeid removal

___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Next-hop objects and scalable multipath routing project status update [May 8]

Hi, I would like to share the current state and the next steps for the nhops/multipath project. To recap: project is about modernising the current routing stack and implementing scalable multipath routing. Most changes are based on introduction of the concept of nexthops. Nexthops, which

Next-hop objects and scalable multipath routing project status update

Hi, I would like to share the current state and the next steps for the nhops/multipath project. To recap: project is about modernising the current routing stack and implementing scalable multipath routing. Most changes are based on introduction of the concept of nexthops. Nexthops, which

Re: r360294: buildkernel failure: etinet/tcp_stacks/bbr.c:5605:35: error: incomplete definition of type

25.04.2020, 11:18, "O. Hartmann" : > Hello, > > recent commits to CURRENT makes buildkernel to fail due to some incomplete > definition errors > during compiling: Should be fixed by r360295. Sorry for the breakage. > > [...] > - --- all_subdir_tcp --- > - --- bbr.o --- >

Re: FreeBSD CI Weekly Report 2020-04-12

15.04.2020, 15:10, "Kristof Provost" : > On 15 Apr 2020, at 15:34, Kristof Provost wrote: >>  On 15 Apr 2020, at 0:37, Li-Wen Hsu wrote: >>>  (Please send the followup to freebsd-testing@ and note Reply-To is >>>  set.) >>> >>>  FreeBSD CI Weekly Report 2020-04-12 >>>  

CFT: Next-hop objects and scalable multipath routing

I would like to introduce an implementation of scalable multipath routing. Previous implementation (RADIX_MPATH) focused on a simpler case like having 2 defaults, with performance falling linearly proportional to the number of paths. That implementation was also tightly coupled lookup algorithm

Re: current does not boot on vmware fusion 11

15.02.2020, 20:44, "Toomas Soome" : >>  On 15. Feb 2020, at 22:19, Alexander V. Chernikov wrote: >> >>  Hi folks, >> >>  I upgraded vmware fusion to version 11 recently and noticed that my -amd64 >> VM stops booting immediately after printing

current does not boot on vmware fusion 11

Hi folks, I upgraded vmware fusion to version 11 recently and noticed that my -amd64 VM stops booting immediately after printing EFI framebuffer information. VM pops up a message stating that "The firmware encountered an unexpected exception. The virtual machine cannot boot." Further digging

Re: ip_divert.c:374:7: error: use of undeclared identifier

25.01.2020, 19:14, "AN" : > FYI Should be fixed by r357144. Thanks for the report! > > FreeBSD Free_BSD_13 13.0-CURRENT FreeBSD 13.0-CURRENT #22 r356360: Sat Jan > 4 20:10:21 EST 2020 > root@Free_BSD_13:/usr/obj/usr/src/amd64.amd64/sys/MYKERNEL amd64 1300074 > > --- all_subdir_dtrace --- > ---

Re: panic: Assertion in_epoch(net_epoch_preempt) failed at ... src/sys/net/if.c:3694

oulders of giants. > >>  On 21 Jan 2020, at 18:38, Alexander V. Chernikov >> wrote: >> >>  21.01.2020, 17:25, "Nick Hibma" : >>>  When using a trivial program to read from the divert socket and post back >>> the machine panics instantly whe

Re: panic: Assertion in_epoch(net_epoch_preempt) failed at ... src/sys/net/if.c:3694

21.01.2020, 17:25, "Nick Hibma" : > When using a trivial program to read from the divert socket and post back the > machine panics instantly when a packet is sent to userland and back again > (incoming packet for the interface, so ifname is set). This is current from > today with no changes > >

Re: panic "wlock already held" when changing ipv6 default route

25.03.2016, 02:11, "Guy Yur" : > Hi, > > When changing the ipv6 default route I get a panic on wlock already held. > Could be related to r293424 lock changes, haven't checked an older version > yet. Hi, Yes, there is a problem when the default route next hop is filled in

Re: forwarding didn't work if wlan0 is member of a bridge

___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: forwarding didn't work if wlan0 is member of a bridge

13.01.2016, 13:02, "Olivier Cochard-Labbé" <oliv...@cochard.me>: > On Wed, Jan 13, 2016 at 9:45 AM, Alexander V. Chernikov <melif...@ipfw.ru> > wrote: > >>  I suspect the reason here is link state bridge handling. >>  ix0 does not seem to have IFCA

Re: forwarding didn't work if wlan0 is member of a bridge

12.01.2016, 23:48, "Olivier Cochard-Labbé" : > On Tue, Jan 12, 2016 at 7:22 PM, Adrian Chadd > wrote: > >>  This is actually the intended behaviour, right? The routed interface >>  is down, so the IP address on it and connected to it are unreachable. >

Re: forwarding didn't work if wlan0 is member of a bridge

12.01.2016, 01:53, "Olivier Cochard-Labbé" : > After weeks of troubleshooting, at last I found how to reproduce this > problem ;-) Hi Olivier, > > Here is the setup: > > LAN0 <--> [(re0) fbsd router (bridge0 addm re1 addm wlan0)] <--> Wireless > LAN > > If interface re1

Re: panic: refcount inconsistency: found: 0 total: 1

03.11.2015, 17:05, "David Wolfskill" : > This was on my laptop; yesterday, it built & booted: > > FreeBSD g1-252.catwhisker.org 11.0-CURRENT FreeBSD 11.0-CURRENT #230 > r290270M/290270:1100085: Mon Nov 2 05:03:07 PST 2015 >

Re: panic in arptimer in r289937

31.10.2015, 05:32, "Adrian Chadd" : > Hiya, > > Here's a panic from arptimer: Hi Adrian, As far as I see, line 205 in if_ether.c is IF_AFDATA_LOCK(ifp) which happens after LLE_WUNLOCK(). So, it looks like (pre-cached) ifp had been freed before locking ifdata. Do you have

Re: panic in arptimer in r289937

31.10.2015, 16:46, "Adrian Chadd" <adr...@freebsd.org>: > On 31 October 2015 at 09:34, Alexander V. Chernikov > <melif...@freebsd.org> wrote: >>  31.10.2015, 05:32, "Adrian Chadd" <adr...@freebsd.org>: >>>  Hiya, >>> >>&g

Re: r288951: ifconfig -alias, arp not removed

30.10.2015, 00:57, "Bryan Drewery" : > On 10/29/2015 9:46 AM, Bryan Drewery wrote: >>  On 10/29/15 9:42 AM, Eric van Gyzen wrote: >>>  On 10/29/2015 11:25, Bryan Drewery wrote:  # ifconfig  igb0: flags=8843 metric 0 mtu 1500

Re: kernel dtrace and current

13.09.2015, 23:54, "Mark Johnston" <ma...@freebsd.org>: > On Sun, Sep 13, 2015 at 04:23:23PM +0300, Alexander V. Chernikov wrote: >>  Hello all, >> >>  I keep running in >>  "dtrace: failed to compile script: "/usr/lib/dtrace/psinfo.d

kernel dtrace and current

Hello all, I keep running in "dtrace: failed to compile script: "/usr/lib/dtrace/psinfo.d", line 39: failed to copy type of 'pr_uid': Type information is in parent and unavailable" message more and more often while trying to trace different -current kernels. Typically the reason besides that is

Re: Panic on kldload/kldunload in/near callout

12.09.2015, 20:30, "hiren panchasara" <hi...@strugglingcoder.info>: > On 09/12/15 at 03:32P, Alexander V. Chernikov wrote: >>  12.09.2015, 02:22, "hiren panchasara" <hi...@strugglingcoder.info>: >>  > On 09/11/15 at 09:06P, Hans Pett

Re: Panic on kldload/kldunload in/near callout

12.09.2015, 02:22, "hiren panchasara" : > On 09/11/15 at 09:06P, Hans Petter Selasky wrote: >>  On 09/10/15 21:23, hiren panchasara wrote: >>  > I am on 11.0-CURRENT FreeBSD 11.0-CURRENT #4 r286760M: Thu Sep 10 >>  > 08:15:43 MST 2015 >>  > >>  > I get random (1 out of

Re: Why does netstat not work in jails?

28.08.2015, 04:56, Chris H bsd-li...@bsdforge.com: I've been attempting to run jails on an 11-CURRENT for the purpose of building world/kernel ports for all of our 9-STABLE production servers. I'm using standard/classic jail setup(s) -- not using any of the convenience ports/applications

Re: The KASSERT from r282155 fired; have crash dump. will travel

30.04.2015, 15:31, David Wolfskill da...@catwhisker.org: From /var/crash/core.txt.6: Thu Apr 30 05:21:22 PDT 2015 FreeBSD  11.0-CURRENT FreeBSD 11.0-CURRENT #47  r282269M/282269:1100071: Thu Apr 30 05:07:08 PDT 2015 r...@g1-254.catwhisker.org:/common/S3/obj/usr/src/sys/CANARY  amd64

Re: panic: resize_storage() notify failure [Was: HEADS UP: Merging projects/ipfw to HEAD]

On 11.10.2014 18:15, David Wolfskill wrote: On Sat, Oct 04, 2014 at 04:35:51PM +0400, Alexander V. Chernikov wrote: Hi, I'm going to merge projects/ipfw branch to HEAD in the middle of next week. OK; I was able to build install head @r272938 this morning on my laptop; on reboot, I

Re: HEADS UP: Merging projects/ipfw to HEAD

On 04 Oct 2014, at 16:35, Alexander V. Chernikov melif...@freebsd.org wrote: Hi, I'm going to merge projects/ipfw branch to HEAD in the middle of next week. Merged in r 272840. What has changed: Main user-visible changes are related to tables: * Tables are now identified by names

HEADS UP: Merging projects/ipfw to HEAD

Hi, I'm going to merge projects/ipfw branch to HEAD in the middle of next week. What has changed: Main user-visible changes are related to tables: * Tables are now identified by names, not numbers. There can be up to 65k tables with up to 63-byte long names. * Tables are now set-aware

Re: Looping during boot-up process in FreeBSD-11 current

On 01.10.2014 02:02, Mike. wrote: On 9/30/2014 at 7:25 PM José Pérez Arauzo wrote: |[snip] |Try the 271146, |[snip] = This might be related with r271207. Can you try r271206 (or any recent HEAD with reverted r271207) ? I installed the 10.0 release CD. Then (after

Re: dhclient sucks cpu usage...

On 10.06.2014 07:03, Bryan Venteicher wrote: Hi, - Original Message - So, after finding out that nc has a stupidly small buffer size (2k even though there is space for 16k), I was still not getting as good as performance using nc between machines, so I decided to generate some flame

Re: dhclient sucks cpu usage...

On 10.06.2014 20:24, John-Mark Gurney wrote: Alexander V. Chernikov wrote this message on Tue, Jun 10, 2014 at 13:17 +0400: On 10.06.2014 07:03, Bryan Venteicher wrote: Hi, - Original Message - So, after finding out that nc has a stupidly small buffer size (2k even though

Re: dhclient sucks cpu usage...

On 10.06.2014 22:11, Bryan Venteicher wrote: - Original Message - On 10.06.2014 07:03, Bryan Venteicher wrote: Hi, - Original Message - So, after finding out that nc has a stupidly small buffer size (2k even though there is space for 16k), I was still not getting as good as

Re: dhclient sucks cpu usage...

On 10.06.2014 22:56, John-Mark Gurney wrote: Alexander V. Chernikov wrote this message on Tue, Jun 10, 2014 at 21:33 +0400: On 10.06.2014 20:24, John-Mark Gurney wrote: Alexander V. Chernikov wrote this message on Tue, Jun 10, 2014 at 13:17 +0400: On 10.06.2014 07:03, Bryan Venteicher wrote

Re: New and exciting panic, possibly re(4)

On 07.05.2014 23:24, Sean Bruno wrote: While screwing around with comcast, I can trivially get this panic out of my desktop machine, and am very confused. It seems to happen on link change up/down events. I'm running 11.0-CURRENT FreeBSD 11.0-CURRENT #5 r265280M. I don't have any direct

Re: r265279 causes gpf at sys/net/route.c:930

On 04.05.2014 00:02, Trond Endrestøl wrote: Hi, I updated one of my amd64 base/head VMs this afternoon. It crashes in rt_expunge(), and I think r265279 is to blame. If someone's interested, here's the crash report: http://ximalas.info/~trond/amd64-head-VBOX-crash/r265283/core.txt.0

Re: r265279 causes gpf at sys/net/route.c:930

On 04.05.2014 00:06, Alexander V. Chernikov wrote: On 04.05.2014 00:02, Trond Endrestøl wrote: Hi, I updated one of my amd64 base/head VMs this afternoon. It crashes in rt_expunge(), and I think r265279 is to blame. If someone's interested, here's the crash report: http://ximalas.info

Re: picking a new AF_* number for NETLINK ?

On 17.01.2014 03:19, Luigi Rizzo wrote: In porting the kernel openvswitch code to FreeBSD we have implemented netlink sockets, so we need to pick a Wow, great! How deep you're planning to go with netlink support? E.g. sockets with NETLINK_GENERIC OVS-related CMDs, or NETLINK_ROUTE (and other

Re: interesting routing bug...

On 09.01.2014 05:18, John-Mark Gurney wrote: Well, I was trying to manually add a route for a host on the local network (I can explain why, but it doesn't matter) and I got this: Hello! There are several different kernel userland bugs :) # netstat -rnfinet Routing tables Internet:

Re: [rfc] migrate lagg to an rmlock

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 24.08.2013 00:54, Adrian Chadd wrote: Hi, I'd like to commit this to -10. It migrates the if_lagg locking from a rw lock to a rm lock. We see a bit of contention between the transmit and We're running lagg with rmlock on several hundred

Re: (i)frame based sites cause horrible performence in firefox 14.0.1

On 15.08.2012 07:04, Aryeh Friedman wrote: Sites that are based on frames or iframes (such as google mail and most of google's non-search services) kill the performance of www/firefox [firefox-14.0.1_1,1] (last updated yesterday on a 9.1 built at the same time) here is the uname: Same for me,

Re: null pointer panic in bpf_peers_present

On 04.06.2012 02:22, Andriy Gapon wrote: on 03/06/2012 23:56 Andriy Gapon said the following: I wonder if anybody else is seeing this and if there is a fix... This is very recent (today's) FreeBSD head with pretty dull network configuration. During boot I run into the following panic:

Re: bpf kernel crash

On 04.06.2012 18:31, Michael Pounov wrote: Kernel crash when you wish to change interface name from vlan0 to other name It seems to be in arrival/departure events. Yes, this is already fixed in r236559. -- WBR, Alexander ___

Re: MPLS in freebsd

On 06.05.2012 12:11, Kurt Jaeger wrote: Hello, is there any on-job work on MPLS support in FreeBSD? Do you know this site ? It points to some svn repository with mpls patches. http://freebsd.mpls.in/ Major number of depends are already merged to the tree. I'm currently working to update

Re: Some performance measurements on the FreeBSD network stack

On 20.04.2012 01:12, Andre Oppermann wrote: On 19.04.2012 22:34, K. Macy wrote: This is indeed a big problem. I'm working (rough edges remain) on changing the routing table locking to an rmlock (read-mostly) which This only helps if your flows aren't hitting the same rtentry. Otherwise you

Re: Problem with r233937 on i386

On 06.04.2012 16:09, David Wolfskill wrote: Kernel build @ r233941 failed for me this morning, running: FreeBSD g1-227.catwhisker.org 10.0-CURRENT FreeBSD 10.0-CURRENT #525 233918M: Thu Apr 5 04:42:37 PDT 2012 r...@g1-227.catwhisker.org:/usr/obj/usr/src/sys/CANARY i386 thus: ...

Re: Thoughts on TMPFS no longer being considered highly experimental

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Matthew Jacob wrote: I gave up on using it after a brief try earlier this year. I can't remember the details, but it did lock up my amd64 system. On Thu, 23 Jun 2011, David O'Brien wrote: Does anyone object to this patch? David Wolfskill

[patch] permit fib to be set on interface

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 At the moment the only possible way to set packet fib from userland is ipfw(8) setfib rule. Since no 'setfib tablearg' exists ruleset grows with every fib. Additionally, there is no way to set packet fib before netgraph processing: L2 ipfw hook is