Greg
Greg Playle wrote the following at 17:31 03.08.2003:
Erich:
The output was something like this:
Variables
eth
/proc/net/dev
60
NICS = 1
Count = 0
Count updated
1
Devs = 1
expr [ 1 -eq 60 -o 1 -eq 1 ]
OK, the loop breaks here because we expect exactly one eth device and we
found
Greg
At 19:32 30.07.2003 -0600, Greg Playle wrote:
This is essentially what I ended up doing. As Mr. Sturdevant observed,
card services do not come up in time.
I added a script at the end of the boot sequence in rc2.d that restarts
networking, dhcpd and shorewall, and suddenly Bob's your Uncle!
B
y 28, 2003 03:30
To: Erich Titl; [EMAIL PROTECTED]; [EMAIL PROTECTED]
Subject: RE: [leaf-user] followup to interfaces / shorewall assist
If it is a question of interface not coming up, why not put the commands in
if-up and in rmnologon in /etc/init.d, add the "svi networking r
nt: Tuesday, July 29, 2003 8:41 AM
Subject: RE: [leaf-user] followup to interfaces / shorewall assist
An earlyer message indicated that iot was a 3c589. This is a PCMCIA
card.
As I recall, card services do not usually start until after networking.
This could be the "out of order" issue.
J
EMAIL PROTECTED]; '[EMAIL PROTECTED]'
>Subject: Re: [leaf-user] followup to interfaces / shorewall assist
>
>
>Greg
>
>At 18:14 27.07.2003, Greg Playle wrote:
>>Tom, Steve and George:
>> Thank you; the information you gave was helpful.
>>
1:18 AM
To: [EMAIL PROTECTED]; '[EMAIL PROTECTED]'
Subject: Re: [leaf-user] followup to interfaces / shorewall assist
Greg
At 18:14 27.07.2003, Greg Playle wrote:
>Tom, Steve and George:
> Thank you; the information you gave was helpful.
> I checked a bit more; in sh
Greg
At 14:20 27.07.2003 -0600, Greg Playle wrote:
Erich:
Thank you for spotting this; yes, I had backed it up. It turns
out to get
picked up by backing up /etc.
I am using the assert script with only this modification: an "echo
" line as the script starts, just before the loop
Steve Wright wrote:
I know Linux and WISP-DIST, but I am not familiar with Bering, per se.
Try these things ;
boot Bering, and see if pump is running on eth0. It should not be.
Start from scratch, with a perfectly clean image and have another go.
Write a little script that that restarts the n
Greg Playle wrote:
I tried building in a simple "wait 60 seconds" script, which ran at S29. That didn't help.
I've got something out of order, but I'm still not sure what.
What diagnostics would be useful here?
I know Linux and WISP-DIST, but I am not familiar with Bering, per se.
Try these t
: Sunday, July 27, 2003 14:39
To: [EMAIL PROTECTED]
Subject: Re: [leaf-user] followup to interfaces / shorewall assist
Greg Playle wrote:
>
> Thank you; the information you gave was helpful.
> I checked a bit more; in short, eth0 does not come up on boot, but see
Greg Playle wrote:
Thank you; the information you gave was helpful.
I checked a bit more; in short, eth0 does not come up on boot, but seems
to take a while
interfaces that take ages to come up are usually waiting for some dhcp
server to answer.. 8-)
Your eth0 should configure nearly instant
pectfully,
Greg
-Original Message-
From: Erich Titl [SMTP:[EMAIL PROTECTED]
Sent: Sunday, July 27, 2003 13:48
To: [EMAIL PROTECTED]; '[EMAIL PROTECTED]'
Subject: Re: [leaf-user] followup to interfaces / shorewall assist
Greg
At 18:14 27.07.2003, Greg Playle wrot
Greg
At 18:14 27.07.2003, Greg Playle wrote:
Tom, Steve and George:
Thank you; the information you gave was helpful.
I checked a bit more; in short, eth0 does not come up on boot,
but seems
to take a while--perhaps longer than Erich Titl's script allows. I've got
to check more on
On Sun, 2003-07-27 at 09:14, Greg Playle wrote:
> 4: eth0: mtu 1500 qdisc noop qlen 100
> link/ether 00:60:08:b1:ea:f5 brd ff:ff:ff:ff:ff:ff
>
Demonstrates that eth0 isn't configured yet.
>
> *
> /etc/init.d/networking restart < should have been eth0 inst
14 matches
Mail list logo
