Bug report: vpn (ipsec) interface number in snmp always change

Hi,
this is a bug report for RV082 hardware version 3 and 4, firmware version 1.x, 2.x and 4.x (all latest versions). I hope someone from cisco/belkin reads it.
Summary:
The snmp interface number of a VPN Tunnel change when the VPN tunnel disconnect and then re-connects.
What should happend:
The VPN Tunnel number 1, should always have the same snmp interface number. In RV082 v4, this number should always be 10. For example, the LAN, WAN1 and WAN2 always have the same snmp interface number.
What is the problem:
The VPN Tunnel number 1 change the snmp interface number, from 10, to 11, to 12, etc.
How to reproduce:
create a VPN Tunnel using 2 RV082 or 1 RV082 and 1 RV042. Once the VPN Tunnel is connected write down the snmp interface number. A few days later, disconnect the cable of block internet access. Then restore the internet conection and write down the snmp interface number, you should note that the snmp interface number have changed.
Tools used:
PRTG Network Monitor
Please take a look at the attached image, note all the "ppp" interfaces, theres only 1 VPN Tunnel (gateway-to-gateway) defined.

Hi Tom,
many thanks for your reply.
I see that I have to call Tech-support, in order to report a very technical situation, explaining them this is a bug report and I want them to make a better product.
Since I won't pay a dime for this problem to be fixed, I can only see pain in this path(calling to speak with a tech support representative).
I also readed that Belkin has bought Linksys, so I don't know if the RV082 will remain with Cisco or will go with Belkin.
So, my only hope is to document this bug, that is pressent inall firmware version and hardware version of the RV082 as of today.
many thanks for your help,
regards,
Oliver

Similar Messages

Remote Access VPN (ipsec) can ping LAN interface of firewall but not clients on the company network.

