(04-12-2015, 01:48 PM)GISED_Link Wrote: This post contains a lot of "blablabla" ...

It's impossible to follow all the ideas here and it miss a lot of graphical elements. Maybe you can be inspired by a format like the RFC (http://en.wikipedia.org/wiki/Request_for_Comments)

I'm sure a lot of people want to help you (like me), but for the moment I think it's not complete about the main informations. I need detailed explanations about wich layer you are talking about, how each layer works, a good and clear spereation for each layer and some pic' to support your explanation.

Here you will found some examples (for everybody) :

OSI model : http://en.wikipedia.org/wiki/OSI_model
ip datagram (layer 3) : http://www.linktionary.com/i/ip3.jpg
rfc917 : http://tools.ietf.org/html/rfc917
RS232 (layer 1 only) : http://www.bnoack.com/graphics/rs232data.gif
TCP (layer 4), connection diagram: http://upload.wikimedia.org/wikipedia/commons/6/6c/Tcp_connect.svg

If you can give us picture like this, it would be perfect. And Maybe update the first post with the current final description.

(04-12-2015, 03:15 PM)slugdude Wrote:

(04-12-2015, 01:48 PM)GISED_Link Wrote: This thread contains a lot of "blablabla" ...

It's impossible to follow all the ideas here and it miss a lot of graphical elements. Maybe you can be inspired by a format like the RFC (http://en.wikipedia.org/wiki/Request_for_Comments)

I'm sure a lot of people want to help you (like me), but for the moment I think it's not complete about the main informations. I need detailed explanations about wich layer you are talking about, how each layer works, a good and clear spereation for each layer and some pic' to support your explanation.

Here you will found some examples (for everybody) :

OSI model : http://en.wikipedia.org/wiki/OSI_model
ip datagram (layer 3) : http://www.linktionary.com/i/ip3.jpg
rfc917 : http://tools.ietf.org/html/rfc917
RS232 (layer 1 only) : http://www.bnoack.com/graphics/rs232data.gif
TCP (layer 4), connection diagram: http://upload.wikimedia.org/wikipedia/commons/6/6c/Tcp_connect.svg

If you can give us picture like this, it would be perfect. And Maybe update the first post with the current final description.

w0t



I don't even know what you're talking about m8.

(04-12-2015, 07:22 PM)GISED_Link Wrote:

(04-12-2015, 03:15 PM)slugdude Wrote:

(04-12-2015, 01:48 PM)GISED_Link Wrote: This thread contains a lot of "blablabla" ...

It's impossible to follow all the ideas here and it miss a lot of graphical elements. Maybe you can be inspired by a format like the RFC (http://en.wikipedia.org/wiki/Request_for_Comments)

I'm sure a lot of people want to help you (like me), but for the moment I think it's not complete about the main informations. I need detailed explanations about wich layer you are talking about, how each layer works, a good and clear spereation for each layer and some pic' to support your explanation.

Here you will found some examples (for everybody) :

OSI model : http://en.wikipedia.org/wiki/OSI_model
ip datagram (layer 3) : http://www.linktionary.com/i/ip3.jpg
rfc917 : http://tools.ietf.org/html/rfc917
RS232 (layer 1 only) : http://www.bnoack.com/graphics/rs232data.gif
TCP (layer 4), connection diagram: http://upload.wikimedia.org/wikipedia/commons/6/6c/Tcp_connect.svg

If you can give us picture like this, it would be perfect. And Maybe update the first post with the current final description.

w0t



I don't even know what you're talking about m8.

It wasn't about only your post, but the thread in general ^^. So I've replaced post by thread ...

• packet number
  
• physical port (routers)
  
• some connections protocol ("At the start of a single continuous stream of data, the packet number will be 0000")
  
• source address (routing)
  
• layer 1 protocol ("There will be four wires, two each way")
  
• and more

• Layer 1 : physical. Describe the size of the packet (8 bit, 10 bit, etc...) and how to seperate and validate each packet (start bit, stop bit, etc...)
  
• how many diffrent layer 1 protocol will be supported (maybe only one ?)
  
• Layer 2 : Data Link. How you will send more than one packet between 2 routers or 2 devices directly connected (MAC adress ?)
  
• layer 3 : network. How intOREnet will send a packet form A to C and where is the best path/route, how your routers will learn the routes ? (ARP request ?, IP adress ?)
  
• layer 4 : Transport. How your numbered packet are transfered, how to open a session (if this exists), etc. (TCP ?, UDP ?)
  

(04-12-2015, 11:12 PM)GISED_Link Wrote: I wich that you write a main post where everybody can find easily where you project is now and where it goes. To do that, I wich that you create some pictures like my examples to illustrate your words. Because your are talking about :

• packet number
  
• physical port (routers)
  
• some connections protocol ("At the start of a single continuous stream of data, the packet number will be 0000")
  
• source address (routing)
  
• layer 1 protocol ("There will be four wires, two each way")
  
• and more
  

I think it's a good project and I'm sure a lot of people will use intOREnet. The problem is that you have said a lot of informations in several posts. So we (and maybe you ?) will always misunderstand something because we will not alway search the information in 10 posts.

So you can devide intOREnet into layers. The layers are defined in the OSI model. If you define clearly what layer do what, wich component of intOREnet is for wich layer etc., it will really simplify the life of everybody. What I suggest to make clearer :

• Layer 1 : physical. Describe the size of the packet (8 bit, 10 bit, etc...) and how to seperate and validate each packet (start bit, stop bit, etc...)
  
• how many diffrent layer 1 protocol will be supported (maybe only one ?)
  
• Layer 2 : Data Link. How you will send more than one packet between 2 routers or 2 devices directly connected (MAC adress ?)
  
• layer 3 : network. How intOREnet will send a packet form A to C and where is the best path/route, how your routers will learn the routes ? (ARP request ?, IP adress ?)
  
• layer 4 : Transport. How your numbered packet are transfered, how to open a session (if this exists), etc. (TCP ?, UDP ?)
  

The message I will give to you is : Please take time to make the things clearer for everyone. The pictures don't need to be beautiful; useful is enough. With this, we will begin faster to create some devices for intOREnet and help you to expand the network.

Are my words more understable now ?

(05-17-2015, 09:54 AM)Hastumer Wrote: Slug, because I'm Builder now, I would like to join when it get's started.