[CVALE] My next big step with Linux...

[Jason Roysdon]

NAT - Network Address Translation, but let's start with why you need it:

I didn't give you all the details: The linksys will act as a DHCP server
( http://en.wikipedia.org/wiki/Dhcp ) and assign, by default, a private
address (RFC1918 http://www.faqs.org/rfcs/rfc1918.html ) in the
192.168.1.X range.  These addresses don't work on the internet, so you
need to have them NAT'd.

NAT (RFC1631 http://www.faqs.org/rfcs/rfc1631.html ) takes an IP Address
and Translates it into another address.  A one-to-one NAT would take a
single IP address and NAT every single port to the exact port of the
NAT'd IP.  Most cheap routers don't support this, but then you usually
only have one public IP address for SOHO users.

So that's the next point: since you only have one public (internet
routable) IP address, but more than one PC, you need NAT.  PNAT, PAT or
NAT overload as some routers call it, will allow you to take one public
IP address and allow many private IPs to do Port (Network) Address
Translation and share that same public IP address as far as the outside
world sees your traffic origination (for the most part).

PPPoE (RFC2516 http://www.faqs.org/rfcs/rfc2516.html ) is what most DSL
providers (and some cable) require you to use so they can get
authentication information before they allow you on their network.
Usually you run it as some extra software on your PC.  With all modern
routers, you can have the router do the PPPoE authentication and not run
any software on your PC.

As I was saying, you could have a home PC do DHCP, NAT, PPPoE, but it's
rather hard to get each going, and these days with home routers to
cheap, more hassle than it's worth.
-- 
Jason Roysdon
http://jason.roysdon.net/


Landon Blake wrote:
> I just want to let everyone know that this LUG is what makes Linux
> possible for me. Thanks so much!
>
> I had some questions for Jason.
>
> Jason wrote: " You definitely can do all that.  I would suggest starting
> small..."
>
> This is excellent advice that I will follow.
>
> Jason wrote: " Use a Linksys or the like router to share your internet."
>
> That seems to be the common consensus. I will go this route for now.
>
> Jason wrote: " While you
> could have two network cards in your Linux machine and share it with
> that, every time you reboot your wife is going to get upset with you.
> Make life easier."
>
> Yup. I don't want to be eating a bunch of cold leftovers. This is a good
> advice. :]
>
> Jason wrote: "The Linksys will do the NAT and PPPOE auth for you."
>
> What is NAT and PPPOE?
>
> Jason wrote: "SAMBA/filesharing can be tough, but you can do it.  I'd
> start by making
> a share on the Windows side and connecting to it.  Remember you need to
> give share and filesystem permissions."
>
> Someone posted about setting up an FTP on the Windows box to do the
> filesharing. Is this what you are talking about?
>
> I will try to do that, and will read up on Samba in the meantime. There
> were some links posted for Samba documentation, and this should be a
> good place to start.
>
> Landon
>
>
>
> -----Original Message-----
> From: cvale-bounces at lists.fire2wire.com
> [mailto:cvale-bounces at lists.fire2wire.com] On Behalf Of Jason Roysdon
> Sent: Friday, May 04, 2007 11:22 AM
> To: cvale at cvale.org
> Subject: Re: [CVALE] My next big step with Linux...
>
> Landon,
>    You definitely can do all that.  I would suggest starting small:
>
> Use a Linksys or the like router to share your internet.  While you
> could have two network cards in your Linux machine and share it with
> that, every time you reboot your wife is going to get upset with you.
> Make life easier.
>
> The Linksys will do the NAT and PPPOE auth for you.
>
> SAMBA/filesharing can be tough, but you can do it.  I'd start by making
> a share on the Windows side and connecting to it.  Remember you need to
> give share and filesystem permissions.