The VPN will connect.
I can ping and connect to the ASA 5510 on it's LAN interface.
My problem is that I cannot ping or access anything on the LAN past the firewall. What am I doing wrong?
Here is my config.
Result of the command: "show config"
: Saved
: Written by enable_15 at 22:55:02.299 UTC Tue Jan 10 2012
ASA Version 8.2(5)
hostname ********
enable password UbBnTPKwu27ohfYB encrypted
passwd 2KFQnbNIdI.2KYOU encrypted
names
interface Ethernet0/0
nameif outside
security-level 0
ip address x.x.x.x x.x.x.x
interface Ethernet0/1
nameif inside
security-level 100
ip address 10.0.4.1 255.255.255.0
interface Ethernet0/2
shutdown
no nameif
no security-level
no ip address
interface Ethernet0/3
shutdown
no nameif
no security-level
no ip address
interface Management0/0
nameif management
security-level 100
ip address 192.168.1.1 255.255.255.0
management-only
ftp mode passive
same-security-traffic permit inter-interface
same-security-traffic permit intra-interface
object-group network BC
network-object 10.0.3.0 255.255.255.0
network-object 10.0.4.0 255.255.255.0
access-list outside_access_in extended permit tcp any any eq ssh
access-list outside_access_in extended permit tcp any any eq 50000
access-list outside_access_in extended permit tcp any any eq 3390
access-list outside_access_in extended permit tcp any any eq 8066
access-list outside_access_in extended permit tcp any any eq 22225
access-list outside_access_in extended permit tcp any any eq 1600
access-list outside_access_in extended permit tcp any any eq 37260
access-list outside_access_in extended permit tcp any any eq 37261
access-list outside_access_in extended permit tcp any any eq 37262
access-list outside_access_in extended permit tcp any any eq 37263
access-list outside_access_in extended permit tcp any any eq 37264
access-list outside_access_in extended permit tcp any any eq 1435
access-list outside_access_in extended permit tcp any any eq 250
access-list outside_access_in extended permit tcp any any eq citrix-ica
access-list outside_access_in extended permit tcp any any eq 8080
access-list outside_access_in extended permit tcp any any eq www
access-list outside_access_in extended permit tcp any any eq 85
access-list outside_access_in extended permit tcp any any eq 8069
access-list outside_access_in extended permit tcp any any eq 3389
access-list outside_access_in extended permit tcp any any eq 23032
access-list outside_access_in extended permit tcp any any eq 32023
access-list outside_access_in extended permit tcp any any eq 3399
access-list outside_access_in extended permit udp any any eq 250
access-list outside_access_in extended permit udp any any eq 5008
access-list outside_access_in extended permit icmp any any
access-list splittunn-ppso extended permit ip 10.0.4.0 255.255.255.0 10.10.10.0 255.255.255.0
access-list splittunn-ppso extended permit ip 10.0.3.0 255.255.255.0 10.10.10.0 255.255.255.0
access-list nonat extended permit ip 10.0.4.0 255.255.255.0 10.10.10.0 255.255.255.0
access-list nonat extended permit ip 10.0.3.0 255.255.255.0 10.10.10.0 255.255.255.0
pager lines 24
logging asdm informational
mtu outside 1500
mtu inside 1500
mtu management 1500
ip local pool vpn-pool 10.10.10.1-10.10.10.254 mask 255.255.255.0
icmp unreachable rate-limit 1 burst-size 1
icmp permit any outside
icmp permit any inside
no asdm history enable
arp timeout 14400
nat-control
global (outside) 101 interface
nat (inside) 0 access-list nonat
nat (inside) 101 0.0.0.0 0.0.0.0
static (inside,outside) tcp interface 50000 10.0.4.58 50000 netmask 255.255.255.255
static (inside,outside) tcp interface ssh 10.0.4.7 ssh netmask 255.255.255.255
static (inside,outside) tcp interface 3390 10.0.3.249 3390 netmask 255.255.255.255
static (inside,outside) tcp interface 8066 10.0.3.249 8066 netmask 255.255.255.255
static (inside,outside) tcp interface 22225 10.0.4.58 22225 netmask 255.255.255.255
static (inside,outside) tcp interface 1600 10.0.4.58 1600 netmask 255.255.255.255
static (inside,outside) tcp interface 37260 10.0.4.58 37260 netmask 255.255.255.255
static (inside,outside) tcp interface 37261 10.0.4.58 37261 netmask 255.255.255.255
static (inside,outside) tcp interface 37262 10.0.4.58 37262 netmask 255.255.255.255
static (inside,outside) tcp interface 37263 10.0.4.58 37263 netmask 255.255.255.255
static (inside,outside) tcp interface 37264 10.0.4.58 37264 netmask 255.255.255.255
static (inside,outside) tcp interface 1433 10.0.4.240 1433 netmask 255.255.255.255
static (inside,outside) udp interface 5008 10.0.4.240 5008 netmask 255.255.255.255
static (inside,outside) udp interface 249 10.0.4.240 249 netmask 255.255.255.255
static (inside,outside) tcp interface 250 10.0.4.240 250 netmask 255.255.255.255
static (inside,outside) tcp interface www 10.0.4.15 www netmask 255.255.255.255
static (inside,outside) tcp interface citrix-ica 10.0.4.15 citrix-ica netmask 255.255.255.255
static (inside,outside) tcp interface 8080 10.0.4.15 8080 netmask 255.255.255.255
static (inside,outside) tcp interface 85 10.0.4.15 85 netmask 255.255.255.255
static (inside,outside) tcp interface 8069 10.0.4.236 8069 netmask 255.255.255.255
static (inside,outside) tcp interface 3399 10.0.4.236 3389 netmask 255.255.255.255
static (inside,outside) tcp interface 23032 10.0.4.244 23032 netmask 255.255.255.255
static (inside,outside) tcp interface 32023 10.0.4.244 32023 netmask 255.255.255.255
access-group outside_access_in in interface outside
route outside 0.0.0.0 0.0.0.0 x.x.x.x 1
route inside 10.0.3.0 255.255.255.0 10.0.4.205 1
timeout xlate 3:00:00
timeout conn 1:00:00 half-closed 0:10:00 udp 0:02:00 icmp 0:00:02
timeout sunrpc 0:10:00 h323 0:05:00 h225 1:00:00 mgcp 0:05:00 mgcp-pat 0:05:00
timeout sip 0:30:00 sip_media 0:02:00 sip-invite 0:03:00 sip-disconnect 0:02:00
timeout sip-provisional-media 0:02:00 uauth 0:05:00 absolute
timeout tcp-proxy-reassembly 0:01:00
timeout floating-conn 0:00:00
dynamic-access-policy-record DfltAccessPolicy
http server enable
http 0.0.0.0 0.0.0.0 inside
http 0.0.0.0 0.0.0.0 management
http x.x.x.x x.x.x.x outside
no snmp-server location
no snmp-server contact
snmp-server enable traps snmp authentication linkup linkdown coldstart
crypto ipsec transform-set ESP-AES-256-MD5 esp-aes-256 esp-md5-hmac
crypto ipsec transform-set ESP-DES-SHA esp-des esp-sha-hmac
crypto ipsec transform-set ESP-DES-MD5 esp-des esp-md5-hmac
crypto ipsec transform-set ESP-AES-192-MD5 esp-aes-192 esp-md5-hmac
crypto ipsec transform-set ESP-3DES-MD5 esp-3des esp-md5-hmac
crypto ipsec transform-set ESP-AES-256-SHA esp-aes-256 esp-sha-hmac
crypto ipsec transform-set ESP-AES-128-SHA esp-aes esp-sha-hmac
crypto ipsec transform-set ESP-AES-192-SHA esp-aes-192 esp-sha-hmac
crypto ipsec transform-set ESP-AES-128-MD5 esp-aes esp-md5-hmac
crypto ipsec transform-set ESP-3DES-SHA esp-3des esp-sha-hmac
crypto ipsec security-association lifetime seconds 28800
crypto ipsec security-association lifetime kilobytes 4608000
crypto dynamic-map outside_dyn_map 20 set transform-set ESP-3DES-SHA
crypto map outside_map 65535 ipsec-isakmp dynamic outside_dyn_map
crypto map outside_map interface outside
crypto ca trustpoint _SmartCallHome_ServerCA
crl configure
crypto ca certificate chain _SmartCallHome_ServerCA
certificate ca 6ecc7aa5a7032009b8cebcf4e952d491
    308205ec 308204d4 a0030201 0202106e cc7aa5a7 032009b8 cebcf4e9 52d49130
    0d06092a 864886f7 0d010105 05003081 ca310b30 09060355 04061302 55533117
    30150603 55040a13 0e566572 69536967 6e2c2049 6e632e31 1f301d06 0355040b
    13165665 72695369 676e2054 72757374 204e6574 776f726b 313a3038 06035504
    0b133128 63292032 30303620 56657269 5369676e 2c20496e 632e202d 20466f72
    20617574 686f7269 7a656420 75736520 6f6e6c79 31453043 06035504 03133c56
    65726953 69676e20 436c6173 73203320 5075626c 69632050 72696d61 72792043
    65727469 66696361 74696f6e 20417574 686f7269 7479202d 20473530 1e170d31
    30303230 38303030 3030305a 170d3230 30323037 32333539 35395a30 81b5310b
    30090603 55040613 02555331 17301506 0355040a 130e5665 72695369 676e2c20
    496e632e 311f301d 06035504 0b131656 65726953 69676e20 54727573 74204e65
    74776f72 6b313b30 39060355 040b1332 5465726d 73206f66 20757365 20617420
    68747470 733a2f2f 7777772e 76657269 7369676e 2e636f6d 2f727061 20286329
    3130312f 302d0603 55040313 26566572 69536967 6e20436c 61737320 33205365
    63757265 20536572 76657220 4341202d 20473330 82012230 0d06092a 864886f7
    0d010101 05000382 010f0030 82010a02 82010100 b187841f c20c45f5 bcab2597
    a7ada23e 9cbaf6c1 39b88bca c2ac56c6 e5bb658e 444f4dce 6fed094a d4af4e10
    9c688b2e 957b899b 13cae234 34c1f35b f3497b62 83488174 d188786c 0253f9bc
    7f432657 5833833b 330a17b0 d04e9124 ad867d64 12dc744a 34a11d0a ea961d0b
    15fca34b 3bce6388 d0f82d0c 948610ca b69a3dca eb379c00 48358629 5078e845
    63cd1941 4ff595ec 7b98d4c4 71b350be 28b38fa0 b9539cf5 ca2c23a9 fd1406e8
    18b49ae8 3c6e81fd e4cd3536 b351d369 ec12ba56 6e6f9b57 c58b14e7 0ec79ced
    4a546ac9 4dc5bf11 b1ae1c67 81cb4455 33997f24 9b3f5345 7f861af3 3cfa6d7f
    81f5b84a d3f58537 1cb5a6d0 09e4187b 384efa0f 02030100 01a38201 df308201
    db303406 082b0601 05050701 01042830 26302406 082b0601 05050730 01861868
    7474703a 2f2f6f63 73702e76 65726973 69676e2e 636f6d30 12060355 1d130101
    ff040830 060101ff 02010030 70060355 1d200469 30673065 060b6086 480186f8
    45010717 03305630 2806082b 06010505 07020116 1c687474 70733a2f 2f777777
    2e766572 69736967 6e2e636f 6d2f6370 73302a06 082b0601 05050702 02301e1a
    1c687474 70733a2f 2f777777 2e766572 69736967 6e2e636f 6d2f7270 61303406
    03551d1f 042d302b 3029a027 a0258623 68747470 3a2f2f63 726c2e76 65726973
    69676e2e 636f6d2f 70636133 2d67352e 63726c30 0e060355 1d0f0101 ff040403
    02010630 6d06082b 06010505 07010c04 61305fa1 5da05b30 59305730 55160969
    6d616765 2f676966 3021301f 30070605 2b0e0302 1a04148f e5d31a86 ac8d8e6b
    c3cf806a d448182c 7b192e30 25162368 7474703a 2f2f6c6f 676f2e76 65726973
    69676e2e 636f6d2f 76736c6f 676f2e67 69663028 0603551d 11042130 1fa41d30
    1b311930 17060355 04031310 56657269 5369676e 4d504b49 2d322d36 301d0603
    551d0e04 1604140d 445c1653 44c1827e 1d20ab25 f40163d8 be79a530 1f060355
    1d230418 30168014 7fd365a7 c2ddecbb f03009f3 4339fa02 af333133 300d0609
    2a864886 f70d0101 05050003 82010100 0c8324ef ddc30cd9 589cfe36 b6eb8a80
    4bd1a3f7 9df3cc53 ef829ea3 a1e697c1 589d756c e01d1b4c fad1c12d 05c0ea6e
    b2227055 d9203340 3307c265 83fa8f43 379bea0e 9a6c70ee f69c803b d937f47a
    6decd018 7d494aca 99c71928 a2bed877 24f78526 866d8705 404167d1 273aeddc
    481d22cd 0b0b8bbc f4b17bfd b499a8e9 762ae11a 2d876e74 d388dd1e 22c6df16
    b62b8214 0a945cf2 50ecafce ff62370d ad65d306 4153ed02 14c8b558 28a1ace0
    5becb37f 954afb03 c8ad26db e6667812 4ad99f42 fbe198e6 42839b8f 8f6724e8
    6119b5dd cdb50b26 058ec36e c4c875b8 46cfe218 065ea9ae a8819a47 16de0c28
    6c2527b9 deb78458 c61f381e a4c4cb66
