WRT600N Bugs..

Summary
  • WRT600N Firmware 1.01.36 Build 3 provides DHCP clients w/ DNS entries in a strange order.
  • ISP's DNS -> Router -> Your static DNS entries



By and large, I really like my WRT600N router. The thing is so dang versatile, but be warned it is not without it's issues. I'm currently using the latest firmware build 1.01.36 Build 3. There seems to be issues w/ the router's DHCP server. It issues DNS addresses in a weird order. It provides systems w/ the ISP's DNS servers as your primary and secondary, then the router itself as a tertiary, followed by any static DNS entries you've entered yourself.

For most people this isn't an issue, but if are doing any kind of home networking, this leads to issues resolving local system names. Since the first thing your clients try to resolve a name against would be your ISP's DNS servers. They wouldn't have the first clue where to find "mylocalsystem". Windows is pretty good about this though and can normally find your local networked devices without using DNS.

If you want to get to admin console that is web based, this is where the problems tend to occur. I have reported this as an issue to Linksys/Cisco, but have not heard back from them yet. Hopefully it'll be resolved in the next firmware revision.

It's being complained about on the forums too:
http://forums.linksys.com/linksys/board/message?board.id=Wireless_Routers&thread.id=79516&view=by_date_ascending&page=1

Comments

Post a Comment

Popular posts from this blog

NSX-T: Release associated invalid node ID from certificate

Image
Summary: Basically had an expiring certificate registered in NSX-T that was associated to a node_id that is no longer valid.  Long story short, there wasn't anything obvious in API to delete or disassociate a certificate from a node_id for 3.2.2.  Not sure how things got in this state, but annotating for future reference.  This may change in future revisions, so always check API for latest. Details: Effectively had a stale node associated w/ a certificate that was expiring.  Could not delete certificate until that node was disassociated from the certificate. To get certificate details and associated node_id's, you can use the following curl call (UI works too): curl -k -X GET -H "Content-Type: application/json" -u admin https://<manager ip>/api/v1/trust-management/certificates/<cert UUID> Above will return something like this: Below must be run from one of the manager nodes via elevation to root: ONLY RUN THIS IF YOU ARE ABSOLUTELY SURE OF WHAT YOU ARE DO...
Read more

NSX-T: vCenter and NSX-T Inventory out of Sync (Hosts in vSphere not showing up in NSX-T)

Image
Summary: NSX-T loses synch w/ vCenter inventory, but statuses don't appear to show an issue.  Basically, you add a host to a vCenter cluster, NSX-T bits should start to automatically installing on new host.  Assuming you've created a Transport Node Profile and associated w/ the cluster.  The problem is that NSX-T doesn't see the new host and its link to the compute manager (vCenter) looks fine. Looks fine, Y U NO WORK!? So what's going on here?  This appears to affect NSX-T 2.5 and 2.5.1.  Cause is unknown. Workaround: Restart the cm-inventory service on each NSX-T mgmt/controller node using API or CLI. Details: If you were to query the status of the cm-inventory via API or CLI, you could query all 3 manager/controller nodes and get a status of running.  Even if the primary node associated w/ the VIP, if configured, is not necessarily in charge of inventory.  So you could restart the cm-inventory service till you are blue in the face ...
Read more

MacOS: AnyConnect VPN client was unable to successfully verify the IP forwarding table modifications.

Image
The VPN client was unable to successfully verify the IP forwarding table modification.  A VPN connection will not be established. Summary: I started running into issue utilizing Cisco AnyConnect on my Mac basically complaining about not able to overwrite IP forwarding tables.  This was on 4.6.x.  Since my VPN endpoints were not providing me w/ an updated client and w/ no access to Cisco Anyconnect downloads, my only option was to try openconnect.  It was totally worth it, here is why and how to set it up. PreReqs: Homebrew Installing OpenConnect: Launch MacOS Terminal brew install openconnect Getting VPN IP's/DNS Endpoints from AnyConnect: The information is typically located in your profile xml files located here: /opt/cisco/anyconnect/profile/somethingsomething.xml In the xml file, you are looking for "<HostAddress>typicallyaDNSName.com</HostAddress>" entry.  These are your VPN endpoints that you would need to pass to openconnec...
Read more