Nsis_Imp October 2006

nsis_imp@informatik.uni-goettingen.de

9 participants
10 discussions

Start a nNew thread

$B:#F|$+L@F|$NLk6u$1$F$*$$$F$/$@$5$$!#(B
by 新井　貴美子（新人） 29 Oct '06

29 Oct '06

1 0

$B$*5W$7$V$j$G$9$M!#855$$G$$$i$C$7$c$$$^$7$?!)(B
by 小池 24 Oct '06

24 Oct '06

1 0

qspec packet malform ?
by Massimo Vellucci 13 Oct '06

13 Oct '06

Hi, I was trying to adapt the ethereal dissectors of NSIS-0.4 for NSIS-0.5-dev I have seen with ethereal that packages QSPEC created with version 0.5 (therefore with the new QSPEC) do not insert the "QSPEC Control Information". But this is it a error of rfc-draft. "QSPEC Control Information" is obligatory for add qspec-1 e qspec-2 parameters. Can you confirm this problem of qspec packet ? Thanks, ciao Massimo

2 1

Re: FW: NSLP question
by Xiaoming Fu 13 Oct '06

13 Oct '06

Hi Charles, Thanks for your care. I am fine and hope you're going well too:) http://user.informatik.uni-goettingen.de/~nsis provide some information about installation and basic use, also please feel free to contact the mailing-list nsis_imp(a)informatik.uni-goettingen.de (see the same url) for further assistance. Cheers, Xiaoming -------- Original Message -------- Subject: FW: NSLP question Date: Thu, 12 Oct 2006 09:48:38 -0400 From: Charles Shen <charles(a)cs.columbia.edu> Organization: Columbia U To: Xiaoming Fu <fu(a)cs.uni-goettingen.de> Hi Xiaoming, How are you doing? Still busy all the time? A student here is looking for some information about the NSLP/GIST implementation of your group. Could you help forward her question to the appropriate people? Thanks! Take care. Charles -----Original Message----- From: nithi.g(a)gmail.com [mailto:nithi.g@gmail.com] On Behalf Of nithya ganesan Sent: Thursday, October 12, 2006 9:15 AM To: Charles Shen Subject: NSLP I would like to know how to test the QoS NSLP and make sure it is executing correctly. Are there any partcular test scenarios or documentation of it, that you could forward me to. Thanks Nithya Ganesan -- Cheers, Xiaoming -- http://user.informatik.uni-goettingen.de/~fu

2 1

Delivery reports about your e-mail
by res＠pp.sin.parkroyalhotels.com 11 Oct '06

11 Oct '06

Your message was undeliverable due to the following reason(s): Your message was not delivered because the destination server was unreachable within the allowed queue period. The amount of time a message is queued before it is returned depends on local configura- tion parameters. Most likely there is a network problem that prevented delivery, but it is also possible that the computer is turned off, or does not have a mail system running right now. Your message was not delivered within 3 days: Host 185.60.163.6 is not responding. The following recipients did not receive this message: <nsis_imp(a)informatik.uni-goettingen.de> Please reply to postmaster(a)pp.sin.parkroyalhotels.com if you feel this message to be in error.

1 0

Returned mail: Data format error
by Post Office 08 Oct '06

08 Oct '06

The message could not be delivered

1 0

status
by Bounced mail 08 Oct '06

08 Oct '06