quit
crypto isakmp enable outside
crypto isakmp policy 10
authentication pre-share
encryption 3des
hash sha
group 2
lifetime 86400
telnet x.x.x.x 255.255.255.255 outside
telnet 0.0.0.0 0.0.0.0 inside
telnet 0.0.0.0 0.0.0.0 management
telnet timeout 5
ssh 0.0.0.0 0.0.0.0 inside
ssh 0.0.0.0 0.0.0.0 management
ssh timeout 5
console timeout 0
management-access inside
dhcpd address 192.168.1.2-192.168.1.254 management
threat-detection basic-threat
threat-detection statistics access-list
no threat-detection statistics tcp-intercept
webvpn
enable outside
group-policy ppso internal
group-policy ppso attributes
dns-server value 10.0.4.241 10.0.4.14
split-tunnel-policy tunnelspecified
split-tunnel-network-list value splittunn-ppso
default-domain value ppso.local
split-dns value ppso.local
address-pools value vpn-pool
tunnel-group VPN type remote-access
tunnel-group VPN general-attributes
address-pool vpn-pool
default-group-policy VPN
tunnel-group VPN ipsec-attributes
pre-shared-key *
class-map inspection_default
match default-inspection-traffic
policy-map type inspect dns preset_dns_map
parameters
message-length maximum client auto
message-length maximum 512
policy-map global_policy
class inspection_default
inspect dns preset_dns_map
inspect ftp
inspect h323 h225
inspect h323 ras
inspect rsh
inspect rtsp
inspect esmtp
inspect sqlnet
inspect skinny
inspect sunrpc
inspect xdmcp
inspect sip
inspect netbios
inspect tftp
inspect ip-options
inspect icmp
service-policy global_policy global
prompt hostname context
call-home reporting anonymous
Cryptochecksum:88a9b69fc3d718c3badfa99db2c7ce4f

Yeah, I figured out where my problem was.
My IP Local Pool range was the problem.
I was using 10.10.10.0 which conflicted with a point-to-point connection where the serial interfaces were numbered and using 10.10.10.1 and 10.10.10.2.
Traffic would leave the firewall, hit the intended host, go back through my core router, then off to the other network.
I changed my ip local pool to a different range (192.168.100.0) and my problem was solved.

How to submit a bug report for OSB? - restore fails if number of items per page is changed from the default of 30

In the OSB web gui, one of my users found that if the number of items per page is changed from the default of 30, the restore of the file will fail. He tested this using recent versions of Firefox and IE. We have verified this to also be the case using Chrome.
In a directory containing over 100,000 files, moving 30 at a time to find the one to be restored is a very frustrating user experience.
How do I file a bug report for this issue? Is there a workaround for this bug to enable my users to more easily find the file to restore without being restricted to the default of 30 items per page?

Yes there is a bug in the webtool in the current release. You can use the commandline obtool to do the restore, that is much faster and works fine.
Thanks
Rich

Bug report: entering serial number does not work with azerty keyboard

