Re: Setting up ntl cable modem/DHCP?

2002-04-21 Thread Jason Chambers

Not sure if this will help but anyway :-)

I had a similar problem at work where by my desktop PC running Debian 
couldn't get an IP address from the DHCP server (which was a M$ NT 
server).  Other windows machines (including my desktop when booted into 
windows) could.  However this only happened if I was on a different 
subnet to the DHCP server - if I was on the same subnet the Debian box 
got an IP every time without a hitch.


The way I solved this was to install the dhcp-relay package on the 
debnian box which simply forwards any DHCP offers to a specific IP address.


As it works perfectly this way I have never bothered to find out what 
the problem was.


Like I said not sure if this would work in your case.

I'd be interested in knowing when you get it working though as I 
considering NTL broadband jobby aswell, although I not going back to 
windows just to use a faster connection :-)



--

Jason Chambers ([EMAIL PROTECTED])
Leicester, England




[EMAIL PROTECTED] wrote:

Hi

I think I could be tantalisingly close to getting a cable modem up and
running with my Debian box (Woody on a Compaq Professional Workstation
5000 PPro SMP) if I could just get my DHCP client to talk to my cable
operator's DHCP server.

The story so far:

*Cable Modem side - My cable operator is ntl (England, SE London/Kent)
I know that the line in to my home, the set top box (Pace DITV-1000
Phase 1b) and the cat5 UTP (crossover) cable to my Debian box is
working. This is because an ntl installation technician has connected
to the service using his laptop. When I have tried to connect my
Debian box I know the service is available because of the info on the
user information screen I can display on my TV.

*My Debian Box - I believe that my Ethernet card is set-up OK because
when using dmesg | more I can find:

ThunderLAN driver v1.14a
TLAN: eth0 irq=20, io=1400,
Compaq Netelligent Integrated 10/100 TX UTP, Rev. 16
TLAN: 1 device installed, PCI: 1 EISA: 0

Also when I run ifconfig I get:

eth0
Link encap:Ethernet  HWaddr 00:80:5F:C1:55:40  
UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1

RX packets:27288 errors:8 dropped:0 overruns:0 frame:8
TX packets:35281 errors:26 dropped:0 overruns:0 carrier:26
collisions:1536 txqueuelen:100 
RX bytes:3840126 (3.6 MiB)  TX bytes:3130668 (2.9 MiB)
Interrupt:20 Base address:0x1400 

lo
Link encap:Local Loopback  
UP LOOPBACK RUNNING  MTU:16436  Metric:1

RX packets:9195 errors:0 dropped:0 overruns:0 frame:0
TX packets:9195 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0 
RX bytes:3010625 (2.8 MiB)  TX bytes:3010625 (2.8 MiB)


For what its worth I am also getting a solid green and flashing amber
LEDs on the card, unfortunately I don't have a home network or other
Ethernets devices I can use to test it.

The DHCP client software I am using is chcp3-client v3.0+3.0.1r when I
run the dhclient command I get the following:

Listening on LPF/eth0/00:80:5f:c1:55:40
Sending on   LPF/eth0/00:80:5f:c1:55:40
Listening on LPF/lo/
Sending on   LPF/lo/
Sending on   Socket/fallback
DHCPDISCOVER on lo to 255.255.255.255 port 67 interval 4
DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 3
DHCPDISCOVER on lo to 255.255.255.255 port 67 interval 8
DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 4
DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 11
DHCPDISCOVER on lo to 255.255.255.255 port 67 interval 10
DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 12
DHCPDISCOVER on lo to 255.255.255.255 port 67 interval 21
DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 11
DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 9
DHCPDISCOVER on lo to 255.255.255.255 port 67 interval 12
DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 11
DHCPDISCOVER on lo to 255.255.255.255 port 67 interval 6
No DHCPOFFERS received.
No working leases in persistent database - sleeping.

Tried the dhclient -s option on the two ntl DNS address' listed in
DHCP mini-HOWTO and the STB IP addr of my box but still no joy.

Ntl do not officially support Linux and getting any form of in-depth
technical information out of them is almost impossible. But the DHCP
mini-HOWTO and anecdotal evidence from a conversation with the ntl
installation technician (unfortunately he don't know how) indicate that
a Linux box can be connected.

I would be very grateful if anyone could give me some pointers as to
what I am missing or getting wrong.

Thanks in advance

James


--
Personalised email by http://another.com




--
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]




