🚀 go-pugleaf

In article <914162305.19967.0.nnrp-03.c2dea8e2@news.demon.co.uk>,
	"Andrew Taylor" <news@hot-shot.demon.co.uk> writes:
> 
> Linux Box running 24/7 on the floor without a monitor. Set up an internet
> connection which can be called from NT. All mail to be downloaded to the
> Linux box, andrew@hot-shot.demon.co.uk to be delivered to Outlook 98,
> linux@hot-shot.demon.co.uk to be delivered to an account on the linux box.
> Also I would like to maybe store all my documents, downloads etc on the
> linux box with a network drive mapped under NT.
> 
> I have a little bit of Linux knowledge. Is this task way above me ?
> 

I found out it was a good way to learn a fair bit. Try using pop3 access
to the linux box to get mail, and samba for it to act as a file server for
NT.

Personally I read all of my mail on my linux box, because it is quicker
than booting the other machine to read it, but then I have a monitor on it.

-- 
Peter Chant
pete@neither.demon.co.uk

In article <914162305.19967.0.nnrp-03.c2dea8e2@news.demon.co.uk>,
          news@hot-shot.demon.co.uk ("Andrew Taylor") wrote:

>
> What I want to do is this :
>
> Linux Box running 24/7 on the floor without a monitor. Set up an internet
> connection which can be called from NT. All mail to be downloaded to the
> Linux box, andrew@hot-shot.demon.co.uk to be delivered to Outlook 98,
> linux@hot-shot.demon.co.uk to be delivered to an account on the linux box.
> Also I would like to maybe store all my documents, downloads etc on the
> linux box with a network drive mapped under NT.
>
> I have a little bit of Linux knowledge. Is this task way above me ?
>
> Best Regards
> Andrew Taylor
>
> PS Anyone near Newcastle fancy giving me a hand ? I'll pay transport.
>
I'm running a very similar set-up - my wife's mail is delivered to her Win 95 PC,
she can see all the disks on the Linux box via Samba. My mail is actually delivered
to an Acorn box via SMTP. Unfortunately St Albans is a long way from Newcastle :-(

Feel free to e-mail me with specific questions; although not over Christmas as I'm away.



-- 
Steve Dicks - Starswan Systems Ltd
Hertfordshire's premier one-man Systems Consultancy

Peter Chant wrote:
> 
> In article <914162305.19967.0.nnrp-03.c2dea8e2@news.demon.co.uk>,
>         "Andrew Taylor" <news@hot-shot.demon.co.uk> writes:
> >
> > Linux Box running 24/7 on the floor without a monitor. Set up an internet
> > connection which can be called from NT. All mail to be downloaded to the
> > Linux box, andrew@hot-shot.demon.co.uk to be delivered to Outlook 98,
> > linux@hot-shot.demon.co.uk to be delivered to an account on the linux box.
> > Also I would like to maybe store all my documents, downloads etc on the
> > linux box with a network drive mapped under NT.
> >
> > I have a little bit of Linux knowledge. Is this task way above me ?
> >
> 
> I found out it was a good way to learn a fair bit. Try using pop3 access
> to the linux box to get mail, and samba for it to act as a file server for
> NT.

You should use IMAP4 for this, and leave everything on the server. That
way, you can read and handle mail from any other box, including a remote
one and the linux box itself. If you're brave, try using LDAP! Netscape
4.5 is a good client for this, but there are lots of others.

Cheers, Laurie.

In article <367FBEDC.B7D97035@brownowl.com>,
	Laurie Brown <laurie@brownowl.com> writes:
> 
> You should use IMAP4 for this, and leave everything on the server. That
> way, you can read and handle mail from any other box, including a remote
> one and the linux box itself. If you're brave, try using LDAP! Netscape
> 4.5 is a good client for this, but there are lots of others.
> 

I must have another go at IMAP, but I could not get it sorted out with
the shadow passwords in Slackware.

-- 
Peter Chant
pete@neither.demon.co.uk

I have a similar-ish setup here, I have a linux box (a P133 with monitor
though) which has the modem on connected to it and an NE2000 ethernet card
in it, and then I have an old Compaq Prosignia 486DX2/66 which runs Win95.

I use Samba for the file sharing, I have actually set up Win95 to
physically log into the linux box, as if it were a NT server (running a
logon script), I use Redhat 5.1 as well, if you look in /usr/doc/samba...
there is loads of documentation for you to look through, it would probably
be an idea to read the HOWTO as well.  As you are using NT4, you'll either
have to get Samba to use Encrypted passwords, or you'll have to do a
registry hack on the NT box to use unencrypted passwords.

On the mail side, all mail goes to the linux box, so I can read it there if
I want to, or I can use Outlook Express, Pegasus or Eudora on the Win95 box
to grab my mail using POP3 (this is easy, and requires no configuration).

For newsgroups, I use leafnode on the linux box (www.troll.no) to grab all
the newsgroups I read regularly, and then I use the Win95 box (using
OutlookExpress) to read/post news (thats what I'm doing now).

For internet surfing from Win95, I use Internet Explorer 4, but you must
set up IP Masquerading for this to work properly - see the IP-Masq-HOWTO
for details on how this works. To bring to gateway up and down, I use 'rsh'
(which is included with NT).

Hope this helps, please feel free to mail me if you need any other help.
Merry Christmas


Steven Freegard
stevenf@alpha-centori.demon.co.uk

In article <914162305.19967.0.nnrp-03.c2dea8e2@news.demon.co.uk>,
	"Andrew Taylor" <news@hot-shot.demon.co.uk> writes:
>Hi,
>
>I'm running RH5.1 as a dual boot with NT4 wkstation. I've just been rakin
>
>

Hi

I've got something like this. I never found I needed the file server bit as
I had bigger disks on the pc so I never got round to running samba but I
run a Win Xserver on the pc when I want to play linux.

Dave

-- 
D. J. Ford
15 Crawford Road                         E-mail:  dford@ansur.demon.co.uk
Hatfield, Herts                          Phone:   +44 (0)1 707 886 095
AL10 0PF, U.K.                           Fax:     +44 (0)1 707 261 836

<Double quoted, as I don't have the original :)>

>> Linux Box running 24/7 on the floor without a monitor. Set up an internet
>> connection which can be called from NT. All mail to be downloaded to the
>> Linux box, andrew@hot-shot.demon.co.uk to be delivered to Outlook 98,
>> linux@hot-shot.demon.co.uk to be delivered to an account on the linux box.
>> Also I would like to maybe store all my documents, downloads etc on the
>> linux box with a network drive mapped under NT.
>>
>> I have a little bit of Linux knowledge. Is this task way above me ?

Nah... Just a matter of setting up the different bits one by one. I have
to confess, I've not actually set up such a system, but, having had
Linux for a few years now, I'm begining to get into the stage of
answering questions, not just asking them :)

Right, what you'd need is the following:

1)A Linux box set up and able to somehow connect to the internet (I can
help with this, if needed)