I did not find a place to submit bug reports, so I'm posting here.
During the instalation of Photoshop Elements 8 for Mac, I was not able to enter any numbers in the serial number fields. Some other keys did work (like &é$...). My keyboard is an azerty (Belgium). Notice the numbers on an azerty keyboard have to be entered while holding the shift key. I tried switching the keyboard to "French - Numerical" (wich enables numbers to be entered with shift lock on), and then some number keys worked, and others didn't.
I solved this with a workaround, by temporary switching my keyboard to U.S. English.

You can submit a bug report by clicking "Feature Request/Bug Report" in the upper-right corner:
http://www.adobe.com/support/photoshopelements/
Despite what it says, I've seen no hard evidence that Adobe ever pays attention to PSE bug reports.

Bug report: Quicktime Audio recording with multichannel interfaces

I have problems recording audio in Quicktime using a multichannel audio interface. I tried two firewire interfaces, an Apogee Ensemble and the RME Fireface. Both are supported by core audio and work as expected with any audio sequencer such as Garage band, Logic, Studio One etc. However, both show the same strange behavior in Quicktime 10.2 and as well in iMovie and FCPx:
First, i selected interface channels 1 / 2 in the audio-midi-settings window as the stereo input source. In the quicktime audio recording window, I select the audio interface (fireface or ensemble) as the audio source. I expected that the recorded audio would be stereo. However, regardless of these settings, the recording is always mono. Actually quicktime records only channel 1 and ignores all other channels. This might be a bug in Quicktime with regard to the handling of multichannel interfaces. The same bug occurs in Final Cut Pro X and iMovie, which seem to use the same audio engine as Quicktime. However, Garage band and Logic do not show the problem.
It does also not seem to occur with simple stereo interfaces. I tried a Logitech C920 webcam with a built-in stereo microphone and a Zoom Q2HD recorder used in stereo USB microphone mode. In both cases, the recordings in FCPx are 2 channel stereo as it should be. Thus the problem is specific for multichannel interfaces.
Can anybody reproduce or explain this behaviour?
I am using OS X Mountain Lion (10.8.2), MacBook Pro 15 Retina 2.3 GHz.
Regards, Werner

It seems that apple has reacted to this bug report without notice. Recently I tried it once more with quicktime and an apogee ensemble interface. Surprisingly, the problem did not occur anymore. I have not tested it with iMovie and FCPX yet.
The sad side of Apples support strategy is that I spent time and money searching for a workaround without knowing that Apple had removed the bug in the meantime.

Bug report: Safari 5 fails to handle 8192 bit RSA certificates

Running Safari 5.1.7 on OS X 10.6.8 -- I haven't confirmed for the version of Safari running on 10.7 -- and trying to access a site over https that uses an 8192 bits large RSA cert causes Safari to bug out. It can't display the certificate details correctly, giving just a garbled text output, and even a buggy interface dialog, and manually trying to accept the certificate to get the website to load causes Safari to run in an endless loop, displaying the certificate warning anew, over and over, making it impossible to load the page. The exact same certificate details put in a 4096 bit cert works just fine.
Could anyone in the core dev team take a look at this? The number of sites making use of 8192 bit large certs is growing, and Safari is the only browser out there that can't handle it.
add.: it seems the problem sits at a more fundamental level than in Safari, possibly in some underlying framework - apparently several other applications in OS X fails with handling an RSA cert of 8192 bits size, as mentioned in this thread: https://discussions.apple.com/message/11728527
Possibly related: https://discussions.apple.com/message/3650856

Could anyone in the core dev team take a look at this? The number of sites making use of 8192 bit large certs is growing, and Safari is the only browser out there that can't handle it.
It might be worth registering (for free) as an Apple Developer:
http://developer.apple.com/programs/register/
... and then you can use the Bug Reporter to submit trackable bug reports:
http://developer.apple.com/bugreporter/

Bug report follow-up

is there a way to follow-up on a bug report that i submitted? i have the bug number, but would like to see if the report was understood, filled out properly and determine the status of the bug report.
thanks,
doug

They comment on bugs if actions were taken. Otherwise - don't expect any feedback.

Solaris8 and 9 (possibly 7) /dev/poll driver bug report.

