Hello,
this is my configuration:
#1. RT-AC87U with asuswrt-merlin firmware 378.56_2 acting as main router. Some devices connected to it through ethernet cable, some others through wireless 2,4 or 5 Ghz.
#2. RT-N66U with asuswrt-merlin firmware 378.56_2 in bridge mode to main router on 5Ghz wireless. Some devices connected through ethernet cable to it.
Everything is working fine.
When I've tried to upgrade the #2 firmare to last version (380.57) the bridge mode worked fine. I was able to reach devices ethernet connected to #1 and to reach websites.
The problem is when I tried to open #2 admin UI:
- if I try from a device directly connected to #2 the #2 admin page is unreacheable and the router #2 reboot itself
- if I try from a device connected to #1 (both ethernet or wireless) the #2 admin page is reacheable and I can restore #2 default settings
If I restore #2 default settings I can reach the #2 admin page from devices directly connected to #2, so I think the problem is only in bridge mode and only in firmware version 380.57.
Is someone able to confirm if it is a bug or not?
Sorry for my poor english.
Thanks,
Andrea
this is my configuration:
#1. RT-AC87U with asuswrt-merlin firmware 378.56_2 acting as main router. Some devices connected to it through ethernet cable, some others through wireless 2,4 or 5 Ghz.
#2. RT-N66U with asuswrt-merlin firmware 378.56_2 in bridge mode to main router on 5Ghz wireless. Some devices connected through ethernet cable to it.
Everything is working fine.
When I've tried to upgrade the #2 firmare to last version (380.57) the bridge mode worked fine. I was able to reach devices ethernet connected to #1 and to reach websites.
The problem is when I tried to open #2 admin UI:
- if I try from a device directly connected to #2 the #2 admin page is unreacheable and the router #2 reboot itself
- if I try from a device connected to #1 (both ethernet or wireless) the #2 admin page is reacheable and I can restore #2 default settings
If I restore #2 default settings I can reach the #2 admin page from devices directly connected to #2, so I think the problem is only in bridge mode and only in firmware version 380.57.
Is someone able to confirm if it is a bug or not?
Sorry for my poor english.
Thanks,
Andrea