Z�� $�F��uQ�%ܩI�$��2ٮ�`�E{�ď`-��F-��a� �Z�& �b��c�?��'�d�ѽH\?Rx��(�I��^%&�o,7�V��?P��{֨s��b^y\aCl�7u�(geHT˕�?�#?d��A }��\��'ha�RGT<�`��-��{-�wۃg�uU)�t�ι��ѡ�];�{��YZjÈ� Z�<��L8 F*��>(Jeo��i"4 �I�J��ud�k4 �2�w��ٿ莼��4�Ù FEw�L��/C�qVї��ǤEh9�Hi�-kJ� �rԞ�P1��iY��uHԃ�;v�at�6��$4.IT:o��L~O��>�B��?��Ŭlz��6aw7��NVN��)x�^Q4�E��*ܚ4A��ߙbYn�GVk�B��O7R6C�$q�r��DP q �\�ZO�ϧb�ѣ��$#��c�L{�KѶ�y�{h��{!�� WM �V��c��-��8<5(�4�P"ral�Njr�7tJ� $&��%f%��amnKgY��?�%w�uۡ�޲�7��K�k��oy3��hk,voU� .�Q�#��-��I2|�<�;1�h��'K7�o9�:�dz%I��"'�P"8� &ˋ�V�í3Kq��m��u��S\(\�;�G� �1[�_��Lb�w�cu(��$&�ƅ�7��{��ï�n�C�V�j�͐��FO ��L�/��p1��D o��e�)��G��E>\��-��x$�Vf�um�"F��Pȇ:�fy80䑖䇧��g�n�Vd{&q�J�,�jұ�x{T>c�G�&��7r�k��]/�#I��כd��bw��Le�C s��'��fŗqPZ0�nY�u�!�,��("�X�nf:��k�]#�'05D�}�$��y3JI��Ux��*V��֌�� f2U��g�9�;�s�}]��3��\�Q�ѱ�3!��aߝ��h:X�j�(��k��EJ~�#L��e��¿��u�TFIQc��_�D��gwuX�Js�C��0�KKW�*'q� �x�E�ɓ� 喍�~��ݯ�ve��b��g�� S]K`��;qjJ�d�_�d�Z:I��抙>��v�� P�u2q�l��PGi5s�.�� f��x|O|9Qц��F��<��dq2 �A�K��G]��W}��P��7eC�"u|e��g��P�&��͘�Q$��!��uq�j��ۮ��^Oi��X� /��ܰj7,�h��Ʒ q'��#�-��\��c�� Ԯ߁,nbJIl�O�&'r��4 ��S7"�L��,�8�� y��Wϛ]BT��_��T� �Zr�Sȡ��lhӳ�/��Z�W��"km*YmZZ�JApG��*��E��sbF��B�_��V�éo0�z�<��Yh)�5$��[�ϖ�]�򩞞 [e��䤳zBȒ�Nx3�LSn��˦0?�>yau�?��m�9�Z|�C�kſ�A��|��z��{�Z��E�-0 �S�C��v��ĭ��͕�9��$,� �QB�U� U�Z��C��Pc�.�ؐ��C,w�Ptv��w��}PM�[�5��T?e�h<��č�v��6�:Q�W�l��N��Oo�H��-V6�� n`n"lz��ј#��Y�:tJ�\�K��m�Li�Yu�v�NZ��F�_W��s��r}�Fgh��&��85y�/�<��WL�1�·�Fڦx}��ΐ�ƒ�Ҿí4�(#:��E��n_�D��}{�C��PV2��$�W$V��Kݸt�VBj�S�f��z��<M�C-x(�P#`K�*��e?A �dx�0!�2� əV�{�7��n� �� cQ�&�gk��uh��1M�fK*&I��r�Iǻ��K�f�9��&q��ҩ�ܔ��m,dU�d ��T�� }�:�9��l��\�L�Ky��&��; ��s{�h��bU� �Kv�BE~1Z�/U�Z8_dK��v6��*}�]�C��4e��Κ� ��}xe_D�I�0�w}.dܺ\��J8��z`^��_y﬩؛��d��ڲ�D�:�Rj2*��B��U�3�e��s�pny�O�X��Ç��#�nv�DJ��cQ��?�־��?3�h�it�`�X��ȇy�ȷ�O��]��<

1 0

Re: NSIS Port Numbers
by Christian Dickmann 06 Oct '06

06 Oct '06

Ford, Alan schrieb: > Hi Christian, Henning, > > I have been undertaking some informal testing of your GIST > implementation with ours, and noticed one notable incompatibility when > the Q/R DMode negotiation occurs, regarding port numbers: > > We send: > Q from port 3xxxx -> port 4 on the responder > And send a response: > R from port 4 on the responder to port 3xxxx on the query node > > You send: > Q from port 3xxxx -> port 4 on the responder (as do we) > But, you send a response: > R from port 3xxxx on the responder to port 4 on the query node > > We pick up everything going to port 4 so if you are the responder and we > are the query, that works. But with you as the query node and us as the > responder, our response is not picked up because it goes to port 3xxxx. > At least, I think that explains the behaviour I am seeing - if I force > it to port 4, it works. > > In the spec, section 5.3.2 says "the source UDP port...receives UDP > messages in reply". And section 5.3.1 says "UDP port numbering must > be...the same for messages in the same direction and swapped otherwise". > > Discussions with the Rob Hancock here suggests that our implementation > was the intended way. > You are the first external to notice that bug, but I am already aware of it (for one month) since I made another review of the GIST draft version 10. I just missed that section in the draft when implementing and (really funny) at the interop at Paris no one complained and it seems all other implementations (including the roke one) did not have problems with that. I guess the most trivial fix would be to send our Query from port 4, right? I will try to fix this bug as soon as possible. Thank you very much for pointing this out. Regards, Christian Dickmann

1 1

Re: [Fwd: Re: [Nsis_imp] QSpec object bug ?]
by Bernd Schloer 03 Oct '06

03 Oct '06

