Text 2081, 56 rader
Skriven 2005-01-20 17:39:28 av Russell Tiedt (5:7105/1)
   Kommentar till text 2067 av mark lewis (1:3634/12)
Ärende: Router/Firewall Advice
==============================
Hello mark.

19 Jan 05 23:30, you wrote to me:

 ml> [coyote firewall]

 ml>> it seems to work ok and i (finally) figured out and located
 ml>> the chat.tgz file i needed to be able to set it up for POTS
 ml>> linkage... now i just need to figure out if/how i can set it
 ml>> up to keep those machines that are going to be using it in the
 ml>> same 192.168.2 (sub?)net so that they will still be accessible
 ml>> and continue to operate in the netbios/samba environment we
 ml>> use inhouse without blowing everything up...

 ml> i finally decided to set it smack in the middle of the 192.168.2 range
 ml> (.126) and leave everything else set as they were except for the
 ml> gateway which i manually set to .126... the only other thing needed to
 ml> be done was to put in a script to default 192.168.1 thru 192.168.2.1
 ml> which is another (the main, actually) "router"... now all the machines
 ml> can still get to the resource mappings they had before and they all go
 ml> out thru the modem on that router machine at .126... i let .126 handle
 ml> 80 (IIRC) dhcp addresses which is more than needed but they all get
 ml> the proper gateway, dns and such info as desired...

Nice ...

 ml>> we don't use dhcp much at all and that mainly because we map
 ml>> resources to the machine names (ie: \\beehive\hp99cse) but i
 ml>> have considered setting up dhcp /if/ i can find a way to get
 ml>> the coyote box to update hosts or internal dns with the
 ml>> dynamic ip for each machine name... i know that many providers
 ml>> update their dns (forward and reverse) with this info when a
 ml>> machine connects and gets its dynamic ip... the big question
 ml>> is if a package exists that i can do this with and if it is
 ml>> small enough to fit on the coyote boot floppy...

 ml> i'd still like to do this so i can eliminate the HOSTS files on each
 ml> box... coyote sets up a caching dns but i've not dug that far into
 ml> it... if i were to do the above, that coyote box would be the main dns
 ml> for all the machines on the internal LAN... then again, i've been
 ml> playing with JdeBP's DNS servers for OS/2 and could toss them in and
 ml> make that the default DNS with the outside one(s) at ncren as the
 ml> "secondaries" for the outside stuff...

Maybe I should nab a copy of coyote, to play with, on the other hand, not 
having a great deal of time to play "silly buggers", maybe I should leave it 
alone ... :-)

 ml> so many decisions! O;)

The problem with Linux, the choices are unlimited ... <BG>

Russell

--- GoldED+/LNX 1.1.4.7
 * Origin: Rusty's BBS - Bloemfontein, Free State, South Africa (5:7105/1)