I recently got all three above working, with print and mail spooling also
working.
Here's the order that I did all of this:
1. Set up bind on the gateway machine so that it was the DNS authority for the
192.168.1-255/24 subnet and my own little domain name (non-registered) sitting
on these addresses. Also, all other DNS requests were forwarded to my ISP's DNS
machines and cached.
2. Got the pppconfig package working, so that I could use pon/poff on the
gateway machine.
3. Got the ipf stuff working. Here's the details:
A. When I installed debian, I made sure it loaded all the ipfXX modules.
B. From the IP-Masquarade-HOWTO, changed the built /etc/rc.boot/ipmasq
to (basically, it is the easy way to route 192.168.1.1-255):
/sbin/ipfwadm -F -f
/sbin/ipfwadm -F -p deny
/sbin/ipfwadm -F -a m -S 192.168.1.0/24 -D 0.0.0.0/0
C. At this point, it is also a good idea to make sure that from a client
machine other than the gateway, you can telnet to the gateway, login as
as a user, 'su' to root, do pppconfig's 'pon', and then once the
internet connection is up, run netscape successfully from the client
machine.
4. Got diald to work. This I needed a little help from the debian-users,
because I wanted to use the connection script built from pppconfig. It turns
out this was fixed by changing the connect and disconnect properties in
/etc/diald/diald.options to:
connect "chat -v -f /etc/chatscripts/provider"
disconnect "/usr/bin/poff"
I then also modified /etc/diald/standard.filter by commenting out
the 'accept' parts, and modifying the global entries:
accept tcp 900 any
accept udp 900 any
accept any 900 any
I believe the above pretty much globally tells diald to keep a connection up 15
minutes one it starts up. The 'accept's that I commented out put a much smaller
keep-alive timelimit on certain ip packets, I personally think is silly !
5. Once 4 is working, then on to samba. This is tricky because Samba is so
configurable. The best I can say is pour over the documentation on Samba and
email to debian-users to get this set up the exact way you would like.
The biggest "trick" part to samba I have found is knowing how to have
inetd/xinetd correctly set up. If samba is not working as a standalone daemon,
then it is getting started up through the ip listening of inetd/xinetd.
On 23-Aug-98 debian-user list wrote:
> Hello. I'm trying to set up a debian 2.0 box as a server in a small
> office, using samba to serve files to a few win95 boxes, and ipmasq and
> diald to connect to the rest of the world via modem, intermittantly. I
> can get each of the parts to work individually without trouble, but
> various things go wrong when I put them all together. It seems like
> every fix I try creates a new problem-- getting diald to work raised the
> problem of SMB paackets being forwarded to the modem. I fixed that only
> to find that a tcp request from a win95 box would cause diald to bring up
> the link, but the connect would time out (but a request with the link
> already up would work fine). I worked on that for a while only to find
> that my samba server isn't showing up in the win95 browse lists. You get
> the picture. Obviously, my knowledge of networking is not deep enough to
> untangle this mess. I've spent about a week searching through dejanews,
> faqs, and web sites, and I don't feel any closer to an answer. I've
> upgraded diald and ipmasq using packages from slink, but so far no luck.
>
> I know there's at least one user out there who has a working config,
> right? If you do, could you please get in touch with me? I don't want to
> tell my client that he has to buy a modem for each win95 machine-- this is
> a project with an almost nonexistant budget (all of the machines are
> 486 class boxes).
>
> I will put together a mini-howto if I ever get this working.
>
> please respond to the address below-- I have a separate account subbed to
> the list, and I'm likely to miss a reply sent there.
>
> Discouraged in Seattle,
> --Ed Slocomb,
> [EMAIL PROTECTED]
>
>
> --
> Unsubscribe? mail -s unsubscribe [EMAIL PROTECTED] <
> /dev/null
----------------------------------
E-Mail: Geoffrey L. Brimhall <[EMAIL PROTECTED]>
Date: 27-Aug-98
Time: 11:24:16
This message was sent by XFMail
----------------------------------
