All,
I've just been gifted with a Cox Cable TV/Internet/Phone(someday)
hookup.
The TV works (naturally), the phone is vaporware until they "enable my
neighborhood", but the Internet works if you're an MS-Windows user.
My connection is live, I can see data being exchanged when I try to
connect (via the connection "ADSL/PPPoE" tool, the only thing looking
even close to appropriate), but the connection fails with a message
whose most useful content seems to be "Sorry, I scanned one
[Ethernet] interface but the Access Concentrator of your provider
did not respond."
1) Is what I'm attempting even possible, or must I buy a dual-boot
computer ("brokenputer" and "slowputer" are both
Debian/KDE/SimplyMEPIS lashups, but far past their working lives)
and only see the Internet from the WinXP side? [Bummer.] That is,
does the Cox Cable Modem service work through Debian Linux for
anyone reading this?
2) Before I natter at Cox, do I need a different connection tool than
the ADSL/PPPoE one? If so, what, and where do I get it, or do I
already have it and just not recognize it?
3) Will I need other information from Cox, like the IP address for
whatever an/their Access Concentrator is, or its hardware 6 byte
universal identifier?
4) Is the Cox Cable Modem service a "proxy" or a "direct internet
connection" (and how would I discover the difference for myself)?
If a proxy, I'm guessing I'll need to insert it as the proxy in each
of my browsers, something I'm confident I can do, since that's
how I'm communicating now. Would this have any implications on
the connectivity problem I'm trying to solve now?
5) Would it help to interpolate an 802.11g wireless service
between the cable modem and my (several) computers, in terms
of simplifying the (initial, get it working at all for one computer)
connectivity issues? [Getting my wireless to connect in libraries
seems fairly straightforward and well understood technology.]
If so, how?
6) Any other advice, dumbed down so my third grader could
follow it step by step, that would let me make this work, would be
appreciated, as would email memo copies of the postings, since
right now my Internet access seems to be at the "once a week"
level, and this newsgroup is busy enough to make finding
responses among all the other multilogs after that long
"challenging".
xanthian.

Kent Paul Dolan wrote:
All,

I've just been gifted with a Cox Cable TV/Internet/Phone(someday)
hookup.

The TV works (naturally), the phone is vaporware until they "enable my
neighborhood", but the Internet works if you're an MS-Windows user.

My connection is live, I can see data being exchanged when I try to
connect (via the connection "ADSL/PPPoE" tool, the only thing looking
even close to appropriate), but the connection fails with a message
whose most useful content seems to be "Sorry, I scanned one
[Ethernet] interface but the Access Concentrator of your provider
did not respond."

1) Is what I'm attempting even possible, or must I buy a dual-boot
computer ("brokenputer" and "slowputer" are both
Debian/KDE/SimplyMEPIS lashups, but far past their working lives)
and only see the Internet from the WinXP side? [Bummer.] That is,
does the Cox Cable Modem service work through Debian Linux for
anyone reading this?

2) Before I natter at Cox, do I need a different connection tool than
the ADSL/PPPoE one? If so, what, and where do I get it, or do I
already have it and just not recognize it?

3) Will I need other information from Cox, like the IP address for
whatever an/their Access Concentrator is, or its hardware 6 byte
universal identifier?

4) Is the Cox Cable Modem service a "proxy" or a "direct internet
connection" (and how would I discover the difference for myself)?
If a proxy, I'm guessing I'll need to insert it as the proxy in each
of my browsers, something I'm confident I can do, since that's
how I'm communicating now. Would this have any implications on
the connectivity problem I'm trying to solve now?

5) Would it help to interpolate an 802.11g wireless service
between the cable modem and my (several) computers, in terms
of simplifying the (initial, get it working at all for one computer)
connectivity issues? [Getting my wireless to connect in libraries
seems fairly straightforward and well understood technology.]
If so, how?

