Ipv4 ping does not work

bluray93 · December 19, 2024, 10:02am

Hi,
I've installed and configured openwrt on x86, I'm connected directly to the sky wifi ont and i've configured it with map-t. It mostly works, ipv4 ping for some reason dows not work while ipv6 does. internet over ipv4 works and also traceroute for an ipv4 address seems to respond correctly. What could possibly be the issue?
Thanks in advice

frollic · December 19, 2024, 10:12am

depends on the error message while doing the ping, doesn't it ?

don't post it, we love fumbling in the dark ...

bluray93 · December 19, 2024, 10:49am

sorry, I'm an advanced noob.

_bernd · December 19, 2024, 11:02am

Is icmpv4 with literal ipv4 addresses supported by map-t?

On v6 only networks I used DNS64 and nat64 to bypass these kind of issues...

bluray93 · December 19, 2024, 11:16am

I can't find any specific documentation about it, I think they should be, the original sky wifi router was able to handle them and in the documentation they provide regarding the installation of different router nothing is mentioned about this issue

_bernd · December 19, 2024, 12:30pm

Could you post ip -d link show and ip -d address show?

And yes regarding to https://pc.nanog.org/static/published/meetings/NANOG71/1452/20171004_Gottlieb_Mapping_Of_Address_v1.pdf literals seams to work...

bluray93 · December 19, 2024, 12:48pm

It seems openwrt doen't linke the -d flag but I hope there are enough details

root@OpenWrt:~# ip address show
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN qlen 1000
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    inet 127.0.0.1/8 scope host lo
       valid_lft forever preferred_lft forever
    inet6 ::1/128 scope host
       valid_lft forever preferred_lft forever
2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel master br-lan state UP qlen 1000
    link/ether bc:24:11:6c:f5:cd brd ff:ff:ff:ff:ff:ff
3: ip6tnl0@NONE: <NOARP> mtu 1452 qdisc noop state DOWN qlen 1000
    link/tunnel6 00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00 brd 00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00
4: eth1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UP qlen 1000
    link/ether 9c:31:c3:b4:3d:98 brd ff:ff:ff:ff:ff:ff
    inet6 fe80::9e31:c3ff:feb4:3d98/64 scope link
       valid_lft forever preferred_lft forever
5: eth2: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc fq_codel master br-lan state DOWN qlen 1000
    link/ether d0:00:06:22:68:55 brd ff:ff:ff:ff:ff:ff
6: eth3: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc fq_codel master br-lan state DOWN qlen 1000
    link/ether d0:00:06:22:68:56 brd ff:ff:ff:ff:ff:ff
7: eth4: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel master br-lan state UP qlen 1000
    link/ether d0:00:06:22:68:57 brd ff:ff:ff:ff:ff:ff
8: eth5: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel master br-lan state UP qlen 1000
    link/ether d0:00:06:22:68:58 brd ff:ff:ff:ff:ff:ff
9: wlan0: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN qlen 1000
    link/ether 34:13:e8:cf:25:c4 brd ff:ff:ff:ff:ff:ff
10: br-lan: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP qlen 1000
    link/ether bc:24:11:6c:f5:cd brd ff:ff:ff:ff:ff:ff
    inet 192.168.0.1/24 brd 192.168.0.255 scope global br-lan
       valid_lft forever preferred_lft forever
    inet6 2a0e:423:8d65::1/64 scope global dynamic noprefixroute
       valid_lft 2307sec preferred_lft 2307sec
    inet6 fe80::be24:11ff:fe6c:f5cd/64 scope link
       valid_lft forever preferred_lft forever
11: eth1.101@eth1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP qlen 1000
    link/ether 9c:31:c3:b4:3d:98 brd ff:ff:ff:ff:ff:ff
    inet6 fe80::9e31:c3ff:feb4:3d98/64 scope link
       valid_lft forever preferred_lft forever
12: map-WAN6_4: <POINTOPOINT,NOARP,UP,LOWER_UP> mtu 16384 qdisc noqueue state UNKNOWN qlen 1000
    link/[65534]
    inet6 fe80::ef6e:cbcf:b205:9010/64 scope link flags 800
       valid_lft forever preferred_lft forever

ip link show
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN qlen 1000
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel master br-lan state UP qlen 1000
    link/ether bc:24:11:6c:f5:cd brd ff:ff:ff:ff:ff:ff
3: ip6tnl0@NONE: <NOARP> mtu 1452 qdisc noop state DOWN qlen 1000
    link/tunnel6 00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00 brd 00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00
4: eth1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UP qlen 1000
    link/ether 9c:31:c3:b4:3d:98 brd ff:ff:ff:ff:ff:ff
5: eth2: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc fq_codel master br-lan state DOWN qlen 1000
    link/ether d0:00:06:22:68:55 brd ff:ff:ff:ff:ff:ff
