[altq 714] Re: altq 3 and openbsd 2.8

[Stefan Laudat <stefan@worldbank.ro>]

I've been through this quite some time ago...
You can reproduce this nicely running altqd BEFORE bringing up device ppp0.
As the server on that date had no videocard I didn't have the opportunity
to switch on debugger and make a stack dump (sorry Kenjiro :(( ).
You can use altq+ppp BUT you have to reboot the machine and start altqd AFTER
the ppp device is up. Or maybe using ppp as kernel module and trying to
unload/load it after a ppp failure.


> wonder what i've done wrong, ever seen a lockup using altqd + openbsd 2.8,
> happened twice, so i disabled altqd and went back to userland-ppp until i
> find out why. it runs fine for a few minutes as altqstats shows
> me.. previous uptimes were 100days before altq
> 
> not sure i am still experimenting and trying to get to grips with it
> any tips/tricks would be welcome, as would an ICMP rule that lets me vary
> it and see if having it is the problem? (lack of)
> 
> lo1: flags=8008<LOOPBACK,MULTICAST> mtu 32972
> ne3: flags=8863<UP,BROADCAST,NOTRAILERS,RUNNING,SIMPLEX,MULTICAST> mtu
> 1500
>         media: Ethernet autoselect (10baseT)
> de0: flags=8863<UP,BROADCAST,NOTRAILERS,RUNNING,SIMPLEX,MULTICAST> mtu
> 1500
>         media: Ethernet autoselect (10baseT)
>         status: active
>         inet 203.164.10.230 netmask 0xffffff80 broadcast 203.164.10.255
> ppp0: flags=8010<POINTOPOINT,MULTICAST> mtu 1500
>   ^^^^
> swap ppp0 and tun0 here as i had kernel-pppd with altqd when it was
> working/locked up.. i think i can duplicate it but prefer not to as having
> a link go down hurts/ouch.
> 
> tun0: flags=11<UP,POINTOPOINT> mtu 1500
>         inet 203.101.1.142 
> 
-- 
Stefan Laudat
-------------
The only thing I feel when I kill is recoil.