- User Since
- Feb 27 2016, 2:23 AM (261 w, 2 d)
Tue, Feb 9
Attribution via git commit --author= would be nice next time please.
Mon, Feb 8
Adjust to latest git head.
Sun, Feb 7
wpa_supplicant now supports SO_RERROR upstream:
Mon, Feb 1
Now dealing with FreeBSD bugzilla routing socket overflow reports
Jan 30 2021
Jan 7 2021
Jan 1 2021
SO_RERROR for ntpd, which FreeBSD also uses.
All changes requested to the SO_RERROR approach have been made.
I have done as asked and queried this approach on the freebsd-arch mailing list. No replies which I read as no-one has anything bad to say about the approach, but sadly nothing positive either.
I would really like to see some traction here in 2021 :)
Oct 8 2020
Break out of the loop early on matching an address.
Oct 5 2020
Move SO_RERROR so it sits within the correct place.
Oct 4 2020
@melifaro any update on this?
Use SO_RERROR in route(8).
Warn on any errors returned by read(2) rather than assuming we always get a route message.
Adjusted man page as requested.
Oct 3 2020
Oct 2 2020
Sep 24 2020
Sep 23 2020
Ensure no uninitialised padding is leaked.
Hopefully this is now enough context.
May 11 2020
Jul 12 2016
Let me clarify.