HELP:Setup IPForwarding and PPP on Solaris 2.6 Intel with USR modem

The Outlander

unread,

Nov 4, 1997, 3:00:00 AM11/4/97

to

Hello all,

Just got my hands on a Solarix 2.6 Intel Version and I have it connected
to a "Local LAN" at home. (Powerbook, PowerMac 7600 running MKlinux and a
NEC Ready with Solaris 2.6)

Here's the deal:
I want my NEC to be a router to my local ISP so that I can access the
Internet from any machine on my network. I need a top level approach at
this.
I know that I will need to do an ifconfig for the modem so that I will be
able to use the NEC as a router.
Here are some issues that I'm wondering about....

1) I dont want PPP to startup everytime I boot up but only on demand
2} How exactly do I implement IPforwarding and the routing
3) How would I set up the PPP
4) How would I get Solaris to "see" the modem
5) And any other tips you may think I need for this task

Thanks in Advance

Marvin

Bruce Riddle

unread,

Nov 5, 1997, 3:00:00 AM11/5/97

to The Outlander

The Outlander wrote:
>
> Hello all,
>
> Just got my hands on a Solarix 2.6 Intel Version and I have it connected
> to a "Local LAN" at home. (Powerbook, PowerMac 7600 running MKlinux and a
> NEC Ready with Solaris 2.6)
>
> Here's the deal:
> I want my NEC to be a router to my local ISP so that I can access the
> Internet from any machine on my network. I need a top level approach at
> this.
> I know that I will need to do an ifconfig for the modem so that I will be
> able to use the NEC as a router.
> Here are some issues that I'm wondering about....
>
> 1) I dont want PPP to startup everytime I boot up but only on demand
> 2} How exactly do I implement IPforwarding and the routing
> 3) How would I set up the PPP
> 4) How would I get Solaris to "see" the modem

Take a look at
http://www.riddleware.com/solx86/ppp-config.html.

This answers all but the ipforwarding/routing.

That is another game if I understand what you want to do.

> 5) And any other tips you may think I need for this task
>
> Thanks in Advance
>
> Marvin

--
Bruce Riddle 610-694-8244
mailto:bri...@www.riddleware.com
http://www.riddleware.com

Josh Duncan

unread,

Nov 6, 1997, 3:00:00 AM11/6/97

to

Hello,

Please note that(as I understand these things) if you're going to
do things like this you will need an IP address at your ISP for each of
the machines on your network that you plan to get the internet to/from.
You cannot simply turn on forwarding and have info from the outside world
forwarded to your internal network(again, as I understand these things)
what you can do is throw linux(gasp) on that nec and do ip masquerading.
What is this, you ask? It amounts to this: one ip address at isp, one
modem or isdn link, whatever. infinite local addresses(make sure they
dont conflict with valid internet host addresses) the nec running linux
would make it seem to the isp that anythign from any machine on the local
network has come from the nec, so that the info is returned right back to
the nec. its then resent internally to whatever machine originally
requested it. This is probably what you need if its a dynamic ppp
connection, one ip address... if you have valid internet ip addresses
given by the isp for all your machines then this method of ip forwarding
should work fine as well.

I hope this information helps you, anyone who sees an error in it please
dont hesitate to correct me.

Josh

On Thu, 6 Nov 1997, Dan Anderson wrote:

> pan...@webexpert.net (The Outlander) wrote:
> > Just got my hands on a Solarix 2.6 Intel Version and I have it connected
> >to a "Local LAN" at home. (Powerbook, PowerMac 7600 running MKlinux and a
> >NEC Ready with Solaris 2.6)

> > I want my NEC to be a router to my local ISP so that I can access the
> >Internet from any machine on my network. I need a top level approach at
> >this.
>

> >1) I dont want PPP to startup everytime I boot up but only on demand
> >2} How exactly do I implement IPforwarding and the routing

> To disable ip_forwarding:
> % ndd -set /dev/ip ip_forwarding 0
>
> To enable ip_forwarding:
> % ndd -set /dev/ip ip_forwarding 1
>
> For routing, add a static route to route "default" to the NEC from your other
> machines (man route).
> For your internal network, use IP addresses reserved for internal networks only
> (see RFC 1597), such as 10.0.0.0 or 192.168.0.0.
>
> -
> Dan Anderson anderson
> San Diego, - @ -
> California, USA computer.org
>
>

Josh Duncan
dun...@digitek.com
Systems Technician, Rand Technologies

If religion is the opiate of the masses, then I want to be a drug dealer! :)

Dan Anderson

unread,

Nov 6, 1997, 3:00:00 AM11/6/97

to

Peter Arnold

unread,

Nov 7, 1997, 3:00:00 AM11/7/97

to dun...@digitek.com

Josh Duncan wrote:
>
> Hello,
>
> Please note that(as I understand these things) if you're going to
> do things like this you will need an IP address at your ISP for each of
> the machines on your network that you plan to get the internet to/from.
> You cannot simply turn on forwarding and have info from the outside world
> forwarded to your internal network(again, as I understand these things)
> what you can do is throw linux(gasp) on that nec and do ip masquerading.
> What is this, you ask? It amounts to this: one ip address at isp, one

What you need is a NAT (Network Address Translator).
IP-Filter (http://cheops.anu.edu.au/~avalon/ip-filter.html) does this on
solaris.
Works very well on sparc (not sure about intel). Version 3.2 can handle
dynamic IP addresses.

> modem or isdn link, whatever. infinite local addresses(make sure they
> dont conflict with valid internet host addresses) the nec running linux
> would make it seem to the isp that anythign from any machine on the local
> network has come from the nec, so that the info is returned right back to
> the nec. its then resent internally to whatever machine originally
> requested it. This is probably what you need if its a dynamic ppp
> connection, one ip address... if you have valid internet ip addresses
> given by the isp for all your machines then this method of ip forwarding
> should work fine as well.
>