I actualled found it out by snmpwalk'ing it, but that works too. Still,
being able to check at a glance would be nice. As far as I'm concerned, on a
project such as m0n0wall, the less someone has to venture into exec.php and
manual configuaration/troubleshooting, the better.

Gary T. Giesen 

-----Original Message-----
From: Graham Dunn [mailto:gdunn at inscriber dot com] 
Sent: July 9, 2004 10:36 AM
To: Gary T. Giesen
Cc: m0n0wall at lists dot m0n0 dot ch
Subject: Re: [m0n0wall] feature request

On Fri, Jul 09, 2004 at 10:23:11AM -0400, Gary T. Giesen wrote:
> I'll second the idea for an ethernet error counter on the interface 
> status page. I recently had a problem with intermittent connections 
> that turned out to be a cabling problem, even though I had replaced the
cable twice.

Until then ...

netstat -i

in exec.php will show

$ netstat -i
Name    Mtu Network       Address              Ipkts Ierrs    Opkts Oerrs
Coll
sis0   1500 <Link#1>    00:e0:18:00:00:03        6     0        6     0
0
sis0   1500 209.183.144.1 194.inscrfibre.        2     -        4     -
-
de0    1500 <Link#2>    00:80:c8:77:31:d5       51     0        1     0
0
de0    1500 10/24         m0n0-vpn              28     -       23     -
-
lo0   16384 <Link#3>                             0     0        0     0
0
lo0   16384 your-net      localhost              0     -        0     -
-
ppp0*  1500 <Link#4>                             0     0        0     0
0
sl0*    552 <Link#5>                             0     0        0     0
0
faith  1500 <Link#6>                             0     0        0     0
0


---------------------------------------------------------------------
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