[Device]: Teltonika TRM240 4G Industrial Cellular Modem #362
Labels
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
jaylouisw/packetforge#362
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Vendor
Teltonika
Exact model name
Teltonika TRM240 4G Industrial Cellular Modem
Category
Router
Ports and interfaces
PoE budget (watts)
None
Datasheet or product page URL
https://www.4gon.co.uk/teltonika-trm240-4g-industrial-cellular-modem-p-9894.html
What do you want to model with it?
A router/gateway node in a routed lab (NAT, DHCP, VPN, cellular WAN).
Capabilities
routing, NAT, DHCP, l3-forward
Before submitting
TRM240 is in the catalogue (
devices/teltonika/trm240.json): No Ethernet port - a Cat 1 modem with a virtual network interface over micro-USB. Recorded withwirelessas its only capability, because a radio with no forwarding engine is not a router.Reopened - this project does not resolve a device request by declaring it impossible.
That closure used the same reasoning I have been applying to RF parts, optical modules and any box whose port table I could not find: "it has no Ethernet ports, so it cannot be modelled". The maintainer's rule is now the opposite, and it is the better one: a device that cannot be modelled yet is still a real device someone asked for, and the request is the record of that. Closing it deletes the interest and loses the evidence that a person wanted it.
So this stays open. What changed in practice:
OptiXtrans E6616/E6608);If you already know the port complement, or have a datapath requirement that this device exists to serve, say so here and it moves up the queue.
Already in the catalogue:
devices/teltonika/trm240.json- Teltonika TRM240, 1 interface(s): wwan1 (10M).This is the second correction on this issue. It was first closed as impossible to model; it is reopened and now closed the only way this project closes a device request - the catalogue answers it, and here is the file that does. The earlier closure was not just against policy, it was wrong on the facts: the device has been modelled the whole time.
If the spec is missing something you need - a port, a radio, a capability - say which and it gets fixed. A wrong entry is worth more attention than a missing one, because it looks answered.