Date: Sat, 19 Dec 1998 14:49:07 -0400 From: Luis =?iso-8859-1?Q?Mu=F1oz?= <lem@cantv.net> To: "Dru Nelson" <dnelson@redwoodsoft.com>, freebsd-hackers@FreeBSD.ORG Subject: Re: Source address Message-ID: <3.0.6.32.19981219144907.007a7120@pop.cantv.net> In-Reply-To: <19981219031219.10031.qmail@findmail.com> References: <87r9u0tkgr.fsf@pens.ion.sci.fi>
next in thread | previous in thread | raw e-mail | index | archive | help
The source IP address is (or *should*) be set to the primary address of the interface through which the packet is sent. I have quite a few FreeBSD boxes with multiple NICs and this is exactly what we see here, though I still don't have any of them with multiple IP addresses on each interface. Regards. -lem At 03:12 AM 19/12/98 -0000, Dru Nelson wrote: > > >I think this is a great idea. > >> So. If there is no current solution to this problem, I'm >> thinking of doing the neccesary modifications to the kernel. I'm not a >> kernel hacker but this problem does'nt seem too hard to solve. >> >> So I'd like to get your oppinnions. I'm thinking of using the >> sysctl interface to the kernel. Introduce a new variable and if this >> variable is set outgoing packets are given source address described in >> this variable. This would be done just before the source address is >> set to the outgoing interface if it's not already set. (in ip_output.c) >> >> I really have no real clue if this is the right way to go it's >> just my first idea and I'd like to hear whay you think about it. Thanks. >> >> >> Jamie Bowden <jamie@itribe.net> writes: >> >> > On Tue, 15 Dec 1998, Richard Smith wrote: >> > >> > > Antti Kaipila wrote: >> > > > >> > > > I have a interesting problem here. I have FreeBSD accting as a router >> > > > between our LAN and Internet. I have a ET5025 card as interface eth0 and >> > > > Intel EtherExpress as interface fxp0. >> > > > >> > > > eth0 has address 10.156.214.2 and remote ends address is 10.156.214.1. >> > > > fxp0 has address 195.74.8.138 >> > > > >> > > > So, now when I try to connect from this machine acting as router to >> > > > anywhere on the internet my source address get set to >> > > > 10.156.214.2. Which is not nice, because all routers are dropping my >> > > > packets thinking they should'nt be routed (that's the right thing to >> > > > do ofcourse). >> > > > >> > > > Is there any way around this? >> > > >> > > You need to run natd on your FBSD router, so that all packets 'appear' >> > > to >> > > originate from *it* (195.74.8.138). See man natd. >> > >> > Not quite. His ISP is using 1918 networks between routers. >> > >> > I do this as well. With Cisco you can set the primary IP of the router, >> > and all traffic appears to come from that IP, no matter which interface it >> > goes through. If there is a way to have FreeBSD always report the >> > connection as coming from it's usable IP, all that has to be done is to do >> > it, but I don't know if FreeBSD can do that. >> > >> > Jamie Bowden >> > >> > -- >> > Systems Administrator, iTRiBE.net >> > >> > If we've got to fight over grep, sign me up. But boggle can go. >> > -Ted Faber (on Hasbro's request for removal of /usr/games/boggle) >> > >> > >> > To Unsubscribe: send mail to majordomo@FreeBSD.org >> > with "unsubscribe freebsd-hackers" in the body of the message >> > >> >> -- >> Antti Kaipila <anttik@iki.fi> >> >> To Unsubscribe: send mail to majordomo@FreeBSD.org >> with "unsubscribe freebsd-hackers" in the body of the message >> >> > > > >----- >See the original message at http://www.egroups.com/list/freebsd-hackers/?start=31780 > >To Unsubscribe: send mail to majordomo@FreeBSD.org >with "unsubscribe freebsd-hackers" in the body of the message > > > 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?3.0.6.32.19981219144907.007a7120>