|
||||||||||
Brilliant. Thanks - it was 1000 that i wanted, but i wasn't sure whether it was just as simple as putting in 8... cheers. r Justin Ellison wrote: >Doing this without coffee :-( > >From the RFC: Corresponding Hex >1000 -- minimize delay 0x8 >0100 -- maximize throughput 0x4 >0010 -- maximize reliability 0x2 >0001 -- minimize monetary cost 0x1 >0000 -- normal service 0x0 > >HTH, > >Justin > >On Wed, 2004-08-04 at 09:22, Robert Hughes wrote: > > >>Does anyone have a reference for what the corresponding binary/hex >>numbers are for the various levels of QoS in the traffic shaper? >>I have some VoIP kit that I want to assign minimal delay packets to but >>it only accepts numbers in Hex. >>It seems a shame to have the option in the shaper only not to be able to >>use it!! >> >>Any offers? >> >>--------------------------------------------------------------------- >>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 >> >> -- Robert Hughes Senior Partner Dynamic Systems rh at dynsysgroup dot com tel: 020 7039 0094 |