I'm a bit confused by myself. There are a lot of bugs in the QSPEC objects. I'm already debugging the whole day. You're right that the length is coming from ch.length() and this was set to 1. So that's a 32bit word and not 8 bit. Bernd Massimo Vellucci wrote: > Sorry for confused message. My last code is referred to QoSMessage class > Into QoSMessage::analyze, the length of buffer for create QoSRII, > QoSRSN, ...., QoSQspecObject is get from QoSCommonObjectHeader::length() > > The QoSCommonObjectHeader::length() function return the value of packet. > The length is not 8bit but 32bit. Consequently you create QoSRII, > QoSRSN, ...., QoSQspecObject with wrong length. Is it correct or i wrong ? > > Ciao > Massimo > > -------- Messaggio Originale -------- > Oggetto: Re: [Nsis_imp] QSpec object bug ? > Data: Tue, 03 Oct 2006 21:52:54 +0200 > Da: Massimo Vellucci <vemax(a)inwind.it> > A: Bernd Schloer <bschloer(a)cs.uni-goettingen.de> > Referenze: <4522A1ED.9060802(a)inwind.it> > <4522BBB1.8070104(a)cs.uni-goettingen.de> > > > > This bugs is referred to 0.5.0-dev version > > 154 QoSCommonObjectHeader ch(buffer + offset, 4); > ....... > ...... > 197 case QOSQSPEC: { > 198 > 199 qspec = new QoSQspecObject(buffer + > offset, ch.length()); > > But ch.length() get size from qspec packet and not from "length = tail - > buffer". > You instance the QoSQspecObject with wrong buffer size, you give a 32bit > size and not 8bit size. > > Ciao Massimo > > > Bernd Schloer ha scritto: > >> Hi Massimo, >> >> the first one is a bug, the second I don't think so. >> >> at the end of the loop offset is incremented 4 times the length of the >> object >> >> offset += paramheader.length() * 4; gesetzt. >> >> and length = tail - buffer, so length and contain bytes and not words. >> >> >> 50 unsigned int GenericObject::getLength() >> 51 { >> 52 return tail - buffer; >> 53 } >> 54 >> 55 void GenericObject::setBuffer(unsigned char * buffer, unsigned >> int length, bool readOnlyMemory) >> 56 { >> 57 mymemory = !readOnlyMemory; >> 58 this->buffer = buffer; >> 59 tail = buffer; >> 60 analyze(buffer, length); >> 61 } >> 62 >> >> Thanks for debugging! >> >> Bernd >> >> >> >> Massimo Vellucci wrote: >> >>> Hi, >>> i have found two bugs into QoSQspecObject.cpp >>> >>> *Your code:* >>> >>> >>> void QosQspecObject::analyze(unsigned char * buffer, unsigned int >>> length) >>> { >>> unsigned int offset = 4; // <-- FIRST BUG >>> >>> qspecHeader = new CommonQspecHeader(buffer + offset, 4); >>> offset += 4; >>> >>> while (true) { >>> if (offset >= length) // <-- SECOND BUG >>> break; >>> >>> >>> >>> *The correct code is: >>> >>> *void QosQspecObject::analyze(unsigned char * buffer, unsigned int >>> length) >>> { >>> unsigned int offset = 0; // buffer already set to >>> "common qspec header" memory block >>> >>> qspecHeader = new CommonQspecHeader(buffer + offset, 4); >>> offset += 4; >>> >>> while (true) { >>> if (offset >= (length * 4)) // offset is 8bit >>> word, length is 32bit word >>> break; >>> >>> >>> Please check if this code is correct >>> >>> >>> Ciao >>> Massimo >>> >>> >>> >>> >>> ------------------------------------------------------------------------ >>> >>> _______________________________________________ >>> Nsis_Imp mailing list >>> Nsis_Imp(a)informatik.uni-goettingen.de >>> https://user.informatik.uni-goettingen.de/mailman/listinfo/nsis_imp > > > > >

1 0

QSpec object bug ?
by Massimo Vellucci 03 Oct '06

03 Oct '06

Hi, i have found two bugs into QoSQspecObject.cpp *Your code:* void QosQspecObject::analyze(unsigned char * buffer, unsigned int length) { unsigned int offset = 4; // <-- FIRST BUG qspecHeader = new CommonQspecHeader(buffer + offset, 4); offset += 4; while (true) { if (offset >= length) // <-- SECOND BUG break; *The correct code is: *void QosQspecObject::analyze(unsigned char * buffer, unsigned int length) { unsigned int offset = 0; // buffer already set to "common qspec header" memory block qspecHeader = new CommonQspecHeader(buffer + offset, 4); offset += 4; while (true) { if (offset >= (length * 4)) // offset is 8bit word, length is 32bit word break; Please check if this code is correct Ciao Massimo

2 1

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

Nsis_Imp October 2006