Hello,
I'd like to report a bug in the solaris 8 and 9 /dev/poll driver (poll(7d)).
As i do not have a support account with sun or anything like that, there
seems to be no other way to do that here (which is of course a very sad
thing).
Bug details:
The /dev/poll device provides an ioctl-request (DP_ISPOLLED) for checking
if a particular filedescriptor is currently in the set of monitored
filedescriptors for that particular /dev/poll fd set (open /dev/poll fd).
A quote from the documentation of the poll(7d) manual page taken from
Solaris9:
"DP_ISPOLLED ioctl allows you to query if a file descriptor is already in
the monitored set represented by fd. The fd field of the pollfd structure
indicates the file descriptor of interest. The DP_ISPOLLED ioctl returns 1
if the file descriptor is in the set. The events field contains the
currently polled events. The revents field contains 0. The ioctl returns 0
if the file descriptor is not in the set. The pollfd structure pointed by
pfd is not modified. The ioctl returns a -1 if the call fails."
It says that when you query for an filedescriptor which is currently being
monitored in the set, that it would return 1, and change the events field of
the pollfd structure to the events it's currently monitoring that fd for.
The revents field would be set to zero.
However the only thing which actually happens here, is that FD_ISPOLLED
returns 1 when the fd is in the set and 0 if not. When the fd is in the
set, when FD_ISPOLLED returns 1, the events field remains unmodified, but
the revents field gets changed.
A small sample code to illustrate:
#include <stdio.h>
#include <unistd.h>
#include <sys/types.h>
#include <sys/stat.h>
#include <fcntl.h>
#include <sys/devpoll.h>
main() {
struct pollfd a;
int dp_fd = open("/dev/poll", O_WRONLY);
a.fd = 0; /* stdin */
a.events = POLLIN; /* we monitor for readability, POLLIN=1 */
a.revents = 0;
write(dp_fd, &a, sizeof(a));
a.fd = 0;
a.events = 34; /* filled in with bogus number to show malfunctioning */
a.revents = 0;
printf("DP_ISPOLLED returns: %d\n", ioctl(dp_fd, DP_ISPOLLED, &a));
printf("a.fd=%d, a.events=%hd, a.revents=%hd\n", a.fd, a.events,
a.revents);
According to the documentation of /dev/poll and namely DP_ISPOLLED this
program is supposed to print the following:
DP_ISPOLLED returns: 1
a.fd=0, a.events=1, a.revents=0
However it prints the following:
DP_ISPOLLED returns: 1
a.fd=0, a.events=34, a.revents=1
You can take any number instead of '34' and it will simply remain untouched
after the DP_ISPOLLED ioctl-request.
I hope it's clear now that the solaris8 and solaris9 (and probably solaris7
with /dev/poll patch too) DP_ISPOLLED implementation is broken.
This bug is also easily illustrated by looking at the solaris8 kernel sourcecode:
<snippet osnet_volume/usr/src/uts/common/io/devpoll.c:dpioctl()>
case DP_ISPOLLED:
pollfd_t pollfd;
polldat_t *pdp;
if (pollfd.fd < 0) {
mutex_exit(&pcp->pc_lock);
break;
pdp = pcache_lookup_fd(pcp, pollfd.fd);
if ((pdp != NULL) && (pdp->pd_fd == pollfd.fd) &&
(pdp->pd_fp != NULL)) {
pollfd.revents = pdp->pd_events;
if (copyout(&pollfd, (caddr_t)arg,
sizeof(pollfd_t))) {
mutex_exit(&pcp->pc_lock);
DP_REFRELE(dpep);
return (set_errno(EFAULT));
*rvalp = 1;
</snippet>
its' clearly visible that the code writes the current monitored events to
the revents field:
'pollfd.revents = pdp->pd_events;'
and that it doesnt set revents to zero.
It's funny to see that this has been like this since Solaris8 (possibly 7). That means nobody ever used DP_ISPOLLED that way or people were simply to lazy to file a bug report.
Another funny thing related to this. is that Hewlett-Packard did seem to know about this. Since HP-UX11i version 1.6 they also support /dev/poll. From their manual page i ll quote some sentences from their WARNING session:
"The ioctl(DP_ISPOLLED) system call also returns its result in the revents member of the pollfd structure, in order to be compatible with the implementation of the /dev/poll driver by some other vendors."
Hopefully this will get fixed.
I also like to reexpress my very negative feelings towards the fact that you're not able to file bug reports when you do not have a support contract. Ridiculous.
Thanks,
bighawk

Have I mentioned how much i love my playbook now Great job on os 2.0

Bug Report: The keyboard focus doesn't automatical...

Bug Report: When a conversation window opens, the focus doesn't automatically land in the chat entry text field.
Since the new interface for Skype was introduced officially in Skype 7.0, there is a bug with the system/keyboard focus for a new conversation window. When Skype is in "Split Window View" and each new conversation automatically pops up in a separate window, the system/keyboard focus doesn't land in the chat entry edit field. Instead, the user has to press Shift+TAB a couple of times, to move it there and reply to the chat message received. This especially problematic for screen reader users, who rely on keyboard navigation. This mainly occurs when a new conversation is started with an incoming message, but it sometimes occurs when moving the focus out of that conversation window and later back in it again (while it is still opened).
Steps to reproduce it:
1. From "View" menu, activate the "Split Window View", if it is not already enabled.
2. From Tools -> Options -> IM & SMS -> IM settings, enable "Open a new window when I receive a new message in Split Window View", if it is not already enabled.
3. From Tools -> Options -> Advanced, activate "Enable accessible mode", if it is not already enabled.
4. Activate the "Save" button, to save the changes.
5. Close all windows, related to Skype. You may keep only the main window opened.
6. Tell someone to send you a chat message. When the message arrives, Move the system focus to the conversation window in question, preferably with Alt+TAB. The system/keyboard will not land in the chat entry edit field as it did in Skype 6.21 and earlier and as it should by default, but in some unknown place in the window.
7. Move the system/keyboard focus in the chat entry edit field and keep it there.
8. Switch to another window, preferably from another application.
9. With Alt+TAB, switch back to the window of the opened Skype conversation. There is a chance that the system/keyboard focus will not land in the chat entry edit field as it did in Skype 6.21 and earlier and as it should do by default, but again in some unknown place in the conversation window. But that is harder to reproduce.
Test environment:
- Operating system: Windows 8.1 Pro N, 64-bit, in Bulgarian with all locale settings set to "Bulgarian".
- Skype version: 7.0.0.102 for Desktop.

This is a known problem, but Skype have not given us an estimated time for a fix.
Traditionally, Skype updates have been roughly monthly, so we are due a new version sometime soon. Many of us here are hoping that is has a bunch of fixes for the UI, the focus problem being one of them.
Sean Ellis - uses Skype chat for serious work
Click here to read my blog post on Skype 7 and basic principles of GUI design

Bug report: Naming a Bin after creating it with drag'n'drop

There seems to be a small bug when giving a newly created bin a name after creating it by drag'n'drop of several clips onto the "New Bin" icon.
To reproduce:
Select some clips in your project browser
Drag them onto the New Bin button
A new bin is created with the clips in it
- the bin name for it appears to be selected, and editable - just as if you had created a new empty bin by clicking the New Bin button
- type in a new name - it accepts the name fine, now press enter.
- your new name disappears, and *now* you are really in the mode to edit the bin name
- type your name again, and it works.
Work around:
When creating new bins by using drag'n'drop of clips onto the New Bin button, first press enter once to enter into the proper edit mode before giving the bin a new name.
(is there a better place to file bug reports?)
Version 6.0.1 (014 (MC: 264587))
Hardware Overview:
Model Name:          Mac Pro
Model Identifier:          MacPro5,1
Processor Name:          Quad-Core Intel Xeon
Processor Speed:          2.8 GHz
Number Of Processors:          1
Total Number Of Cores:          4
L2 Cache (per core):          256 KB
L3 Cache:          8 MB
Memory:          8 GB
Processor Interconnect Speed:          4.8 GT/s
Boot ROM Version:          MP51.007F.B03
SMC Version (system):          1.39f11
SMC Version (processor tray):          1.39f11
OS X 10.6.8

Er, just answered my question about bug reports by reading the "read this before posting" link above
But I'll leave this here for the work-around in case anyone else needs it.

Bug report, Beta 2.12 Standard Edition

Bug report: redundant, confusing, and apparently erroneous calls to
jdoPreClear
and jdoPostLoad. Note in output the null name in the third iteration.
Hi,
A lot of information being sent. Sorry, but I think you'll find it
helpful. I expected the exact same sequence of calls to jdoPreClear
and jdoPostLoad on the 2nd and third iteration. In fact, since,
retain values is true, and no changes are being made, I expected that
jdoPreClear and jdoPostLoad would not be called at all on the 2nd and
3rd iteration.
David Ezzio
Using 2.12 Beta, standard edition
Business method uses one PM. Configured to datastore transaction,
retainValues == true, non-TR == false, and non-TW == false.
The business methods open a transaction and leave it open.
The client calls commitTransaction() to close the open
transaction.
Two persistent objects, Widget and Box. Each implement
InstanceCallbacks and put out a message in jdoPreClear ("will be
made hollow") and in jdoPostLoad ("has been made persistent-clean").
The Widget has a reference to its Box. The number in parenthesis
is the sequence number obtained from the object ID.
Business methods implementation:
public ArrayList getWidgetsByName(String name)
Transaction trans = pm.currentTransaction();
if (!trans.isActive())
trans.begin();
Collection c = (Collection) widgetsByOneName.execute(name);
ArrayList aList = new ArrayList(c);
widgetsByOneName.close(c);
return aList;
public void commitTransaction()
Transaction trans = pm.currentTransaction();
if (trans.isActive())
trans.commit();
Output: from three loops that:
call findWidgetsByName("Maxi-Widget")
list the widgets returned
call commitTransaction()
finding Maxi-Widgets ...
Widget Maxi-Widget (650) has been made persistent-clean
Box Large (652) has been made persistent-clean
Widget Maxi-Widget (650): Box Large (652) at location Top Shelf
Widget Maxi-Widget (709) has been made persistent-clean
Box Large (710) has been made persistent-clean
Widget Maxi-Widget (709): Box Large (710) at location Middle Shelf
Widget Maxi-Widget (708) has been made persistent-clean
Box Large (713) has been made persistent-clean
Widget Maxi-Widget (708): Box Large (713) at location Top Shelf
Widget Maxi-Widget (700) has been made persistent-clean
Box Large (717) has been made persistent-clean
Widget Maxi-Widget (700): Box Large (717) at location Top Shelf
Widget Maxi-Widget (707) has been made persistent-clean
Box Large (716) has been made persistent-clean
Widget Maxi-Widget (707): Box Large (716) at location Top Shelf
Finding them again
finding Maxi-Widgets ...
Widget Maxi-Widget (650) will be made hollow
Widget Maxi-Widget (650): Box Large (652) at location Top Shelf
Widget Maxi-Widget (709) will be made hollow
Widget Maxi-Widget (709): Box Large (710) at location Middle Shelf
Widget Maxi-Widget (708) will be made hollow
Widget Maxi-Widget (708): Box Large (713) at location Top Shelf
Widget Maxi-Widget (700) will be made hollow
Widget Maxi-Widget (700): Box Large (717) at location Top Shelf
Widget Maxi-Widget (707) will be made hollow
Widget Maxi-Widget (707): Box Large (716) at location Top Shelf
Finding them yet again
finding Maxi-Widgets ...
Widget null (650) will be made hollow
Widget Maxi-Widget (650) has been made persistent-clean
Widget Maxi-Widget (650): Box Large (652) at location Top Shelf
Widget null (709) will be made hollow
Widget Maxi-Widget (709) has been made persistent-clean
Widget Maxi-Widget (709): Box Large (710) at location Middle Shelf
Widget null (708) will be made hollow
Widget Maxi-Widget (708) has been made persistent-clean
Widget Maxi-Widget (708): Box Large (713) at location Top Shelf
Widget null (700) will be made hollow
Widget Maxi-Widget (700) has been made persistent-clean
Widget Maxi-Widget (700): Box Large (717) at location Top Shelf
Widget null (707) will be made hollow
Widget Maxi-Widget (707) has been made persistent-clean
Widget Maxi-Widget (707): Box Large (716) at location Top Shelf
-- All done!

Due to better understanding on my part, and the fixes in Beta 2.2, the
issues raised in this thread are put to rest.
Abe White wrote:
>
We'll investigate further. Stay tuned...
"David Ezzio" <[email protected]> wrote in message
news:[email protected]..
Abe,
Actually, it doesn't make sense. The first iteration shows
jdoPostLoad is called just prior to using the fields of Widget and Box.
After the commit, the instances are not cleared. So far, so good.
In the second iteration, we see that jdoPreClear is called, but
jdoPostLoad is not called. Yet the values are there for use during the
call to Widget.toString() and Box.toString() within the iteration. How
did that happen?
On the third iteration, now the value of name is null, but last we
looked it was available in the second iteration. Other than that, I
agree that the third iteration looks ok, since it is being cleared and
loaded prior to use. But in the jdoPreClear, the values should be there
since the values were used in the previous iteration and are not cleared
at transaction commit due to retainValues == true.
David
Abe White wrote:
David --
I believe the behavior you are seeing to be correct. Section 5.6.1 of
the
JDO spec outlines the behavior of persistent-nontransactional instancesused
with data store transactions. As you can see, persistentnon-transactional
instances are cleared when they enter a transaction; thus the calls to
jdoPreClear. When the default fetch group is loaded again (like whenyou
access the name of the widget) a call to jdoPostLoad is made.
You are seeing the name of one instance as 'null' in the third iterationof
your loop because the instance has been cleared in the second iteration,and
the jdoPreClear method is not modified by the enhancer (see section10.3).
Make sense?

Bug report, how do I find out what is wrong?

my computer keeps getting bug reports stuck all over the desktop. When I print them it is 3 pages long and I dont know how to use the information from it. It only occurs when my son is using Runescape an online game. My son says he has reported all the errors when the computer prompts him to. I did find an Bug Report that seems to be associated with this problem. Our computer did shut down occasionally also, but since I switched the location of the new memory I added it has not continued. The reason I am checking with this website is because this is where the reports are going. The first part of the error report from my computer is this:
Unexpected Signal : EXCEPTION_ACCESS_VIOLATION (0xc0000005) occurred at PC=0x809D50E
Function=JVM_FindSignal+0x10882
Library=C:\PROGRA~1\Java\J2RE14~1.2\bin\client\jvm.dll
Current Java thread:
     at r.a(Unknown Source)
     at r.a(Unknown Source)
     at client.t(Unknown Source)
     at client.B(Unknown Source)
     at client.a(Unknown Source)
     at a.run(Unknown Source)
     at client.run(Unknown Source)
     at java.lang.Thread.run(Unknown Source)
And the last part of the report reads this:
Local Time = Fri Mar 04 21:38:29 2005
Elapsed Time = 58
# HotSpot Virtual Machine Error : EXCEPTION_ACCESS_VIOLATION
# Error ID : 4F530E43505002EF
# Please report this error at
# http://java.sun.com/cgi-bin/bugreport.cgi
# Java VM: Java HotSpot(TM) Client VM (1.4.2-b28 mixed mode)
What do I need to do to fix this problem? Could it be Runescapes issue? Is there other information that is more important to this? I really appreciate any help I can get with this problem. And I am sorry for being so long. I have included the Bug Report I found that is an almost exact duplicate of our issue.
Thank you again, Linda Peterson.
COPIED FROM BUG REPORT SEARCH AREA
Bug ID: 5092499
Votes 1
Synopsis IA64 - EXCEPTION_ACCESS_VIOLATION on IA664 W2003
Category java:runtime
Reported Against 1.4.2_05
Release Fixed
State In progress, bug
Related Bugs
Submit Date 26-AUG-2004
Description OS: Windows2003 [5.2.3790]
Chip: Itanium 2
JVM: Sun 1.4.2_05-b04 64-bit server VM
Error message:
EXCEPTION_ACCESS_VIOLATION (0xc0000005) occurred at PC=0x84D5F10
Function=[Unknown]
Library=C:\j2sdk1.4.2_05\jre\bin\server\jvm.dll
Error ID: 4F530E43505002EF
xxxxx@xxxxx 10/5/04 20:02 GMT
Work Around N/A
Evaluation Post tiger
xxxxx@xxxxx 2004-09-02
Comments
Include a link with my name & email
Submitted On 05-FEB-2005
JavaJava13 Hey just wondering. Java is used for runescape on my computer, and it seems to be constantly crashing lately. Not only the game is crshing, it seems to even take down the whole computer with it. Sometimes the computer restarts and I get an error message.
"Your system has recovered from a serious error"
Java continues to add error reports to my desktop with this code: 4F530E43505002EF
Anyone help?

try checking with runescapes FAQ/tech support. I play
WC3: RoC and i only got that same memory location
error(0xc0000005). I got that memory error when I
used a no-cd third party program when they upgraded
the server. So, my advice is check on the FAQ for
errors and ask your son if he is using
ANY third party programs.The 0xc0000005 error is a standard error on Windows that can occur for any number of reasons.
It means something in the application tried to access memory to which windows knows the application should not be accessing.

FAQ: I found a bug. How do I write a useful bug report? Or send bug files to Adobe?

If you think you've found a bug in Photoshop CS6, please post your findings here on the forums.
Here is a list of the information we'll want for you to gather at a minimum:
Clear and concise steps so that someone who isn't in front of your comptuer can reproduce the issue you are seeing
Include information on the operating system/version you are running. (e.g. "Mac OS 10.7.3" or "Win XP Service Pack 3")
Here are some more detailed instructions for writing a useful, complete bug report for us on the forums:
Provide a descriptive title that includes your OS information:Example: "Photoshop crashes when I save a JPEG file using the File>Save For Web & Devices... command (Mac OS 10.7.3)"
Provide concise, step-by-step details on how to reproduce the issue you are seeing.
Example:
Open an 8-bit, RGB image by selecting File>Open...
Create a new layer by clicking the "Create New Layer" button on the bottom of the Layers panel
Paint on the layer created in Step #2 using the default Brush tool
Choose File>Save For Web & Devices...
Make sure the optimized format is set to "JPEG" and set the Quality setting to "80"
Click the Save button at the bottom of the Save For Web & Devices dialog, choose the desktop as the location for saving the file
Provide a description of the "Result" you are observing:
Example: "Result: Photoshop crashes"
If there is an error dialog, please include the exact wording displayed in the dialog or provide a screen shot or video of the entire screen so we can see the dialog as well as the state of the application - i.e. what panels are shown, the state of the Layers panel, etc.
If the error is a visual defect, either in the user interface or the image itself, provide a screen shot or video of the entire screen so we can see the dialog as well as the state of the application - i.e. what panels are shown, the state of the Layers panel, etc.
Provide a description of the "Expected Result":
Example: "Expected Result: Photoshop to save JPEG file to the desktop, no crash"
In some cases this may be obvious (such as in the case of a crash) but in others, what you expect to happen may be different than what the application was designed to do. Please be as specific as possible.
Provide the crash log by submitting all crash reports, including your email address, for every single crash your encounter:
You may also include the contents of your crash log in your forum posts as well, but always submit them using the above instructions as well.
Crash logs are located on Macintosh here: Users/<your user name>/Library/Logs/CrashReporter
Provide your System Info from Photoshop: What's even more useful is if you can share your System Info from Photoshop as it contains all kinds of useful information (OS/version, graphics card, driver version, 3rd party plug-ins used, etc) that will help the team track down your issue.
On occasion, the Photoshop engineers may request that you provide problematic files in order to reproduce and debug your issue.
In these cases, please post the file somewhere using your own servers or one your favorite online document/distribution services and provide a URL/instructions to download the file:
Dropbox
Adobe SendNow
YouSendIt
If the file isn't something you can post publically, you can request that someone from the engineering team contact you to figure out a secure way to get the affected files.
Thanks,
The Photoshop Development Team

First thing would be to realise the exact error. Second would be to check your logs to see what you have installed/upgraded which might be causing this error. Third, google your error and see if matches turn up. Fourth, search in Arch bugtracker to see if a match exist. Else file a report.

FAQ: How do I submit a bug report or feature request or otherwise give feedback about Premiere Pro?

The best way to submit a bug report or feature request is to use the bug-report/feature-request form.
The Premiere Pro team doesn’t necessarily see and record every post on every forum and social network, but we do see, record, and track every entry through the the official feature-request/bug-report form.
It also helps a lot if you opt into the Product Improvement Program.
Also, be sure to use the crash reporter.
We really do read all of the bug reports and feature requests, and the software really does get a lot of benefit from detailed crash reports.
Don’t forget about contacting Adobe Technical Support or Customer Service, too. For information on how to contact Adobe Technical Support, see this page. (Note that you must register your product before you can open a technical support case for it.)
If you have tried to get help from our support staff, but the service was inadequate, I can help you to escalate your issue if you send me your case number at kopriva at adobe dot com. You must provide me a case number. I am not offering to solve your problem myself; rather, I am willing to forward your information to someone if you have already hit a dead end with our Technical Support or Customer Service.
If you have feedback about the content of the Premiere Pro Help document, then please add a comment at the bottom of the relevant page. You can add comments to add information, to add links, to make corrections, or to ask for clarification.
If you want to keep up with the Premiere Pro team, then you can follow our blogs, Facebook page, and Twitter feed and so on.
Oh, and I can’t resist this opportunity to remind you to update to the most recent version of the application. Don’t be surprised when the first thing that you hear back from us is that you need to install the latest updates. We fix a lot of things in updates, and we don’t want to go chasing bugs that we’ve already fixed. We’ll keep you posted on our blogs, Facebook page, and Twitter feed about updates as they become available.

Hi qwerty,
Dun tink that creative customer support sucks cos I had been dealing with them in the past and I can say that their service are quite gd and fast. If you wanted a refund, I tink you need to contact the store that sells you the product. Dun tink creative will refund you though.

Bug Report - Some items in your iTunes Library ... because the file could not be found.

10.6 and this is still this is a problem?!?!?!?!
Not like this is an obscure issue only affecting a few noobs. Google returns 11,200 results on this issue!t'
Can we PLEASE at least allow the list of broken files to be dumped as a text file so I can find them manually! guess not,
I'll just have to get out a pencil and write down 100 songs to spend my saturday looking up and fixing. Or I could let my wife purchase 100 songs she already has whenever this comes up...
What's really infurating is that non-technical wife thinks this means she must go to the iTunes store and buy them again. Is it just coincidence that this only happens to songs that we ripped from the CD with iTunes? Hmmmm?....
what follows is for the programmers, please make sure this get's to the development group.
iTunes is the only music library manager, Media player was not even activated.
iTunes is configured to "Keep folder organized", "Copy files to folder when adding"
this has been a recurring issue since iTunes 9.x for us
The issue is persisted accross system and library rebuilds.
some of the same songs recurr but most of the time the list differs.
Library survived transfer to new computer and back for a system rebuild (new hdd) w/o this issue.
I'm guessing 100 songs is an arbitrary limit for error reporting.
Songs seem to get lost for the following reasons.
Track number added to filename
Spelling of some tags like Album, Artist, Title differ in iTunes library and the file path !!!!
Only seems to happen to mp3 files.
My suspicion is that iTunes is downloading meta data from the store and updating the mp3 tags and iTunes Music Library.xml then predicting the new file location without actually moving the file to that new location. I've enabled insert/update auditing on the NTFS folder to see if that provided any new info. I'm also capturing iTunes Music Library.xml so I can compare it to the new one WHEN this happens again and see if there is a pattern there.
Would love a bug number and feedback chanel on this.

The missing file thing happens when files are no longer where iTunes expects to find them. Possible causes are that you or some third party tool has moved, renamed or deleted the files, or that the drive they live on has had a change of drive letter. It is also possible that iTunes has changed from expecting the files to be in the pre-iTunes 9 layout to post-iTunes 9 layout, or vice-versa, and so is looking in slightly the wrong place.
Select a track with an exclamation mark, use Ctrl-I to get info, then cancel when asked to try to locate the track. Look on the summary tab for the location that iTunes thinks the file should be. Now take a look around your hard drive(s). Hopefully you can locate the track in question. If a section of your library has simply been moved, or a drive letter has changed, it should be possible to reverse the actions.
Alternatively, as long as you can find a location holding the missing files in a relatively sensible structure, then you should be able to use my FindTracks script to reconnect them to iTunes .
Although you say you haven't used Media Player it can be raised as a background process by visiting enabled web sites. Possibly worth you reviewing this post: Getting iTunes & Windows Media Player to play nicely
jerunamuck wrote:
...My suspicion is that iTunes is downloading meta data from the store and updating the mp3 tags and iTunes Music Library.xml then predicting the new file location without actually moving the file to that new location. I've enabled insert/update auditing on the NTFS folder to see if that provided any new info. I'm also capturing iTunes Music Library.xml so I can compare it to the new one WHEN this happens again and see if there is a pattern there.
Unlike Windows Media player iTunes doesn't have a feature to automatically update tag data, although it will sometimes spot when a 3rd party program has (say during playback) and then update its own copy of the data. The iTunes (Music) Library xml file is provided for querying by third party software and is rewritten every time there is a change to the library, but is otherwise of no relevance to iTunes. The library is maintained in the iTunes Library.itl file. I suppose what could be happening is that iTunes issues a command to the file system to move a file based upon its tag, updates its knowledge of where the file is supposed to be, but the OS fails to move the file for some reason. Alternatively everything could go as planned, but iTunes could fail to get the updated copy of the library written out to disk so next time you start you get the previously stored locations.
I have ideas of my own about the best way to organise my media, but I'm quite familiar with the way iTunes does it. It might be interesting to see the details of one of the broken tracks, the path iTunes thinks it is at, and the actual path, in case there is anything that can be deduced.
Apple don't run an open bug tracking system so you won't be able to follow reports/progress based on a bug number. You can drop a line to iTunes Feedback or get a free Apple Developer account and submit a bug report report there.
tt2

Bug report: vpn (ipsec) interface number in snmp always change

Similar Messages

Maybe you are looking for