This is my first question here, so hope it's correctly done.
Im trying to get some information from a Epson L365. The thing is when i try to get the Total page printed, I get the response in HEX-String
.1.3.6.1.4.1.1248.1.2.2.1.1.1.4.1 0x40 42 44 43 20 53 54 32 0D 0A 62 00 01 01 04 06 02 01 00 0F 0D 03 01 00 69 03 01 69 04 02 69 05 03 69 10 03 01 09 4E 13 01 01 19 0C 00 00 00 00 00 75 6E 6B 6E 6F 77 6E 24 02 00 00 28 04 FF 01 00 00 2F 01 01 36 14 FF FF FF FF FF FF FF FF DB 2C 00 00 09 09 00 00 A0 00 00 00 37 05 02 00 00 00 00 40 0A 58 32 4E 5A 34 36 31 33 39 31 OctetString
And this is the response that I get
.1.3.6.1.4.1.1248.1.2.2.1.1.1.4.1 #BDC ST2 b......... ...i..i..i..i... N..........unknown$...(...../..6..........,.. ......7......# X2NZ461391 OctetString
I have already researched and do not know where to go.
I want to build a system for counting people based on wifi packets. I am using esp8266 for sniffing packets. But i read that android and iphones are now randomizing mac ids when they are not connected to any network. I thought of using probe requests but i saw that whenever i press refresh in mobile, the mac address is changed. So my program would detect it as a new device.
This is what i am getting in different packets from the same device.
Mac Address - da a1 19 9f bb 5c
d4 10 68 50 00 00 00 00 00 00 05 00 40 00 00 00 ff ff ff ff ff ff **da a1 19 9f bb 5c** ff ff ff ff ff ff e0 a4 00 0b 77 69 66 69 63 68 61 68 69 79 65 01 04 02 04 0b 16 32 08 0c 12 18 24 30 48 60 6c 03 01 04 2d 1a 6e 01 03 ff 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 dd 07 00 50 f2 08 00 00 00 7f 05 00 00 0a 02 01 3d 16 04 05 01 00 00 00 00 00 00 00 01 00 68 00
Mac Address - da a1 19 00 44 2f
d3 10 2e 50 00 00 00 00 00 00 0c 00 40 00 00 00 ff ff ff ff ff ff **da a1 19 00 44 2f** ff ff ff ff ff ff 90 c1 00 00 01 08 02 04 0b 16 0c 12 18 24 32 04 30 48 60 6c 00 00 34 34 50 43 01 08 82 84 8b 96 12 24 48 6c 03 01 0b 32 04 0c 18 30 60 07 06 49 4e 20 01 0d 14 23 02 13 00 46 05 f3 c0 01 00 04 05 04 00 01 00 14 dd 1a 00 50 f2 01 01 00 00 50 f2 02 02 00 00 50 f2 02 00 50 01 00 2e 00
Mac Address - da a1 19 ea d3 58
d7 10 67 50 00 00 00 00 00 00 03 00 40 00 00 00 ff ff ff ff ff ff **da a1 19 ea d3 58** ff ff ff ff ff ff a0 c2 00 0a 5a 54 45 2d 4b 62 72 79 59 47 01 04 02 04 0b 16 32 08 0c 12 18 24 30 48 60 6c 03 01 01 2d 1a 6e 01 03 ff 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 dd 07 00 50 f2 08 00 00 00 7f 05 00 00 0a 02 01 00 d7 75 eb 1d 7c e1 2f 06 a2 2c a3 df 01 00 67 00
I don't want to track individual user, my goal is to count the number of people in an area. Can I use any other packet type than probe request ? or will there be some similarity in probe request packets originating from same device, that way I can discard the new packet from the same device even if the source address (mac address) is changed.
So Im trying to create a new db_space for my informix database.
I already created a file ( /matiasInformixDBSpaces/dbspace_proyectoUTU ) and gave necessary permissions to the informix user and group.
Now, logged in as root user I am attempting to create a new db_space. The first one was 500 MB and this one I intended to be 1 GB. the problem I am facing is that when I run the command below, it says "Verifying physical disk space, please wait..." and it just stays there forever.
No errors or warnings are thrown. The first time I did it it was super fast. I dont know what is going on now.
onspaces -c -d proyectoUTUinformix -p /matiasInformixDBSpaces/dbspace_proyectoUTU -o 5000 -s 1000240
Can someone help me to figure out what is going wrong?
Steps towards diagnosis
I’m curious about why you have a non-zero offset. If the name refers to a raw device and the volume manager uses the start, then it makes sense. Otherwise, it is rare to use a non-zero offset. However, that has a negligible effect on speed; it just wastes a little space.
Please identify your platform, and the version of Informix you are using.
Have you looked at the size of the file from another terminal window?
$ a6 timecmd -m -- onspaces -c -d auxilliary -p /opt/informix/dev/$IXS.auxilliary.c0 -o 0 -s 1000240
2018-04-16 22:27:07.348 [PID 71071] onspaces -c -d auxilliary -p /opt/informix/dev/osiris_19.auxilliary.c0 -o 0 -s 1000240
Verifying physical disk space, please wait ...
Space successfully added.
** WARNING ** A level 0 archive of Root DBSpace will need to be done.
2018-04-16 22:27:07.969 [PID 71071; status 0x0000] - 0.620s
$
I ran the command above on my own Mac (running macOS 10.13.4, with Informix 12.10.FC6 — I need to upgrade!) having created the empty file and set the permissions. This Mac has solid-state disk (SSD). The a6 command runs programs 'as informix'; the timecmd echoes more timing information than the simple time command — start time, command executed, PID, and then finish time, exit status and duration. I use it more for long-running commands, where knowing that it started a couple of hours ago is helpful.
Clearly, 0.620s is quick — essentially immediate. It shouldn't take very long on your system — a few seconds at most — to write a file that's 1,024,245,760 bytes long, which is the size of the file I ended up with.
So, you need to look hard at the disk you're using. If it's a memory stick, or a remote mounted file system connected via a modem line, then it could take a long time. But a mainstream SSD or spinning disk shouldn't take very long at all.
Given what's happened, interrupt the command. Review what's in your online log file — onstat -m for me showed:
05:27:07 Space 'auxilliary' added.
05:30:18 Space 'auxilliary' dropped.
I run my servers in UTC time zone; I'm in US/Pacific, currently UTC-7. Hence 22:27 locally corresponds to 05:27 in UTC.
Obviously, the 'dropped' message corresponded to my onspaces -d auxilliary command, run about three minutes after the add command. If you can't find a 'space added' message in your online log file, then the operation failed. If you find a 'space added' message, your terminal froze. (You didn't type control-S in it, did you? Try a control-Q to restart it.) You'll need to do the archive mentioned, of course (there's one required after the drop, too) if the space was added.
Try using:
time dd if=/dev/zero of=/matiasInformixDBSpaces/dbspace_proyectoUTU bs=1024 count=1000240
and see how long that takes. I ran:
$ a6 timecmd -m -- dd if=/dev/zero of=/opt/informix/dev/$IXS.auxilliary.c0 bs=1024 count=1000240
2018-04-16 22:43:05.006 [PID 71161] a6 dd 'if=/dev/zero' 'of=/opt/informix/dev/osiris_19.auxilliary.c0' 'bs=1024' 'count=1000240'
1000240+0 records in
1000240+0 records out
1024245760 bytes transferred in 6.740104 secs (151962902 bytes/sec)
2018-04-16 22:43:11.765 [PID 71161; status 0x0000] - 6.758s
$
That's much longer than the onspaces command, which means that onspaces did not write to every block in the disk file. When I analyzed the content of the file, I got:
$ a6 timecmd -m -- odx $opt/$IXS.auxilliary.c0
2018-04-16 23:10:26.836 [PID 71321] odx /opt/informix/dev/osiris_19.auxilliary.c0
0x0000: 00 00 00 00 04 00 50 35 00 00 00 18 18 00 E4 0F ......P5........
0x0010: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
* (253)
0x0FF0: 00 00 00 00 00 00 00 00 00 00 00 00 42 35 16 00 ............B5..
0x1000: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
* (255)
0x2000: 02 00 00 00 04 00 50 35 01 00 08 08 20 00 D8 0F ......P5.... ...
0x2010: 00 00 00 00 00 00 00 00 35 00 00 00 97 D0 03 00 ........5.......
0x2020: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
* (252)
0x2FF0: 00 00 00 00 00 00 00 00 18 00 08 00 40 35 16 00 ............#5..
0x3000: 03 00 00 00 04 00 55 35 00 00 04 08 18 00 E4 0F ......U5........
0x3010: 00 00 00 00 00 00 00 00 03 00 00 00 00 00 00 00 ................
0x3020: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
* (252)
0x3FF0: 00 00 00 00 00 00 00 00 00 00 00 00 44 35 16 00 ............D5..
0x4000: 04 00 00 00 04 00 51 35 05 00 02 08 D4 00 14 0F ......Q5........
0x4010: 00 00 00 00 00 00 00 00 01 00 40 00 01 28 00 00 ..........#..(..
0x4020: 88 00 00 00 00 00 00 00 01 00 00 10 12 8F D5 5A ...............Z
0x4030: 01 00 00 00 32 00 00 00 32 00 00 00 32 00 00 00 ....2...2...2...
0x4040: 02 00 00 00 00 00 00 00 FF FF FF FF 01 00 40 00 ..............#.
0x4050: 01 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
0x4060: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
0x4070: 00 00 00 00 01 00 00 00 00 00 00 00 01 00 00 00 ................
0x4080: 01 00 00 00 00 00 00 00 01 00 00 00 0C 00 00 00 ................
0x4090: 18 00 6D 00 00 00 00 00 00 00 00 00 00 00 00 00 ..m.............
0x40A0: 61 75 78 69 6C 6C 69 61 72 79 00 69 6E 66 6F 72 auxilliary.infor
0x40B0: 6D 69 78 00 54 42 4C 53 70 61 63 65 00 00 00 00 mix.TBLSpace....
0x40C0: 00 00 00 00 00 04 00 00 00 03 00 00 00 32 00 00 .............2..
0x40D0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
* (240)
0x4FE0: 00 00 00 00 00 00 00 00 C0 00 14 00 C0 00 00 00 ................
0x4FF0: C0 00 00 00 A0 00 20 00 18 00 88 00 47 35 16 00 ...... .....G5..
0x5000: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
* (64014079)
0x3D0CC000:
2018-04-16 23:10:30.808 [PID 71321; status 0x0000] - 3.971s
$
As you can see, some control information was written into the first 0x5000 bytes, but thereafter, the file was all null bytes. I'm not quite sure what it means by 'verifying physical disk space' given that the sub-second timing for onspaces means that it did not actually write to the space.
Resolution
If you follow the discussion in the comments below, you will see that the cause of the hold up was that the system was in the state CKPT REQ (checkpoint required). This could be seen from onstat output, for example. To get past that, either new logs needed to be added or the logical logs needed to be backed up.
Caution: By setting the backup device to /dev/null, you can let the server run without getting blocked, which might be OK while setting up the system, but won't be a good idea in production.
Check out the Backup and Restore Guide to learn about ON-BAR and ON-Tape, the two possible backup systems.
A lot depends on the context where you'll be running the server. If there's already a system for running backups that uses the BSA interface, using ON-BAR to integrate with that may be most appropriate. If you don't have such a corporate backup system, then ON-Tape may be simpler.
Before you go into production, please ensure you have a proper backup strategy, and you have practiced both backups and restores of the system.
You need to be confident that your backups work. You need to be confident that you know how to use them.
Do make sure your disks are not hard-wired directly to device names. You can use symlinks, or use the names of files. You need to be able to relocate the data, and hard-wired device names can make that difficult.
I am working with pcap in C and comparing the lengths of EAPOL handshakes with those get in wireshark, and the EAPOL packets captured with pcap are longer. The strange thing is that the added length is variable, some days it adds a header of 26 bytes and a footer of 4, making a 185 bytes packet (instead of the 155 byte in wireshark for the first message of the handshake). Some days it adds a 18 byte header with no footer, making a 173 byte packet. When it captures a packet of a certain length, it keeps that format for the whole day and the next day it switches to the other one.
I have read this Libpcap File Format but the lengths of those headers don't fill the gap, and wireshark doesn't show Radiotap Headers so I guess I don't have any. The captured packet comes always between the same devices and wireshark returns always the same length.
Anyone knows what is going on here? Thanks in advance guys!
As requested, I add some examples of the packets captured. For the sake of clarity I will paste only the first message of the handshake, and only for the 185 byte case, as it is the length I get today:
As captured by pcap (185 bytes). Extra bytes in bold:
00 00 1a 00 2f 48 00 00 f3 7c 7b 00 00 00 00 00 10 02 85 09 a0 00 db 01 00 0088 02 3a 01 85 74 13 51 b4 a8 d8 b7 b8 17 92 81 d8 b7 b8 17 92 81 00 00 00 00 aa aa 03 00 00 00 88 8e 02 03 00 75 02 00 8a 00 10 00 00 00 00 00 00 00 03 ed 35 bb b6 7d d9 0a 43 ba aa 09 23 f1 f6 6e c9 25 f3 13 c3 91 1c cd ae f5 47 98 0e 6b 15 7a fe 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 16 dd 14 00 0f ac 04 c2 8c 80 68 37 d8 87 fa 37 ab bd 07 1f c3 96 eecb f9 0b 91
The EAPOL packet as shown in Wireshark (155 bytes):
88 02 3a 01 85 74 13 51 b4 a8 d8 b7 b8 17 92 81 d8 b7 b8 17 92 81 00 00 00 00 aa aa 03 00 00 00 88 8e 02 03 00 75 02 00 8a 00 10 00 00 00 00 00 00 00 03 ed 35 bb b6 7d d9 0a 43 ba aa 09 23 f1 f6 6e c9 25 f3 13 c3 91 1c cd ae f5 47 98 0e 6b 15 7a fe 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 16 dd 14 00 0f ac 04 c2 8c 80 68 37 d8 87 fa 37 ab bd 07 1f c3 96 ee
This question already has answers here:
jcop applet upload error
(3 answers)
Closed 9 years ago.
i am new to java card development.i have jcop 31(36k) card and scl010 reader.i have install jcop plugin for eclipse.when i run my helloworld java applet in simulater(using jcop shell) it works fine.now i want to upload .cap file in to my card.i thought the way is uploading .cap file in to card run the applet in reader.(i don't know it is the best way i have attached the process i followed). when i load cap file it gives this error
**upload -b 250 "C:\Projects\Javacard\MytestThree\bin\hms\javacard\testthree\javacard\testthree.cap"
=> 80 E6 02 00 15 08 6D 79 61 70 70 6C 65 74 08 A0 ......myapplet..
00 00 00 03 00 00 00 00 00 00 00 ...........
(26209 usec)
<= 00 90 00 ...
Status: No Error
=> 80 E8 00 00 FA C4 82 01 65 01 00 29 DE CA FF ED ........e..)....
02 02 04 00 01 08 6D 79 61 70 70 6C 65 74 16 68 ......myapplet.h
6D 73 2F 6A 61 76 61 63 61 72 64 2F 74 65 73 74 ms/javacard/test
74 68 72 65 65 02 00 21 00 29 00 21 00 10 00 0B three..!.).!....
00 2E 00 0E 00 7F 00 18 00 12 00 00 00 71 02 F0 .............q..
00 02 00 01 00 0B 01 01 00 04 00 0B 01 02 01 07 ................
A0 00 00 00 62 01 01 03 00 10 01 0C 6D 79 61 70 ....b.......myap
70 6C 65 74 2E 61 70 70 00 08 06 00 0E 00 00 00 plet.app........
80 03 00 FF 00 07 01 00 00 00 1C 07 00 7F 00 01 ................
10 18 8C 00 03 7A 05 30 8F 00 09 3D 8C 00 06 18 .....z.0...=....
1D 04 41 18 1D 25 8B 00 02 7A 02 23 18 8B 00 01 ..A..%...z.#....
60 03 7A 19 8B 00 05 2D 1A 03 25 11 00 FF 53 5B `.z....-..%...S[
32 1A 04 25 11 00 FF 53 5B 29 04 1F 10 80 6A 08 2..%...S[)....j.
11 6E 00 8D 00 00 16 04 73 00 10 FF 80 FF 80 00 .n......s.......
09 18 19 8C 00 07 70 08 11 6D 00 8D 00 00 7A 05 ......p..m....z.
22 19 8B 00 05 2D 7B 00 0A 92 32 7B 00 0A 03 00 "....-{...2{....
(779869 usec)
<= 6A 80 j.
Status: Wrong data
jcshell: Error code: 6a80 (Wrong data)
jcshell: Wrong response APDU: 6A80
Unexpected error; aborting execution**
can anyone tell me what is wrong and it is help to give me some reference!
Try with -b 230 instead. -b 250 could work if the Global Platform channel was fully plain, but if it contains a 8 byte MAC over the command data then you would get a total command data size of 250 + 8 = 258, which is over the maximum of 255 bytes that is supported.
Note that 6A80 wrong data can mean a whole lot of things. You can get the same message if you have compiled/converted against the wrong target platform, for instance. ISO 7816-4 status words are not very helpful in that regard. They may show some syntax errors, but normally semantic errors are shoe-horned into these syntax errors as well.