2)A working network between the Linux box and the NT box.

3)Suitable routing rules on the Linux to send Internet packets to the
Internet, and NT packets to the NT machine

4)on the Linux box, one of:
  (i) fetchmail, which is a program to get stuff from a pop3 mailbox
(Like an ISP), and deliver it locally
  (ii) smtp set up to accept all incoming mail, not just to previously
defined users

5)a 'andrew' user needs to exist on the Linux box

6)Outlook should be configured to use the Linux box as a POP3 server,
with the username 'andrew' and the relevant password

7)Firewalls set up on the Linux box to stop anyone else attempting to
break in.

8)Assuming you want the NT machine to be able to access the Internet,
you'd need diald (There would be other ways; this (might) be easiest.
You'd also need one of the following: Masquerading [Easy to set up,
works with any OS, but not all protocols], squid of other proxy server
[would only work with http, and maybe ftp]
<diald only needed if non-permanant net connection>

9)Samba installed and running, enabling you to use linux-exported drived
under NT (And printers, if you wanted)



I have written reasonably quick notes on each of these, posted in this
thread, but seperate articles (to avoid bunging up this one).



None of these are above your head, you just have to go slowly :)
If you need (Although I live in Portsmouth, so email comms would be the
way to do it), I can help with items 1,2,3,4(ish),5,6(ish),7(ish),9

Although I'm not an expert on all of these (if any...), I could probably
help you get through a setup :)

My school email, which I'll be reading more often now it's term-time
again, is pstoneman@yahoo.com.


HTH,
Phil.

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

    "He who laughs last thinks slowest!"

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?"

Ascender  <ascender@NOSPAM!.deathsdoor.com> wrote:
>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.

Debian - good as it is - is not really trying to be novice-friendly.

>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.

Don't run sendmail. Use exim or something.

