>On Tue, Jun 13, 2000 at 11:22:09AM +1000, George Vieira wrote: >| I remember people talking about connecting cable to linux and just yesterday >| I managed to have a go. My nephew asked if I could get his linux box going >| with his new Optus cable and I agreed. >[...] >| After playing around I found the network card to be the fault and replacing >| it worked. Now the thing is that DHCP would not allocate me an IP unless I >| specified my machine name to be that supplied by Optus, which was something >| like CO744034-A and then it worked. > >Yes, this is their setup. > >| Once we established a connectiona nd confirmed it all was OK, I then >| attempted to get the linux box going. >| I setup DHCP on eth1 and when I started up the device, I could see >| activity/DHCP requests on the cable modem but it only failed. I thought >| possibly it required a name so I modified: >| /etc/hosts > >This won't help - that's name lookup, not hostname, > >| /etc/HOSTNAME > >Hmm. Something uses thing? > >| and this still failed. I then as a test just used the last known IP address >| of the windows configuration and all worked OK (until the IP expires I >| guess). > >Yah. Mine's been stable for months, but you really do want DHCP working so >that if they change things your end will track transparently. > >| What else could be the problem. I never actually set up a DHCP client under >| linux but I think it was requesting an IP. > >The Redhat DHCP client is known to have troubles. I'm using dhcpcd which >comes from the same people who issue BIND. > >Now, others on this list have said that it was enough to make redhat use pump >(was it pump?) I had limited success that way (my own cluelessness perhaps) and >went the whole hog: Pump is used to update the leased lines. So your not trying to use a outofdate ip. > > - disable the optus-side ethernet by setting ONBOOT=no in my > ifcfg-eth1 file (i.e. stop the stock redhat startup using it) > > - installed dhcpcd from the ISC site (www.isc.org ?) > > - added a new startup file to /etc/rc.d/init.d called dhcpcd > to bring the link up and ran chkconfig to activitate it. > >I'll just ssh into my home machine (god I love cable!) and get the files... >Ok. Attached is a tar file with my setup in it. > >You'll find: > > etc/rc.d/init.d/dhcpcd the startup script > etc/dhcpc/dhcpcd-eth1.exe run by dhcpcd when the link comes up > etc/dhcpc/dhcpcd-eth1.info the dhcpcd config: adjust to suit > etc/rc.d/init.d/firewall the firewalling rules, will require > much adjustment; they're setup for a > home network on 192.168.1.* > >Of course, you must install DHCP from the ISC people. I'm using >dhcp-3.0b1pl13. This will all need some adjustment for your machine. >Read and understand before use! > >Cheers, >-- >Cameron Simpson, DoD#743 [EMAIL PROTECTED] http://www.zip.com.au/~cs/ > >To understand recursion, you must first understand recursion. > -- SLUG - Sydney Linux Users Group Mailing List - http://www.slug.org.au To unsubscribe send email to [EMAIL PROTECTED] with unsubscribe in the text
