Sys Log : Interface 'wan6_4' is setting up now... now down. In loop

mdpatel9558 · February 10, 2024, 6:10pm

Hi,
i try to use 464XLAT but get continue bellow sys log error:

Sat Feb 10 23:31:47 2024 daemon.notice netifd: Interface 'wan6_4' is now down
Sat Feb 10 23:31:47 2024 daemon.notice netifd: Interface 'wan6_4' is setting up now
Sat Feb 10 23:31:50 2024 daemon.notice netifd: Interface 'wan6_4' is now down
Sat Feb 10 23:31:50 2024 daemon.notice netifd: Interface 'wan6_4' is setting up now
Sat Feb 10 23:31:54 2024 daemon.notice netifd: Interface 'wan6_4' is now down
Sat Feb 10 23:31:54 2024 daemon.notice netifd: Interface 'wan6_4' is setting up now
Sat Feb 10 23:31:57 2024 daemon.notice netifd: Interface 'wan6_4' is now down
Sat Feb 10 23:31:57 2024 daemon.notice netifd: Interface 'wan6_4' is setting up now
Sat Feb 10 23:32:00 2024 daemon.notice netifd: Interface 'wan6_4' is now down
Sat Feb 10 23:32:00 2024 daemon.notice netifd: Interface 'wan6_4' is setting up now
Sat Feb 10 23:32:03 2024 daemon.notice netifd: Interface 'wan6_4' is now down
Sat Feb 10 23:32:03 2024 daemon.notice netifd: Interface 'wan6_4' is setting up now
Sat Feb 10 23:32:06 2024 daemon.notice netifd: Interface 'wan6_4' is now down
Sat Feb 10 23:32:06 2024 daemon.notice netifd: Interface 'wan6_4' is setting up now
Sat Feb 10 23:32:10 2024 daemon.notice netifd: Interface 'wan6_4' is now down
Sat Feb 10 23:32:10 2024 daemon.notice netifd: Interface 'wan6_4' is setting up now
Sat Feb 10 23:32:13 2024 daemon.notice netifd: Interface 'wan6_4' is now down
Sat Feb 10 23:32:13 2024 daemon.notice netifd: Interface 'wan6_4' is setting up now
Sat Feb 10 23:32:16 2024 daemon.notice netifd: Interface 'wan6_4' is now down
Sat Feb 10 23:32:16 2024 daemon.notice netifd: Interface 'wan6_4' is setting up now
Sat Feb 10 23:32:19 2024 daemon.notice netifd: Interface 'wan6_4' is now down

How to solve this?

AndrewZ · February 10, 2024, 6:24pm

Please show your current configuration - a fragment from /etc/config/network; a fragment of your system log from the moment connection attempt is started and also a result of nslookup ipv4only.arpa.

mdpatel9558 · February 10, 2024, 6:36pm

network


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

config globals 'globals'
	option ula_prefix 'fd84:d2b4:fbf9::/48'
	option packet_steering '1'

config device
	option name 'br-lan'
	option type 'bridge'
	list ports 'lan1'
	list ports 'lan2'
	list ports 'lan3'

config interface 'lan'
	option device 'br-lan'
	option proto 'static'
	option ipaddr '192.168.1.1'
	option netmask '255.255.255.0'
	list dns '1.1.1.1'
	list dns '1.0.0.1'
	list dns '2606:4700:4700::1111'
	list dns '2606:4700:4700::1001'
	option dns_metric '255'

config interface 'wan6'
	option device 'wan'
	option proto 'dhcpv6'
	option reqaddress 'try'
	option reqprefix 'auto'

root@OpenWrt:~# nslookup ipv4only.arpa
Server:127.0.0.1
Address:127.0.0.1:53

Non-authoritative answer:

Non-authoritative answer:
Name:ipv4only.arpa
Address: 192.0.0.171
Name:ipv4only.arpa
Address: 192.0.0.170

AndrewZ · February 10, 2024, 6:43pm

Remove all the custom DNS servers, reboot and check with the same nslookup again.
Also run nslookup openwrt.de and show the result.

mdpatel9558 · February 10, 2024, 6:49pm

root@OpenWrt:~# nslookup openwrt.de 
Server:         127.0.0.1
Address:       127.0.0.1:53                                                                            ** server can't find openwrt.de: REFUSED                                                                ** server can't find openwrt.de: REFUSED            
root@OpenWrt:~# nslookup
BusyBox v1.36.1 (2023-12-28 13:27:49 UTC) multi-call binary.

Usage: nslookup [-type=QUERY_TYPE] [-debug] HOST [DNS_SERVER]

Query DNS about HOST

QUERY_TYPE: soa,ns,a,aaaa,cname,mx,txt,ptr,srv,any

AndrewZ · February 10, 2024, 6:51pm

ifstatus wan6 output please

mdpatel9558 · February 10, 2024, 6:57pm

