aboutsummaryrefslogtreecommitdiffstatshomepage
path: root/src/device.c (follow)
Commit message (Collapse)AuthorAgeFilesLines
...
* socket: use dst_cache instead of handrolled cacheJason A. Donenfeld2016-11-041-1/+0
|
* device: use ARPHDR_VOID instead of ARPHDR_NONEJason A. Donenfeld2016-11-031-1/+1
| | | | | | These amount to the same exact thing, except that IPv6 auto configuration won't assign it a (useless) random address and add multicast routes.
* device: better debug message for unroutable packetsJason A. Donenfeld2016-10-221-1/+5
|
* device: show debug message when no peer has allowed-ips for packetJason A. Donenfeld2016-10-141-0/+1
|
* Rework headers and includesJason A. Donenfeld2016-09-291-1/+1
|
* build system: revamp building and configurationJason A. Donenfeld2016-07-181-2/+1
|
* persistent keepalive: use authenticated keepalivesJason A. Donenfeld2016-07-101-1/+1
|
* persistent keepalive: start sending immediatelyexperimental-0.0.20160708.1Jason A. Donenfeld2016-07-081-0/+2
| | | | | | | | | | | | | | | Rather than only start sending the persistent keepalive packets when the device first sends data, this changes it to send the packets immediately on `ip link set up`. This makes things generally seem more stateless, since the administrator does not have to manually ping the endpoint. Of course, if you have a lot of peers and all of them have persistent keepalive enabled, this could cause a lot of unwanted immediate traffic. On the other hand, if all of those peers are at some point going to be sending packets, this would happen anyway. I suppose the moral of the story is that persistent keepalive is a feature really just for clients behind NAT, not for servers, and it should be used sparingly, which is why we've set it off by default in the first place.
* device: move unlikely check to if clauseJason A. Donenfeld2016-07-051-2/+2
|
* device init: free wq after padataJason A. Donenfeld2016-06-301-3/+3
| | | | | The padata free functions make reference to their parent workqueue, so it's important that we wait to free the workqueue after the padata.
* device: remove updating of trans_startJason A. Donenfeld2016-06-291-2/+0
| | | | | | | | | | | | | | | | | | | | | Per http://lists.openwall.net/netdev/2016/05/03/87 dev->trans_start has been removed, and updates are now supposed to be handled with netif_trans_update, which now updates the particular txqueue's trans_start instead. However, netdev_start_xmit already updates this member after calling ndo_start_xmit, so the new netif_trans_update function smartly makes the comment that for drivers that don't use LLTX, it's not neccessary to call netif_trans_update. Except we do use LLTX, so it would seem again that we do need to be calling netif_trans_update. However, glancing at drivers like vxlan and other similar virtual tunnels, this doesn't seem to be the case. I suspect the reason is that we both also set IFF_NO_QUEUE, so we aren't even using a txqueue for updating. Thus, this patch removes updating of trans_start all together. I believe this should be okay for older kernels too.
* Initial commitJason A. Donenfeld2016-06-251-0/+352
Copyright © 1996 – 2023 Jason A. Donenfeld. All Rights Reverse Engineered.