hey, i'm really new to this, so i have no idea how to start. i'm running a 200mhz pentium machine with two ethernet cards. what i really want to do is run the cable modem through the first card and then out the other card to a hub. does that make any sense? i have at least 6 other machines i want to ipmasq into it. correct me if i'm wrong, can't i run the connection through the box and just use it as a gateway for the rest of them? any replies would be SO appreciated. tia ren -- 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/
Check out LRP at http://lrp.c0wz.com They have a single diskette distro that does just that. -----Original Message----- From: Katherine Chant [mailto:rengeko@kc.rr.com] Sent: Tuesday, May 09, 2000 9:09 PM To: suse-linux-e@suse.com Subject: [SLE] cable modem hey, i'm really new to this, so i have no idea how to start. i'm running a 200mhz pentium machine with two ethernet cards. what i really want to do is run the cable modem through the first card and then out the other card to a hub. does that make any sense? i have at least 6 other machines i want to ipmasq into it. correct me if i'm wrong, can't i run the connection through the box and just use it as a gateway for the rest of them? any replies would be SO appreciated. tia ren -- 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/
on 5/9/00 21:09, Katherine Chant at rengeko@kc.rr.com wrote:
hey, i'm really new to this, so i have no idea how to start.
i'm running a 200mhz pentium machine with two ethernet cards. what i really want to do is run the cable modem through the first card and then out the other card to a hub. does that make any sense? i have at least 6 other machines i want to ipmasq into it. correct me if i'm wrong, can't i run the connection through the box and just use it as a gateway for the rest of them? any replies would be SO appreciated.
tia ren
ok, i guess i didn't really explain. i can't even seem to get online right now-am i forgetting something? how do i configure ppp? like i said, newbie newbie newbie. i'm fairly experienced with mac, and slightly with windows. i think i will d/l that distro mentioned for using the machine as a router, but i still can't connect. mind you that i did have a g4 running yellow dog that we had connected before. so let's start with the connection. i can't risk the cable connection for everyone. (i have a husband who has hysterics if he can't connect to mplayer-which reminds me, how do i set it up so he can connect properly through the firewall?) thanks ren -- 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 this construction at home. The ipadress of the modem card must be a different adress from the rest of the network. The machine with two nic is the gateway between two networks. The card wich is connected to the hub must have a inside ipadress. The cable modem gets a outside ipadress. The inside card must redirect all different ip requests to the outside card(ipforwarding). You need a proxy server to manage all outside ip requests from the network to the modem card. The proxy server function acts as a network adress translator. Any NAT program will do this for you. Jaap -----Original Message----- From: Katherine Chant [mailto:rengeko@kc.rr.com] Sent: woensdag 10 mei 2000 6:45 To: Katherine Chant; suse-linux-e@suse.com Subject: Re: [SLE] cable modem -- 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/
Apologies for an over-lengthy post. I've put together just such setups on Suse machines connecting to the RoadRunner ISP (currently on MediaOne). WARNING! By hooking your Linux box up to the internet full-time in this manner, you become a 'real' UNIX systems administrator, with all the security headaches this entails. If you're a complete Linux newbie, you should carefully consider whether you want to do this at all, and certainly shouldn't do this until you've read up some on Linux security issues. Linux can be secure, but isn't secure by default. A very good (if ponderous) tome on Linux security is 'Maximum Linux Security' by 'Anonymous'. There are many others to be had at amazon.com or wherever. Read up now and possibly save yourself grief later! Also, Road Runner acknowledges, grudgingly, the existence of home LANs, but some other ISPs do not. Check carefully your service agreement. In any event you will be masquerading the output of the machines on your home network via the hub through the dual-ethernet carded Suse machine which in turn is connected to the Road Runner service (or other similar ISP). The machines on the home network (and the card on your gateway that connects to your internal network) will need locally assigned IP addresses. You may select from the following ranges (all from either one range or the other): 192.168.x.x, or 10.x.x.x The card connecting to the cable modem and through this to the ISP (I'll assume here Road Runner), will likely be receiving a dynamically assigned IP address through DHCP. Get the internal portion of your network talking to each other first, then worry about your gateway machine. Your gateway machine's Suse distro includes almost everything you need right out of the box. I say 'almost' because the DHCP client that comes with distros through 6.3, 'dhcpclient' does not work well, if at all, with the Road Runner service. You will need the improved client shipped with Suse 6.4, 'dhcpcd' which is also available at sunsite.unc.edu/pub/linux/system/network/daemons You will need to have loaded the correct hardware driver(s) for your cards. and have confirmed that the two cards are initializing properly after bootup by looking at the output of the command 'ifconfig'. Assign the card on the internal side of the suse machine an ip address from the range you're using for your network. Confirm that you can ping this address from other machines in the network; or even telnet in from the other machines (not as root, of course). See if the outbound card can obtain an address via DHCP from your service. Assuming eth0 is card connecting to the service, run 'dhcpcd eth0'. If it returns a prompt in a couple of seconds, it was likely successful. run 'ifconfig eth0' to see if the card now has an address in the range used by your ISP. If your ISP is Road Runner, there seems to be a moderate glitch here, as Suse default-assigns a dummy address to the outbound card of 192.168.x.x at bootup pending DHCP; Windows-centric Road Runner seems to expect 0.0.0.0, and frequently DHCP fails if the 192.168.x.x address is left in. 0.0.0.0 may not be assigned in Suse through YAST; you have to edit /etc/rc.config directly to input this value. You get an error message at boot, but at least DHCP seems to work. Once the 'left brain' and the 'right brain' of your gateway are working independently, you need to get the two halves talking to each other through ip forwarding and ip masq. This was fairly simple in Suse 6.2, but a real pain in the tookis in 6.3, where most of the firewalling was taken out of the file /etc/rc.config and put in a separate file. (On one machine in sheer frustration I installed and ipmasqued Suse 6.2, and then package-upgraded to 6.3, since in that way the masquing portion of /etc/rc.config and the masquerade were left alone, but I received the improved security of the 2.2.13 kernel. Hopefully 6.4 and beyond are easier to configure masquing.) ip masq itself is a topic much too long for this forum, but suffice to say that an updated how-to exists and may be consulted in the support/how-to's section of www.linux.org Depending on which version of Suse you're running, you'll end up having to do a bit of manual editing of /etc/rc.config and perhaps /etc/rc.firewall Make sure you have IP chains installed from the 'security' package in YAST and enable IP forwarding at bootup. If you are using the Road Runner service as your ISP, there is a web site dedicated to RR with various Linux distros (but mostly Red Hat, of course). This may be found at: www.vortech.net/rrlinux Good luck. --Kevin On Tue, 9 May 2000, Katherine Chant wrote:
hey, i'm really new to this, so i have no idea how to start.
i'm running a 200mhz pentium machine with two ethernet cards. what i really want to do is run the cable modem through the first card and then out the other card to a hub. does that make any sense? i have at least 6 other machines i want to ipmasq into it. correct me if i'm wrong, can't i run the connection through the box and just use it as a gateway for the rest of them? any replies would be SO appreciated.
tia ren
-- 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/
On Wed, 10 May 2000 klcroxen@fas.harvard.edu wrote:
Apologies for an over-lengthy post.
Don't apologize! It's a vey good article and greatly improves the signal to noise ratio on this list :-) I just have one comment:
Your gateway machine's Suse distro includes almost everything you need right out of the box. I say 'almost' because the DHCP client that comes with distros through 6.3, 'dhcpclient' does not work well, if at all, with the Road Runner service. You will need the improved client shipped with Suse 6.4, 'dhcpcd' which is also available at sunsite.unc.edu/pub/linux/system/network/daemons
I also had problems with dhclient using it with the DHCP server of the University of Massachusetts and Adelphia Cable. As it turns out SuSE ships an old version of dhclient. When I downloaded and installed a current version 2 from http://www.isc.org/products/DHCP/ all problems vanished. I reccomend that SuSE updates their rpm! Kai PS: dhcpcd works, too! -- 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/
Yikes! Now *there* was a bolt from the blue... :) You know, it had never even occurred to me that the dhcpclient shipped with Suse 6.3 (all of, what, 5 months ago?) might just be seriously out-of-date, rather than simply defective in the given environment. Next time I have a couple of hours to kill, I'll give the currentmost version of dhcpclient a try and see whether I like it better than dhcpcd in conjuction with RoadRunner or not. Thanks for the tip! --Kevin From: mailinglists@bolay.de Date sent: Thu, 11 May 2000 15:09:33 -0400 (EDT) To: suse-linux-e@suse.com Copies to: feedback@suse.com Subject: [SLE] dhclient (was: [SLE] cable modem)
On Wed, 10 May 2000 klcroxen@fas.harvard.edu wrote:
Apologies for an over-lengthy post.
Don't apologize! It's a vey good article and greatly improves the signal to noise ratio on this list :-)
I just have one comment:
Your gateway machine's Suse distro includes almost everything you need right out of the box. I say 'almost' because the DHCP client that comes with distros through 6.3, 'dhcpclient' does not work well, if at all, with > the Road Runner service. You will need the improved client shipped with > Suse 6.4, 'dhcpcd' which is also available at > sunsite.unc.edu/pub/linux/system/network/daemons
I also had problems with dhclient using it with the DHCP server of the University of Massachusetts and Adelphia Cable.
As it turns out SuSE ships an old version of dhclient. When I downloaded and installed a current version 2 from http://www.isc.org/products/DHCP/ all problems vanished. I reccomend that SuSE updates their rpm!
Kai
PS: dhcpcd works, too!
-- 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/
Hi, I've just had a cable modem installed, I first tested the connection with a laptop and it worked very well ;-) As I currently use a proxy server running on an NT box, I have yet to figure out this on Linux, I obviously now moved the cable connection to a second NIC in my proxy server. At this point it failed to negotiate and IP address etc. after 7 hours of service, packs, trying different PCs and configurations it dawned on me that as it still only worked on the original Laptop that it may be the Cable Modem / DHCP server has registered the MAC address of the laptop and will not accept another NIC. I then hacked the PC to overide the Burnt-in MAC, this fixed the problem. Is the MAC address is stored in the Cable Modem, then it may be possible to fix the problem by power-cycling the modem, I haven't tried this!! Just thought you all may find this useful. Now to Linux and Proxies..... David -- 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/
On Sat, 13 May 2000, David Bottrill wrote:
it dawned on me that as it still only worked on the original Laptop that it may be the Cable Modem / DHCP server has registered the MAC address of the laptop and will not accept another NIC. I then hacked the PC to overide the Burnt-in MAC, this fixed the problem. Is the MAC address is stored in the Cable Modem, then it may be possible to fix the problem by power-cycling the modem, I haven't tried this!!
Just thought you all may find this useful.
Yup, I can confirm this, at least in my area, the cable modems that Comcast uses bind to the MAC address, and a simple power cycle on the cable modem gets over this. I also understand, but haven't had to resort to it, that they can reset the MAC address desired by the cable modem remotely. -- "Contrary to popular belief, penguins are not the salvation of modern technology. Neither do they throw parties for the urban proletariat." -- 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 (7)
-
david.bottrill＠ntlworld.com -
jpelgrom＠wanadoo.nl -
klcroxen＠fas.harvard.edu -
mailinglists＠bolay.de -
naurgrim＠karn.org -
noc＠kulish.com -
rengeko＠kc.rr.com