No code yet and no test device. The README maps LANCOM's four operating systems (LCOS, LCOS SX, LCOS LX, LCOS FX) to planned entry points and napalm-device-types role bases. docs/lcos-sx3.md covers the first target (GS-23xx on LCOS SX 3.34): CLI model, getter-to-command map from the GS-2300 CLI reference, and the open get_config question (TFTP-only export). docs/fixtures.md lists the output to record from a real device. Refs NetOrk/netork#1094
20 lines
852 B
Markdown
20 lines
852 B
Markdown
# LCOS FX (Unified Firewalls)
|
||
|
||
Not started. No test device.
|
||
|
||
## What is known
|
||
|
||
- LCOS FX runs on LANCOM's (Rohde & Schwarz) Unified Firewalls.
|
||
- It has a **REST API**. The device's web client links its Swagger documentation under
|
||
Help → REST API Documentation. Requests need an auth token from the login endpoint
|
||
(category "Authentication").
|
||
- LANCOM's API documentation database publishes the API per firmware version
|
||
(11.1.1–11.2.1 at the time of writing), including change lists between versions.
|
||
- This makes LCOS FX the best-documented family: a REST client can be written from the spec
|
||
without a device. Tests still need recorded responses.
|
||
- Open: whether a used firewall is usable without an active license. Check before buying.
|
||
|
||
## Role
|
||
|
||
`FirewallDriver` (NAT/VPN, firewall rules, DHCP server, health metrics, package management).
|