Mediabridge not working on 5Ghz (Firmware 378.55)

[Sjekke]

I installed the latest version of Merlin Firmware 378.55. I have 2x RT-AC66U.'s. 1 router is used in Mediabridge mode to connect other network devices in an other room. Since the upgrade I can only connect to my other router in 2Ghz. 5Ghz doesn't work anymore. With older firmware it's works without any issues.

Suggestion?

Rgrds
Sjekke

 

[T-Nation]

I installed the latest version of Merlin Firmware 378.55. I have 2x RT-AC66U.'s. 1 router is used in Mediabridge mode to connect other network devices in an other room. Since the upgrade I can only connect to my other router in 2Ghz. 5Ghz doesn't work anymore. With older firmware it's works without any issues.

Suggestion?

Rgrds
Sjekke

So, Ill try and help if I can...

I have a 66R and 68U bridged to the 87U on the 5GHz band. I did run into an issue if I rebooted one of those devices with in 5mins or less I could not connect to the one I rebooted. I started to think it was Asus firmware since I had stock on those two and Merlin on the 87U. I installed Merlin on the 68U and problem still happened. So I put the stock back on with hard reset ( did it with Merlin too ) and problem still happened. So I started to think it was the stupid 5Ghz driver part of the 87U or the way the DHCP was handling things. Long story short and a lot of swearing... I found if I reboot the routers connected to the main 87U bridge first then reboot the 87U last everything is golden and works perfect. Pain in the butt but solved the problem.

 

[JohnNerd]

On Merlin build Media bridge is still not working here. Videoplay stops, and not responsive, problem reading folders. On DD-WRT its working a whole lot better, fast and responsive.

I get this message:
"eth2: received packet with own address as source address"

 

[Sjekke]

I changed the function on both routers (media bridge vs router) and now it works. Strange.

 

[R1-Limited]

I may be having the same issue. This never happened until I went to 55_0

I updated three days ago, I have noticed in the past 3 days each morning I have had to reboot the RT-ac66u to get connection back to my PC. I get the dang APIPA Default as I cannot get connected to the router. All devices fail to get internet or an IP. I cannot ping the Bridge (ac66u) nor the AP. Of course this is from the APIPA so no worries. I have had to reboot the 66u each morning to get an IP. Thinking of moving back to previous build which was 54-2 beta. I may just try defaulting all and seeing what happens

Set is simple
AP = RT-ac68u
Wireless Bridge = RT-ac66u (To AP)
Netgear Prosafe router to 66
PC, Printer, 2 VoiP, 1 WyseP25, Linux Mint box connected to 66U

And for the record, I see nothign out of the ordinary in the logs of either router. Stilllooking at logs on Windows

 

[R1-Limited]

I may be having the same issue. This never happened until I went to 55_0

I updated three days ago, I have noticed in the past 3 days each morning I have had to reboot the RT-ac66u to get connection back to my PC. I get the dang APIPA Default as I cannot get connected to the router. All devices fail to get internet or an IP. I cannot ping the Bridge (ac66u) nor the AP. Of course this is from the APIPA so no worries. I have had to reboot the 66u each morning to get an IP. Thinking of moving back to previous build which was 54-2 beta. I may just try defaulting all and seeing what happens

Set is simple
AP = RT-ac68u
Wireless Bridge = RT-ac66u (To AP)
Netgear Prosafe router to 66
PC, Printer, 2 VoiP, 1 WyseP25, Linux Mint box connected to 66U

And for the record, I see nothing out of the ordinary in the logs of either router. Still looking at logs on Windows

Update 6:41 AM PST
I reverted back to latest stable build and shut it all down (PCs) as a normal day. Hard booted the AP and Bridge. This morning I am happy to say my PC and wyse booted to its reserved IP without issues. Ya 55_0 has issues at least for me. I am not willing to update again as next step would be to factory defauilt both AP and Bridge then start again to test.

 

[T-Nation]

Well as much as I would love to say its not 55_0, I believe it stems from this version for some reason. I switch to the latest beta on my 87U and the media bridge works as it should. I watch a few movies and so far so good...

Note: I left the routers up for about 24hrs before I watched movies to make sure I could still access the bridged routers, which is where I could see if the problem reappeared. I even rebooted one to see if it lost connection after a short while as it did with 55_0. As of right now everything is working as it should...

Setting wise I turn off NAT Acceleration on all the routers, I've done this way before I bought the 87U due to how fickle it can be. I leave the 5Ghz and 2.4Ghz settings mainly at default but change Preamble Type to short. Beamforming I gave up on along time ago and leave it off. Oh on Merlin's I would turn off STP, Asus i believe its on by default. Pretty much everything under the USB apps is off also. Not sure if this would make a difference either but I manually assign the bridged routers 192.168.1.2 and 192.168.1.3 with the DNS and gateway set to 192.168.1.1.

Hopefully some info here helps track down whats going on cause I actually like running Merlins builds. But for now Asus betas are working so I'll sit with them for now.

PS... I always reset my routers after updates, and manually enter the info.... pain in the butt but saves some odd glitch getting written back into the new firmware.

 

[R1-Limited]

^^ Echo that, day 2 n the last stable build (54_2) and no issues what so ever. Coincidence? I think not