406 Trivia

[richardr]

And the answer is...

14 (max) and it was from rfc2509

Linkey: http://www.ietf.org/rfc/rfc2509.txt

(I'm getting good at this!)

[unhap]

44 , Rfc-2684 ?

[dtkflex]

14 bytes in the added headers, from RFC 2516
www.rfc-editor.org/rfc/rfc2516.txt

[snubs]

keep guessing!

[doxid]

Could we get the question in a written form? :P

[computoman]

rfc2516 - 112 bytes?

(http://www.faqs.org/rfcs/rfc2516.html)

[dtkflex]

Can we submit multiple guesses if the first isn't right?
14 bytes RFC 2516

[computoman]

I would be nice to eventually know the real answer, so someone please get it right!!!

[tragic-nate]

I'm confused RFC 2516 says the header is 6 octets not 14... Where are you getting this 14 from?

So I suppose my official answer is, 6 bytes, RFC 2516

[computoman]

IIt is so much fun to let other people win.

[snubs]

I'm confused RFC 2516 says the header is 6 octets not 14... Where are you getting this 14 from?

So I suppose my official answer is, 6 bytes, RFC 2516



You got it!

So guys, why is it 6 and not 14?

[doxid]

You got it!

So guys, why is it 6 and not 14?

Because "So I suppose my official answer is, 6 bytes", 6 bytes = 8bit * 6 =

1 octet = 8 bits
6 bytes = 6 octets (8 bit /byte is the standard in most systems)
I'd might get the next part a bit wrong since it was 5 years since i activly worked with these things.

a PPPoE header contains the following data:
4 bits = Ver
4 bits = Type
(now total of 1 byte)
8 bits = code
(2 bytes)
16 bits = session id
(4 bytes)
16 bits = length of the PPPoE payload
(6 bytes)

Assuming this is what you were looking for.
God if i'm wrong this is gona send me back to the study books for ages -.-

[snubs]

Yea, thats pretty much what I was looking for. I knew the answer, but I didn't know the other info surrounding PPPoE headers. I've never studied in school, just learned a few things on my own.

[doxid]

Yea, thats pretty much what I was looking for. I knew the answer, but I didn't know the other info surrounding PPPoE headers. I've never studied in school, just learned a few things on my own.

Same here, started programming some high level stuff, moved down lower and lower until i got to ASM. Started understanding the actual behavior of things. Started analyzing package data and RFC standards and here we are : ) quoting RFC from the head ^^ glad i got it right from the top of my head ^^

To bad i felt lazy and never wrote the answer before the other guys did :/

[bani-banan]

Same here, started programming some high level stuff, moved down lower and lower until i got to ASM. Started understanding the actual behavior of things. Started analyzing package data and RFC standards and here we are : ) quoting RFC from the head ^^ glad i got it right from the top of my head ^^

To bad i felt lazy and never wrote the answer before the other guys did :/

I so respect you right now.

ASM is not for the weak:(

[unn0129]

I so respect you right now.

ASM is not for the weak:(

Just takes a lot of patience and hard work. Congrats to the winner.

[doxid]

I so respect you right now.

ASM is not for the weak:(

as unn0129 sad, it's all about patience, hard work AND. You need to want to understand how a processor, memory storage and such works.
And the hardest part tho imo was to find a compiler that worked on the system i was on ^^

Still, i'm not that good at ASM yet so don't give me to much respect ;P thanks tho :)

[doxid]

Sorry for the double post but it appears as if i can't edit my last post.


Just thought i'd share some Assembly links for those who are eager to learn:
- http://flatassembler.net/ First off,
...awsome assembler since it's developed on multiple platforms.
...It also has some examples that might come in handy for educational purposes.
...If you don't like the syntax of the assembly structure in this assembler
...ther's always nasm, tasm that are ok assemblers (if not the best).

- One of the main issues with Assembly is the debugging,
...there are usualy no real debugging features around that are more then "ok",
...i'd reccomend getting "ollydb" or "PEBrowse".
...PEBrowse can be found here: http://www.smidgeonsoft.prohosting.com/pebrowse-pro-file-viewer.html
...What they do is basicly diss-assemble your application so you can see where you hit on a error and such.

- Some Assembly references that will most likely be useful at the start or even later on in your developing stages.
...http://users.dickinson.edu/~braught/courses/cs251f03/tools/asm.html
- Finally two pages with some source code for references,
...seeing how the source varriate from compiler to compiler, these might be useful and they might not be.
...But here are two ok sites.
...http://www.beroset.com/
...http://www.sirkussystem.com/asm.html

Hope it's of some use.