[Bug 243703] fe80 route need to add manually and NDP doesn't populate itself

2020-04-12 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=243703

Alexander V. Chernikov  changed:

   What|Removed |Added

   Assignee|n...@freebsd.org |melif...@freebsd.org
 CC||melif...@freebsd.org

-- 
You are receiving this mail because:
You are on the CC list for the bug.
You are the assignee for the bug.
___
freebsd-net@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-net
To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org"


Problem reports for n...@freebsd.org that need special attention

2020-04-12 Thread bugzilla-noreply
To view an individual PR, use:
  https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=(Bug Id).

The following is a listing of current problems submitted by FreeBSD users,
which need special attention. These represent problem reports covering
all versions including experimental development code and obsolete releases.

Status  |Bug Id | Description
+---+---
In Progress |221146 | [ixgbe] Problem with second laggport  
In Progress |235700 | oce(4) driver causes fatal trap 12 on boot with e 
New |204438 | setsockopt() handling of kern.ipc.maxsockbuf limi 
New |205592 | TCP processing in IPSec causes kernel panic   
New |213410 | [carp] service netif restart causes hang only whe 
Open|  7556 | ppp: sl_compress_init() will fail if called anyth 
Open|187835 | ngctl(8) strange behavior when adding more than 5 
Open|193452 | Dell PowerEdge 210 II -- Kernel panic bce (broadc 
Open|194453 | dummynet(4): pipe config bw parameter limited to  
Open|200319 | Bridge+CARP crashes/freezes   
Open|202510 | [CARP] advertisements sourced from CARP IP cause  
Open|207261 | netmap: Doesn't do TX sync with kqueue
Open|210726 | tcp connect() can return invalid EADDRINUSE (Eg:  
Open|73 | igb(4): Kernel panic (fatal trap 12) due to netwo 
Open|225438 | panic in6_unlink_ifa() due to race
Open|225792 | ECMP is broken since tryforward() 
Open|227720 | Kernel panic in ppp server
Open|230807 | if_alc(4): Driver not working for Killer Networki 
Open|235524 | igb(4): Ethernet interface loses active link stat 
Open|236888 | ppp daemon: Allow MTU to be overridden for PPPoE  
Open|236983 | bnxt(4) VLAN not operational unless explicit "ifc 
Open|237072 | netgraph(4): performance issue [on HardenedBSD]?  
Open|237391 | route get returns no result for network addresses 
Open|237840 | Removed dummynet dependency on ipfw   
Open|238324 | Add XG-C100C/AQtion AQC107 10GbE NIC driver   
Open|240530 | netgraph/ng_source: Allow ng_source to inject int 
Open|240944 | em(4): Crash with Intel 82571EB NIC with AMD Pile 
Open|240969 | netinet6: Neighbour reachability detection broken 
Open|241106 | tun/ppp: panic: vm_fault: fault on nofault entry  
Open|241162 | Panic in closefp() triggered by nginx (uwsgi with 
Open|241191 | route flush panic with RADIX_MPATH
Open|243463 | ix0: Watchdog timeout 
Open|244066 | divert: Add sysctls for divert socket send and re 
Open|118111 | rc: network.subr Add MAC address based interface  

34 problems total for which you should take action.
___
freebsd-net@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-net
To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org"


[Bug 241191] route flush panic with RADIX_MPATH

2020-04-12 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=241191

Alexander V. Chernikov  changed:

   What|Removed |Added

   Assignee|n...@freebsd.org |melif...@freebsd.org

-- 
You are receiving this mail because:
You are on the CC list for the bug.
You are the assignee for the bug.
___
freebsd-net@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-net
To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org"


[Bug 237391] route get returns no result for network addresses (netmask portion of address is zero)

2020-04-12 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=237391

Alexander V. Chernikov  changed:

   What|Removed |Added

 CC||melif...@freebsd.org
   Assignee|n...@freebsd.org |melif...@freebsd.org

-- 
You are receiving this mail because:
You are on the CC list for the bug.
You are the assignee for the bug.
___
freebsd-net@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-net
To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org"


[Bug 225792] ECMP is broken since tryforward()

2020-04-12 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=225792

Alexander V. Chernikov  changed:

   What|Removed |Added

   Assignee|n...@freebsd.org |melif...@freebsd.org
 CC||melif...@freebsd.org

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-net@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-net
To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org"


Re: dummynet performance

2020-04-12 Thread Alexandr Baryshnyev

Dear Luigi!
The fact that the regular FreeBSD shaper Dummynet is still single-threaded is the reason that many people switch to 
using Linux. This is a real problem that really limits the use of the FreeBSD system as a high-speed router and shaper. 
I understand that this is not an easy task, but most likely no one but you can do it now. Please, correct the source 
code of the Dummynet and make it multi-threaded! I think a lot of people who still use FreeBSD will be very grateful to 
you. Can we hope that this problem will be resolved by you in the foreseeable future?  In any case, thank you very much 
for your work!


09.04.2020 20:28, Luigi Rizzo wrote:

On Thu, Apr 9, 2020 at 2:18 AM Özkan KIRIK  wrote:


Hello,

I wonder if it is possible to update dummynet code multi-threading capable
practically?
My idea is below:
- A new sysctl tunable will be defined as
"net.inet.ip.dummynet.thread_count" (default 1)
- To distribute tasks along threads, each sched instance can be assigned to
different thread.
- By default, all schedulers assigned to thread 0 if no thread_id is set.
With a new option named "thr_id" affinity can be set. as below:
   ipfw sched 1 config type QFQ   (by defaut thr_id = 0)
   ipfw sched 2 config type QFQ thr_id 1
   ipfw sched 3 config type QFQ thr_id 2
   ipfw sched 4 config type FIFO thr_id 3
   ipfw sched 5 config type FIFO thr_id 3  ( sched 4 & 5 assigned to same
thread 3 )

I think this approach is more easy then completely rewrite or other
solutions.



This change may not be completely trivial given that dummynet was designed as
single threaded and protected by a single lock.

If you want to proceed, you should do as follows:
- some members of struct dn_parms need to be duplicated for each thread,
   including prev_t, evheap, curr_time, the locks, and perhaps others.
   Probably may be useful to create a new struct for them, with a back
   pointer to the parent dn_parms, and include a refcount.

- add another rwlock to protect access to dn_cfg

- dummynet_io() does the initial demultiplexing calling dn_ht_find(),
   currently protected DN_BH_WLOCK(). This could be changed to an RWLOCK
   and I believe this initial step could be protected by a read lock
   (maybe there are corner cases where you need to create a new entry
   so you need to drop the lock, acquire in write mode and retry...)

- once the demux has returned a dn_fsk, maybe you can use a refcount
   to avoid the object being destroyed, release the read lock on
   dn_cfg.fshash, acquire an exclusive lock on the thread handling the
   dn_fsk, and proceed from there.

- the kernel thread that process the heap should now run each on
   one instance of the evheap

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



--
   Best regards,
   Alexandr B. Baryshnyev, e-mail: a...@abbon.net
___
freebsd-net@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-net
To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org"