🚀 go-pugleaf

Point 1 - Getting a working Linux system
-------
Personally, I use Slackware, so I'll advise on that. Redhat, Debian, or
similar, shouldn't be too different, just read the docs on the CD.
Bear in mind, though, that Redhat or Debian are better for complete
newcomers.

You need to set partitions up first. Get one for Linux, one for swap,
and one for DOS/Windows (If needed). If Dos is already installed, you
can just nuke it, or use FIPS to resize the partition.

Go into the rootdsks directory on the CD, and use the which.one file,
along with the DOS util rawrite, or the *nix util dd, to write a
rootdisk image to a disk.
Do the same (different disk) with the bootdsks.144 directory.

Put the bootdisk in, reboot the linux box, and follow instructions.
You'll probably just need the disk sets a and n. Possibly ap might be
useful, as well.

After various steps, you (should) end up with a bootable Linux system.

Get ezppp, or some other ppp setup script from somewhere. Run it, and
follow instructions. Test that you can connect to the ISP.



Part 2 - Setting up that network
------
You'll need the kernel with support for your network card. Either
modprobe the relevant module (ne for a NE2000 card, which most are), or
compile it into the kernel.

When Slackware installed, it should have asked you about your network.
When it does, you need to put in an IP and domainname made up by you
(The IP should be in the range 10.x.x.x or 168.192.x.x, are good ones).
It'll put a 'default' route in /etc/rc.d/rc.inet1.
Remove the default route from there, and put in a network only route.
Set up the TCP/IP on the NT machine to use the Linux machine as the
gateway, and set up a suitable IP.

the NT machine should be able to telnet to the Linux box.

This is by no means complete - mail me if you need help.

You might want to set up a DNS mini-server, as well, (which you can set
as the NT's DNS server), which, as well as identifing the machines on
your network, would pass real DNS enquiries to the internet.


Part 3 - Routeing
------
Really covered in the last one. Basically,

route add 192.168.0.0/24 dev eth0

should set it up just about right.


Part 4 - Fetchmail or sendmail
------
Sendmail is an absolute pig to set up. The default set-up should be
nearly right (not forgetting to fiddle with /etc/aliases), but you'd
have to ask in a NG abuot how to accept mail for invalid usernames.

Fetchmail isn't too hard at all, except I forget the syntax of the
config file :) Study the examples that come with fetchmail. It is
designed to get all mail from a POP3 server, and deliver it to the local
SMTP daemon (in this case, sendmail)


Part 5 - user 'andrew'
------
type 'adduser' as root.


Part 6 - Outlook
------
I think it's in Tools... Accounts that you fiddle with POP3 accounts.
The Linux machine can be your pop3 server, with the username and
password as you created in Part 5.


Part 7 - Firewalling (Eeek!)
------
(i)Compile the kernel with firewall support. Ideally,
CONFIG_IP_FIREWALL_VERBOSE should be on, as well.
(ii)Run various commands like

ipfwadm -I -a accept -S 168.192.0.0/24
ipfwadm -I -a deny -S 0.0.0.0/0

THIS NEEDS TO BE MORE DETAILED!!!!!! Read a firewall FAQ, or ask the
gurus here who know much more than humble moi :), for an ideal firewall
setup.


Part 8 - Diald, Masq'ing and proxying
------
Diald - Never touched it (Not by choice, I've just never needed it)
Designed to detect an attempted connection to the 'net, and activate the
modem when needed, then timeout after a time.
You'd need to be careful with DNS lookups, though. I've heard of named
triggering diald every so often.
I spose you could also do this by a batch file on the NT machine which
attempts to connect to a certain port on the Linux one, and when inetd
in the linux one detects an incoming connection on the port, starts up a
dialer script. Same, but different port for disconnect.

Masquerading - This is what I have plans for for my home network (When I
get enough computers to /have/ a home network...)
Basically, the NT machine sends the Linux machine a packet addressed for
the Internet. The Linux machine fiddles with the packet, so that when
the packet is sent over the Internet, it appears to be from the Linux
machine (This is needed because the NT machine doesn't have an allocated
IP address, and doesn't exist as such, directly on the Internet).
When it gets a reply to that packet, the Linux machine recognises it as
complimentary to the one sent out from the NT machine, and passes it
back to the NT machine. I believe that NAT (Network Address Translation)
on Cisco routers does a similar thing.
To set it up:
ipfwadm -I -a masq -S 168.192.0.0/24
(Also compile masquerading into the kernel, or compile and load the
relevant modules)

Proxying - Slightly different. Rather than setting the Linux machine up
as your gateway in the NT TCP/IP settings, Netscape (sheer), IE (Boo!
Hiss!), Opera (Whizz), or Gecko (Speedy child of Netscape) need to be
set to use the Linux machine as their proxy server.
This works by them making a connection to the Linux machine, saying
"Please retrieve this page for me". The proxy program on the Linux
machine then goes to that site, gets the data, and sends it back to the
NT machine. So, rather than the NT machine trying to talk to the remote
site, and the packets getting intercepted by the Linux machine, the NT
machine instead asks the Linux machine to go the site on the NT
machine's behalf.
I've never used squid, but this is the most comonly used proxy program
(Except for my college, who use Netscape proxy for Windows NT - Unstable
as hell, and costs about $500 - whereas Squid is free...)
Shouldn't be /too/ hard to setup. Read the docs :)


Part 9 - Samba
------
Ages since I've installed this. I can't remember the details, but could
probably find them if needed :)
Simply put, install it as per instructions, add an entry in /etc/rc.d
(or whereever) to run it at boottime, and edit the config file to export
the relevant directories.

Oh, yes - I do remember a problem with this. NT uses encrypted
passwords. You need to find and apply a patch to samba to support these
encrypted passwords that NT sends. It'll be in the docs.





There we go, those are most of the basic concepts. You may well need
help - I, or many other people hanging around in Usenet would be happy
to help, I'm sure :)

Phil.


-- 
    . o O ( Phil Stoneman ) O o .
       ascender@deathsdoor.com
  Sometimes on dominion.net.uk:2468

  "Why is "abbreviated" such a long word?"