Date: Fri, 4 Dec 1998 15:22:55 -0800 (PST) From: Doug White <dwhite@resnet.uoregon.edu> To: andrea <andrea.franceschini@linet.it> Cc: freebsd-current@FreeBSD.ORG Subject: Re: R: ip-masquerading.natd,ip-aliasing .... Message-ID: <Pine.BSF.4.03.9812041521310.9820-100000@resnet.uoregon.edu> In-Reply-To: <007a01be1f6c$0abf70c0$4d18b9c2@oma.linet.it>
next in thread | previous in thread | raw e-mail | index | archive | help
On Fri, 4 Dec 1998, andrea wrote: > >I don't know how fancy your router is, if it can be taught to natd certain > >packets or not (I think ipfw can do it, not sure). > > > >> I'have tried assigning 2 ip address at the same interface ,and using > >> this machine as a gateway on the same phisical net. > > > >You have to use an alias (with the netmask of that network, not > >0xffffffff) on the interface to get the second IP programmed in. > > First of all thank you for replying!:) > > Now the configuration you described is pretty the same of mine. > And that's the problem it doesn't works at all.:( That's no good. > The rule in the firewall that 'divert' the socket to natd seem to > work,because i can see the > counters of packets increasing.. > But natd doesn't get anything ,or so seems( i set-up natd in verbose mode > but nothing happens...) Check your natd configuration (see the manpage). Hopefully this isn't pathological -- this is the second case of ipfw+natd failing from a stock install. I need to test this myself. Doug White Internet: dwhite@resnet.uoregon.edu | FreeBSD: The Power to Serve http://gladstone.uoregon.edu/~dwhite | www.freebsd.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.BSF.4.03.9812041521310.9820-100000>