The mysterious "passthrough" mode is actually very simple - in fact, it is very close to what you might call "bridge mode". You choose an L2 interface, and RouterOS creates a DHCP server on it, which responds to a request from a single client - either to the very first one to send a DHCPDISCOVER, or to the one whose IP address is specified as the
passthrough-mac parameter of the
/interface lte apn row.
Internally, RouterOS obtains the IP address provided by the mobile network from the LTE modem, builds the smallest possible subnet (a /30 or, if not possible, a /29) around that address, and assigns another address from that subnet to itself on the L2 interface. But on the Mikrotik itself, this other address cannot be used for any other purpose than being a gateway for the DHCP client, as from the point of view of the mobile network, it is assigned to some other LTE modem.
The above is true if
passthrough-subnet-selection is set to
auto; if you set it to
p2p, the DHCP server delegates the address provided by the mobile network to the client as a /32 one and provides a randomly chosen 10.x.x.x address as a gateway. This way, the adjacent public addresses remain accessible, but some DHCP clients may not accept such an assignment.
I don't know the default configuration of LHGG plus you may have changed it, so post an anonymized export of the LHGG (see my automatic signature below) to get a step-by-step guide which doesn't require climbing to the roof.
Without knowing the minute details, the guide looks like this:
- on the LHGG, attach an /interface vlan with some vlan-id you like, e.g. 777, either directly to ether1 or, if ether1 is a member of some bridge, to that bridge. Let's name it ether1.777 or bridge.777 to make it self-explanatory, but it's just a name, you can as well call it myLteWanVlan.
- on the pfSense, attach a VLAN interface with the same VLAN ID to the interface connected to the LHGG
- on the pfSense, attach a DHCP client to that VLAN interface, and set up firewall rules, as this interface will get the address from the mobile network and get directly connected to the internet in the next step - the LHGG does no firewalling on that interface.
- on the LHGG, set passthrough-interface on the /interface lte apn row you use to ether1.777 or bridge.777 or whatever name you have assigned to the /interface vlan added in the first step.
That's all - the pfSense now gets the public IP on that VLAN interface.
The above is the simplest way. You may prefer to reverse the role of the "native VLAN" and the "tagged VLAN" on the cable, in terms that the tagged VLAN will be used for management of the LHGG and the tagless one for the passthrough mode, as the tagging and untagging is done in software at both ends so you can save a couple of CPU cycles per packet for the WAN traffic if you don't tag it.
To do it that way, the first and second step are the same, but you have to create another private subnet in the added VLAN (attach static IP addresses from the same subnet, different from 192.168.88.0/24, to the VLAN interfaces at the LHGG and the pfSense), adjust firewall rules at the LHGG, and check that you can connect to the LHGG using its address in this new subnet. Once you've checked that, stay connected to the LHGG that way, remove all the IP configuration (address, dhcp server) from
ether1 or
bridge on the LHGG and from the physical ethernet on the pfSense, attach a DHCP client to the physical interface on the pfSense, and indicate
ether1 or
bridge as the
passthrough-interface on the LHGG.