Search the Community
Showing results for tags 'networking'.
Found 5 results
This is a centralized repository to allow users to communicate on what port numbers their programs use, and to reserve them in an effort to minimize overlap. This is a copy of: https://github.com/GlobalEmpire/OC-Programs/blob/master/Reserved OC network card ports.txt If you would like to reserve a number, please do any of the following: 1. Post in this thread 2. Message MajGenRelativity#4971 on Discord 3. Message MajGenRelativity on irc.esper.net Currently Reserved Ports: Port 14: Ethernet over OC: Reserved by SolraBizna Port 148: GUI service: Reserved by Dustpuppy Ports 324-325: Stargate Dialing Service: Reserved by Demokela Port 4096: Minitel: Reserved by Izaya Ports 4378-4379: GERTi: Reserved by Global Empire Port 4662: Short messages: Reserved by Dustpuppy Port 9100: Network Print Service: Reserved by Dustpuppy Port 9900: Zorya BIOS LAN boot: Reserved by awoo
(leave a comment if you want to register an MMTI type) Multipurpose Media Type Identifier, Version 1.0 Purpose The MMTI provides a way to identify data types without an extension, and to differentiate files with the same extension. One can only make so many recognisable extensions with 4 latin characters. Some data is not to be used as a file, but still needs a way to be identified. Format An MMTI string takes the format of category/type. For example, a Lua script would be application/lua. A CPIO archive would be archive/cpio, etc. MMTI strings should only use US-ASCII characters. Unregistered MMTI strings MMTI strings that aren't registered should prefix the type with x-, such as application/x-zoryapkg. Categories As of Version 1.0, the following categories are available for use. application - Any type of format which is to be executed archive - Any type of format which is used to archive other files media - Any type of format which contains video or audio model - Any type of format which contains data used to construct a 3D model text - Any type of format which is used to transmit textual data message - Any type of format which is used to transmit data over a network other - Any type of format which is not covered in the other categories Registed MMTI types. MMTI type Extensions Registration date application/lua .lua 2019-7-30 application/lua-binary .luac 2019-7-30 application/lua-assembly .luas 2019-7-30 archive/binary-cpio .bcpio, .cpio 2019-7-30 archive/urf .urf 2019-7-30 media/dfpwm .dfpwm 2019-7-30 text/txt .txt 2019-7-30 application/json .json 2019-7-30 application/lua-table N/A 2019-7-30 text/ohml .ohml 2019-7-30
Minitel Minitel is a simple, efficient networking protocol implementing layers 3, 4 and 5 of the OSI model. It supports automatic configuration and routing over large and small networks. Currently supported platforms include OpenOS, KittenOS NEO (via this package), and embedded devices. Features include: Flood routing with route caching Reliable packet delivery Packet segmentation Ordered delivery Bidirectional, ordered, reliable streams Installation instructions and API documentation can be found in the Github repo, though they can be summarised as "oppm install minitel". Demos: Minitel and the net API Mail over Minitel FRequest in action
I am trying to connect multiple computers over a network but the monitors keep displaying on the other computers monitor. In the ONLY english official tutorials which are outdated the computers are directly connected. I don’t want to have to put a power distributor and a relay on every computer. wireless is to much a hassle and on servers it can be picked up by other players. Is there any other way to use wired networks?
Back in the day, I had started to look into and even attempted to develop An advanced networking system for OC. I failed before, but I feel I now have the experience and knowledge to truly pull it off (thanks to working in the field). So, I would like to re-introduce the Unet Project! The Unet framework is a full stack IP routing solution, featuring 64 bit IP address and subnet masks, VLANs, MAC (modem address) aware interfaces and the ability to be filtered by routers. The key behind Unet is its abstraction layer, aggregating all communications media (Loopback, Wired Modems, Wireless Modems, Tunnel Cards, etc) into an interface, completely independent of the media. This vastly simplifies the transmission process. These interfaces are then farther hidden behind the basic send command. When presented with an IP address, will automatically resolve which media to use and how in the following process. If an interface with this address exists on the local system, the message is immediately looped back on behalf of the interface. If an interface resides on the same subnet as this address, it will be used to transmit the message If a route entry is found in the local route table that points to the subnet in which this interface resides, the routing information will be used in transmission If a default route is found, it will be used If no route is found, a route not found message will be looped back. In addition, an advanced series of router operating systems, both for microcontrollers (using side based transmission control) and full-fledged servers (using modem-side bindings and tunnel cards) Will allow massively scaled networks. In addition to the Unet IP addresses, the headers will have space for auxiliary transport layer info. An int will be used for Source IP addresses, a second int will be used for Destination IP Addresses, and a third int will contain an 8-bit hop counter, and a 16-bit protocol flag showing what the packet is carrying. At this time there is no other data, and comments are more than welcome regarding what to do with the extra space The project is still very early stage, as I work on it in my spare time at home, but should there be enough interest in this (Admittedly competing) system, I have however committed the code to Github and loaded the WiKi with information about the current designs. Anyone is welcome to discuss this with me! https://github.com/LetDevDev/unet