Hi all! Raise your hand if you have cable modem, use DHCP cuz yer provider hands out dynamic addresses, and have 2 or more machines on a private net (eg, 192.168.0.0/16) talking through a masqerading box (that speaks DHCP to your provider to get its "to the rest of the world" address), hence sharing the cable. Now... of those that have your hand(s) raised, does it work well? Problems? Hurdles? Comments appreciated. :) PS -- I'd be using a SuSE 6.2 box for the masquerading/DHCP stuff, kernel 2.2.15. Regards, kw /* Keith Warno ** Developer & Sys Admin ** http://www.HaggleWare.com/ */ -- To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com For additional commands send e-mail to suse-linux-e-help@suse.com Also check the FAQ at http://www.suse.com/Support/Doku/FAQ/
Works very well and is quite easy to do with 6.2. Either update the
included dhcpclient package with a (very) current one, or replace it
entirely with the current version of dhcpcd. You'll need the correct
module versions for your kernel; then install the firewall package
and ipchains; use YAST to configure the eth0 and eth1 interfaces;
then set ipforward to yes and edit the masquerading section in
rc.config (made into a separate rc.firewall starting with 6.3) and
away you go. (Unless your provider does high-port blocking...)
Suse evidently uses a 192.168.x.x dummy address to initialize the
cable modem's NIC pending DHCP address assignment. Your
provider's DHCP server may like this fine or it may be expecting
the obsolete 0.0.0.0, in which latter case it is possible you might not
get DHCP address assignment until you edit a fixed but invalid IP
into rc.config (e.g. 0.0.0.0) and then run your dhcp client manually
after boot. YMMV
In any event, like anything else Linux-related you have to fiddle
considerably with your masquerading firewall to get it set up right,
and then it just runs and runs and runs and runs...
Read a good Linux security book, though, to remind you to disable
all the stray and mostly useless daemons and whatnot that seem to
get installed and activated by default and also to remind you to take
the other measures appropriate for helping to keep Bad Guys out
of your firewall.
Cheers,
--Kevin
From: "Keith Warno"
Hi all!
Raise your hand if you have cable modem, use DHCP cuz yer provider hands out dynamic addresses, and have 2 or more machines on a private net (eg, 192.168.0.0/16) talking through a masqerading box (that speaks DHCP to your provider to get its "to the rest of the world" address), hence sharing the cable.
Now... of those that have your hand(s) raised, does it work well? Problems? Hurdles? Comments appreciated. :)
PS -- I'd be using a SuSE 6.2 box for the masquerading/DHCP stuff, kernel 2.2.15.
Regards, kw /* Keith Warno ** Developer & Sys Admin ** http://www.HaggleWare.com/ */
-- To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com For additional commands send e-mail to suse-linux-e-help@suse.com Also check the FAQ at http://www.suse.com/Support/Doku/FAQ/
-- To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com For additional commands send e-mail to suse-linux-e-help@suse.com Also check the FAQ at http://www.suse.com/Support/Doku/FAQ/
I have adsl that uses dhcp connecting my lan. Works fine for me. My gateway machine has two nics - one gets it ip via dhcp from the isp, the other is an invalid ip for the lan. Setup masqing and firewalling rules and a cacheing dns server and point the other machines to look to the masqing machine as their gateway and everything works great. On Fri, 02 Jun 2000, Keith Warno wrote:
Hi all!
Raise your hand if you have cable modem, use DHCP cuz yer provider hands out dynamic addresses, and have 2 or more machines on a private net (eg, 192.168.0.0/16) talking through a masqerading box (that speaks DHCP to your provider to get its "to the rest of the world" address), hence sharing the cable.
Now... of those that have your hand(s) raised, does it work well? Problems? Hurdles? Comments appreciated. :)
PS -- I'd be using a SuSE 6.2 box for the masquerading/DHCP stuff, kernel 2.2.15.
Regards, kw /* Keith Warno ** Developer & Sys Admin ** http://www.HaggleWare.com/ */
-- To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com For additional commands send e-mail to suse-linux-e-help@suse.com Also check the FAQ at http://www.suse.com/Support/Doku/FAQ/
-- Chad Whitten cwhitten@intop.net http://whitten.dhs.org -- To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com For additional commands send e-mail to suse-linux-e-help@suse.com Also check the FAQ at http://www.suse.com/Support/Doku/FAQ/
<raises hand> I am doing exactly that, and I have another friend who is doing the same thing. I'm using SuSE 6.4 on my system. It works reasonably well so far (I set it up last weekend); the only thing to really note is that it's a bad idea to use the same Ethernet card for the different networks. It would tick off the cable company and all. :) If you are RedHat literate, there is a mini-HOWTO that will get you up and running quickly. It is in the howto.rpm package under /usr/doc/howto/en/mini/. There's also copious documentation elsewhere. I'm planning to get internal nameservice set up this weekend. -tara On Fri, Jun 02, 2000 at 02:16:25PM -0400, Keith Warno wrote:
Hi all!
Raise your hand if you have cable modem, use DHCP cuz yer provider hands out dynamic addresses, and have 2 or more machines on a private net (eg, 192.168.0.0/16) talking through a masqerading box (that speaks DHCP to your provider to get its "to the rest of the world" address), hence sharing the cable.
Now... of those that have your hand(s) raised, does it work well? Problems? Hurdles? Comments appreciated. :)
PS -- I'd be using a SuSE 6.2 box for the masquerading/DHCP stuff, kernel 2.2.15.
Regards, kw /* Keith Warno ** Developer & Sys Admin ** http://www.HaggleWare.com/ */
-- To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com For additional commands send e-mail to suse-linux-e-help@suse.com Also check the FAQ at http://www.suse.com/Support/Doku/FAQ/
-- To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com For additional commands send e-mail to suse-linux-e-help@suse.com Also check the FAQ at http://www.suse.com/Support/Doku/FAQ/
participants (4)
-
cwhitten＠intop.net -
keith＠HaggleWare.com -
klcroxen＠fas.harvard.edu -
tla＠akamai.com