Network not stable in AP mode
Hi,
My deco p9 continue crashing by creating issue on network, in attach a log file created just after have loaded the firmware.
Seems that this issue is present also for other users, how can I solve this issue?
- Copy Link
- Subscribe
- Bookmark
- Report Inappropriate Content
Hi, have you checked the Backhaul type on the Deco P9, WiFi only or PLC/WiFi Backhaul?
How long have you had this issue and when did the disconnection start?
here is a beta firmware for Deco P9 and please install this beta firmware and check whether it helped with the current issue:
Deco_P9_V1_V2_1.1.3_build 20210616
Wait for your reply.
Best regards.
- Copy Link
- Report Inappropriate Content
@Luke112 Hi, thanks for your reply, about your question:
Hi, have you checked the Backhaul type on the Deco P9, WiFi only or PLC/WiFi Backhaul? --> Only Wifi
How long have you had this issue and when did the disconnection start? --> after the switch from router mode to ap mode ( that I have to use with this configuration ), so we can say 2 weeks more or less
about firmware --> by looking the name should be a fw linked to the version V1, in my case I should load a fw for hardware version v2, could you share a link to use for upload my Deco p9?
thanks
Luca
- Copy Link
- Report Inappropriate Content
Hi, the beta is for V1 and V2.
Since you mentioned they are on the WiFi Backhaul, is your house under a different power circuit? If P9s are separated by different walls or floors, the wireless Backhaul sometimes could be very unstable and its powerline Backhaul would help in this way. And Did the wireless Backhaul have at least 2 bars?
By the way, could you please also help me check some details:
1. Would any P9s turn to flash red during the disconnection?
2. Can I have a picture of your current network layout, such as:
Internet--main ISP router---main P9---<WiFi>1st satellite P9----<WiFi>---2nd satellite P9
3. How often would the disconnection repeat? Do you need to restart the Deco P9 to get the connection back?
Wait for your reply.
Best regards.
- Copy Link
- Report Inappropriate Content
ok clear, thanks for explanation, by using your link "Deco_P9_V1_V2_1.1.3_build 20210616" I can't able to download / or find it in TP-Link website
however, let me answer to you question:
Backhaul would help in this way. And Did the wireless Backhaul have at least 2 bars? --> yep, but also if I'm close to the "main" p9 nothing change
1. Would any P9s turn to flash red during the disconnection? I need to check, I will back to you soon
2. Can I have a picture of your current network layout, such as:
Internet--main ISP router---main P9---<WiFi>1st satellite P9----<WiFi>---2nd satellite P9---<WiFi>---3nd satellite P9 ---> right this is my network picture
3. How often would the disconnection repeat? Do you need to restart the Deco P9 to get the connection back? --> very often, with whatsapp ( video call ), with microsoft teams also, with netflix also, so in each time that I have to use the wifi
Wait for your reply.
Best regards.
- Copy Link
- Report Inappropriate Content
- Copy Link
- Report Inappropriate Content
in attach some log may could help ;), and below last part of log that coming from Master p9
Fri May 12 13:07:59 2023 daemon.emerg procd: RTNETLINK answers: Cannot assign requested address
Fri May 12 13:07:59 2023 user.emerg IMPROXY: FATAL[init_interface@251]: exiting.....
Fri May 12 13:08:01 2023 daemon.emerg procd: /etc/rc.common: line 1: can't create /proc/sys/net/ipv6/conf/br-wan/disable_ipv6: nonexistent directory
Fri May 12 13:08:04 2023 user.emerg IMPROXY: FATAL[init_interface@251]: exiting.....
Fri May 12 13:08:05 2023 daemon.emerg procd: uci: Entry not found
Fri May 12 13:08:05 2023 daemon.emerg procd: uci: Entry not found
Fri May 12 13:08:05 2023 daemon.emerg procd: uci: Entry not found
Fri May 12 13:08:05 2023 daemon.emerg procd: uci: Entry not found
Fri May 12 13:08:05 2023 daemon.emerg procd: uci: Entry not found
Fri May 12 13:08:05 2023 daemon.emerg procd: uci: Entry not found
Fri May 12 13:08:05 2023 daemon.emerg procd: uci: Entry not found
Fri May 12 13:08:05 2023 daemon.emerg procd: uci: Entry not found
Fri May 12 13:08:05 2023 daemon.emerg procd: uci: Entry not found
Fri May 12 13:08:05 2023 daemon.emerg procd: uci: Entry not found
Fri May 12 13:08:05 2023 daemon.emerg procd: uci: Entry not found
Fri May 12 13:08:06 2023 daemon.emerg procd: uci: Entry not found
Fri May 12 13:08:06 2023 daemon.emerg procd: uci: Entry not found
Fri May 12 13:08:06 2023 daemon.emerg procd: uci: Entry not found
Fri May 12 13:08:06 2023 daemon.emerg procd: uci: Entry not found
Fri May 12 13:08:06 2023 daemon.emerg procd: uci: Entry not found
Fri May 12 13:08:09 2023 user.emerg IMPROXY: FATAL[init_interface@251]: exiting.....
Fri May 12 13:08:14 2023 user.emerg IMPROXY: FATAL[init_interface@251]: exiting.....
Fri May 12 13:08:19 2023 user.emerg IMPROXY: FATAL[init_interface@251]: exiting.....
Fri May 12 13:08:24 2023 user.emerg IMPROXY: FATAL[init_interface@251]: exiting.....
Fri May 12 13:09:40 2023 user.emerg syslog: tp215,22[9758]:
- Copy Link
- Report Inappropriate Content
Information
Helpful: 0
Views: 511
Replies: 6
Voters 0
No one has voted for it yet.