Koozali.org: home of the SME Server

Legacy Forums => General Discussion (Legacy) => Topic started by: Paul Hoy on February 02, 2000, 02:01:28 AM

Title: @Home Cable Config. & dhcpcd
Post by: Paul Hoy on February 02, 2000, 02:01:28 AM

Hi folks,

Recently, my ISP switched from "normal" calbe to @Home. An active connection
with @Home requires that the machine be assigned a name. There's no problem
doing so in Windows 2000 and on a direct Linux connection. However, when using
e-smith, I'm unable to establish an Internet connection, despite employing the
command, dhcpcd -h CA-XXXXXXX. The command automatically is assigned to the
nic that handles my intranet, thereby locking up the entire system. And if I assign
the dhcpcd command to my internet nic (dhcpcd -h -s eth1), ifconfig tells me that
my ip is 000000, etc. It appears I need to provide some parameters, defining the eth1
card. Any hints or directions?

Cheers
Paul Hoy

Title: RE: @Home Cable Config. & dhcpcd
Post by: Joseph Morrison on February 02, 2000, 02:09:45 AM

Hello Paul,

> intranet, thereby locking up the entire system. And if I assign
> the dhcpcd command to my internet nic (dhcpcd -h -s eth1),

The -s argument specifies IP address, not interface. The interface can just be specified at the end of the command line without any special argument. So try:

dhcpcd -h CA-XXXXXXX eth1

or perhaps:

dhcpcd -h CA-XXXXXXX -s ##.##.##.## eth1

where ##.##.##.## is your assigned IP address.

If one of these works, please let us know! We're still looking for reliable recipes for the @home service.

- Joe Morrison

Title: RE: @Home Cable Config. & dhcpcd
Post by: Paul Hoy on February 02, 2000, 08:02:05 AM

Hi Joe,

Well, thanks for your help. It works. I used
dhcpcd -I XXXXXXXX eth1.

If you know how I might automate this process, I'd be interesteing in hearing from you.

Thanks again Joe.

Paul

Title: RE: @Home Cable Config. & dhcpcd
Post by: Charlie Brady on February 02, 2000, 08:19:38 AM

Paul Hoy wrote:

> Hi Joe,
>
> Well, thanks for your help. It works.
> I used "dhcpcd -I XXXXXXXX eth1".

That's quite odd. DHCP is supposed to tell you your IP address, not ask you it!! :-)

> If you know how I might automate this process, I'd be
> interesteing in hearing from you.

Edit

/etc/e-smith/templates/etc/sysconfig/network-scripts/ifup

Replace '-h "{ $SystemName }"' with '-I XXXXXXXX' then
run:

/sbin/e-smith/signal-event console-save

That should make the change permanent.

Out of interest, please find out whether

dhcpcd -h XXXXXX -I XXXXXX eth1

also works.

Thanks

Charlie

Title: RE: @Home Cable Config. & dhcpcd
Post by: Joseph Morrison on February 02, 2000, 04:47:38 PM

Hi Paul,

Thanks for your response!

> Well, thanks for your help. It works. I used dhcpcd -I XXXXXXXX
> eth1.

I was wondering, what exactly did you supply for the XXXXXXXX? Is that where you put the CA-XXXXXXX identifier? Or did you remove the CA- bit and just include the number? Or was it the IP address?

You may have just solved an important problem for us! And like Charlie, I'm also very interested to find out whether:

dhcpcd -h XXXXXX -I XXXXXX eth1

works too. Then the e-smith server can simply supply both arguments.

Thanks!
- Joe

Title: RE: @Home Cable Config. & dhcpcd
Post by: Glenn Kennedy on February 02, 2000, 10:43:36 PM

You didn't mention which @Home ISP you are using -- I understand configurations vary somewhat by cableco. I too was assignedthe CR-XXXXX number, which I entered as the server name in the console configuration (perhaps unnecessarily). Works like a charm.

I am using Rogers Cablesystems' @Home service in southern Ontario, Canada. I believe Rogers is also the major cable company in British Columbia and parts of Alaska.

Glenn Kennedy