[GH-ISSUE #137] [TRACKED] IPv4 Access from Modem with Passthrough? #51

Closed
opened 2026-02-27 14:38:52 +03:00 by kerem · 6 comments
Owner

Originally created by @jhenkens on GitHub (Mar 23, 2025).
Original GitHub issue: https://github.com/iamromulan/quectel-rgmii-toolkit/issues/137

Hi,

When I enable IPPT via SimpleAdmin on the modem, I lose the ability to connect to IPv4 services from the modem itself.

root@sdxlemur:~# ping ipv6.google.com
PING ipv6.google.com(nuq04s45-in-x0e.1e100.net (2607:f8b0:4005:812::200e)) 56 data bytes
64 bytes from nuq04s45-in-x0e.1e100.net (2607:f8b0:4005:812::200e): icmp_seq=1 ttl=53 time=43.8 ms
64 bytes from nuq04s45-in-x0e.1e100.net (2607:f8b0:4005:812::200e): icmp_seq=2 ttl=53 time=42.0 ms
^C
--- ipv6.google.com ping statistics ---
2 packets transmitted, 2 received, 0% packet loss, time 1001ms
rtt min/avg/max/mdev = 41.972/42.873/43.775/0.901 ms
root@sdxlemur:~# ping google.com
PING google.com(sfo03s32-in-x0e.1e100.net (2607:f8b0:4005:814::200e)) 56 data bytes
64 bytes from sfo03s32-in-x0e.1e100.net (2607:f8b0:4005:814::200e): icmp_seq=1 ttl=53 time=49.9 ms
64 bytes from sfo03s32-in-x0e.1e100.net (2607:f8b0:4005:814::200e): icmp_seq=2 ttl=53 time=44.7 ms
^C
--- google.com ping statistics ---
2 packets transmitted, 2 received, 0% packet loss, time 1001ms
rtt min/avg/max/mdev = 44.738/47.330/49.922/2.592 ms
root@sdxlemur:~# ping ipv4.google.com
PING ipv4.l.google.com (142.251.46.238) 56(84) bytes of data.
ping: sendmsg: Operation not permitted
ping: sendmsg: Operation not permitted
^C

It appears to work correctly at my router/laptop level, going through the modem, just not connections originating on the modem itself (thus, I can't speedtest, or download the latest version of the toolkit, without disabling IPPT).

Originally created by @jhenkens on GitHub (Mar 23, 2025). Original GitHub issue: https://github.com/iamromulan/quectel-rgmii-toolkit/issues/137 Hi, When I enable IPPT via SimpleAdmin on the modem, I lose the ability to connect to IPv4 services from the modem itself. ``` root@sdxlemur:~# ping ipv6.google.com PING ipv6.google.com(nuq04s45-in-x0e.1e100.net (2607:f8b0:4005:812::200e)) 56 data bytes 64 bytes from nuq04s45-in-x0e.1e100.net (2607:f8b0:4005:812::200e): icmp_seq=1 ttl=53 time=43.8 ms 64 bytes from nuq04s45-in-x0e.1e100.net (2607:f8b0:4005:812::200e): icmp_seq=2 ttl=53 time=42.0 ms ^C --- ipv6.google.com ping statistics --- 2 packets transmitted, 2 received, 0% packet loss, time 1001ms rtt min/avg/max/mdev = 41.972/42.873/43.775/0.901 ms root@sdxlemur:~# ping google.com PING google.com(sfo03s32-in-x0e.1e100.net (2607:f8b0:4005:814::200e)) 56 data bytes 64 bytes from sfo03s32-in-x0e.1e100.net (2607:f8b0:4005:814::200e): icmp_seq=1 ttl=53 time=49.9 ms 64 bytes from sfo03s32-in-x0e.1e100.net (2607:f8b0:4005:814::200e): icmp_seq=2 ttl=53 time=44.7 ms ^C --- google.com ping statistics --- 2 packets transmitted, 2 received, 0% packet loss, time 1001ms rtt min/avg/max/mdev = 44.738/47.330/49.922/2.592 ms root@sdxlemur:~# ping ipv4.google.com PING ipv4.l.google.com (142.251.46.238) 56(84) bytes of data. ping: sendmsg: Operation not permitted ping: sendmsg: Operation not permitted ^C ``` It appears to work correctly at my router/laptop level, going through the modem, just not connections originating on the modem itself (thus, I can't speedtest, or download the latest version of the toolkit, without disabling IPPT).
kerem closed this issue 2026-02-27 14:38:52 +03:00
Author
Owner

@iamromulan commented on GitHub (Mar 23, 2025):

Which module is it? I'll try to see if I see the same thing.

<!-- gh-comment-id:2746351659 --> @iamromulan commented on GitHub (Mar 23, 2025): Which module is it? I'll try to see if I see the same thing.
Author
Owner

@ripclap commented on GitHub (Apr 10, 2025):

Modem: RM520N-GL
Firmware Version: RM520NGLAAR01A08M4G_01.206.01.206

Summary:
The modem's rmnet_data1 interface (IP 169.254.5.1) wasn't accessing the Internet because an iptables rule was dropping all traffic from the 169.254.0.0/16 range.

This rule is created automatically when running:
AT+QMAP="mpdn_rule",0,1,0,1,1,"FF:FF:FF:FF:FF:FF"

This issue was replicated on firmware version RM520NGLAAR01A08M4G_01.206.01.206 and does not occur on other releases.

Workaround:

  1. Find the rule:
    Run this command to list the OUTPUT chain with line numbers:

    iptables -L OUTPUT --line-numbers
    

    You should see something like:

    Chain OUTPUT (policy ACCEPT)
    num  target     prot opt source               destination
    1    DROP       all  --  169.254.0.0/16       anywhere
    
  2. Delete the rule:
    Remove the rule by its number (for example, if it's rule number 1):

    iptables -D OUTPUT 1
    

After that, the modem's internal connection should work, though the DROP rule will reinitialize on reboot.

<!-- gh-comment-id:2795024304 --> @ripclap commented on GitHub (Apr 10, 2025): **Modem**: RM520N-GL **Firmware Version**: RM520NGLAAR01A08M4G_01.206.01.206 **Summary:** The modem's rmnet_data1 interface (IP 169.254.5.1) wasn't accessing the Internet because an iptables rule was dropping all traffic from the 169.254.0.0/16 range. This rule is created automatically when running: ```AT+QMAP="mpdn_rule",0,1,0,1,1,"FF:FF:FF:FF:FF:FF"``` This issue was replicated on firmware version RM520NGLAAR01A08M4G_01.206.01.206 and does not occur on other releases. **Workaround:** 1. **Find the rule:** Run this command to list the OUTPUT chain with line numbers: ```bash iptables -L OUTPUT --line-numbers ``` You should see something like: ``` Chain OUTPUT (policy ACCEPT) num target prot opt source destination 1 DROP all -- 169.254.0.0/16 anywhere ``` 2. **Delete the rule:** Remove the rule by its number (for example, if it's rule number 1): ```bash iptables -D OUTPUT 1 ``` After that, the modem's internal connection should work, though the DROP rule will reinitialize on reboot.
Author
Owner

@jhenkens commented on GitHub (Apr 10, 2025):

Sorry, somehow I missed the initial reply in my inbox. Yes, RM520N.

<!-- gh-comment-id:2795130420 --> @jhenkens commented on GitHub (Apr 10, 2025): Sorry, somehow I missed the initial reply in my inbox. Yes, RM520N.
Author
Owner

@ripclap commented on GitHub (Apr 12, 2025):

@jhenkens

Send the output of:
AT+QGMR

<!-- gh-comment-id:2799024688 --> @ripclap commented on GitHub (Apr 12, 2025): @jhenkens Send the output of: AT+QGMR
Author
Owner

@jhenkens commented on GitHub (Apr 14, 2025):

AT+QGMR

RM520NGLAAR01A08M4G_01.206.01.206

OK
<!-- gh-comment-id:2800554351 --> @jhenkens commented on GitHub (Apr 14, 2025): ``` AT+QGMR RM520NGLAAR01A08M4G_01.206.01.206 OK ```
Author
Owner

@ripclap commented on GitHub (Apr 15, 2025):

AT+QGMR

RM520NGLAAR01A08M4G_01.206.01.206

OK

I shared a workaround above, but if you don't specifically need that firmware version, I recommend downgrading — the issue doesn’t occur in earlier versions.

<!-- gh-comment-id:2803925862 --> @ripclap commented on GitHub (Apr 15, 2025): > ``` > AT+QGMR > > RM520NGLAAR01A08M4G_01.206.01.206 > > OK > ``` I shared a workaround above, but if you don't specifically need that firmware version, I recommend downgrading — the issue doesn’t occur in earlier versions.
Sign in to join this conversation.
No labels
pull-request
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/quectel-rgmii-toolkit#51
No description provided.