Re: Connecting to Comcast
> On Tue, 23 Sep 2003, "plussier" == [EMAIL PROTECTED] > wrote: plussier> The "PC/Activity" light is flashing an awful lot, but it plussier> seems to do this even when the interface is down (I'm plussier> assuming this is lowlevel link-layer traffic). I've also noticed that the Send and Receive lights are solid green. This doesn't seem right to me, as I'd expect them to flash with traffic. And, since I know there's no traffic, they shouldn't be flashing, or even on. Of course, I've never used this cable modem before, so maybe they are supposed to be solid all the time. -- Seeya, Paul -- Key fingerprint = 1660 FECC 5D21 D286 F853 E808 BB07 9239 53F1 28EE It may look like I'm just sitting here doing nothing, but I'm really actively waiting for all my problems to go away. If you're not having fun, you're not doing it right! ___ gnhlug-discuss mailing list [EMAIL PROTECTED] http://mail.gnhlug.org/mailman/listinfo/gnhlug-discuss
RE: Connecting to Comcast
You can connect to Comcast with Linux (or a Broadband router etc.), but I believe the initial connection requires a Windows PC in order to run the setup CD they supply you with. In my experiences, to activate your account, you need to provide your Comcast account number and some other number that should be highlighted on the service invoice that the installer should have given you a copy of. This information is put into the GUI that I believe contacts some internal Comcast server, allowing you to then connect to the internet. There is no MAC address registering like the old mediaone/attbi system, you are free to use any NIC once you have completed the initial registration. This could all be sidestepped I guess by calling Comcast and doing it manually over the phone with a technician. You will of course have to lie and say that your setup CD is not working, and then pretend to reboot your "windows" machine when they ask you to, etc. I have done it that way, but I find it is much easier to deal with them as infrequently as possible. Also update your kernel, and patch your system completely. You are entering an entirely new world of exposure by having a Linux box on the outside. If you are unfamiliar with Linux security, I recommend running the Bastille script (http://www.bastille-linux.org/) before connecting your machine to the internet. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of [EMAIL PROTECTED] Sent: Tuesday, September 23, 2003 12:13 AM To: [EMAIL PROTECTED] Subject: Connecting to Comcast Hi All, I've *finally* got a cable modem (after waiting about 7 years:) however, I can't seem to get Linux to connect. I've tried getting a dhcp address from the modem, but nothing happens. The "PC/Activity" light is flashing an awful lot, but it seems to do this even when the interface is down (I'm assuming this is lowlevel link-layer traffic). I've tried using pump to get an address, and watched daemon.log and an ethereal trace, and both show a bootp request going out, but nothing ever comes back. Does Comcast require you to register MAC addresses? I know MediaOne did, but the guy came today and just hooked up the cable modem and left. I just got basic installtion, so he didn't muck with the system at all in order to get a MAC address from it, nor did he mention to my wife that I'd have to do this. Anyone have any ideas? So far I've if[up|down]ed the interface (eth1, netgear), I've power-cycled the cable mode, etc. No firewall script yet, so that's not causing any problems. Kernel 2.4.19 (yeah, I need to upgrade) Debian sid Comcast Motorola Surfboard SB5100 Netgear NIC Any info would be great, thanks! -- Seeya, Paul -- Key fingerprint = 1660 FECC 5D21 D286 F853 E808 BB07 9239 53F1 28EE It may look like I'm just sitting here doing nothing, but I'm really actively waiting for all my problems to go away. If you're not having fun, you're not doing it right! ___ gnhlug-discuss mailing list [EMAIL PROTECTED] http://mail.gnhlug.org/mailman/listinfo/gnhlug-discuss ___ gnhlug-discuss mailing list [EMAIL PROTECTED] http://mail.gnhlug.org/mailman/listinfo/gnhlug-discuss
Re: Connecting to Comcast
On Tue, Sep 23, 2003 at 12:13:29AM -0400, [EMAIL PROTECTED] wrote: > Hi All, > I've *finally* got a cable modem (after waiting about 7 years:) > however, I can't seem to get Linux to connect. 축하합니다! Oh, er, I mean, congratulations! [snip] > I've tried using pump to get an address, and watched daemon.log and > an ethereal trace, and both show a bootp request going out, but > nothing ever comes back. Try using something other than pump, namely dhclient. Or dhcpcd. If you remember, at MCL we used to have some problems where some people could get IPs fine if they used pump, but not dhcpcd. Others had the opposite problem. I've run into this at home, too. > Does Comcast require you to register MAC addresses? Not anymore. > I know MediaOne did, but the guy came today and just hooked up the > cable modem and left. I just got basic installtion, so he didn't > muck with the system at all in order to get a MAC address from it, > nor did he mention to my wife that I'd have to do this. Presumably it was working under Windows? Or did you even try it? Did he give you a CD? You may need to install it. Or call tech support. I vaguely remember having to go through some sort of web-based set-up thing. But I thought that wasn't necessary any more either. > Netgear NIC If Matt B. says this is the problem, don't listen... ;-) On Tue, Sep 23, 2003 at 12:36:56AM -0400, [EMAIL PROTECTED] wrote: > I've also noticed that the Send and Receive lights are solid green. > This doesn't seem right to me, as I'd expect them to flash with > traffic. And, since I know there's no traffic, they shouldn't be > flashing, or even on. One day all of a sudden I noticed the same thing. AT&T/Comcast seems to have done something to reverse the sense of the modem lights. They appear to blink OFF when there is traffic. YMMV. On Tue, Sep 23, 2003 at 12:42:09AM -0400, Greg Bonnette wrote: > You can connect to Comcast with Linux (or a Broadband router etc.), but > I believe the initial connection requires a Windows PC in order to run > the setup CD they supply you with. I thought I remembered that this isn't necessary any longer, but I may be mistaken. > Also update your kernel, and patch your system completely. You are > entering an entirely new world of exposure by having a Linux box on the > outside. If you are unfamiliar with Linux security, I recommend running > the Bastille script (http://www.bastille-linux.org/) before connecting > your machine to the internet. Know anything about security, Paul? =8^) -- Derek D. Martin http://www.pizzashack.org/ GPG Key ID: 0xDFBEAD02 -=-=-=-=- This message is posted from an invalid address. Replying to it will result in undeliverable mail. Sorry for the inconvenience. Thank the spammers. pgp0.pgp Description: PGP signature
Re: Connecting to Comcast
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Tue, 23 Sep 2003 00:42:09 -0400 "Greg Bonnette" <[EMAIL PROTECTED]> wrote: > You can connect to Comcast with Linux (or a Broadband router etc.), > but I believe the initial connection requires a Windows PC in order to > run the setup CD they supply you with. No you do not need the Windows CD, but you do need to be provisioned. They have a web site that you can go to to provision yourself, but that is different for each area. First, try to see if you can access your cable modem at 192.168.100.1. Then try this address: https://sas.ne1.attbb.net/sas/pub/logon/mainauth.jsp?ORIGURL=/sa/prot/admin/euser/activate.jsp While Comcast no longer registers your PC's MAC address, they need to register the Cable Modem MAC address. A quick call to Comcast should take care of this. - -- Jerry Feldman <[EMAIL PROTECTED]> Boston Linux and Unix user group http://www.blu.org PGP key id:C5061EA9 PGP Key fingerprint:053C 73EC 3AC1 5C44 3E14 9245 FB00 3ED5 C506 1EA9 -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.2-rc1-SuSE (GNU/Linux) iD8DBQE/cC7o+wA+1cUGHqkRApp6AJ4/E4ka+q105YVl7TKq4GxAKtKZgACeIR9R XczCYBsIUphQeOC4yZYTLRI= =+0a1 -END PGP SIGNATURE- ___ gnhlug-discuss mailing list [EMAIL PROTECTED] http://mail.gnhlug.org/mailman/listinfo/gnhlug-discuss
Re: Connecting to Comcast
[EMAIL PROTECTED] wrote: I've *finally* got a cable modem (after waiting about 7 years:) however, I can't seem to get Linux to connect. I've tried getting a dhcp address from the modem, but nothing happens. I used Comcast for all of 3 months (went DSL instead). If memory serves, they require you to run their registration app. I was able to run it under Wine or CrossOver Office, I forget which. Once you register you can nuke their app. The registration is tied to the MAC address of your external NIC, so if you ever swap Ethernet cards you have to re-register. HTH, C ___ gnhlug-discuss mailing list [EMAIL PROTECTED] http://mail.gnhlug.org/mailman/listinfo/gnhlug-discuss
Re: Connecting to Comcast
On Tue, Sep 23, 2003 at 06:03:40AM -0400, Chris Brenton wrote: > The registration is tied to the MAC address of your external NIC, so if > you ever swap Ethernet cards you have to re-register. > As of when I left Comcast in March, this was not true. I had dealt with tech support and they told me they no longer do this. I subsequently switched computers (I got the connection working with my laptop and its built-in NIC, and then switched to my firewall without doing anything to mimic the MAC or what have you) with no difficulty. -- Derek D. Martin http://www.pizzashack.org/ GPG Key ID: 0xDFBEAD02 -=-=-=-=- This message is posted from an invalid address. Replying to it will result in undeliverable mail. Sorry for the inconvenience. Thank the spammers. ___ gnhlug-discuss mailing list [EMAIL PROTECTED] http://mail.gnhlug.org/mailman/listinfo/gnhlug-discuss
Re: Connecting to Comcast
> On Tue, 23 Sep 2003, "Jerry" == Jerry Feldman wrote: Jerry> First, try to see if you can access your cable modem at Jerry> 192.168.100.1. I found this IP on the web somewhere after googling around. The question I have is this, how can I access a network for which I have no route? IOW, I have 2 nics, one on my internal LAN, and one for connecting to the CM. The 'external' NIC is obviously unconfigured, since it's supposed to be configured using DHCP, which isn't working. And yes, I've tried manually configuring that NIC to be on the 192.168.100/24 subnet, and that didn't seem to work. (I'm also *very* disappointed that there's no serial port on these modems, though, ironically, on my "Digital Cable" set-top box there is?! :) I'm beginning to hate ComCast already, and I haven't even *used* their stuff yet :) (and I thought DSL was the only technology that had install horror-stories :) Thanks, I'll try the website :) -- Seeya, Paul GPG Key fingerprint = 1660 FECC 5D21 D286 F853 E808 BB07 9239 53F1 28EE If you're not having fun, you're not doing it right! ___ gnhlug-discuss mailing list [EMAIL PROTECTED] http://mail.gnhlug.org/mailman/listinfo/gnhlug-discuss
RE: Connecting to Comcast
> (I'm also *very* disappointed that there's no serial port on these > modems, though, ironically, on my "Digital Cable" set-top box there > is?! :) They don't want you to have to much control of your cable modem. For a while there was a way to configure it with SNMP and get it "uncapped". They fixed that fairly quickly with a firmware upgrade. The serial port on your digital cable box is for it to interface with things like TiVo to control the channels for recording. > I'm beginning to hate ComCast already, and I haven't even *used* > their stuff yet :) (and I thought DSL was the only technology that > had install horror-stories :) I used to hear tons of DSL horror stories.. Those are mostly gone now, unless you're on the frindge of the service area things go very smoothly. My DSL (MV.com) install went easier then any of my cable installs. ___ gnhlug-discuss mailing list [EMAIL PROTECTED] http://mail.gnhlug.org/mailman/listinfo/gnhlug-discuss
Re: Connecting to Comcast
Remember you can ifconfig a single NIC with a secondary IP in when using linux/Solaris. This is kind neat since it allows you to easily run two 'networks' on the same media. rockhopper:/etc/rc3.d# ifconfig -a eth0 Link encap:Ethernet HWaddr 08:00:20:8F:24:04 inet addr:152.148.8.187 Bcast:152.148.255.255 Mask:255.255.252.0 UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:23132456 errors:0 dropped:0 overruns:0 frame:0 TX packets:474038 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:100 RX bytes:1505871693 (1.4 GiB) TX bytes:62763477 (59.8 MiB) Interrupt:32 loLink encap:Local Loopback inet addr:127.0.0.1 Mask:255.0.0.0 UP LOOPBACK RUNNING MTU:16436 Metric:1 RX packets:3863874 errors:0 dropped:0 overruns:0 frame:0 TX packets:3863874 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:337303529 (321.6 MiB) TX bytes:337303529 (321.6 MiB) rockhopper:/etc/rc3.d# ifconfig eth0:1 192.168.100.10 rockhopper:/etc/rc3.d# ifconfig -a eth0 Link encap:Ethernet HWaddr 08:00:20:8F:24:04 inet addr:152.148.8.187 Bcast:152.148.255.255 Mask:255.255.252.0 UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:23132816 errors:0 dropped:0 overruns:0 frame:0 TX packets:474263 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:100 RX bytes:1505895154 (1.4 GiB) TX bytes:62786987 (59.8 MiB) Interrupt:32 eth0:1Link encap:Ethernet HWaddr 08:00:20:8F:24:04 inet addr:192.168.100.10 Bcast:192.168.100.255 Mask:255.255.255.0 UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 Interrupt:32 loLink encap:Local Loopback inet addr:127.0.0.1 Mask:255.0.0.0 UP LOOPBACK RUNNING MTU:16436 Metric:1 RX packets:3863874 errors:0 dropped:0 overruns:0 frame:0 TX packets:3863874 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:337303529 (321.6 MiB) TX bytes:337303529 (321.6 MiB) rockhopper:/etc/rc3.d# ifconfig eth0:1 down rockhopper:/etc/rc3.d# ifconfig -a eth0 Link encap:Ethernet HWaddr 08:00:20:8F:24:04 inet addr:152.148.8.187 Bcast:152.148.255.255 Mask:255.255.252.0 UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:23133912 errors:0 dropped:0 overruns:0 frame:0 TX packets:474746 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:100 RX bytes:1505964880 (1.4 GiB) TX bytes:62839289 (59.9 MiB) Interrupt:32 loLink encap:Local Loopback inet addr:127.0.0.1 Mask:255.0.0.0 UP LOOPBACK RUNNING MTU:16436 Metric:1 RX packets:3863874 errors:0 dropped:0 overruns:0 frame:0 TX packets:3863874 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:337303529 (321.6 MiB) TX bytes:337303529 (321.6 MiB) -- __ | 0|___||. Andrew Gaunt - Computing Development Environment _| _| : : } Lucent Technologies: http://www-cde.mv.lucent.com/~quantum -(O)-==-o\ Personal: http://www.gaunt.org [EMAIL PROTECTED] wrote: On Tue, 23 Sep 2003, "Jerry" == Jerry Feldman wrote: Jerry> First, try to see if you can access your cable modem at Jerry> 192.168.100.1. I found this IP on the web somewhere after googling around. The question I have is this, how can I access a network for which I have no route? IOW, I have 2 nics, one on my internal LAN, and one for connecting to the CM. The 'external' NIC is obviously unconfigured, since it's supposed to be configured using DHCP, which isn't working. And yes, I've tried manually configuring that NIC to be on the 192.168.100/24 subnet, and that didn't seem to work. (I'm also *very* disappointed that there's no serial port on these modems, though, ironically, on my "Digital Cable" set-top box there is?! :) I'm beginning to hate ComCast already, and I haven't even *used* their stuff yet :) (and I thought DSL was the only technology that had install horror-stories :) Thanks, I'll try the website :) ___ gnhlug-discuss mailing list [EMAIL PROTECTED] http://mail.gnhlug.org/mailman/listinfo/gnhlug-discuss
Re: Connecting to Comcast
In a message dated: 23 Sep 2003 09:30:57 EDT Kevin D. Clark said: >[EMAIL PROTECTED] writes: > >> I found this IP on the web somewhere after googling around. The >> question I have is this, how can I access a network for which I have >> no route? The question was mostly rhetorical. I was thinking of the poor slob with a Windows box who doesn't know this stuff. Of course, that poor slob would probably have paid the $100 "professional" installation fee, rather than just getting suckered out $50 for the "basic" installation :) ># assumes eth0 is your external nic ># 10.1.2.3 is arbitrary >ifconfig eth0 10.1.2.3 > >route add 192.168.100.1 eth0 Yeah, I tried that, didn't work. >dhclient eth0 # maybe? I'll try that tonight. I was using pump, and Derek reminded me that pump is sometimes, often times, broken :) >Hope this helps, Thanks! -- Seeya, Paul GPG Key fingerprint = 1660 FECC 5D21 D286 F853 E808 BB07 9239 53F1 28EE If you're not having fun, you're not doing it right! ___ gnhlug-discuss mailing list [EMAIL PROTECTED] http://mail.gnhlug.org/mailman/listinfo/gnhlug-discuss
Re: Connecting to Comcast
[EMAIL PROTECTED] writes: > I found this IP on the web somewhere after googling around. The > question I have is this, how can I access a network for which I have > no route? # assumes eth0 is your external nic # 10.1.2.3 is arbitrary ifconfig eth0 10.1.2.3 route add 192.168.100.1 eth0 dhclient eth0 # maybe? Hope this helps, --kevin -- How many seconds are there in a year? If I tell you there are 3.155 x 10^7, you won't even try to remember it. On the other hand, who could forget that, to within half a percent, pi seconds is a nanocentury? - Tom Duff, Bell Labs ___ gnhlug-discuss mailing list [EMAIL PROTECTED] http://mail.gnhlug.org/mailman/listinfo/gnhlug-discuss
Re: Connecting to Comcast
> On Tue, 23 Sep 2003, "Andrew" == Andrew W. Gaunt wrote: Andrew> Remember you can ifconfig a single NIC with a secondary IP Andrew> in when using linux/Solaris. This is kind neat since it Andrew> allows you to easily run two 'networks' on the same media. Now *that* I hadn't tried or even considered :) Though, I did try manually configuring eth1 (my external nic) for the 192.168.100/24 net and trying to contact the modem at .1, but that didn't work. Thanks though :) -- Seeya, Paul GPG Key fingerprint = 1660 FECC 5D21 D286 F853 E808 BB07 9239 53F1 28EE If you're not having fun, you're not doing it right! ___ gnhlug-discuss mailing list [EMAIL PROTECTED] http://mail.gnhlug.org/mailman/listinfo/gnhlug-discuss
RE: Connecting to Comcast
I agree. My parents have comcast and they didn't need to register the computer MAC, just the modem MAC with some web interface. The "install CD" is basically a pretty front end for the webpage, at least as far as I can tell. Just call up Comcast and tell tech support that the tech dropped off the modem but had to leave before he could set it up and didn't leave you an install CD. They'll walk you thru the webpage. > -Original Message- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] Behalf Of Derek Martin > Sent: Tuesday, September 23, 2003 6:17 AM > To: [EMAIL PROTECTED] > Subject: Re: Connecting to Comcast > > > On Tue, Sep 23, 2003 at 06:03:40AM -0400, Chris Brenton wrote: > > The registration is tied to the MAC address of your external NIC, so if > > you ever swap Ethernet cards you have to re-register. > > > > As of when I left Comcast in March, this was not true. I had dealt > with tech support and they told me they no longer do this. I > subsequently switched computers (I got the connection working with my > laptop and its built-in NIC, and then switched to my firewall without > doing anything to mimic the MAC or what have you) with no difficulty. > > -- > Derek D. Martin > http://www.pizzashack.org/ > GPG Key ID: 0xDFBEAD02 > -=-=-=-=- > This message is posted from an invalid address. > Replying to it will result in undeliverable mail. > Sorry for the inconvenience. Thank the spammers. > > ___ > gnhlug-discuss mailing list > [EMAIL PROTECTED] > http://mail.gnhlug.org/mailman/listinfo/gnhlug-discuss > > ___ gnhlug-discuss mailing list [EMAIL PROTECTED] http://mail.gnhlug.org/mailman/listinfo/gnhlug-discuss
Re: Connecting to Comcast
Derek Martin said: > > As of when I left Comcast in March, this was not true. I had dealt > with tech support and they told me they no longer do this. Is this like Verizon tech's telling you that they don't block port 80 religiously, yet you can run a web server on other non-standard ports? I take much of what the tech support says with a grain of salt, esp. if its tier 1. I try to get on the phone and go directly to 2 or 3, that is if they can transfer the call. I saw someone's suggestion about trying another dhcp client. I know when I was in school I could not get an IP using pump, no matter how hard I tried. I have no experience with comcast though and am not sure about the registration process that may precede it. Derek Doucette http://derek.homeunix.org ___ gnhlug-discuss mailing list [EMAIL PROTECTED] http://mail.gnhlug.org/mailman/listinfo/gnhlug-discuss
RE: Connecting to Comcast
Yes, I have also provisioned myself using that method. I think I have setup an attbi/Comcast connection roughly 10 times, each time doing something slightly different. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Jerry Feldman Sent: Tuesday, September 23, 2003 7:31 AM To: [EMAIL PROTECTED] Subject: Re: Connecting to Comcast -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Tue, 23 Sep 2003 00:42:09 -0400 "Greg Bonnette" <[EMAIL PROTECTED]> wrote: > You can connect to Comcast with Linux (or a Broadband router etc.), > but I believe the initial connection requires a Windows PC in order to > run the setup CD they supply you with. No you do not need the Windows CD, but you do need to be provisioned. They have a web site that you can go to to provision yourself, but that is different for each area. First, try to see if you can access your cable modem at 192.168.100.1. Then try this address: https://sas.ne1.attbb.net/sas/pub/logon/mainauth.jsp?ORIGURL=/sa/prot/ad min/euser/activate.jsp While Comcast no longer registers your PC's MAC address, they need to register the Cable Modem MAC address. A quick call to Comcast should take care of this. - -- Jerry Feldman <[EMAIL PROTECTED]> Boston Linux and Unix user group http://www.blu.org PGP key id:C5061EA9 PGP Key fingerprint:053C 73EC 3AC1 5C44 3E14 9245 FB00 3ED5 C506 1EA9 -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.2-rc1-SuSE (GNU/Linux) iD8DBQE/cC7o+wA+1cUGHqkRApp6AJ4/E4ka+q105YVl7TKq4GxAKtKZgACeIR9R XczCYBsIUphQeOC4yZYTLRI= =+0a1 -END PGP SIGNATURE- ___ gnhlug-discuss mailing list [EMAIL PROTECTED] http://mail.gnhlug.org/mailman/listinfo/gnhlug-discuss ___ gnhlug-discuss mailing list [EMAIL PROTECTED] http://mail.gnhlug.org/mailman/listinfo/gnhlug-discuss
Re: Connecting to Comcast
On Tue, Sep 23, 2003 at 12:36:56AM -0400, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote: > On Tue, 23 Sep 2003, "plussier" == [EMAIL PROTECTED] > wrote: plussier> The "PC/Activity" light is flashing an awful lot, but it plussier> seems to do this even when the interface is down (I'm plussier> assuming this is lowlevel link-layer traffic). I've also noticed that the Send and Receive lights are solid green. This doesn't seem right to me, as I'd expect them to flash with traffic. And, since I know there's no traffic, they shouldn't be flashing, or even on. Of course, I've never used this cable modem before, so maybe they are supposed to be solid all the time. I have a Motorola SB4200, and the send and receive light are solid green. Only the amber activity light flashes. BTW, make sure you give the modem plenty of time after you turn it on -- light at least half-an-hour. I don't know why, but sometime that take that long to kick in gear. -- Bob Bell ___ gnhlug-discuss mailing list [EMAIL PROTECTED] http://mail.gnhlug.org/mailman/listinfo/gnhlug-discuss
Re: Connecting to Comcast
I hooked up to cable with Mediaone a few years ago. Never had a CD but I got hooked up on win98. I switched my nic & later just the mac to another machine & it works just fine. It's now comcast & I still haven't gotten a CD but I have swapped modems. I run OpenBSD with dhclient and it works great. I'd avoid pump. Even redhat doesn't use it anymore. ___ gnhlug-discuss mailing list [EMAIL PROTECTED] http://mail.gnhlug.org/mailman/listinfo/gnhlug-discuss
Re: Connecting to Comcast
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Tue, 23 Sep 2003 09:40:42 -0400 [EMAIL PROTECTED] wrote: > > > The question was mostly rhetorical. I was thinking of the poor slob > with a Windows box who doesn't know this stuff. Of course, that poor > slob would probably have paid the $100 "professional" installation > fee, rather than just getting suckered out $50 for the "basic" > installation :) > > ># assumes eth0 is your external nic > ># 10.1.2.3 is arbitrary > >ifconfig eth0 10.1.2.3 > > > >route add 192.168.100.1 eth0 > > Yeah, I tried that, didn't work. > > >dhclient eth0 # maybe? > > I'll try that tonight. I was using pump, and Derek reminded me that > pump is sometimes, often times, broken :) When you boot and have no upline DHCP server, the cable modem supplies a local address. With a Windoz box, you just set the IP address to automatic. - -- Jerry Feldman <[EMAIL PROTECTED]> Boston Linux and Unix user group http://www.blu.org PGP key id:C5061EA9 PGP Key fingerprint:053C 73EC 3AC1 5C44 3E14 9245 FB00 3ED5 C506 1EA9 -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.2-rc1-SuSE (GNU/Linux) iD8DBQE/cItA+wA+1cUGHqkRApsCAJ9uPaRSWD9vEPwBmJjZYXCEuE8QQACfe7PF liy/WBkDY9Ejfi+j+8vvPSs= =1RcG -END PGP SIGNATURE- ___ gnhlug-discuss mailing list [EMAIL PROTECTED] http://mail.gnhlug.org/mailman/listinfo/gnhlug-discuss
Re: Connecting to Comcast
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Tue, 23 Sep 2003 09:34:42 -0400 "Travis Roy" <[EMAIL PROTECTED]> wrote: > I used to hear tons of DSL horror stories.. Those are mostly gone now, > unless you're on the frindge of the service area things go very > smoothly. My DSL (MV.com) install went easier then any of my cable > installs. David Kramer has DSL and lost his accesss yesterday for about a day. - -- Jerry Feldman <[EMAIL PROTECTED]> Boston Linux and Unix user group http://www.blu.org PGP key id:C5061EA9 PGP Key fingerprint:053C 73EC 3AC1 5C44 3E14 9245 FB00 3ED5 C506 1EA9 -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.2-rc1-SuSE (GNU/Linux) iD8DBQE/cIqj+wA+1cUGHqkRAtUTAJ9KW8w+HgrNyv8J19b+VXsN9VjDlwCZAWbG u952puP6eVDuFLS/H91btYc= =zWcK -END PGP SIGNATURE- ___ gnhlug-discuss mailing list [EMAIL PROTECTED] http://mail.gnhlug.org/mailman/listinfo/gnhlug-discuss
RE: Connecting to Comcast
> > I used to hear tons of DSL horror stories.. Those are mostly gone now, > > unless you're on the frindge of the service area things go very > > smoothly. My DSL (MV.com) install went easier then any of my cable > > installs. > David Kramer has DSL and lost his accesss yesterday for about a day. Yah, I lost mine too. I was told that Verizon made a change and MV had to reset a card.. It was not suppose to cause people to have to reboot their DSL modem, but for me, I did.. But MediaOne was infamous for doing renumbers mid-lease and causing people to have to reboot. ___ gnhlug-discuss mailing list [EMAIL PROTECTED] http://mail.gnhlug.org/mailman/listinfo/gnhlug-discuss
Re: Connecting to Comcast
On Tue, 23 Sep 2003, Jerry Feldman stated in their Email: gaf> From: Jerry Feldman <[EMAIL PROTECTED]> gaf> To: GNHLUG <[EMAIL PROTECTED]> gaf> Date: Tue, 23 Sep 2003 14:02:11 -0400 gaf> Subject: Re: Connecting to Comcast gaf> gaf> -BEGIN PGP SIGNED MESSAGE- gaf> Hash: SHA1 gaf> gaf> On Tue, 23 Sep 2003 09:34:42 -0400 gaf> "Travis Roy" <[EMAIL PROTECTED]> wrote: gaf> gaf> > I used to hear tons of DSL horror stories.. Those are mostly gone now, gaf> > unless you're on the frindge of the service area things go very gaf> > smoothly. My DSL (MV.com) install went easier then any of my cable gaf> > installs. gaf> David Kramer has DSL and lost his accesss yesterday for about a day. On the other hand, I have had DSL for years (4?) and except for the first month (a long story at the phone company's expense) I've had nearly uninterrupted service... gaf> gaf> - -- gaf> Jerry Feldman <[EMAIL PROTECTED]> gaf> Boston Linux and Unix user group gaf> http://www.blu.org PGP key id:C5061EA9 gaf> PGP Key fingerprint:053C 73EC 3AC1 5C44 3E14 9245 FB00 3ED5 C506 1EA9 gaf> -BEGIN PGP SIGNATURE- gaf> Version: GnuPG v1.2.2-rc1-SuSE (GNU/Linux) gaf> gaf> iD8DBQE/cIqj+wA+1cUGHqkRAtUTAJ9KW8w+HgrNyv8J19b+VXsN9VjDlwCZAWbG gaf> u952puP6eVDuFLS/H91btYc= gaf> =zWcK gaf> -END PGP SIGNATURE- gaf> ___ gaf> gnhlug-discuss mailing list gaf> [EMAIL PROTECTED] gaf> http://mail.gnhlug.org/mailman/listinfo/gnhlug-discuss gaf> -- "Linux: Because a PC is a terrible thing to waste." -- As seen on the 'net -- ___ gnhlug-discuss mailing list [EMAIL PROTECTED] http://mail.gnhlug.org/mailman/listinfo/gnhlug-discuss
Re: Connecting to Comcast
In a message dated: Tue, 23 Sep 2003 00:13:29 EDT plussier said: >I've tried using pump to get an address, and watched daemon.log and >an ethereal trace, and both show a bootp request going out, but >nothing ever comes back. Okay, so I swapped out pump for dhclient, and I still get nothing! I've set the eth1 address to 192.168.100.5, and set the route up: route add -net 192.168.100.0 gw 192.168.100.1 netmask 255.255.255.0 dev eth1 and still can't ping anything. I called comcast, and they're sending out a tech "with all the tools" to "diagnose" the problem... I'm wondering if might really be a modem problem?! -- Seeya, Paul -- Key fingerprint = 1660 FECC 5D21 D286 F853 E808 BB07 9239 53F1 28EE It may look like I'm just sitting here doing nothing, but I'm really actively waiting for all my problems to go away. If you're not having fun, you're not doing it right! ___ gnhlug-discuss mailing list [EMAIL PROTECTED] http://mail.gnhlug.org/mailman/listinfo/gnhlug-discuss
Re: Connecting to Comcast
[EMAIL PROTECTED] writes: > Okay, so I swapped out pump for dhclient, and I still get nothing! > I've set the eth1 address to 192.168.100.5, and set the route up: > > route add -net 192.168.100.0 gw 192.168.100.1 netmask 255.255.255.0 dev eth1 > > and still can't ping anything. Let's have another routing flame-war! We haven't had one in, like, weeks... We're overdue now, don't you think? What happens if you type: route add 192.168.100.1 eth1 before you type the command that you wrote about (above)? I've had better luck specifying routes this way then by appending the "dev eth1" like you did above. Regards, --kevin -- You got to meet me by the knuckles of the skinny bone tree... -- Tom Waits ___ gnhlug-discuss mailing list [EMAIL PROTECTED] http://mail.gnhlug.org/mailman/listinfo/gnhlug-discuss
Re: Connecting to Comcast
I think you may find that if you had the "Basic" installation and you didn't register your cable modem using the programs on the CD they left with you, that you won't be able to get a DHCP served address. The way it works is that you setup a proxy address for your computer and then using a web page off a server at the proxy address, you register the cable modem. Normally they do this with a Windows PC but you should be able to use a Linux system to do the same thing. One problem you will run into is that I suspect very few of their technical people will know how to direct you to perform the registration unless you are using a Windows PC (which BTW, they require for this step of the process of signing up). Once the cable modem is registered on the network segment you are logged into, the software on the CD resets the modem, clears the proxy address and you are good to go. At this point a Linux box should work without problem. I'm using a Libranet (Debian) Linux system attached to my LAN which in turn talks to Comcast through a LinkSys wireless access point/firewall/router. -Alex - Original Message - From: <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Tuesday, September 23, 2003 10:13 PM Subject: Re: Connecting to Comcast In a message dated: Tue, 23 Sep 2003 00:13:29 EDT plussier said: >I've tried using pump to get an address, and watched daemon.log and >an ethereal trace, and both show a bootp request going out, but >nothing ever comes back. Okay, so I swapped out pump for dhclient, and I still get nothing! I've set the eth1 address to 192.168.100.5, and set the route up: route add -net 192.168.100.0 gw 192.168.100.1 netmask 255.255.255.0 dev eth1 and still can't ping anything. I called comcast, and they're sending out a tech "with all the tools" to "diagnose" the problem... I'm wondering if might really be a modem problem?! -- Seeya, Paul -- Key fingerprint = 1660 FECC 5D21 D286 F853 E808 BB07 9239 53F1 28EE It may look like I'm just sitting here doing nothing, but I'm really actively waiting for all my problems to go away. If you're not having fun, you're not doing it right! ___ gnhlug-discuss mailing list [EMAIL PROTECTED] http://mail.gnhlug.org/mailman/listinfo/gnhlug-discuss ___ gnhlug-discuss mailing list [EMAIL PROTECTED] http://mail.gnhlug.org/mailman/listinfo/gnhlug-discuss
