Topic: Rogers cablemodem???

[Jean-Guy]

Hi, I have a cable modem and have been trying for about 3 hours to get e-smith (4.1.1) to work on it. I installed 2 identical PCI adaptors and the internal network seems to be ok (I can use the admin http page and get IP via dhcp) but when I try to use extranal websites e-smith say it cannot get the IP of the host. I think my cable modem is not assigning a internal IP to the e-smith box. I tryed put my cr-12345-a hostname in. but do i need the "@home" workgroup??? Please help I am new at this (linux).

Jean-Guy

[alex]

hi, i'm actualy setting it up this moment and was trying to find info my self, but hey i might be able to help.


http://www.linuxdoc.org/HOWTO/Cable-Modem/isps.html#AEN833

this place has how to do it and i was hopeing to get a bit more info on how to do that on e-simith.

[glenn kennedy]

here's the deal with rogers @home:

you don't need to put in the cr# of your cable modem into esmith, you can specify the static ip address given to you on your installation work order. you will also find the gateway and the subnetmask on the work order (be careful with subnet masks, different modems type use different masks -- older lancity is 255.255.252.0 newer terayon is 255.255.255.128). you do not need to put the dns servers into esmith config as esmith has fully fuctional dns server.

i recommend configuring with the static ip address, no dhcp.

if you chose to set up with dhcp, your ip address will probably remain static. but here's the snag that so many people don't realise: if you've had your cable modem directly plugged into a windows box set to dhcp, the cable modem/@home network provisioning will not give your esmith box a dhcp lease for several hours after the windows box makes a dhcp request. don't ask me exactly how long the "lockout" lasts, assume it is for a few hours. many people will configure an esmith box to dhcp using their cr# as a system name, then unplug their previously directly-connected windows box which was set to dhcp and plug the cable modem into the exteral nic of esmith. not gonna work for a few hours. instead, set the esmith to static and don't use the cr#.

this is based on my experience using rogers @home in toronto.

[Gordon Rowell]

glenn kennedy wrote:
>
>
> here's the deal with rogers @home:
>
> you don't need to put in the cr# of your cable modem into
> esmith,

Under 4.1 you can set the SystemName as you like, and put the
cr### name in as the hostname for the "DHCP - send hostname"
option in the console.

> you can specify the static ip address given to you on
> your installation work order.

I did not receive a static IP on my work order. My IP address
(and others I know) was static for five months and then changed.

> you will also find the gateway
> and the subnetmask on the work order (be careful with subnet
> masks, different modems type use different masks -- older
> lancity is 255.255.252.0 newer terayon is 255.255.255.128).
> you do not need to put the dns servers into esmith config as
> esmith has fully fuctional dns server.

YES - do NOT enter any DNS servers - e-smith will do it
correctly without further configuration.

> i recommend configuring with the static ip address, no dhcp.

As above, I was not provided with an IP address on the work-order
and DHCP worked just fine for me. Some people find out what
number they are given from DHCP and hard-code that, but this
is not a safe practice as the DHCP assignment may change.

> if you chose to set up with dhcp, your ip address will
> probably remain static. but here's the snag that so many
> people don't realise: if you've had your cable modem directly
> plugged into a windows box set to dhcp, the cable modem/@home
> network provisioning will not give your esmith box a dhcp
> lease for several hours after the windows box makes a dhcp
> request.

Do ipconfig /release (or something like that) before shutting
down your Windoze box. Windoze doesn't always send a DHCP
release before a clean shutdown

> don't ask me exactly how long the "lockout" lasts,
> assume it is for a few hours. many people will configure an
> esmith box to dhcp using their cr# as a system name, then
> unplug their previously directly-connected windows box which
> was set to dhcp and plug the cable modem into the exteral nic
> of esmith. not gonna work for a few hours. instead, set the
> esmith to static and don't use the cr#.

As above, no need to set the SystemName to cr#### under 4.1
Use the "DHCP - send hostname" option and satisfy the DHCP
server there with the customer hostname.

> this is based on my experience using rogers @home in toronto.

At least for me, in Ottawa, I needed to use DHCP. It was then
static for months.

Gordon

Gordon

[pkidd]

Videon@Home in Winnipeg, our dynamic IP is mostly static (a library connection authenticates by address and will edit their tables for the odd occasion that our IP changes).  There's a good Cable Modem Howto and also the FreeBSD Diary which strongly recommend DHCP for many @Home's even if you have a static IP assigned. However e-smith has worked flawlessly since first go, so I haven't learned from experience!