On Mon, 19 Mar 2007, Gustavo Rios wrote:
> Here is the output:
>
> $ ifconfig -a
> lo0: flags=8049<UP,LOOPBACK,RUNNING,MULTICAST> mtu 33224
> groups: lo
> inet 127.0.0.1 netmask 0xff000000
> inet6 ::1 prefixlen 128
> inet6 fe80::1%lo0 prefixlen 64 scopeid 0x7
> sis0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> mtu 1500
> lladdr 00:00:24:c7:31:20
> media: Ethernet 100baseTX (100baseTX full-duplex)
> status: active
> inet 10.0.0.1 netmask 0xffffff00 broadcast 10.0.0.255
> inet6 fe80::200:24ff:fec7:3120%sis0 prefixlen 64 scopeid 0x1
> sis1: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> mtu 1500
> lladdr 00:00:24:c7:31:21
> media: Ethernet 100baseTX (none)
> status: no carrier
> inet 10.0.1.1 netmask 0xffffff00 broadcast 10.0.1.255
> inet6 fe80::200:24ff:fec7:3121%sis1 prefixlen 64 scopeid 0x2
> sis2: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> mtu 1500
> lladdr 00:00:24:c7:31:22
> media: Ethernet 100baseTX (none)
> status: no carrier
> inet 10.0.2.1 netmask 0xffffff00 broadcast 10.0.2.255
> inet6 fe80::200:24ff:fec7:3122%sis2 prefixlen 64 scopeid 0x3
> pflog0: flags=141<UP,RUNNING,PROMISC> mtu 33224
> pfsync0: flags=0<> mtu 1460
> groups: carp
> enc0: flags=0<> mtu 1536
> pppoe0: flags=8851<UP,POINTOPOINT,RUNNING,SIMPLEX,MULTICAST> mtu 1492
> dev: sis0 state: session
> sid: 0xdda5 PADI retries: 0 PADR retries: 0 time: 2d 21:08:21
> sppp: phase network authproto pap authname "[EMAIL PROTECTED]"
> groups: pppoe egress
> inet6 fe80::200:24ff:fec7:3120%pppoe0 -> prefixlen 64 scopeid 0x8
> inet 201.78.27.251 --> 0.0.0.1 netmask 0xffffffff
> $
>
> So, this is! What i am doing wrong ?
Something to try: ifconfig sis1 down, same for sis2.
The hypothesis is: the interfaces are marked up and have an IP, but no
carrier. rup and ruptime walk the interface list to send broadcasts.
If an interface is up but has no physcial connnection, it wil refuse
packets, signalling that with an ENOBUFS.
-Otto
>
> On 3/19/07, Otto Moerbeek <[EMAIL PROTECTED]> wrote:
> >
> > On Mon, 19 Mar 2007, Gustavo Rios wrote:
> >
> > > Ok,
> > >
> > > Here is my output of netstat:
> > > $ netstat -m
> > > 331 mbufs in use:
> > > 326 mbufs allocated to data
> > > 2 mbufs allocated to packet headers
> > > 3 mbufs allocated to socket names and addresses
> > > 72/152/6144 mbuf clusters in use (current/peak/max)
> > > 420 Kbytes allocated to network (53% in use)
> > > 0 requests for memory denied
> > > 0 requests for memory delayed
> > > 0 calls to protocol drain routines
> > > $
> > >
> > > But rusers still gives that warning message, as also rup:
> > > $ rusers
> > > rusers: can't send broadcast packet: No buffer space available
> > > $ rup
> > > rup: RPC: Unable to send
> > > $
> > >
> > > How could i fix it?
> >
> > This is more probably a case of a funky network interface config than a
> > real mbuf shortage. Check your ip's, netmasks and broadcasts addresses.
> >
> > -Otto
> >
> > >
> > > On 3/19/07, Darren Spruell <[EMAIL PROTECTED]> wrote:
> > > > On 3/19/07, Gustavo Rios <[EMAIL PROTECTED]> wrote:
> > > > > Dear list members,
> > > > >
> > > > > how could i adjust my mbuf size? Need i to compile a news kernel ?
> > > > >
> > > >
> > > > kern.maxclusters allows setting new limits for mbufs.
> > > >
> > > > This would supposedly go out with the same tuning warnings as usual;
> > > > you may find you need a very good reason to adjust that, if it should
> > > > be adjusted at all. Does 'netstat -m' show that you're hitting limits?
> > > >
> > > > This advice may apply to your situation as well:
> > > >
> > > > http://archives.neohapsis.com/archives/openbsd/2004-07/1783.html
> > > >
> > > > DS
