[WBEL-users] strange problem with WBEL 3.0

[Greg Brown]

Yeah, I neglected to mention I rebooted after setting iptables to 
"off".  Oops.

Now, this is where things get interesting.  I reinstalled simply out of 
frustration to a basic install.. no gui, no nothing.

DHCP failes for eth0 on first boot.

I log in, issue iptables -F (though there's nothing in iptables to stop 
DHCP - I'm just doing it for good measure).  Then I issued a 'service 
network restart' and it puked out of the following error:

Bringing up interface eth0: eth0: Host error, FIFO diagnostic register 
2000.
eth0: PCI bus master, bus status 00x00029
eth0: bus-master 1, dirty (11) currrent 1(1)
(followed by lots of lenght and status lines).

Obviously this is something wrong.  But what?  Any ideas?  I'm off to 
google.

Greg

On Monday, Jan 5, 2004, at 10:47 US/Eastern, Daniel T. Gynn wrote:

> 'chkconfig --level 0123456 iptables off' does not turn off iptables.  
> It
> says when you reboot that it won't come on.  To clear your tables, you
> must run '/sbin/iptables -F'.
>
>
> On Mon, 2004-01-05 at 10:31, Greg Brown wrote:
>> I just installed WBEL on a machine which was last running RH 9.0.  The
>> installation went smoothly but I am now having a problem obtaining a
>> DHCP address from my DHCP server.
>>
>> My physical layer is good (I was obtaining a DHCP address on the same
>> box running RH 9) though I have changed from my small desktop linksys
>> switch to my secondary port on my VOIP phone just to test and still no
>> DHCP address.  I am currently plugged back into the small Linksys
>> switch along with my OS X laptop and XP laptop.
>>
>> I stopped iptables (chkconfig --level 0123456 iptables off) and I
>> continue to try to get an address by issuing 'service network restart'
>> commands while plugged into the switch and still I get nothing.  Both
>> my Mac OS X laptop and my XP laptop got DHCP addresses while plugged
>> into the linksys switch, so it would appear I don't have a problem
>> communicating with the DHCP server from this switch.
>>
>> The ethernet card in the WBEL box is a 3c905.  My
>> /etc/sysconfig/network-scripts/ifcfg-eth0 looks like:
>>
>> # 3Com Corportation|3c905 100BaseTX [Boomerang]
>> DEVICE=eth0
>> BOOTPROTO=dhcp
>> ONBOOT=yes
>> DHCP_HOSTNAME=gb-webel
>> USERCTL=no
>> PEERDNS=yes
>> TYPE=ETHERNET
>>
>> I have nearly this exact configuration at home on my WBEL box (P-III,
>> 3c905) and it works flawlessly without and tweaking once the software
>> had been installed.  I can verify that iptables has stopped (just to 
>> be
>> sure ICMP is not being blocked) by checking chkconfig --list | grep
>> iptables which returns:
>>
>> iptables	0:off	1:off	2:off	3:off	4:off	5:off	6:off
>>
>> Any ideas?  I must be missing something very simple here, but I just
>> can't see what it is.
>>
>> Greg
>>
>> _______________________________________________
>> Whitebox-users mailing list
>> Whitebox-users@beau.org
>> http://beau.org/mailman/listinfo/whitebox-users
> -- 
> -----------------------
> Daniel T. Gynn
> RHCE #806200978201621
> Essential Systems, Inc.
> 412-931-5403 ext. 1
> fax: 412-931-5425
> dan.gynn@essensys.com
> GnuPG Key http://www.essensys.com/~dan/gpgring.asc
> Fingerprint: 0979 73B8 847A 349E 7363  66F4 6A79 DD72 495D CD60
> <signature.asc>