Date: Fri, 26 Jan 2001 11:56:30 +1000 From: "Doug Young" <dougy@bryden.apana.org.au> To: <freebsd-questions@FreeBSD.ORG> Subject: routing public & private IP issue Message-ID: <009d01c0873b$38075a00$847e03cb@apana.org.au>
next in thread | raw e-mail | index | archive | help
This is a multi-part message in MIME format. ------=_NextPart_000_009A_01C0878F.05B51340 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable I'm trying to figure out the most expedient way to route traffic on a = LAN with public IP's & other traffic from a dialin ppp connection back = out to the internet via a permanently connected modem (hopefully = upgrading to DSL shortly) I don't have any problems with the LAN machines accessing the net unless = ppp-nat is running, so I figure I'm better off leaving them alone and = finding an alternative way of dealing with remote dialin machines. After messing about with NAT for months & getting nowhere, I'm wondering = it it might not be better to find a way to force the dialin serial port = / modem / ppp interface to use eg 192.168.0.1 & remote dialin machines = 192.168.0.2 - 192.168.0.255, then somehow convince 192.168.0.1 to talk = to the public IPs Is this feasible for someone whthout a few centuries experience ?? ------=_NextPart_000_009A_01C0878F.05B51340 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"> <HTML><HEAD> <META http-equiv=3DContent-Type content=3D"text/html; = charset=3Diso-8859-1"> <META content=3D"MSHTML 5.50.4134.600" name=3DGENERATOR> <STYLE></STYLE> </HEAD> <BODY bgColor=3D#ffffff> <DIV><FONT face=3DArial size=3D2>I'm trying to figure out the most = expedient way to=20 route traffic on a LAN with public IP's & other traffic from a = dialin ppp=20 connection back out to the internet via a permanently connected = modem=20 (hopefully upgrading to DSL shortly)</FONT></DIV> <DIV><FONT face=3DArial size=3D2></FONT> </DIV> <DIV><FONT face=3DArial size=3D2>I don't have any problems with the LAN = machines=20 accessing the net unless ppp-nat is running, so I figure I'm better off = leaving=20 them alone and finding an alternative way of dealing with remote dialin=20 machines.</FONT></DIV> <DIV><FONT face=3DArial size=3D2></FONT> </DIV> <DIV><FONT face=3DArial size=3D2>After messing about with NAT for months = &=20 getting nowhere, I'm wondering it it might not be better to find a way = to force=20 the dialin serial port / modem / ppp interface to use eg = 192.168.0.1 &=20 remote dialin machines 192.168.0.2 - 192.168.0.255, then somehow = convince=20 192.168.0.1 to talk to the public IPs</FONT></DIV> <DIV><FONT face=3DArial size=3D2></FONT> </DIV> <DIV><FONT face=3DArial size=3D2>Is this feasible for someone whthout a = few=20 centuries experience ??</FONT></DIV></BODY></HTML> ------=_NextPart_000_009A_01C0878F.05B51340-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?009d01c0873b$38075a00$847e03cb>