RUTM52 wireguard interface binding

[Teltofan]

Hello,

I am testing a RUTM52 device with 07.18.3 and I wanted to configure interface binding for a wireguard connection.

Since this is a device with two modems, you can bind the tunnel to one or other interface, in my case mob1s1a1 or mob2s1a1.

• If you select mob1s1a1 as persist, you can see in the routes list that a new route is created using interface qmimux1; which corresponds to first modem
• If you select mob2s1a1 as persist, the route is created to wwan1, instead of qmimux0. The interface of the second modem is qmimux0, not wwan1.

Therefore, it binds correctly to the first mobile interface, but it fails to bind to the second mobile interface.

I have found a work-around way, that is to create a static route for the target IP of the tunnel, assigning metric 0 with the interface mob2s1a1. In this case, the tunnel is created using the desired interface, although other routes appear to the same IP with higher metric.

Always, you have the solution to put the main sim card on the first interface, and bind to it.

I have been trying to understand the meaning of /tmp/wireguard/default_status_wireguard file, without much success, but you can see differences there depending on your configuration.

RUTM52 seems to be a great device, just starting to enjoy it.

Regards.

[Matas]

Greetings,

I’ll be taking the time to test this out once I have access to a dual-modem device, and if I’m successful in reproducing this issue, I’ll proceed with creating a query for our R&D team in order to investigate this issue. I will, of course, get back to you with the results & updates once I have anything.

Thank you,
M.

[Teltofan]

Hello Matas,

Thank you for your help.

I have recorded a video, sometimes an image is more clear.

Because of privacy, I generated a new setup with fake data.

The tunnel with qmimux1 interface in the route was working, but that was not the case when wwan1 interface was in the route list.

rutm52.zip (2.4 MB)

Regards

[Matas]

Hi, Teltofan,

Apologies for the very late response. I’ve reviewed everything that you’ve provided and can clearly see the issue. I’d like to escalate this matter for our R&D to investigate, but I’d need a troubleshoot file from your device as well. For that, we’d have to move to a different channel to continue on a private conversation. I have sent you a form to fill out, which you will receive in your e-mail inbox that you have registered your account with in the forums. In the Ticket ID field of the form, please enter the ID of this thread, which is 16396.

Regards,
M.