My primary problem is solved. The deal is that Mediaone (my cable
provider) is configured to speak only to a single NIC identifier. The
cable-guy recorded the NIC's MAC in a web-based database when he came to in
to install the hardware. I didn't realize what he was doing until today.
I suppose that replaces the need for any type of login.
What I had to do was simply take the NIC out of my Win95 box and put it in
my Linux box. As soon as I did that, the DHCP server warmed up to my Linux
box and I'm now masq'ing through that box.
I'm sure that I'll now uncover many of these issues that Bill writes about
below (I have already run into some of the joys of dhcpcd screwing up my
network configuration).
thanks for your help.
--Scott
At 10:05 PM 12/12/98 -0500, Bill Strosberg wrote:
>Scott:
>
>I just went through the same stuff here with my (new) cable modem ISP.
>
>They are all a little different, but here's what worked for me:
>
>1. I set the -h option in the dhcpcd ifup segment to my account name at the
>ISP. This is done in /etc/sysconfig/network-scripts/ifup. See the dhcpc
>man page for details. Since they don't authorize via a "roadrunner" style
>login process, the only way they can know who you are is by the -h
>parameter. You also have to create the /etc/dhcpc directory!
>2. Your ISP may be using a local router / gateway that Windows DHCP client
>sees, but your Linux box doesn't see it automatically. When you do see an
>IP address on the interface appear, (eth0 ?), it still won't work till your
>set up a static default gateway route to the router IP address. Look in the
>/etc/dhcpc directory for a file called hostinfo-eth0 - it'll have the router
>IP address listed as a parameter.
>3. The act of getting the DHCP client working will also screw up your
>hostname, domain and local name server pointers. As well, it screwed named.
>httpd, sendmail and smb. When the DHCP client connects, it runs a bunch of
>network initiation stuff that tries to set up your masq box as a client to
>the dhcp server.
>4. I had to remove the above services from the /etc/rc.d/rc3.d directory and
>start then after I had cleaned up the mess dhcp client had make of my
>network settings.
>5. I fixed the dhcp client mess via resetting my local server name, domain
>name, and resolv.conf file (adding in the name servers from the
>hostinfo-eth0 file). I did these fixes in the /etc/rc.d/rc.local file, run
>after the dhcp initiation was done.
>6. One I had fixed these problems, I restarted the services that had been
>avoided earlier /etc/rc.d/init.d/named start ... (httpd start, sendmail
>start, smb start).
>7. Everybody was happy and things worked from that point forward (till I
>rewired my home's Ethernet cabling, but that's another story).
>
>Bill Strosberg
>(with thanks to Jon Williams - who pointed me in the right direction)
>
>-----Original Message-----
>From: Scott Jangro [mailto:[EMAIL PROTECTED]]
>Sent: Saturday, December 12, 1998 12:28 PM
>To: [EMAIL PROTECTED]
>Subject: [masq] Linus (RH 5.1, 2.0.35) and Cablemodem probs
>
>All,
>
>(I posted this last night but didn't see it come across the list. Sorry
>for any dupes.)
>
>I've just got a new cable modem installed (which currently works fine on my
>Win95 box) and I am trying to set it up on my Linux box.
>
>Currently, I have a successful simple masq configuration with one Linux
>box as a masq server using its 56k modem and my other two machines (one
>Win95, one Linux) going through that to get to the internet. My goal is to
>replace the regular modem with the cablemodem.
>
>Before I add a second nic to my masq Linux box, I'm simply trying to get it
>that box to connect through the cable modem on eth0 and it is not working.
>
>I've reconfigured eth0 to use dhcp (through Redhat's control panel) and
>when I run dhcpcd I get no ip and no connection.
>
>Here's how it goes:
>
>+ I run dhcpdc
>+ I watch ifconfig and see eth0 configured with an ip of 0.0.0.0, etc.
> (I expect that this is normal while it looks for a DHCP server and
> waits for an IP to be allocated.)
>+ after 30 seconds or I get the following message on stdout:
>
> eth0: Setting promiscuous mode
>
> and it says the following in the log file:
>
> dhcpd[pid]: no DHCPOFFER messages
>
>+ run ifconfig and there's no longer has an entry for eth0
>
>I've also tried rebooting Linux to see if the startup will do any better.
>Same behavior.
>
>The cablemodem-mini-howto says it should be this simple. Am I missing
>something? I have also tried starting up a DHCP server of my own on this
>machine and still no satisfaction.
>
>Am I missing a step? Any advice?
>
>thanks.
>
> --Scott
>
>---------------------------------------------------------------------
>To unsubscribe, e-mail: [EMAIL PROTECTED]
>For additional commands, e-mail: [EMAIL PROTECTED]
>For daily digest info, email [EMAIL PROTECTED]
>
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
For daily digest info, email [EMAIL PROTECTED]
