I have seen these messages in three instances. The third may solve your problem.
1.) Software issues. The first occurrence is when you have not properly configured the dhcp client software correctly. I was a lazy butt and put my system identification information--in your case the "cr504xxx-a"--in both the "send host-name" and the "send dhcp-client-identifier" configuration variables of the /etc/dhclient.conf file, or lrcfg 3,4,1--"package", "dhclient", "dhclient daemon config" lrcfg menu items. One weekend my leaf box stopped receiving an ip address. I presume Cox did some weekend work that broke my miss configured settings. In the case of Phoenix cox@home service the system identifier should only be placed in the "send host-name" variable. I don't recall now but I may have also received some other dhcp client messages in the system log file. 2.) ISP changes. After I correctly configured the dhclient daemon, I had another occurrence when ISP changes broke my leaf box. I presume this time Cox was preparing segments of Phoenix cable system to switch over to Data Over Cable Service Interface Specifications (DOCSIS) cable networks. I had a friend that was only a mile away that had to use the 2.0pl5 version of the dhclient.lrp package. I continued to work fine on 2.0p14 until about two weeks latter when I had to use 2.0p15 package. I received another error message from the dhclient package, but it also gave the same symptoms as you list below. 3.) Media failures. The cables and connectors in the networking world are referred to as media or the media link layer. I live in Arizona. The fan on the cpu and power supply filter allot of dust through my router. Every once in awhile I will open it up and vacuum the thing. Tonight I did not push the RJ45 Ethernet connector all the way into the card. I booted up and started seeing those same messages listed below. I thought humm may be Cox is going the way of Rogers. After some futzing about I realized the the cable was secure in the back of the cable modem but not in the router's Ethernet card. I pushed and finally heard the click. Moreover the link lights on the Ethernet card and the back of the cable modem sprang to life. This is a possibility in your situation, if you have a second Ethernet cable that is secure in the back of the Windows computer. You unplug the router from the cable modem side and then plug in your Windows PC and set the CR number in the Windows Networking "Computer Name" field. Everything works great because of the secure connection. However, the cable at the router end is still loose. So when you plug the router back into the cable modem you still see the the DHCP messages. A broken Ethernet cable can cause the same problem. LOL and if it wasn't me causing the problem it could be one of our three cats crawling through the wires while being chased by one of our two dogs. I hope this helps, Greg C Dummy wrote: > Hi. > I'm with Rogers@home. They are leaving @home I think. I succefully ran > ES2B and than ewaldw release of ES2B. I left for few weeks and when I > came back firewall stopped working. I thought that maybe floppy went bad > so I made new Dachstein and I get same symptoms: > floppy loads without any errors, recognizes both ethernet cards and > than I see endless: > ... > DHCPOFFER FROM 24.103.77.1 > DHCPREQUEST ON ETH0 TO 255.255.255.255 PORT67 > DHCPREQUEST ON ETH0 TO 255.255.255.255 PORT67 > DHCPDISCOVER ON ETH0 TO 255.255.255.255 PORT67 interval 5 > DHCPOFFER FROM 24.103.77.1 > etc... > > Same thing with ES2B. Widows computer loads no problem the only > requirement is computer identification "cr504xxx-a" > Any advice would be very helpfull > Andrey _______________________________________________ Leaf-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/leaf-user