Re: Setting up ntl cable modem/DHCP?

2002-04-21 Thread J. MaNN
On Sun, Apr 21, 2002 at 10:41:18AM +0100, [EMAIL PROTECTED] wrote:
 
 I think I could be tantalisingly close to getting a cable modem up and
 running with my Debian box (Woody on a Compaq Professional Workstation
 5000 PPro SMP) if I could just get my DHCP client to talk to my cable
 operator's DHCP server.

Hello, 

I'm not a NTL cable user yet, tho I hope to be soon :) However, I do 
remeber reading that you need to specify your user name to your dhcp
client for the ip request to work. 

Check out:

http://www.linux.org/docs/ldp/howto/Cable-Modem/isps.html

Hope this helps.

j.



-- 
Its a feature not a bug!


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]



Re: Setting up ntl cable modem/DHCP?

2002-04-21 Thread Andy Saxena
On Sun, Apr 21, 2002 at 10:41:18AM +0100, [EMAIL PROTECTED] wrote:
 Hi
 The DHCP client software I am using is chcp3-client v3.0+3.0.1r when I
 run the ?dhclient? command I get the following:
 
 Listening on LPF/eth0/00:80:5f:c1:55:40
 Sending on   LPF/eth0/00:80:5f:c1:55:40
 Listening on LPF/lo/
 Sending on   LPF/lo/
 Sending on   Socket/fallback
 DHCPDISCOVER on lo to 255.255.255.255 port 67 interval 4
 DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 3
 DHCPDISCOVER on lo to 255.255.255.255 port 67 interval 8
 DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 4
 DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 11
 DHCPDISCOVER on lo to 255.255.255.255 port 67 interval 10
 DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 12
 DHCPDISCOVER on lo to 255.255.255.255 port 67 interval 21
 DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 11
 DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 9
 DHCPDISCOVER on lo to 255.255.255.255 port 67 interval 12
 DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 11
 DHCPDISCOVER on lo to 255.255.255.255 port 67 interval 6
 No DHCPOFFERS received.
 No working leases in persistent database - sleeping.
 

And what does your /etc/dhcp3/dhclient.conf say?

-Andy


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]



Re: setting up a cable-modem

1997-12-14 Thread Aaron Walker
The card is an internal PnP card.

George Bonser wrote:

 You have a cable modem that installed into your computer?  Most cable
 modems are external with an ethernet card installed in the computer.

 On Sat, 13 Dec 1997, Aaron Walker wrote:

  Has anyone successfully setup a PnP Cable-Modem in Linux?
  I'm guessing I will have to use isapnptools to set it up.
  If you have been successfull at this, please help.
 
  Thanks for your time.
 
  --
  `
 
  Aaron Walker
 
  Work:
Site: http://www.iconmedia.com
Email: [EMAIL PROTECTED]
 
  Personal:
Site: http://www.iconmedia.com/aaron
Email: [EMAIL PROTECTED]
  ``
 
 
 
 
  --
  TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to
  [EMAIL PROTECTED] .
  Trouble?  e-mail to [EMAIL PROTECTED] .
 
 
 

 George Bonser
 Would you buy a car with the hood welded shut?
 http://www.debian.org
 Debian/GNU Linux ... the maintainable operating system.

 --
 TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to
 [EMAIL PROTECTED] .
 Trouble?  e-mail to [EMAIL PROTECTED] .



--
`
Aaron Walker

Work:
  Site: http://www.iconmedia.com
  Email: [EMAIL PROTECTED]

Personal:
  Site: http://www.iconmedia.com/aaron
  Email: [EMAIL PROTECTED]
``



--
TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to
[EMAIL PROTECTED] . 
Trouble?  e-mail to [EMAIL PROTECTED] .


Re: setting up a cable-modem

1997-12-14 Thread Aaron Walker
The card is made by General Instruments.  The TV cable does go into the back of 
the
card.  In my house, we have only 1 cable box, and that's in the living room.  My
linux box is in my room.  So there's no cable box within 25 feet of my 
computer.  I
read the cable-modem mini-HOWTO and it says that linux supports my ISP 
(MediaOne).
The HOWTO says that it will detect the card, then use DHCP to talk with the 
'net.  I
can't even get Linux to detect it.  Debian won't detect it on boot, so when the 
boot
prompt comes up, I type: linux ether=11, 0x300. This does not work either. Any
ideas?

