Re: [PATCH v2] tcp: Add listening address to SYN flood message

From: Eric Dumazet
Date: Fri Nov 11 2022 - 19:10:47 EST


On Fri, Nov 11, 2022 at 4:00 PM Jamie Bainbridge
<jamie.bainbridge@xxxxxxxxx> wrote:
>
> On Sat, 12 Nov 2022 at 04:20, Stephen Hemminger
> <stephen@xxxxxxxxxxxxxxxxxx> wrote:
> >
> > On Fri, 11 Nov 2022 14:59:32 +1100
> > Jamie Bainbridge <jamie.bainbridge@xxxxxxxxx> wrote:
> >
> > > + xchg(&queue->synflood_warned, 1) == 0) {
> > > + if (IS_ENABLED(CONFIG_IPV6) && sk->sk_family == AF_INET6) {
> > > + net_info_ratelimited("%s: Possible SYN flooding on port %pI6c.%u. %s.\n",
> > > + proto, &sk->sk_v6_rcv_saddr,
> > > + sk->sk_num, msg);
> > > + } else {
> > > + net_info_ratelimited("%s: Possible SYN flooding on port %pI4.%u. %s.\n",
> > > + proto, &sk->sk_rcv_saddr,
> > > + sk->sk_num, msg);
> >
> > Minor nit, the standard format for printing addresses would be to use colon seperator before port
> >
> > if (IS_ENABLED(CONFIG_IPV6) && sk->sk_family == AF_INET6) {
> > net_info_ratelimited("%s: Possible SYN flooding on [%pI6c]:%u. %s.\n",
> > proto, &sk->sk_v6_rcv_saddr, sk->sk_num, msg);
> > } else {
> > net_info_ratelimited("%s: Possible SYN flooding on %pI4:%u. %s.\n",
> > proto, &sk->sk_rcv_saddr, sk->sk_num, msg);
>
> I considered this too, though Eric suggested "IP.port" to match tcpdump.
>
> Please let me know which advice to follow?

IPv6 [address]:port is also a standard (and unambiguous) way.

https://www.rfc-editor.org/rfc/rfc5952#page-11