search for: 0xa2

...0x95 0x01 0x15 0x00 0x27 0xff 0xff 0x00 0x00 0x67 0x21 0xd1 0xf0 0x00 0x55 0x01 0xb1 0x02 0xc0 0x85 0x11 0x09 0x5a 0x75 0x08 0x95 0x01 0x15 0x01 0x25 0x03 0x65 0x00 0x55 0x00 0xb1 0x82 0x09 0x02 0xa1 0x02 0x85 0x32 0x75 0x01 0x95 0x07 0x15 0x00 0x25 0x01 0x81 0x03 0xb1 0x03 0x09 0x62 0x95 0x01 0xb1 0xa2 0x09 0x62 0x81 0xa2 0xb1 0x01 0x81 0x01 0x09 0x69 0xb1 0xa2 0x09 0x69 0x81 0xa2 0x95 0x06 0xb1 0x01 0x81 0x01 0x05 0x85 0x09 0xd0 0x95 0x01 0x81 0xa2 0x09 0xd0 0xb1 0xa2 0x81 0x01 0xb1 0x01 0x95 0x06 0x09 0x42 0x09 0x46 0x09 0x44 0x09 0x45 0x09 0x47 0x09 0x4b 0x81 0xa2 0x09 0x42 0x09 0x46 0x09 0x44...

...ockets, oplocks, etc) and I couldn't improve the performance, so I decide to go for an snoop on the network card serving samba and I'm getting a few messages that I don't understand (see below); Anyone could give me a hand to get this? 0.00052 10.32.3.36 -> zeusv480 SMB C Code=0xa2 Name=SMB NT_CreateX FileName=???????????????????????????????c Error=0 0.00022 zeusv480 -> 10.32.3.36 SMB C Code=0x24 Name=SMBlockingX FileID=0x136d #Unlocks=0x0 #Locks=0x0 Error=0 0.00024 10.32.3.36 -> zeusv480 SMB C Code=0x24 Name=SMBlockingX FileID=0x136d #Unlocks=0x0 #Locks...

Hi Everyone, I'm having trouble getting TrippLite SMX1500LCDT to work on FreeBSD 11.2, nut 2.7.4 installed from FreeBSD port. The debug output is rather big when I'm starting usbhid-ups initially, Please find that attached (gzipped to comply with message size limit). Subsequently, until I unplug and replug the USB cable, I'm geting a shorter debug output, like this: Network UPS

...0x95 0x01 0x15 0x00 0x27 0xff 0xff 0x00 0x00 0x67 0x21 0xd1 0xf0 0x00 0x55 0x01 0xb1 0x02 0xc0 0x85 0x11 0x09 0x5a 0x75 0x08 0x95 0x01 0x15 0x01 0x25 0x03 0x65 0x00 0x55 0x00 0xb1 0x82 0x09 0x02 0xa1 0x02 0x85 0x32 0x75 0x01 0x95 0x07 0x15 0x00 0x25 0x01 0x81 0x03 0xb1 0x03 0x09 0x62 0x95 0x01 0xb1 0xa2 0x09 0x62 0x81 0xa2 0xb1 0x01 0x81 0x01 0x09 0x69 0xb1 0xa2 0x09 0x69 0x81 0xa2 0x95 0x06 0xb1 0x01 0x81 0x01 0x05 0x85 0x09 0xd0 0x95 0x01 0x81 0xa2 0x09 0xd0 0xb1 0xa2 0x81 0x01 0xb1 0x01 0x95 0x06 0x09 0x42 0x09 0x46 0x09 0x44 0x09 0x45 0x09 0x47 0x09 0x4b 0x81 0xa2 0x09 0x42 0x09 0x46 0x09 0x44...

...0x22 0x85 0x05 0x09 0x8b 0xb1 0x22 0x85 0x06 0x09 0x2c 0xb1 0x22 0x85 0x07 0x75 0x08 0x95 0x05 0x25 0x64 0x09 0x83 0x09 0x8d 0x09 0x8e 0x09 0x8c 0x09 0x67 0xb1 0x22 0x95 0x01 0x25 0x41 0x15 0x14 0x09 0x29 0xb1 0x22 0x25 0x64 0x15 0x00 0x85 0x08 0x75 0x08 0x65 0x00 0x09 0x66 0x81 0x22 0x09 0x66 0xb1 0xa2 0x09 0x68 0x75 0x10 0x27 0xff 0xff 0x00 0x00 0x66 0x01 0x10 0x81 0x22 0x09 0x68 0xb1 0xa2 0x09 0x2a 0x26 0x58 0x02 0x81 0x22 0x09 0x2a 0xb1 0xa2 0x85 0x09 0x75 0x10 0x27 0xff 0xff 0x00 0x00 0x05 0x84 0x09 0x40 0x67 0x21 0xd1 0xf0 0x00 0x55 0x06 0xb1 0x22 0x85 0x0a 0x09 0x30 0xb1 0xa2 0x65 0x00 0x55...