George Bonser wrote:

 Right, but I will bet you it is an internal PnP ehthernet card. As for as
 I know so far, nobody is making internal cable-modems ... in other words,
 I will bet that the TV cable does not plug into it, I will bet that the
 cable company gave you a different cable box and there is a separate cable
 between that box and the computer ... that is probably an ethernet coax.

 On Sat, 13 Dec 1997, Aaron Walker wrote:

  The card is an internal PnP card.
 
  George Bonser wrote:
 
   You have a cable modem that installed into your computer?  Most cable
   modems are external with an ethernet card installed in the computer.
  
   On Sat, 13 Dec 1997, Aaron Walker wrote:
  
Has anyone successfully setup a PnP Cable-Modem in Linux?
I'm guessing I will have to use isapnptools to set it up.
If you have been successfull at this, please help.
   
Thanks for your time.
   
--
`
   
Aaron Walker
   
Work:
  Site: http://www.iconmedia.com
  Email: [EMAIL PROTECTED]
   
Personal:
  Site: http://www.iconmedia.com/aaron
  Email: [EMAIL PROTECTED]
``
   
   
   
   
--
TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to
[EMAIL PROTECTED] .
Trouble?  e-mail to [EMAIL PROTECTED] .
   
   
   
  
   George Bonser
   Would you buy a car with the hood welded shut?
   http://www.debian.org
   Debian/GNU Linux ... the maintainable operating system.
  
   --
   TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to
   [EMAIL PROTECTED] .
   Trouble?  e-mail to [EMAIL PROTECTED] .
 
 
 
  --
  `
  Aaron Walker
 
  Work:
Site: http://www.iconmedia.com
Email: [EMAIL PROTECTED]
 
  Personal:
Site: http://www.iconmedia.com/aaron
Email: [EMAIL PROTECTED]
  ``
 
 
 
 

 George Bonser
 Would you buy a car with the hood welded shut?
 http://www.debian.org
 Debian/GNU Linux ... the maintainable operating system.



--
`
Aaron Walker

Work:
  Site: http://www.iconmedia.com
  Email: [EMAIL PROTECTED]

Personal:
  Site: http://www.iconmedia.com/aaron
  Email: [EMAIL PROTECTED]
``



--
TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to
[EMAIL PROTECTED] . 
Trouble?  e-mail to [EMAIL PROTECTED] .


Re: setting up a cable-modem

1997-12-14 Thread Ben Pfaff
   The card is made by General Instruments.  The TV cable does go into the back 
of the
   card.  In my house, we have only 1 cable box, and that's in the living room. 
 My
   linux box is in my room.  So there's no cable box within 25 feet of my 
computer.  I
   read the cable-modem mini-HOWTO and it says that linux supports my ISP 
(MediaOne).
   The HOWTO says that it will detect the card, then use DHCP to talk with the 
'net.  I
   can't even get Linux to detect it.  Debian won't detect it on boot, so when 
the boot
   prompt comes up, I type: linux ether=11, 0x300. This does not work either. 
Any
   ideas?

Might be unrelated, but I think that no spaces are allowed in
arguments; i.e., linux ether=11,0x300 is more correct.


--
TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to
[EMAIL PROTECTED] . 
Trouble?  e-mail to [EMAIL PROTECTED] .


Re: setting up a cable-modem

1997-12-14 Thread George Bonser

On 14-Dec-97 Aaron Walker wrote:
 The card is made by General Instruments.  The TV cable does go into the back
 of the
 card.  

YIKES! That is ALL we need, RF interference problems from computers on the
cable-TV circuit.  The reason I was skeptical was that I was with a company
desinging the power supplies for a couple of different cable modem companies.
WHen asked why they didn't just put it on a card in the PC, the answer was RF
interference problems.  Sorry for doubting you, just that all the cable-modems I
have seen have been ehternet to the computer.


--
TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to
[EMAIL PROTECTED] . 
Trouble?  e-mail to [EMAIL PROTECTED] .