143 posts
still looking....
Posted 29 July 2016 - 06:42 AM
Hello everyone.
I developed IPv1 and it worked quite well and could give someone a basic understanding of how the internet worked – keyword: basic
I have begun work on IPv2 to allow a system where you would have Wi-Fi, modems, GPS, etc. This version would have published protocols and standards. This post is mean to be a Request For Comments (RFC) on the current standards I have in place for IPv2.
Feel free to add in your own RFC for say, a mail system, security door system, etc.
GitHub: https://github.com/InZernetTechnologies/IPv2
IP Scheme
These are scalable and theoretically have no limit.
They are composed of ROUTER.CLIENT.
Each client should have a router to redirect packets and such. The router's ID is the first octet. The second octet is the client/server ID.
Example: Router ID is 2, Client ID is 1. IP is 2.1
This allows for IP's to never collide and simplicity on the networkPackets
VLAN
Wireless
SECURITY
As of now, wireless is so insecure because there is literally no encryption. I don't know of any sort but hopefully someone can help out somehow?
EDIT: http://www.computercraft.info/forums2/index.php?/topic/8836-rc4-encryption-api/Core Routers & ISP's
PROBLEMS
If ISP A and ISP B both have separate DNS servers, there is no way to communicate with them – yet. Thinking of 'forwarders'
SETUP
Each ISP would need: DNS Server, DHCP Server, Auth Server [Optional].DHCP
DNS
In the comments you can add more details, reply to details, request to change, etc.
I developed IPv1 and it worked quite well and could give someone a basic understanding of how the internet worked – keyword: basic
I have begun work on IPv2 to allow a system where you would have Wi-Fi, modems, GPS, etc. This version would have published protocols and standards. This post is mean to be a Request For Comments (RFC) on the current standards I have in place for IPv2.
Feel free to add in your own RFC for say, a mail system, security door system, etc.
GitHub: https://github.com/InZernetTechnologies/IPv2
IP Scheme
Spoiler
IP's are 2 octets X.XThese are scalable and theoretically have no limit.
They are composed of ROUTER.CLIENT.
Each client should have a router to redirect packets and such. The router's ID is the first octet. The second octet is the client/server ID.
Example: Router ID is 2, Client ID is 1. IP is 2.1
This allows for IP's to never collide and simplicity on the network
Spoiler
534.1 {Definitions}
IP = InZernet Protocol
534.2 {Packet Setup}
[Version]
[Protocol]
[TTL]
[Source Address]
[Destination Address]
[DATA]
534.3 {Acceptable Parameters}
534.3.1 {Version}
[1] = IPv1
[2] = IPv2
534.3.2 {Protocol}
[1] = ICMP
[6] = TCP
[17] = UDP
534.3.3 {TTL}
This value is decremented by one at each intermediate node visited by the packet. When the counter reaches 0 the packet is discarded.
534.3.4 {Source Address}
The address of the sending node.
534.3.5 {Destination Address}
The address of the destination node.
534.3.6 {DATA}
Not essential to the packet itself, but should be used so empty packets are not sent.
534.4 {Packet Order}
The table that is sent as the packet is place sensitive as the table does not use strings for keys.Spoiler
By default everything is on VLAN 1. Using a switch or router you can change the VLAN. VLAN numbers range from 1-128. For each VLAN the device listens to, it will open a modem on the channel (VLAN) to receive that information. This allows for less broadcasting on specific devices, etc.Spoiler
When a router detects a modem, it will generate a random SSID along with a random password and display it on startup. The router will scan the wireless channels (150-175) and pick the lowest one that is not being used. The reason for using 25 channels is that each SSID can run on it without overlapping another channel and packet collision, etc.SECURITY
As of now, wireless is so insecure because there is literally no encryption. I don't know of any sort but hopefully someone can help out somehow?
EDIT: http://www.computercraft.info/forums2/index.php?/topic/8836-rc4-encryption-api/
Spoiler
To create your own 'ISP' is pretty easy. All you need to do is setup a network and BAM! It just works! What if your friend has his own ISP and you want his clients to access your servers and vise-versa? That's where a core router comes into play. These handle the requests coming from each ISP as well as stopping attacks. Each ISP plugs into a side of the router and then the router negotiates with each side if the packet will be allowed (firewall). You can also set throttling, etc in the core router. Also used for huge corporate networks, put a core router between the actual internet and the corporate network and setup a firewall rule to setup DMZ, etc.PROBLEMS
If ISP A and ISP B both have separate DNS servers, there is no way to communicate with them – yet. Thinking of 'forwarders'
SETUP
Each ISP would need: DNS Server, DHCP Server, Auth Server [Optional].
Spoiler
DHCP stands for Dynamic Host Configuration Protocol (which is a standard in the actual internet). What happens is the client broadcasts a packet with the source address as ID.ID (ID=computer ID) and the destination address as 0.0. The first router the packet hits, takes the packet and gets the ID and then gets the router ID and returns it with the correct source address and destination address. More info soonSpoiler
Domain Name System [or Server] resolves domains to IP addresses.Edited on 01 August 2016 - 02:59 PM