...0x95 0x01 0x15 0x00 0x27 0xff 0xff 0x00 0x00 0x67 0x21 0xd1 0xf0 0x00 0x55 0x01 0xb1 0x02 0xc0 0x85 0x11 0x09 0x5a 0x75 0x08 0x95 0x01 0x15 0x01 0x25 0x03 0x65 0x00 0x55 0x00 0xb1 0x82 0x09 0x02 0xa1 0x02 0x85 0x32 0x75 0x01 0x95 0x07 0x15 0x00 0x25 0x01 0x81 0x03 0xb1 0x03 0x09 0x62 0x95 0x01 0xb1 0xa2 0x09 0x62 0x81 0xa2 0xb1 0x01 0x81 0x01 0x09 0x69 0xb1 0xa2 0x09 0x69 0x81 0xa2 0x95 0x06 0xb1 0x01 0x81 0x01 0x05 0x85 0x09 0xd0 0x95 0x01 0x81 0xa2 0x09 0xd0 0xb1 0xa2 0x81 0x01 0xb1 0x01 0x95 0x06 0x09 0x42 0x09 0x46 0x09 0x44 0x09 0x45 0x09 0x47 0x09 0x4b 0x81 0xa2 0x09 0x42 0x09 0x46 0x09 0x44...

...???????? Data Variable Absolute No_Wrap Linear > ??????????????????????????? No_Preferred_State No_Null_Position > Non_Volatile Bitfield > ??????????? Item(Local ): Usage, data= [ 0x66 ] 102 > ??????????????????????????? Remaining Capacity > ??????????? Item(Main? ): Feature, data= [ 0xa2 ] 162 > ??????????????????????????? Data Variable Absolute No_Wrap Linear > ??????????????????????????? No_Preferred_State No_Null_Position Volatile > Bitfield > ??????????? Item(Global): Usage Page, data= [ 0x84 ] 132 > ??????????????????????????? Power Device Page > ???????????...

...0x09 0x8b 0xb1 0x22 0x85 0x06 0x09 0x2c 0xb1 0x22 0x85 0x07 0x75 0x08 0x95 > 0x05 0x25 0x64 0x09 0x83 0x09 0x8d 0x09 0x8e 0x09 0x8c 0x09 0x67 0xb1 0x22 0x95 > 0x01 0x25 0x41 0x15 0x14 0x09 0x29 0xb1 0x22 0x25 0x64 0x15 0x00 0x85 0x08 0x75 > 0x08 0x65 0x00 0x09 0x66 0x81 0x22 0x09 0x66 0xb1 0xa2 0x09 0x68 0x75 0x10 0x27 > 0xff 0xff 0x00 0x00 0x66 0x01 0x10 0x81 0x22 0x09 0x68 0xb1 0xa2 0x09 0x2a 0x26 > 0x58 0x02 0x81 0x22 0x09 0x2a 0xb1 0xa2 0x85 0x09 0x75 0x10 0x27 0xff 0xff 0x00 > 0x00 0x05 0x84 0x09 0x40 0x67 0x21 0xd1 0xf0 0x00 0x55 0x06 0xb1 0x22 0x85 0x0a > 0x09 0x30 0xb1...

Hi, I have an UPS with only the marking D1000 on it and it came with Junda-Tech's UpsMate. Its USB id is 3344:0025, which is apparently a microprocessor. I've could get some of the HID interactions as described on the website, but there are some outstanding. Junda-Tech does not respond to any queries. Does anybody else have the same or a similar UPS with more information? What is the

Hi, I just want to know if somebody use 2.6.31.4 xenified kernel (aka OpenSUSE) in production? We have been testing it on new Nehalem Xeon server for few weeks w/o any problem. But as soon we tried it on production machine - after several production domUs started - hard OS failure. We had to switch back to 2.6.18.8 - xen stock kernel. Peter _______________________________________________

>> >> The output was also not as big as you made it out to be. > > Well, I didn't expect the driver to fail *that* badly :-) > > Assuming the UPS is still at /dev/ugen4.2, can you try the following command? (Probably needs to be run as root, with the driver stopped.) > > usbconfig -u 4 -a 2 dump_curr_config_desc Here is output of the command. Thank you for

