natd broken for days
phk at phk.freebsd.dk
Thu Nov 11 08:40:34 PST 2004
In message <20041111163638.GA700 at laptop.6bone.nl>, Mark Santcroos writes:
>On Thu, Nov 11, 2004 at 05:25:23AM -0800, Sean McNeil wrote:
>> It has been reported that both amd64 and i386 architectures will panic
>> in natd by jumping to address 0. There has been no discussion since the
>> reports, however, and I was wondering if anyone is looking into it.
>This should fix it.
We have a problem if that is the case, because then ipdivert
doesn't run through net_init_domain() :-(
>--- sys/netinet/ip_divert.c Mon Nov 8 15:44:53 2004
>+++ sys/netinet/ip_divert.c Thu Nov 11 17:24:07 2004
>@@ -671,6 +671,9 @@
> .pru_send = div_send,
> .pru_shutdown = div_shutdown,
> .pru_sockaddr = div_sockaddr,
>+ .pru_sosend = sosend,
>+ .pru_soreceive = soreceive,
>+ .pru_sopoll = sopoll,
> .pru_sosetlabel in_pcbsosetlabel
>RIPE NCC - Delft University of Technology - The FreeBSD Project
>marks at ripe.net - m.a.santcroos at ewi.tudelft.nl - marks at freebsd.org
>freebsd-current at freebsd.org mailing list
>To unsubscribe, send any mail to "freebsd-current-unsubscribe at freebsd.org"
Poul-Henning Kamp | UNIX since Zilog Zeus 3.20
phk at FreeBSD.ORG | TCP/IP since RFC 956
FreeBSD committer | BSD since 4.3-tahoe
Never attribute to malice what can adequately be explained by incompetence.
More information about the freebsd-current