Known Hosts Configuration for RT-AC66U

[bnhf]

I'm considering moving to an RT-AC66U, running AsusWRT-Merlin, as my primary router in place of a Cradlepoint MBR1400. About half the year I'm connected via Ethernet and the other half using one of several USB Modems. There are some things I'll miss about the MBR1400, but I want to be able to run a router-based OpenVPN client and Merlin is so slick for that!

One feature of that Cradlepoint model is the ability to add a "Known Host" through the GUI. Basically just a local DNS that allows me to assign whatever name I want to a LAN IP address. Only used for devices which have static IP addresses, or DHCP reservations on my network. Sometimes I'll use it to create a short version of a name like "RPi" for "RaspberryPi", sometimes just to reinforce a NETBIOS name that doesn't always resolve reliably, or for a device which doesn't have or doesn't broadcast a NETBIOS name.

So I'm guessing I could edit the router's hosts file -- if so, is anyone doing this? Also, I'm wondering if there's a way to do it through the GUI that I'm missing somehow?

 

[ColinTaylor]

It's simple to do it in the GUI. Just create a DHCP reservation for the device (even if it doesn't use DHCP ) and you can also specify a host name associated with the IP address (a Merlin enhancement over stock). Much easier that manually editing hosts files.

 

[thelonelycoder]

Use the hosts.add which you place in /jffs/configs/
See wiki for more info:
https://github.com/RMerl/asuswrt-merlin/wiki/Custom-config-files

 

[bnhf]

It's simple to do it in the GUI. Just create a DHCP reservation for the device (even if it doesn't use DHCP ) and you can also specify a host name associated with the IP address (a Merlin enhancement over stock). Much easier that manually editing hosts files.

So the Hostname in the manual DHCP assignment section doesn't need to be the actual Hostname (if one exists), but rather can be any name you'd like to use? The MAC address is all that's used for the actual IP reservation? The device's broadcast Hostname will still be resolved too if the router is the Master Browser?

 

[ColinTaylor]

So the Hostname in the manual DHCP assignment section doesn't need to be the actual Hostname (if one exists), but rather can be any name you'd like to use?

Correct

The MAC address is all that's used for the actual IP reservation?

Correct

The device's broadcast Hostname will still be resolved too if the router is the Master Browser?

All the DHCP assignment does is put the MAC to IP addresses in /etc/ethers and the IP to hostnames in a secondary hosts file both of which are used by dnsmasq. NetBIOS name resolution is done by broadcast packets rather than DNS lookups. So that should still work the same.

 

[bnhf]

Cool. You gotta love AsusWRT-Merlin (many, many thanks RMerlin)! Thanks for clueing me in ColinTaylor. I think I just lost my last reason for staying with my Cradlepoint.

 

[bnhf]

Use the hosts.add which you place in /jffs/configs/
See wiki for more info:
https://github.com/RMerl/asuswrt-merlin/wiki/Custom-config-files

I'm going to give the GUI route a shot as outlined by ColinTaylor. I appreciate the heads-up on the hosts.add approach though -- it may come in handy if I want to have more than one alternate Hostname.

BTW, I checked out your website and I really like what you've done with router-based ad blocking. That's definitely been on my wishlist for a while. I'm going to give it a try -- so I think I'll order one of those nano-sized USB flash drives for it. The USB ports on the AC66U are super close together and I need maximum real estate for my USB modem(s). Thanks for the work you've done in this area!

 

[thelonelycoder]

-- so I think I'll order one of those nano-sized USB flash drives for it. The USB ports on the AC66U are super close together and I need maximum real estate for my USB modem(s). Thanks for the work you've done in this area!

I use short USB extension cables. Works better than squeezing devices in.

 

[ColinTaylor]

The USB ports on the AC66U are super close together and I need maximum real estate for my USB modem(s).

I don't know whether you intend using the router's built in USB modem support or have a totally independent external unit. But I've read that the router's modem support is fairly limited, so don't assume a particular device will work. Just sayin'

 

[bnhf]

I don't know whether you intend using the router's built in USB modem support or have a totally independent external unit. But I've read that the router's modem support is fairly limited, so don't assume a particular device will work. Just sayin'

Very good point. Absolutely worth a good testing before cutting-over to the new router.

First test with a Pantech UML290 on Verizon (US). It's easy to think the Asus doesn't work with a particular modem because the settings are so critical, so I'm posting screenshots just in case someone stumbles across this thread:

The modem is working great thus far. Speedtest.net is giving me typical 4G LTE results for this area. This post composed using the above connection. I'll post configuration for my Netgear Beam 340U on AT&T (US), assuming I get it working, in a bit.

 

[bnhf]

So the results with the Sierra AirCard 340U seem good too -- though it's a bit more involved to get it going.

The AC340U needs the following:

A firmware update to the latest using the AT&T All Access Windows application. The app may update and then the new firmware will after that, if needed:

http://www.att.com/att/allaccess/downloads/ATT-ALLACCESS-10-1-305-WIN.zip

Then the AC340U patch for Linux (it's a Windows utility to install it though):

http://www.proxicast.com/support/files/AC340U_linux_patch_v4_S08511.exe

Then the AC340U AutoConnect utility needs to be run:

http://www.proxicast.com/support/files/AC340U_autoconnect_enable.exe

You can turn that off later if you don't want it to auto connect in a future application with this utility:

http://www.proxicast.com/support/files/AC340U_autoconnect_disable.exe

All of these steps are outlined in this post for more detail. The IP Pass-Through patch (mentioned in the post I'm referencing) is permanent and is not required for APN=broadband applications (which is me here in the US):

http://www.proxicast.com/AbsoluteFM/afmviewfaq.aspx?faqid=268

Here are the settings for the RT-AC66U:

No issues so far, except the LCD on the AC340U reads "Ready to connect" even though it's connected. Signal strength in bars and connection type (e.g. 4G LTE) are still shown.