When speaking of the Icecast protocol here, actually it's just the HTTP protocol, and this document will explain further how source clients need to send data to Icecast.
Since Icecast version 2.4.0 there is support for the standard HTTP PUT method.
The mountpoint to which to send the data is specified by the URL path.
| // use il2cppinspector to create a c++ scaffolding project | |
| // import minhook | |
| // replace user/main.cpp with this | |
| // play around! this basically shows you how to hook any function you'd like | |
| // it's obviously not at all what you'd call "complete", but it contains enough stuff i had to figure out through trial and error | |
| #include "pch-il2cpp.h" | |
| #define WIN32_LEAN_AND_MEAN | |
| #include <Windows.h> | |
| #include <iostream> |
This example setup for RouterOS 7.22 configures a MikroTik router as a PPPoE offloader. The router establishes a connection to a PPPoE server (e. g. over GPON or DSL), acquires an IPv4 address and an IPv6 prefix and delegates these to a downstream firewall via DHCP. The MikroTik device acts purely as a router, it has no firewall / NAT rules.
This is motivated by wanting a basic IP over Ethernet connection for the WAN interface of the main firewall (e. g. OPNsense). Specific hardware and protocols required for the WAN uplink are handled by the MikroTik device. RouterOS is known to have a robust PPPoE implementation.
It is assumed that the router has no default configuration like bridges, firewall rules etc.:
