search for: 4f

hi all, i got flooded by these msgs like 1000+ lines, any idea? my kernel is dated Nov-30 FreeBSD 4.9-stable # tail -f /var/log/messages Jan 18 19:43:23 xb /kernel: arp: 202.79.180.1 moved from 00:04:5a:49:eb:74 to 00:50:0f:4f:c0:00 on rl0 Jan 18 19:45:06 xb /kernel: arp: 202.79.180.1 moved from 00:50:0f:4f:c0:00 to 00:04:5a:49:eb:74 on rl0 Jan 18 19:45:18 xb /kernel: arp: 202.79.180.1 moved from 00:04:5a:49:eb:74 to 00:50:0f:4f:c0:00 on rl0 Jan 18 19:45:41 xb /kernel: arp: 202.79.180.1 moved from 00:50:0f:4f:c0:00 to 00...

...= Backup path = /bkp read only = No inherit acls = Yes hide files = /Thumbs.db/lost+found force create mode = 0770 directory mask = 0770 force user = root force group = samba-domain-admins browseable = no *smbd.log* Found policy hnd[0] [0000] 00 00 00 00 05 00 00 00 00 00 00 00 03 4F D4 6A ........ .....O.j [0010] 86 15 00 00 .... [2012/01/03 20:53:40.219505, 4] rpc_server/rpc_handles.c:232(find_policy_by_hnd_internal) Found policy hnd[0] [0000] 00 00 00 00 05 00 00 00 00 00 00 00 03 4F D4 6A ........ .....O.j [0010] 86 15...

...any cost. Further to your reply , i have run the tcpdump on the firewall system while pinging from the dmz system. As you told there is a problem. Now what I need to do. I attach herewith the tcpdump output. Please reply. Regards Siva -------------- next part -------------- 23:00:13.367010 0:c0:4f:4d:fd:a4 0:3:40:90:2:9c ip 74: 203.124.152.67 > 203.124.152.65: icmp: echo request 23:00:13.401100 0:3:40:90:2:9c 0:5:5d:4a:3b:7c ip 74: 203.124.152.65 > 203.124.152.67: icmp: echo reply 23:00:14.867321 0:c0:4f:4d:fd:a4 0:3:40:90:2:9c ip 74: 203.124.152.67 > 203.124.152.65: icmp: echo requ...

...t; put. Is this just an example of implementation or does a size of 764 > BYTES kept as a place holder for putting more data? Yes, opusenc does reserve some space in the header so that tags can later be modified "in place", without having to rewrite the entire file. Jean-Marc > 4f 67 67 53 = Oggs > 00 = Version > 00 = Header > 00 00 00 00 00 00 00 00 = Granule Position > a5 73 00 00 = Bit Stream Serial Number > 01 00 00 00 = Page Sequence Numner > 90 a9 36 42 = Checksum > 03 = Page Segments > ff ff fe = Each Segment Size (TOTAL SIZE IS 764 BYTES) >...

...caching is enabled [ 172.936515] device label srv devid 4 transid 11292 /dev/sdf [44106.091461] ata4.01: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0 [44106.091470] ata4.01: BMDMA stat 0x64 [44106.091478] ata4.01: failed command: READ DMA EXT [44106.091492] ata4.01: cmd 25/00:08:a0:ca:72/00:00:4f:00:00/f0 tag 0 dma 4096 in [44106.091495] res 51/40:00:a3:ca:72/40:00:4f:00:00/f0 Emask 0x9 (media error) [44106.091503] ata4.01: status: { DRDY ERR } [44106.091508] ata4.01: error: { UNC } [44106.120384] ata4.00: configured for UDMA/133 [44106.128349] ata4.01: configured for UDMA/133 [441...

...write_socket(5,4) wrote 4 got smb length of 164 got message type 0x0 of len 0xa4 03/22/1999 07:30:04 Transaction 1 of length 168 size=164 smb_com=0x72 smb_rcls=0 smb_reh=0 smb_err=0 smb_flg=0 smb_flg2=0 smb_tid=0 smb_pid=43 smb_uid=0 smb_mid=143 smt_wct=0 smb_bcc=129 [000] 02 50 43 20 4E 45 54 57 4F 52 4B 20 50 52 4F 47 .&..+... |...&.|. [010] 52 41 4D 20 31 2E 30 00 02 4D 49 43 52 4F 53 4F ..(..... .(...|.| [020] 46 54 20 4E 45 54 57 4F 52 4B 53 20 31 2E 30 33 ...+...| ........ [030] 00 02 4D 49 43 52 4F 53 4F 46 54 20 4E 45 54 57 ..(...|. |...+... [040] 4F 52 4B 53 20 33 2E 30...

...mage is right in the error strings (?) section. 00000170 13 59 5A 58 72 09 40 75 01 42 03 5E 0B E2 CC C3 .YZXr.@u.B.^.âÌà 00000180 03 18 01 27 0D 0A 49 6E 76 61 6C 69 64 20 73 79 ...'..Invalid sy 00000190 73 74 65 6D 20 64 69 73 6B FF 0D 0A 44 69 73 6B stem diskÿ..Disk 000001A0 20 49 2F 4F 20 65 72 72 6F 72 FF 0D 0A 52 65 70 I/O errorÿ..Rep 000001B0 6C 61 63 65 20 74 68 65 20 64 69 73 6B 2C 20 61 lace the disk, a 000001C0 6E 64 20 74 68 65 6E 20 70 72 65 73 73 20 61 6E nd then press an 000001D0 79 20 6B 65 79 0D 0A 00 49 4F 20 20 20 20 20 20 y key...IO 000001E0 53 59 53 4D 5...

On 10/05/16 02:37 PM, Amit Ashara wrote: > Is there a format document on the OpusTag structure? Search always shows > up Vorbis but not Opus. The basic format is shared with Vorbis, but the 'magic signature' is different ('OpusTags' instead of '0x05vorbis') and vorbis puts a 0x01 value in an extra byte after the last tag. The OpusTag packet layout is described in

...00: 44 53 44 54 37 7d 00 00 02 70 53 45 43 43 53 44 DSDT7}...pSECCSD 0010: 53 4e 42 2d 43 50 54 00 00 00 00 00 49 4e 54 4c SNB-CPT.....INTL 0020: 09 11 06 20 08 53 53 31 5f 01 08 53 53 32 5f 00 ... .SS1_..SS2_. 0030: 08 53 53 33 5f 01 08 53 53 34 5f 01 08 53 50 32 .SS3_..SS4_..SP2 0040: 4f 0a 4e 08 53 50 31 4f 0b 4e 16 08 49 4f 31 42 O.N.SP1O.N..IO1B 0050: 0b 00 06 08 49 4f 31 4c 0a 70 08 49 4f 32 42 0b ....IO1L.p.IO2B. 0060: 80 06 08 49 4f 32 4c 0a 20 08 49 4f 33 42 0b 90 ...IO2L. .IO3B.. 0070: 02 08 49 4f 33 4c 0a 10 08 53 50 33 4f 0a 2e 08 ..IO3L...SP3O... 0080: 49 4f...

http://bugzilla.mindrot.org/show_bug.cgi?id=124 ------- Additional Comments From markus at openbsd.org 2002-02-23 06:10 ------- what does "streaming" mean? what does "output reports" mean? do you have more detailed reports? do you have debugging output? what clients are involved? what servers? does the same happen with openssh 3.0.2? does the same happen with a recent

...; BYTES kept as a place holder for putting more data? >> >> Yes, opusenc does reserve some space in the header so that tags can >> later be modified "in place", without having to rewrite the entire file. >> >> Jean-Marc >> >> >> > 4f 67 67 53 = Oggs >> > 00 = Version >> > 00 = Header >> > 00 00 00 00 00 00 00 00 = Granule Position >> > a5 73 00 00 = Bit Stream Serial Number >> > 01 00 00 00 = Page Sequence Numner >> > 90 a9 36 42 = Checksum >> > 03 = Page Segments &...

...> > BYTES kept as a place holder for putting more data? > > Yes, opusenc does reserve some space in the header so that tags can > later be modified "in place", without having to rewrite the entire file. > > Jean-Marc > > > > 4f 67 67 53 = Oggs > > 00 = Version > > 00 = Header > > 00 00 00 00 00 00 00 00 = Granule Position > > a5 73 00 00 = Bit Stream Serial Number > > 01 00 00 00 = Page Sequence Numner > > 90 a9 36 42 = Checksum > > 03 = Page Segments &...

...TANDALONE dos charset = CP850 unix charset = UTF-8 display charset = LOCALE # smbclient -L MYSERVER -Uadmin protocol negotiation failed The samba log file gives me >> [2011/01/11 13:22:53, 10] lib/util.c:dump_data(2230) [000] 02 50 43 20 4E 45 54 57 4F 52 4B 20 50 52 4F 47 .PC NETW ORK PROG [010] 52 41 4D 20 31 2E 30 00 02 4D 49 43 52 4F 53 4F RAM 1.0. .MICROSO [020] 46 54 20 4E 45 54 57 4F 52 4B 53 20 31 2E 30 33 FT NETWO RKS 1.03 [030] 00 02 4D 49 43 52 4F 53 4F 46 54 20 4E 45 54 57 ..MICROS OFT NETW [040] 4F 52 4B 53 20 33 2...

...LIST_DISPOSITION=REJECT MACLIST_LOG_LEVEL=info interfaces: #ZONE INTERFACE BROADCAST OPTIONS net ppp0 217.96.90.242 noping loc eth0 255.255.255.0 routestopped,maclistmaclist: maclist: #INTERFACE MAC IP ADDRESSES (Optional) eth0 00:30:4F:19:73:0C 192.168.1.2 eth0 00:30:4F:19:6E:EF 192.168.1.4 eth0 00:E0:7D:BA:8C:C5 192.168.1.6 eth0 00:09:2C:30:02:AD 192.168.1.7 eth0 00:30:4F:19:73:B2 192.168.1.8 policy: #SO...

....017549 get_answer: (16 bytes) => ab 01 79 01 02 50 00 50 01 00 0e 00 01 00 10 50 0.018769 get_answer: block_number = 1 0.019927 get_answer: need to read 110 more data 0.030671 get_answer: (24 bytes) => ab 01 79 01 02 50 00 50 01 00 0e 00 01 00 10 50 0.031399 4f 57 45 52 57 41 52 45 0.031564 get_answer: block_number = 1 0.032179 get_answer: need to read 102 more data 0.046680 get_answer: (32 bytes) => ab 01 79 01 02 50 00 50 01 00 0e 00 01 00 10 50 0.047836 4f 57 45 52 57 41 52 45 20 55 50 53 20 20 20 5c 0.048017 get...

...i'm sending. They said that I send the cid name in ascii code and to do it working, I need to send it in hex. So I take some traces but i'm unable to figure where is the problem. What I see In case that work: incoming call: < [1c 1c 9f 8b 01 00 a1 16 02 01 01 02 01 00 80 0e 49 4e 46 4f 46 4f 52 54 49 4e 20 46 41 58] < Facility (len=30, codeset=0) [ 0x9F, 0x8B, 0x01, 0x00, 0xA1, 0x16, 0x02, 0x01, 0x01, 0x02, 0x01, 0x00, 0x80, 0x0E, 'INFOFORTIN FAX' ] PROTOCOL 1F What I see in case that doesn't work: outgoing call: > [28 05 b1 69 6e 66 6f] > Display (len= 5)...

...-- -- -- 04 51 01 01 a5 5a a0 Commands leading to the command that caused the error were: CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name -- -- -- -- -- -- -- -- ---------------- -------------------- 08 d6 01 01 a5 5a a0 02 03:14:14.480 DEVICE RESET b0 d6 01 9f 4f c2 a0 00 03:12:29.984 SMART WRITE LOG b0 d5 01 9f 4f c2 a0 00 03:12:29.968 SMART READ LOG b0 d6 01 50 4f c2 a0 00 03:12:26.512 SMART WRITE LOG b0 d9 01 00 4f c2 a0 00 03:12:26.480 SMART DISABLE OPERATIONS Error 3378 occurred at disk power-on lifetime: 0 hours (0 days...

...90:3c:00:a4:01:0a:d7:90:3c:00:a5:01:0a:d7:90:3c:00:a6:01:0a:d7:90:3c:00:a7:01:0a:d7:90:3c:00:a8:01:0a:d7:90:3c:00:a9:01:0a:d7:90:3c:00:aa:01:0a:d7:90:3c:00:ab:01:0a:d7:90:3c:00:ac:01:0a:d7:90:3c:00:83:01:0a:d7:90:3c:bb:bb:01:0a:d7:90:3c:ff:09:cb:00:00:16:4e:65:78:74:20:44:65:76:69:63:65:20:28:42:49:4f:53:2f:45:46:49:29:00:a0:0c:55:62:75:6e:74:75:4e:65:74:78:38:36:00:81:08:44:4f:53:20:55:4e:44:49:00:a1:0c:48:50:20:64:63:37:38:30:30:53:46:46:00:a2:0b:44:65:6c:6c:20:4f:70:74:33:36:30:00:a4:0b:47:58:35:32:30:26:47:58:36:32:30:00:a5:16:42:72:6f:61:64:4e:65:74:58:74:72:65:6d:65:20:49:49:20:47:69:67:61...

...30 30 3e 3b @192.168 .1.100>; 0150 74 61 67 3d 65 34 35 64 65 35 36 62 0d 0a 43 61 tag=e45d e56b..Ca 0160 6c 6c 2d 49 44 3a 20 4e 47 49 33 59 6a 49 7a 4d ll-ID: N GI3YjIzM 0170 6a 49 79 4e 47 49 77 5a 54 6b 77 4d 54 63 35 5a jIyNGIwZ TkwMTc5Z 0180 47 49 77 4d 57 51 33 4d 57 5a 69 4f 57 4a 6b 4e GIwMWQ3M WZiOWJkN 0190 44 59 2e 0d 0a 43 53 65 71 3a 20 31 20 52 45 47 DY...CSe q: 1 REG 01a0 49 53 54 45 52 0d 0a 45 78 70 69 72 65 73 3a 20 ISTER..E xpires: 01b0 33 36 30 30 0d 0a 41 6c 6c 6f 77 3a 20 49 4e 56 3600..Al low: INV 01c0 49 54 45 2c 20 41 43 4b 2c 20 43 41...

...1 < ChanSel: As indicated in following octets PRI Span: 1 < Ext: 1 Coding: 0 Number Specified Channel Type: 3 PRI Span: 1 < Ext: 1 Channel: 1 Type: CPE] PRI Span: 1 < [1c 1d 9f 8b 01 00 a1 17 02 01 01 02 01 00 80 0f 4f 4d 41 58 20 43 4f 52 50 20 4e 20 47 53 4d] PRI Span: 1 < Facility (len=31, codeset=0) [ 0x9F, 0x8B, 0x01, 0x00, 0xA1, 0x17, 0x02, 0x01, 0x01, 0x02, 0x01, 0x00, 0x80, 0x0F, '<source_caller_name>' ] PRI Span: 1 < [6c 0c 21 83 32 35 33 33 38 30 35 35 39 31] PRI Span: 1 < Call...