root@OpenWrt:~# ifstatus wan6                                                                           {                                                                                                               "up": true,                                                                                             "pending": false,                                                                                       "available": true,                                                                                      "autostart": true,                                                                                      "dynamic": false,                                                                                       "uptime": 622,                                                                                          "l3_device": "wan",                                                                                     "proto": "dhcpv6",                                                                                      "device": "wan",                                                                                        "metric": 0,                                                                                            "dns_metric": 0,                                                                                        "delegation": true,                                                                                     "ipv4-address": [                                                                                                                                                                                               ],                                                                                                      "ipv6-address": [                                                                                               {                                                                                                               "address": "2409:40c1:1027:9265:ca7f:54ff:fee1:41d0",                                                   "mask": 64,                                                                                             "preferred": 14398,                                                                                     "valid": 86398                                                                                  }                                                                                               ],                                                                                                      "ipv6-prefix": [                                                                                                                                                                                                ],                                                                                                      "ipv6-prefix-assignment": [                                                                                                                                                                                     ],                                                                                                      "route": [                                                                                                      {                                                                                                               "target": "2409:40c1:1027:9265::",                                                                      "mask": 64,                                                                                             "nexthop": "::",                                                                                        "metric": 256,                                                                                          "valid": 86398,                                                                                         "source": "::/0"                                                                                },                                                                                                      {                                                                                                               "target": "::",                                                                                         "mask": 0,                                                                                              "nexthop": "fe80::604c:2aff:fe0d:2acf",                                                                 "metric": 640,                                                                                          "valid": 1798,                                                                                          "source": "2409:40c1:1027:9265:ca7f:54ff:fee1:41d0/64"                                          }                                                                                               ],                                                                                                      "dns-server": [                                                                                 
],
"dns-search": [

],
"neighbors": [

],
"inactive": {
"ipv4-address": [

],
"ipv6-address": [

],
"route": [

],
"dns-server": [

],
"dns-search": [

],
"neighbors": [

]
},
"data": {

}
}

Use mobile so, text line not copy well.. sorry for that

AndrewZ · February 10, 2024, 7:01pm

Set these custom DNS servers on wan6 and see if it helps.

2606:4700:4700::64
2606:4700:4700::6400

mk24 · February 10, 2024, 9:13pm

All configured DNS servers must run DNS64 and in particular they must return an IPv6 result AAAA record for ipv4only.arpa. The prefix of that result is used to configure 464xlat outgoing prefix. It is almost always 64:ff9b, but some ISPs use a different one and in that case using the ISP's DNS servers will discover it. Using the ISP's DNS servers is always a good idea when starting out.

mdpatel9558 · February 11, 2024, 12:31am

Worked...
some site like speedtest.net take much time to open compare to google.com, fast.com.
And why traceroute add too many request 192.168.0.1 with high 30-40ms ping time?

mdpatel9558 · February 11, 2024, 12:32am

Thank you so much for details..

AndrewZ · February 11, 2024, 10:46am

The initial delay you noticed is typically caused by two factors - time needed for name resolution and the actual connection setup time to the server resolved on the previous step.
You can use dig instead of nslookup and it will show you the "Query time" - this is the DNS processing time. Then in your browser you can see how long it takes to load the particular web page.
The site you mentioned - speedtest.net - has a native IPv6 support, so whatever you see with this site should not have any dependencies on DNS64, 464xlat, etc.

You can use another DNS64 capable server(s) and see if it makes any difference. My understanding your operator does not have any DNS64 capable servers (in the given example they did not provide DNS server address at all), so you can try these Google servers instead of Cloudflare's used now:

2001:4860:4860::6464
2001:4860:4860::64

In my example traceroute shows just two hops, so what you see is probably specific to your particular setup. If you have a few routers daisy chained and the upstream router is IPv4 capable, then you probably don't need to bother about 464xlat at all.

mdpatel9558 · February 11, 2024, 11:18am

5G CPE ZTE MC801A ---> OpenWrt (464XLAT) ---> ASUS GT AX-11000 (merlin)

I use ipv6 only internet isp

Is this possible to work without openWrt ? like bellow..
5G CPE ---> ASUS GT AX-11000

AndrewZ · February 11, 2024, 11:39am

I suppose your 5G CPE has its own 464xlat support, so you don't need one on OpenWrt. Just add a wan interface with DHCP (v4).
Please check what DNS server(s) do you have in 5G CPE GUI and run this on OpenWrt:
nslookup openwrt.de {put DNS server IPv6 here}

I don't see a need in operating 3 routers. If your 5G CPE supports bridge mode you can use one of your devices as a router (+AP) and another as a dumb AP, or just one device (router+AP) if that is sufficient for you.

mdpatel9558 · February 11, 2024, 2:39pm

Yes you are right.. now 5G CPE work with ipv6 internet. i can successfully reach to 1.1.1.1 without openwrt.

BUT, when open http://1.1.1.1 or any ipv4 address in browser get 1-2 time error out of 10.
No get any error when open any ipv6 address like http://[2404:6800:4009:831::200e]/

In asus router DNS selectet by isp. and in 5G CPE DNS is auto
So, what is problem? and where?

AndrewZ · February 11, 2024, 2:54pm

My question was "what was obtained from the carrier", not "what is configured on the device".
You probably have this information on a Status page or something like that.

It looks like your current problem is different from what is in the topic tittle and you're not using OpenWrt anymore, so I suggest to close this topic.

mk24 · February 11, 2024, 2:55pm

I tried to reach that site. Something there answers pings but I don't think it is a web server. Reverse DNS is some sort of internal Google address.

All of the 192.0.0.1 hops you see are inside the ISP. 464 works by having the 64: prefix route to a "PLAT" machine at the edge of the ISP which then NATs your request to the IPv4 Internet. This is considered legacy support. Web sites that want fast access in the modern world should be native v6.

mdpatel9558 · February 11, 2024, 3:15pm

Ok brother.. thank you so much for your help

mdpatel9558 · February 11, 2024, 3:16pm

Ok brother.. thank you for your information..

system · February 21, 2024, 3:16pm

This topic was automatically closed 10 days after the last reply. New replies are no longer allowed.