Date: Sun, 19 Nov 2000 18:01:05 -0500 From: "Louis A. Mamakos" <louie@TransSys.COM> To: Jesper Skriver <jesper@skriver.dk> Cc: hackers@FreeBSD.ORG Subject: Re: React to ICMP administratively prohibited ? Message-ID: <200011192301.eAJN15714300@whizzo.transsys.com> In-Reply-To: Your message of "Sun, 19 Nov 2000 22:38:18 %2B0100." <20001119223818.A79237@skriver.dk> References: <20001118155446.A81075@skriver.dk> <Pine.BSF.4.21.0011181102540.52996-100000@achilles.silby.com> <20001118183632.A99512@skriver.dk> <20001119215357.A41281@skriver.dk> <200011192103.eAJL34713541@whizzo.transsys.com> <20001119220451.B41281@skriver.dk> <20001119223818.A79237@skriver.dk>
next in thread | previous in thread | raw e-mail | index | archive | help
It would seem more appropriate, somehow, to push the response to the ICMP message up into the protocols where they can take the appropriate action. Of course, the problem is that the PRC_* abstracted codes may not be rich enough to express all the semantics you'd wish to convey. So one goal might be to see if this sort of process could get pushed into netinet/tcp_sub.c:tcp_ctlinput(). Personally, I don't really like the idea of the icmp_input() function reaching into TCP's private state and doing stuff. There's too many potential interactions (e.g., what about IPSEC security associations?) I dunno, some of this is probably a matter of taste. louie To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200011192301.eAJN15714300>