----- Original Message -----
From: "Ronneil Camara" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Friday, June 30, 2000 02:45 PM
Subject: RE: [plug] linux flavors
> > -----Original Message-----
> > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]
> > Sent: Friday, June 30, 2000 2:18 PM
> > To: [EMAIL PROTECTED]
> > Subject: Re: [plug] linux flavors
> >
> >
> > What about the 192.168.0.1 to 254 IP? Do you think they can route IP
> > packets. I think no! The PC which has a live IP address like
> > 208.160.233.88 can route a packet. Di ba?
> >
> > Eto diagram:
> >
> > win98 client------->MS NT WS 4.0 proxy------->Internet
> > 192.168.0.2 192.168.0.1
> > (dial-up)
> >
> >
> > I'm talking about the above setup. Di ba non-routable ang di
> > live IP? :)
> > Parang IP masquerading ng Linux. Clients from the outside
> > CAN'T use it as
> > a proxy. While clients inside (i.e. LAN PCs) CAN access it.
> > Please correct
> > me if I'm wrong.
>
> Yeah, when you talk about Internet, RFC1918 ip addresses becomes
> non-routable.
> But still, if you use it for your own WAN, it falls under routed
protocols.
> Examples of routed protocols are tcp/ip, ipx/spx and an example of
> non-routed protocol is netbeui.
> Examples of routing protocols are rip, bgp, igp, egp, igrp, ospf and so
on.
both of you are still confuse :-> tcp/ip is a routable protocol. 10.x.x.x,
172.16.x.x and 192.168.x.x are *private* ip addresses. you can build your
own private wan using these *private ip addresses*. read carefully what rfc
1918 said why these ip addresses *cannot* be use in public wan.
fooler.
-
Philippine Linux Users Group. Web site and archives at http://plug.linux.org.ph
To leave: send "unsubscribe" in the body to [EMAIL PROTECTED]
