订阅以下载
Pony Net (Supporting Pony OS)

Special thanks to "Daddy Daddy Do!"
He was interested in the project, and has fixed some bugs (see latest update).

Pony Net

1. How packets work (ports, MAC)
   
2. Switches
   
3. IPs and nets
   
4. Routers
   
5. Ports
   
6. Cellular network
   
7. Multiplayer warnings

Pony OS

You can create your own apps for Pony OS.
Please look at the description over here


Pony Net is the system that allows communication between multiple devices.
It is based on the IPv4 internet we all know or use. Some parts are a little bit different though.


EACH INDIVIDUAL PART OF THE SYSTEM INCLDUING A MANUAL WILL BE UPLOADED SOON

A packet is a complete composite signal, for one tick. So one package includes 32 numbers (the 32 booleans are ignored).
A packet contains information about the source of the packet (sender) and the destination (receiver). This information is called MAC adress.
It must be a unique identifier and can range from 1-65535. Only 1-65534 can be used by devices, 65535 is a special adress which means "broadcast to everyone in the network". -1 is also a special adress, it means "switch please look up the MAC for a specified IP" (more about that later). the MAC adress 65534 is used by the network testing device, you better do not use that MAC.

IMPORTANT NOTE: because of multiplayer sync, you are ONLY allowed to use MACs between 1-255 for devices!!!


Switches exchange data between multiple devices. Pony Net offers a 4 connection switch and a 5 connection switch. They behave exactly the same: to every connection you connect one device (a host, a switch or a router).
The switch contains one lua script for every connection (queues up incoming packets at the input) and a master script that controls which packets to pop from which queue and to which output it should be sent.
The master script keeps track of which devices are connected on which connection. All devices broadcats an empty packet from time to time, so those tables have up to date information on connected devices.
Switches can be chained, but please make sure you do not create a round about!

A switch will also function as an ARP table (in real life this is not the job of a switch). He is able to translate IPs into MACs. This is necessary when transfering packets between different networks (more on that later).

An IP adress identifies a device (similar to a MAC) but it also identified a network. This allows to split up the internet into many seperated networks. Communication inside networks can happen without blocking bandwith for devices of a different network.
If you send a packet to a device in the same network, it will travel to the next switch and then to destination device. If the destination device is in a different network, you have to first send the packet to the "gateway" (=router) of your network, this happens by choosing the gateways MAC as receiver MAC. This gateway then forwards the packet to the destination network via routers (currently Pony Net only supports static routing). Once it reaches its final destination router, this one will replace the receiver MAC with -1 and forward it to the local switch. This switch has the ARP table and can replace the -1 with the MAC of the destination IP.

IP adresses are made of 3 bytes:
the first 2 bytes is the network adress (e.g. 1.2) the third byte is the host adress (e.g. 230).
Network adresses range from 0.1 to 255.255, host adresses range from 1 to 254. 255 is a special IP, it means broadcast to the full network (a router will replace the receiver MAC with a 65535 = broadcast MAC).
This means you can have a maximum of 65534 networks, and a maximum of 254 devices per network.

If the receiver IP is 0, the packet will be dropped by routers.



Routers connect/split networks. Once they receiver a packet, they check if the receiver IP is in a different network. If that is the case, and the router knows a route to that network, he will send it to the connection that has that route, otherwise it drops the packet. They work the same as switches in terms of queuing incoming packets and controling outgoing packets.

A port defines more or less an application that you want to receive the packet. An application can be a system application (e.g. DHCP) or your own application (e.g. chat system).
The network manager of PonyOS filters incoming packets and forwards them to the apps, depending on the ports (more on that later).

Used ports:

• 999 (network testing device)
  
• 888 (cellular network)
  
• 67 (DHCP)
  
• 53 (reserved for DNS)

A cellular network is replacing the cable connection between a device and a switch with radio antennas. Every base station has sends on the same frequency. A receiver cecks that frequency and will get the configuration for that base station. The configuration includes 3 frequencies: reqgister, uplink, downlink. These frequencies should be different for every base station. Once the receiver notices that he connected to a new base station, he will register himself in the cell. Multiple receivers can be connected to a single cell, the cell will tell the receivers when they are allowed to send packets via the uplink. The downlink is sent to all receivers and they need to filter the packets for ones that are meant to be received by them.

Downlink & Uplink Composite

Info Composite


The packets themselves work fine in multiplayer.
Configurations are also multiplayer proof.
When a new player joins a server, it will take a couple of seconds until "his internet" synchronized the configuration for switches, celullar etc.

Desync can still happen because of Pony OS (more on that later).