search for: erranous

Hi, I managed to get the codec into netmeeting. Unfortunately it doesn't properly work. I tried to talk vie net, but only erranous packets are decoded. Did I possibly register the codec wiht incorrecxt parameters or is this a problem of the acm codec? bye, D A --- >8 ---- List archives: http://www.xiph.org/archives/ Ogg project homepage: http://www.xiph.org/ogg/ To unsubscribe from this list, send a message to 'sp...

...post Solution? (Thanks to Mr Eastep) Enable NEWNOTSYN in shorewall.conf, as the FW was only seing "half" the session between the subnets (Sinte traffic from .224.0/24 never passed the LOC interface of the FW, but rather injected directly into the switch), it dropped the (as it thought) erranous packages silently (This would have been seen if LOGNEWNOTSYN had been enabled in shorewall.conf. Also: I chose to do "echo 0 > /proc/sys/net/ipv4/conf/eth1/send_redirects" in the startup of shorewall to prevent the FW of redirecting hosts directly to the VPN routers. This was done to...

Hi, > I managed to get the codec into netmeeting. Unfortunately it doesn't > properly work. I tried to talk vie net, but only erranous packets are > decoded. Did I possibly register the codec wiht incorrecxt parameters or > is this a problem of the acm codec? I can't tell why. Try to register mode 8kHz Mono mode Q3 or Q4 for Netmeeting. Only these modes pack exactly 1 speex frame into one data packet. That ensures low...

Hi! Just updated to 1.0 rc15, but the problem remains. I think it could be client-dependent to some extent. I have only IMAPS access and Maildir. I have one mailbox which contains some 10,200 mails. That mailbox takes forever (have waited 30 minutes and then aborted) to open with Thunderbird 1.5.0.7. Other mailboxes (like dovecot :-), only 6984 mails) opens quickly. When Thunderbird tries to

http://bugzilla.mindrot.org/show_bug.cgi?id=423 dtucker at zip.com.au changed: What |Removed |Added ---------------------------------------------------------------------------- OtherBugsDependingO| |627 nThis| | Status|NEW |ASSIGNED ------- Additional

Normally the FreeBSD Project tries very hard to avoid ABI breakage in "Stable Branches". However occasionally the fix for a bug can not be implemented without ABI breakage, and it is decided that the fix warrants the impact of the ABI breakage. We have one of those situations coming along for RELENG_7 (what will become FreeBSD 7.1). The ABI breakage should only impact kernel modules