For the List. Anyone have an idea on reboot issues?

_________________________________
James W. McKeand

 

-----Original Message-----
From: Rene Wieldraaijer [mailto:rene at realwheel dot nl] 
Sent: Thursday, 13 October 2005 12:22 PM
To: James W. McKeand
Subject: RE: [m0n0wall] Network problem with Compaq EN 400s (since
1.2b8)

Hi James.
Thanks for your input.
I fixed the problem!
Just to be sure, I added these 6 line to my config
		<shellcmd>ifconfig tl0 down</shellcmd>
		<shellcmd>ifconfig xl0 down</shellcmd>
		<shellcmd>ifconfig tl0 up</shellcmd>
		<shellcmd>ifconfig xl0 up</shellcmd>
		<shellcmd>ifconfig tl0 media 100BaseTX mediaopt
full-duplex </shellcmd>
		<shellcmd>ifconfig xl0 media 100BaseTX mediaopt
full-duplex </shellcmd>

Now it boots without problems.

Only one problem remains.
I can't reboot the system.
Is hangs at the "rebooting" prompt.

Anywas...thanks a lot.

Regards,

Rene Wieldraaijer

-----Original Message-----
From: James W. McKeand [mailto:james at mckeand dot biz] 
Sent: donderdag 13 oktober 2005 14:22
To: m0n0wall at lists dot m0n0 dot ch
Subject: RE: [m0n0wall] Network problem with Compaq EN 400s (since
1.2b8)

Chris Buechler wrote:
> On 10/12/05, Rene Wieldraaijer <rene at realwheel dot nl> wrote:
>> I am having the following problem, can anyone help?
>> 
>> 
>> 
>> I am using m0n0wall on my Compaq EN 4000s.
>> 
>> All versions up to version 1.2b7 were working fine.
>> 
>> In versions 1.2b8 up to 1.2 final I am having the following problem.:
>> 
>> The onboard network interface is unreachable after booting.
>> 
> 
> I recall something similar on another box, where it was later
> determined that ifconfig after boot would bring up the interface
> (sounds like the same thing, since assign interfaces does an
> ifconfig).  Seems to be a driver issue in FreeBSD 4.x.  The rebooting
> not restarting the machine issue is probably related to the same.
> 
> Best I can offer is stick with 1.2b7 if it works well for you, or try
> different hardware or a different NIC.
> 
> Also make sure plug and play OS in your BIOS is disabled, and make
> sure you're using the latest BIOS on the machine.

If a ifconfig after boot brings it up, could a workaround be to add a
command in the config.xml to do a ifconfig on boot? (Sorry don't
remember the command to put in the xml, I just know you can...)

_________________________________
James W. McKeand




---------------------------------------------------------------------
To unsubscribe, e-mail: m0n0wall dash unsubscribe at lists dot m0n0 dot ch
For additional commands, e-mail: m0n0wall dash help at lists dot m0n0 dot ch