-- 
David/Kirsty Damerell, damerell@chiark.greenend.org.uk.  All Hail Discordia!
|   | And then they came and took me out, The men of doom and malice:  |   |
|---|Destroyed my life, removed my sense, Gave me the poisoned chalice.|---|
| | | My betrayal's life to me...                Elder Sign: Treachery | | |

David Damerell wrote:

> >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.
> 
> Don't run sendmail. Use exim or something.

Sendmail is an absolute pig if you try to edit sendmail.cf. So don't -
use the M4 macros. Then it becomes really easy. On Red Hat 5.1 install
sendmail-cf-8.8.7-17 and the macros are in /usr/lib/sendmail-cf/cf.
Other distributions would I hope be similar. To accept mail for invalid
usernames the line is:

define(`LUSER_RELAY', `local:postmaster')dnl

This sends such mail to "postmaster", which is defined in /etc/aliases
as an alias to the user which should receive the mail.

Hope this helps, Ian

Wahey, I'm there! It's taken me a week but I'm there. I haven't got my new
machine yet but I was so sure that I'd set my linux partition up right on my
machine I stole a customers machine and added a network card etc. I've got
everything working apart from samba (didn't have time) and news (this needs
some thinking about).

Thanks for everyone's help, it proves that if you are prepared to read a lot
of how-tos and ask a lot of stupid questions you can get there in the end.

I'm going to write a website detailing my accounts in case any would be
linux users have the same idea as me.

Andy

PS One other thing! Sendmail, I've upgraded the rpms and it's working fine
except "masquerade as", I've followed the how-tos and man pages etc, it
looks right, I've m4'd it and ran newaliases but it's still putting out
localhost.localdomain instead of hot-shot.demon.co.uk. Is there something
I'm missing ?
Ian Northeast wrote in message
<3693BB68.A03DD7E@house-from-hell.demon.co.uk>...
>David Damerell wrote:
>
>> >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.
>>
>> Don't run sendmail. Use exim or something.
>
>Sendmail is an absolute pig if you try to edit sendmail.cf. So don't -
>use the M4 macros. Then it becomes really easy. On Red Hat 5.1 install
>sendmail-cf-8.8.7-17 and the macros are in /usr/lib/sendmail-cf/cf.
>Other distributions would I hope be similar. To accept mail for invalid
>usernames the line is:
>
>define(`LUSER_RELAY', `local:postmaster')dnl
>
>This sends such mail to "postmaster", which is defined in /etc/aliases
>as an alias to the user which should receive the mail.
>
>Hope this helps, Ian

On Tue, 5 Jan 1999 19:46:52 +0000, Ascender
<ascender@nospam.deathsdoor.com> wrote:

>(The IP should be in the range 10.x.x.x or 168.192.x.x, are good ones).
                                            ^^^^^^^
Oops! 192.168.x.x
-- 
Roger

"Andrew Taylor" <news@hot-shot.demon.co.uk> writes:

> PS One other thing! Sendmail, I've upgraded the rpms and it's working fine
> except "masquerade as", I've followed the how-tos and man pages etc, it
> looks right, I've m4'd it and ran newaliases but it's still putting out
> localhost.localdomain instead of hot-shot.demon.co.uk. Is there something
> I'm missing ?


If there is a line like 
#Dj
in the sendmail.cf file, change it to 
Djhot-shot.demon.co.uk

-- 
ACTUALLY reachable as @free-lunch.demon.(whitehouse)co.uk:james+usenet

On 06 Jan 1999 11:57:02 +0000 (GMT), David Damerell 
<damerell@chiark.greenend.org.uk> wrote:

>Ascender  <ascender@NOSPAM!.deathsdoor.com> wrote:
>>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.
>
>Debian - good as it is - is not really trying to be novice-friendly.

I will add that SuSE, while novice-friendly, is very non-standard in
some respects. (For example, the init scripts present in /etc/rc.d
simply don't get run; they're run from a separate tree in /usr/etc/rc.d, 
or somewhere similarly bizarre.)

Not sure I'd recommend Red Hat to a beginner right now. 4.2 was
rock-solid; 5.2 is fairly good, but has a few quirks (like egcs as a C++
compiler but old Gcc 2.7.2 as a C compiler). And I _don't_ like the
default desktop environment. Maybe Red Hat 6 will be better?

I have a copy of Caldera Open Linux 1.3 waiting to install on a test
machine. KDE as default desktop, StarOffice 4.0 as standard ... if it
lives up to expectation, _this_ is the ideal novice-friendly system. I'll
report back when I've done some testing (including getting my pet novice
to install it for me :).



-- Charlie