6) Any other advice, dumbed down so my third grader could
follow it step by step, that would let me make this work, would be
appreciated, as would email memo copies of the postings, since
right now my Internet access seems to be at the "once a week"
level, and this newsgroup is busy enough to make finding
responses among all the other multilogs after that long
"challenging".

xanthian.

Hi;
I'm new to linux and have just done a Debian 3.1r1 install (Sarge) - I
have Cable Internet and a "wired" Router + Cable Modem - all using
Ethernet (cat5) cabling (not USB!).
My system self-configured the Internet during Setup. I also know I have
DHCP enabled on the router (you can usually access BTH the Router
-and- the Modem separately through a URL in your Web Browser e.g.,
http://192.168.x.x) and note I also have a Dual boot system so at
anytime I can configure from the other S (but not necessary). In your
circumstance, perhaps a LiveCD will help you configure properly
(Knoppix or Ubuntu or MEPIS, etc)

I agree - ADSL/PPPoE is not appropriate for Cable internet - it's a
TelCo thing (usually)

In KDE - go to Kmenu (find) _Control Center_ listed under the "All
Applications" heading -- expand "Internet and Network" and click
"Proxy", ensure "Connect to the Internet Directly" is
tickedApply/K (just like winblows - gawd = I'm starting to really
despise this xDE - it's why (one reason) I loathe the recent NT Ses).

Also use Kmenu System Info Center (Network Interfaces) for info
(though I know how to obtain many of these parameters through the CLI),
I'm not sure you are even familiar with CLI at all

Wed, 15 Feb 2006 19:12:54 -0800, Kent Paul Dolan wrote:

All,

I've just been gifted with a Cox Cable TV/Internet/Phone(someday)
hookup.

The TV works (naturally), the phone is vaporware until they "enable my
neighborhood", but the Internet works if you're an MS-Windows user.

My connection is live, I can see data being exchanged when I try to
connect (via the connection "ADSL/PPPoE" tool, the only thing looking
even close to appropriate), but the connection fails with a message
whose most useful content seems to be "Sorry, I scanned one
[Ethernet] interface but the Access Concentrator of your provider
did not respond."

1) Is what I'm attempting even possible, or must I buy a dual-boot
computer ("brokenputer" and "slowputer" are both
Debian/KDE/SimplyMEPIS lashups, but far past their working lives)
and only see the Internet from the WinXP side? [Bummer.] That is,
does the Cox Cable Modem service work through Debian Linux for
anyone reading this?

2) Before I natter at Cox, do I need a different connection tool than
the ADSL/PPPoE one? If so, what, and where do I get it, or do I
already have it and just not recognize it?

3) Will I need other information from Cox, like the IP address for
whatever an/their Access Concentrator is, or its hardware 6 byte
universal identifier?

4) Is the Cox Cable Modem service a "proxy" or a "direct internet
connection" (and how would I discover the difference for myself)?
If a proxy, I'm guessing I'll need to insert it as the proxy in each
of my browsers, something I'm confident I can do, since that's
how I'm communicating now. Would this have any implications on
the connectivity problem I'm trying to solve now?

5) Would it help to interpolate an 802.11g wireless service
between the cable modem and my (several) computers, in terms
of simplifying the (initial, get it working at all for one computer)
connectivity issues? [Getting my wireless to connect in libraries
seems fairly straightforward and well understood technology.]
If so, how?

6) Any other advice, dumbed down so my third grader could
follow it step by step, that would let me make this work, would be
appreciated, as would email memo copies of the postings, since
right now my Internet access seems to be at the "once a week"
level, and this newsgroup is busy enough to make finding
responses among all the other multilogs after that long
"challenging".

xanthian.

You should be connecting through a router, the router will take care of
whatever protocol the cable company needs. You connect to the router
through vanilla TCP/IP. The router also serves as a hardware firewall,
and it allows you to share the connection with multiple machines. Routers
cost almost nothing these days, one that has wireless capability costs
slightly more.

Thursday 16 February 2006 14:49, General Schvantzkoph
<schvantzkoph@yahoo.com(<pan.2006.02.16.21.49.27.972117@yahoo.com>)
wrote:

Wed, 15 Feb 2006 19:12:54 -0800, Kent Paul Dolan wrote:
>
>I've just been gifted with a Cox Cable TV/Internet/Phone(someday)
>hookup.
>>
You should be connecting through a router, the router will take care of
whatever protocol the cable company needs.

I recently set up a Linksys "broadband router with wireless" for someone
without broadband. The manual was written for the clueless and since I had
about two clues, I was confused about the device's capabilities.

Might I expect that a device sold as a "broadband router with wireless" will
negotiate the cable company's DHCP and/or PPPoE connection internally? It
would be nice if it did, and the device appeared from the wired and
wireless router side as just another router with NAT.

Thu, 16 Feb 2006 19:23:30 -0700, Jules Dubois wrote:

Thursday 16 February 2006 14:49, General Schvantzkoph
<schvantzkoph@yahoo.com(<pan.2006.02.16.21.49.27.972117@yahoo.com>)
wrote:
>
>Wed, 15 Feb 2006 19:12:54 -0800, Kent Paul Dolan wrote:
>>
I've just been gifted with a Cox Cable TV/Internet/Phone(someday)
hookup.

>You should be connecting through a router, the router will take care of
>whatever protocol the cable company needs.
>
I recently set up a Linksys "broadband router with wireless" for someone
without broadband. The manual was written for the clueless and since I
had about two clues, I was confused about the device's capabilities.

Might I expect that a device sold as a "broadband router with wireless"
will negotiate the cable company's DHCP and/or PPPoE connection
internally? It would be nice if it did, and the device appeared from the
wired and wireless router side as just another router with NAT.

Have you tried to dig the info out of Windows?
Control Panel.Network.Properties(?) (sorry, don't use M$ Win-stuff) should
provide you with lots of useful info.

thing to look for in case of non-PC hardware: boxes that can interface
between an external provider and your home-net has one port (usually
marked 'WAN') and, spaced a bit away, up to 4,5 or even 8 ports marked
'LAN'. Wireless thingies of course also have their antenna connector or
fixed antenna. When you connect your PC-to-be-used-for-setup, you do it on
the LAN-side.

most (but experience shows unfortunately not all) routers you can
change the connection type on the WAN-port (PPPoE, DHCP etc.) to match
what your provider (be it cable, xDSL or whatever) requires. Your ISP's
helpdesk should be able to tell you what they want - and don't let them
put you off with "Don't worry, it's all on the install-CD. Just put that
into your PC and Windows takes care of the rest." (been there)

(In case you connect directly to your providers media-interface
(cable/ADSL modem etc.) just read references to WAN as to your netcard in
the PC.)

IME the ISP doing run-of-the-mill Ethernet usually has a DHCP server. In
this case just set the WAN-side for DHCP. In the no-server scenario they
WILL be able to tell you what IP you should set up. Go for static, fixed
or similar wording and put in the supplied numbers.
Similar procedure for the other options.
While you're at it, remember to disable ping, ssh and remote setup (SNMP?)
on the WAN-port - go figure

HTH

Jan, Z1DKE.

Either a D-Link or a Linksys wireless router will work just fine and be
very easy to configure, with Linux and the Motorola Surfboard you get
from Cox. you can just use dhclient or pump and connect directly to
the Surfboard. You might have to setup DNS IP's if dhcp doesn't get
these for you.

Kent Paul Dolan wrote:

[How do I get Cox Cable to work under Debian?]

Thanks for all the responses, now to try to make them
work, and to find and download the recommended
software. A router is unfortunately out of the question,
poverty is rife around my place.

xanthian.

Kent Paul Dolan wrote:

Thanks for all the responses, now to try to make them
work, and to find and download the recommended
software.

Looks like something called "pump" may do the trick, it
seems to incorporate a dhcp configuration capability. I
couldn't install dhcpcd, it conflicted with a part of "pump"
somehow.

I'll check out "pump" when I get home.

xanthian.