> What does that revision number correspond to in FreeBSD release numbers? (e.g. 9.3, 10.0) FreeBSD 10.2-RELEASE #0 r286738M the last person probably wasn't able to give the ./configure probably because most people uses the precompiled iso to install NAS4Free.? if you need the ./configure I might have to look for their source on GitHub or something. /usr/local/libexec/nut/usbhid-ups -a

...s and they are surprisingly quite disparate in content. I've included them here for your inspection (my apologies for the length). (Unrelated packets have been filtered out). Your comments/opinions are very welcome. ***** SUCCESS ***** 81 0.82899 winclient -> sambaserver SMB C Code=0xa2 Name=SMB NT_CreateX FileName=?????i???????????????????????????????????????????????????????????????? ?????????????????????????????????????????????????????????? Error=0 82 0.00880 sambaserver -> winclient SMB R Code=0xa2 Name=SMB NT_CreateX FileID=0xd Error=0 83 0.00069 winclient ->...

...cal Maximum, data= [ 0xff 0xff 0x00 0x00 ] 65535 Item(Global): Report Size, data= [ 0x10 ] 16 Item(Global): Report ID, data= [ 0x35 ] 53 Item(Local ): Usage, data= [ 0x68 ] 104 Run Time To Empty Item(Main ): Input, data= [ 0xa2 ] 162 Data Variable Absolute No_Wrap Linear No_Preferred_State No_Null_Position Volatile Bitfield Item(Global): Report ID, data= [ 0x35 ] 53 Item(Local ): Usage, data= [ 0x68 ] 104 Run Time T...

...uite disparate in content. I've included them here for > your inspection (my apologies for the length). (Unrelated packets have > been filtered out). Your comments/opinions are very welcome. > > ***** SUCCESS ***** > > 81 0.82899 winclient -> sambaserver SMB C Code=0xa2 Name=SMB > NT_CreateX > FileName=?????i???????????????????????????????????????????????????????????????? > > ?????????????????????????????????????????????????????????? Error=0 > 82 0.00880 sambaserver -> winclient SMB R Code=0xa2 Name=SMB > NT_CreateX FileID=0xd Error=0...

...Flags: 0x18 (PSH, ACK) Window size: 65700 (scaled) Checksum: 0xf3d6 [validation disabled] [SEQ/ACK analysis] NetBIOS Session Service SMB (Server Message Block Protocol) SMB Header Server Component: SMB [Response in: 110] SMB Command: NT Create AndX (0xa2) NT Status: STATUS_SUCCESS (0x00000000) Flags: 0x18 Flags2: 0xc807 Process ID High: 0 Signature: 0000000000000000 Reserved: 0000 Tree ID: 4 (\\UNREAL\PROFDATA) Process ID: 980 User ID: 102 (LARC\jon) Multipl...

On Sun, 7 Jun 2015, Charles Lepple wrote: > [please use reply-all to include the list, as the list does not override the Reply-To header.] > > On Jun 7, 2015, at 5:02 PM, Greg Hersch <hersch.greg at gmail.com> wrote: > >> Here is the driver debug log. If I just let it run, it pops up with >> libusb_get_string_invalid argument over and over again, mixed in the

...e No_Wrap Linear No_Preferred_State No_Null_Position Volatile Bitfield Item(Global): Report ID, data= [ 0x0f ] 15 Item(Local ): Usage, data= [ 0x8c ] 140 Warning Capacity Limit Item(Main ): Feature, data= [ 0xa2 ] 162 Data Variable Absolute No_Wrap Linear No_Preferred_State No_Null_Position Volatile Bitfield Item(Global): Report ID, data= [ 0x11 ] 17 Item(Local ): Usage, data= [ 0x29 ] 41 Remaining C...

Sorry Martin to bother you again! I have an ISDN flux with 100 numbers. The local PSTN is sending now the DNIS/DID (so they said!!!) (I have set the immediate=no in zapata.conf) but I have the same problem as before : NOTE : the number is alphanumeric-DID alphanumeric (I will make tests with numeric mumber!). WARNING[9226]: File chan_zap.c, Line 5275 (pri_fixup): Call specified, but not

...t to Samba shares when authenticating with Kerberos. Basically, the Leopard Macs insert a few extra bytes (Padding and reqFlags, according to wireshark) into the security blob within the Session Setup AndX Request packet, bytes whose start tag is 0xa1, in a spot where Samba's parser expects 0xa2. The critical error is "Failed to parse negTokenTarg at offset 54", which looks like it's being caused by the call asn1_start_tag(&data, ASN1_CONTEXT(2)); in parse_negTokenTarg(). Here's an excerpt from the smbd log with debug=10: [2008/08/01 16:07:07, 3] smbd/proce...