Setting up Raspberry Pi on Asus RT-AC66U

[TheHellYouSay]

I quickly moved over to asuswrt-merlin after I could not get things working properly with upgraded stock firmware. The Raspberry Pi has an EDIMax wireless dongle. I am tech savvy (for the most part) and I had this working great on my old Linksys WRT54GL router using dd-wrt. It just connected because all the configuration was done on the Linux side of the house. Tell it the SSID and password and you were in.

This time, it simply won't connect. I found some articles suggesting that a very simple UI be installed on the Raspberry Pi called wicd-curses. I have used that and it still won't connect and doesn't tell me why. Where can I look to troubleshoot this problem?

A separate issue is my Squeezebox. If you're not familiar with Squeezebox, there are quite a few components. In my case, I have a Squeezebox Receiver which connects to my Netgear Duo storage appliance on port 9000 which is where the Squeezebox service is running. The receiver has a wired connection, but also a wireless connection. The router picks it up on the wireless, but I would much prefer it used the wired connection. Oddly enough, I've seen both the controller and the receiver on the wired side at one time or another, but the controller only has a wireless connection. How can I make sure that the receiver connects on the wired side? I have had nothing but trouble with getting this to work, usually I have to turn off the firewall, but I did have it working at one time with firewall on and ports 9000 and 3843 forwarded to the NAS.

Are there logs I should be looking at? Just tell me how to troubleshoot these issues and I'll try them, but right now I am quite frustrated with this thing having been working on getting things right for over a week now.

 

[lyanna]

In order to have Pi working with the new Asus router you should:
1) set the same SSID and encryption (as the old router)
2) set the same password
3) enable both 2.4GHz and 5GHz bands at least until you have everything working.

 

[martinr]

Why not connect the Pi temporarily to the router using an ethernet cable, firstly to see if you can (and thereby prove that your problem really is related to the wireless connection) and, secondly, to access the apprpriate config file where SSID, password and, if you're using it, static IP address is located.

 

[joegreat]

I quickly moved over to asuswrt-merlin after I could not get things working properly with upgraded stock firmware. The Raspberry Pi has an EDIMax wireless dongle. I am tech savvy (for the most part) and I had this working great on my old Linksys WRT54GL router using dd-wrt. It just connected because all the configuration was done on the Linux side of the house. Tell it the SSID and password and you were in.

This time, it simply won't connect. I found some articles suggesting that a very simple UI be installed on the Raspberry Pi called wicd-curses. I have used that and it still won't connect and doesn't tell me why. Where can I look to troubleshoot this problem?

Hi,

I am running multiple RaspBerries Pi 2 wiht the EdiMax dongle without any issue (on both routers - see footer).

Re-Check your configuration and avoid strange characters (and no spaces!) in SSID and password! Try using only a-z or A-Z and 0-9....

With kind regards
Joe

 

[wh7qq]

I've run my Raspi B+ on both the Edimax wifi and ethernet on both my N66U and N56U...no problems. I have noticed some problems with it fighting with my wireless keyboard/mouse. Try going with a USB keyboard/mouse if you aren't already doing so.

 

[TheHellYouSay]

Thank you for all your replies. Now I am 100% convinced that its definitely not something on the router. Also, many things have just fallen into place. Last night I got it to hook up to the router, but had to use wicd-curses, which meant console level, lots of frustration. Took a couple of tries, but it connected, then I successfully connected with ssh. Was able to assign the static IP because the router could now see the MAC address. Rebooted the router and went to bed. This morning the Squeezebox setup looks to be right (has an amber colored light instead of blue) and I attribute this to fiddling with the ipV6 firewall setting or just pure dumb luck. I am just not a networking type person, I just want it to work. Unfortunately, the Squeezebox has its own nuances and so I thought I might lose my mind. I may still, but today I've got chores, and if the Squeezebox works, I'm happy for now. The option Enable IPv6 Firewall is now set to Yes. Even though I don't know a whole lot about firewalls, I heard they're good, so I leave them on. Unless stuff stops working... then I fiddle and forget...

The Model B has had some struggles lately with power supplies (only works with 1 I've found so far) and spontaneous reboots were happening and so perhaps something is messed up with the Pi's boot-up files and/or the USB dongle is hosed. I promise I'll post when I figure it out, if the Pi posters are interested. I have invested so many hours in setting that thing up, it's frustrating when its not working like I expect it to. I have rolled back to an image from last year and it behaves similarly so I'm just baffled.

Have a great day all. Thanks again...

 

[wh7qq]

The Model B has had some struggles lately with power supplies (only works with 1 I've found so far) and spontaneous reboots were happening and so perhaps something is messed up with the Pi's boot-up files and/or the USB dongle is hosed. I promise I'll post when I figure it out, if the Pi posters are interested. I have invested so many hours in setting that thing up, it's frustrating when its not working like I expect it to. I have rolled back to an image from last year and it behaves similarly so I'm just baffled.
Have a great day all. Thanks again...

One of the biggest problems with the RPi is trying to run a phone grade USB charger...often the demands on the USB lines will put the system over the top of their current capability resulting in reboots and other problems. Small wire gauge on long charger cables will also cause significant voltage drop and the RPi is very sensitive if the voltage drops much. You need a 2+ amp output power brick of 5, or preferably 5.25 volt output. Many computer USB ports will not run it either. See Adafruit.com for power bricks/cables that will do it.

 

[Cake]

One of the biggest problems with the RPi is trying to run a phone grade USB charger...often the demands on the USB lines will put the system over the top of their current capability resulting in reboots and other problems. Small wire gauge on long charger cables will also cause significant voltage drop and the RPi is very sensitive if the voltage drops much. You need a 2+ amp output power brick of 5, or preferably 5.25 volt output. Many computer USB ports will not run it either. See Adafruit.com for power bricks/cables that will do it.

A little off topic but, I have had the exact same issue in the past with some of mine, it sometimes then gets frustratingly compounded by corrupting possibly bricking cheap sdcards (knockoffs) too. I ended up doing something similar to this link when I had a couple usb hard drives plugged in just to get passed boot (hd spin up at same time).
http://www.instructables.com/id/Solder-USB-power-cable-to-Raspberry-Pi/
I still needed a decent power supply like you mention, but it wouldn't trip the breaker on the pi board.

 

[wh7qq]

A little off topic but, I have had the exact same issue in the past with some of mine, it sometimes then gets frustratingly compounded by corrupting possibly bricking cheap sdcards (knockoffs) too.

That's the other big thing with the RPi...you can't count on cheap SD and microSD cards...the high grade cards from San Disk are the way to go. The same with USB sticks for use with a router...if you expect to beat it a lot as with media recording and playback, go with the good stuff.

 

[TheHellYouSay]

Thanks for the help on the Raspberry Pi power issue, sorry about going off topic. I got a new Edimax dongle and it connected just fine with the simplest of configurations. I spent quite a few evenings trying to understand the problems with the spontaneous reboots, but eventually, when it always failed trying to start MySQL I figured it was either a corrupt image OR possibly a power supply. When I finally got it to boot up once or twice, then I knew it was the power cord and invested in some better quality ones. I think the wireless USB dongle must have taken a hit somewhere along the line because this new one works great.