6: eth3: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc fq_codel master br-lan state DOWN qlen 1000
    link/ether d0:00:06:22:68:56 brd ff:ff:ff:ff:ff:ff
7: eth4: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel master br-lan state UP qlen 1000
    link/ether d0:00:06:22:68:57 brd ff:ff:ff:ff:ff:ff
8: eth5: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel master br-lan state UP qlen 1000
    link/ether d0:00:06:22:68:58 brd ff:ff:ff:ff:ff:ff
9: wlan0: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN qlen 1000
    link/ether 34:13:e8:cf:25:c4 brd ff:ff:ff:ff:ff:ff
10: br-lan: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP qlen 1000
    link/ether bc:24:11:6c:f5:cd brd ff:ff:ff:ff:ff:ff
11: eth1.101@eth1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP qlen 1000
    link/ether 9c:31:c3:b4:3d:98 brd ff:ff:ff:ff:ff:ff
12: map-WAN6_4: <POINTOPOINT,NOARP,UP,LOWER_UP> mtu 16384 qdisc noqueue state UNKNOWN qlen 1000
    link/[65534]

_bernd · December 19, 2024, 1:05pm

Thanks.

Shouldn't there be any IPv4 address on the map-WAN6_4 interface?
Sorry I forgot to ask about ip -4 route show...

bluray93 · December 19, 2024, 1:13pm

the map-WAN6_4 interface appeared automatically after I installed the map package in openwrt. I can't configure it

root@OpenWrt:~# ip -4 route show
default dev map-WAN6_4 scope link
192.168.0.0/24 dev br-lan scope link  src 192.168.0.1

_bernd · December 19, 2024, 1:22pm

I tried to verify but I can't....
I'm still not sure but I think the map-t interface needs a global IPv6 address and at least some ipv4...
See i.e. https://www.jool.mx/en/run-mapt.html (from the point of you of a provider/network operator)

mk24 · December 19, 2024, 1:53pm

I don't see how this works without wan holding an IPv4 address. There is no place to originate pings from.

What does a traceroute from a LAN computer to an external v4 address such as 1.1.1.1 report?

bluray93 · December 19, 2024, 2:00pm

root@Wireguard:/# traceroute 1.1.1.1
traceroute to 1.1.1.1 (1.1.1.1), 30 hops max, 60 byte packets
 1  192.168.0.1 (192.168.0.1)  0.436 ms  0.350 ms  0.321 ms
 2  101.56.184.214 (101.56.184.214)  0.832 ms  0.793 ms  0.757 ms
 3  101.56.184.214 (101.56.184.214)  7.239 ms  7.195 ms  7.131 ms
 4  * * *

I've also noticed these errors when i ping 1.1.1.1 for example

_bernd · December 19, 2024, 6:15pm

I don't think is related.... Ok putting the sarcasm aside, how did you configured the interface with UCI in etc config network?

porshuram · December 19, 2024, 6:52pm

maybe some external firewall is preventing ipv4 ping flood

_bernd · December 19, 2024, 10:10pm

Sry but one ping a second is hardly a flood.

porshuram · December 20, 2024, 10:53am

instead of detecting flood the firewall is set to block all icmp echo request.

_bernd · December 20, 2024, 1:34pm

When this is done by the ISP it would be more then dump. Also the user said it was working before with the provider equipment...

bluray93 · December 20, 2024, 5:12pm

Afterall the configuration is very basic

config interface 'loopback'
        option device 'lo'
        option proto 'static'
        option ipaddr '127.0.0.1'
        option netmask '255.0.0.0'

config globals 'globals'

config device
        option name 'br-lan'
        option type 'bridge'
        list ports 'eth0'
        list ports 'eth2'
        list ports 'eth3'
        list ports 'eth4'
        list ports 'eth5'

config interface 'lan'
        option device 'br-lan'
        option proto 'static'
        option ipaddr '192.168.0.1'
        option netmask '255.255.255.0'
        option ip6assign '64'
        option delegate '0'

config interface 'WAN'
        option proto 'dhcp'
        option device 'eth1.101'
        option peerdns '0'
        list dns '1.1.1.1'

config device
        option name 'eth1'
        option macaddr '9C:31:C3:B4:3D:98'

config device
        option type '8021q'
        option ifname 'eth1'
        option vid '101'
        option name 'eth1.101'

config interface 'WAN6'
        option proto 'dhcpv6'
        option device 'eth1.101'
        option reqaddress 'try'
        option reqprefix 'auto'
        option peerdns '0'
        list dns '2606:4700:4700::1111'

_bernd · December 20, 2024, 6:45pm

I see but where do you configure the wan interface as map-t device?

_bernd · December 21, 2024, 12:39am

@bluray93 you might find this of interest: https://www.ripe.net/media/documents/Richard_Patterson_-_Sky_Italia_and_MAP-T_-_RIPE_Open_House_2021.pdf