Recommended Posts

I recently signed up with at&t uverse. They had provided me with a wireless modem. However the modem has pretty bad range and speed isn't that great. So I wanted to just add my router and use that.

I have a Asus rt n56u. Once plugged in everything does light up fine and my phone does detect the router. When trying to connect to the router however 1/10 times it actually connects gives me full bars but no actual internet. Will this not work while using wireless modem? Any ideas on this?

Link to comment
https://www.neowin.net/forum/topic/1204069-setting-up-wireless-help/
Share on other sites

To add coverage you would use your n56u as an accesspoint only  - not as a wireless/nat router.

 

Change the LAN IP of your n56u to be on your new networks network.. Look at a client connected to your att router wired or wireless.  What does it show for your network and mask? 192.168.1.? what does it show for your gateway.  This is the IP address of your att router.

 

To use your n56u as just an accesspoint.  Change its network to be on the same network as your att, I am guessing your att is 192.168.1.254 ?   While your n56u is prob 192.168.1.1 - which puts them on the same network and your good.  So on your n56u just turn off its dhcp server.  An then connect it to your att router via a LAN port on the n56u vs its wan/internet port.  Shazam you have an AP.

 

Now connect to your n56u IP and configure its wireless.. For easy transition between the 2 routers depending on where you client is - make them the same SSID, same encryption psk, etc.  Just most likely put them on different channels - so say channel 1 and channel 11 if your using 2.4 ghz

First I can't take credit for the instructions below - I had saved them sometime ago because I had run into the same issue as SylentSlayer. First Slayer do I assume correctly that you wish to use your Asus router as a wi-fi range extender? If so then follow the instructions listed below:

 

How to setup wireless with routers as access points
 
router1 = internet port connected to cable/fios/dsl modem. dhcp enabled, ssid of router1 = myssid
router2 = ethernet cable from a port on router 1 to any internal port on the router, the internet/wan port is not to be used. dhcp is disabled. ssid of router2 = myssid
 
Pay attention to the ssid of both router1 and router2....they are the same, there is a reason for this. The network card will pick whatever access point has the strongest signal and seamlessly switch between them so you don't drop when connecting to different access points. you can move about your house without noticeably dropping off and switching between areas. 
 
Or:
 
1. Using a PC wired into the current router, unplug it from the wired connection and plug into a LAN port on the secondary router. Access the secondary router using your browser via its default LAN IP address and default password. Since the PC was attached to the previous router you will have tell the PC to obtain a LAN IP from the new device. Use 'winipcfg' in win9x or 'ipconfig release/renew' with W2K/XP on the PC.
 
2. On the secondary router (hereafter called the AP)
 
a. change the default password to a minimum combination of 8 letters/numbers/symbols.
 
b. Change the SSID to a unique name and make all the necessary wireless configurations.
Note: If attaching a WiFi router as an AP/switch to an existing wifi network, one should keep the SSIDs the same for seamless roaming, or separate if one wants to manually decide which AP to connect to. If you decide to use the existing ESSID as your existing wireless network, your security settings should be the same. Also, ensure channel separation (1-6-11 common for three devices). Two wireless AP on the same channel does not work very well. 
 
3. In the AP, go to the LAN setup page:
 
a. Turn DHCP serving OFF on the AP (i.e secondary router being configured as AP). This is necessary so that your DHCP clients obtain correct settings (with correct gateway) from the primary router instead of the incomplete/erroneous one from the AP.
 
b. Change the LAN IP of the AP from its default so that it lies within the subnet of the primary router but preferably outside the dynamic LAN IP range of the primary router. (examples below) Note: This is not a requirement, but keeping everything in the same IP range can make administration and file sharing easier.
 
c. Disable or turn RIP off, if there is that option.
 
d. Disable or turn off Universal Plug and Play (UPnP) support (if any).
 
4. Plug the PC back into the wired connection and repeat the process of getting new LAN IP. A reboot of the PC may be needed.
 
5. Plug the AP into the primary router, LAN port TO LAN port directly or via switch/patch panel etc. Leave the WAN port of AP disconnected.
 
6. It may be necessary to reboot one or both routers but one should be able to assign LAN IPs wirelessly and connect at this point, ensuring WiFi card setup properly.
 
Example:
 
Primary Router
LAN IP 192.168.1.1
old Dynamic DHCP Pool 192.168.1.2 - 192.168.1.xx
subnet mask 255.255.255.0
 
Will need to change Dynamic DHCP pool
new DCHP Pool 192.168.1.33 - 192.168.1.xx (for example)
Subnet mask 255.255.255.0
 
Secondary Router (our Access Point)
old LAN IP 192.168.0.1 -or any other default
 
Will need to change LAN IP to be within subnet of primary.
new LAN IP 192.168.1.2
Subnet mask 255.255.255.0

Those are very drawn out instructions sure -- but they are NOT for a "as a wi-fi range extender?"  They are just as an accesspoint, which I already gave instructions on how to do ;)

 

A wi-fi range extender or repeater would be if 2nd router connects to first router over wireless.  Not when your just using it as an AP on your network connecting with a wire.

 

Turning off RIP and UPnP are just noise in your instructions.. And would not matter if those were on or off since your not using its wan port.  And only if the devices was turn to router vs gateway would RIP even be an option to enable.

Yeah anything that can access the routers interface can do it.. To be honest you have really 1 setting to make since from what I google the IP address of att router is 192.168.1.254, and the IP of n56u is 192.168.1.1 - all you have to do is turn off the dhcp server on your n56u and connect it to your att via lan port not wan.

 

But we can verify that - what IP address is your gateway when you connect to the att router?

 

Why do you not have a computer but home internet access?  Why don't you just uses the phones internet?

Well when you connect to your wireless on your n56u what do you see?

 

if its 192.168.1.1 your still good.. Just turn off its dhcp server.  .2 seems like ODD for router default - did you change it at some point?  You sure its not .254?

This topic is now closed to further replies.
  • Recently Browsing   0 members

    • No registered users viewing this page.
  • Posts

    • Speaking of right, right dominant only which, as with most, makes this meaningless to me.
    • No, size is not the only selling point. I did not even remotely say that. Your claim was that "building your own will be faster and cheaper". This is false. You cannot build something close to that form factor with off-the-shelf parts. You can build a Mini-ITX PC and pay more, or something larger and pay less. But these are different market segments. It's apples and oranges.
    • There is a default resolution setting in Settings > Display that can be changed with a click. You can also change the settings on a per-game basis. No CLI needed. Also, Steam has countless games that are not "[perpetual] alpha/beta games", so no need for the straw man. Plus you can use other stores as well. And console games (e.g. PS5) cost a fortune, which itself more than negates the price subsidy on the system, unless you plan on exclusively playing 1 or 2 games. It's true that you shouldn't buy a system that doesn't support the game(s) you want to play, but I think that's kinda obvious, and applies to every console as well as PC. I don't game in the living room and have no need of a Steam Machine, but there is a clear market segment that would find it useful.
    • RSS Guard 5.2.0 by Razvan Serea RSS Guard is a simple (yet powerful) feed reader. It is able to fetch the most known feed formats, including RSS/RDF and ATOM. It's free, it's open-source. RSS Guard currently supports Czech, Dutch, English, French, German, Italian. RSS Guard will never depend on other services - this includes online news aggregators like Feedly, The Old Reader and others. RSS Guard is developed on top of the Qt library and it supports these operating systems: Windows GNU/Linux OS/2 (eComStation) Mac OS X xBSD (possibly) Android (possibly) other platforms supported by Qt The core features of RSS Guard are: support for online feed synchronization via plugins, Tiny Tiny RSS (from RSS Guard 3.0.0). multiplatform, support for all feed formats, simplicity, import/export of feeds to/from OPML 2.0, downloader with own tab and support for up to 6 parallel downloads, message filter with regular expressions, feed metadata fetching including icons, simple Adblock functionality, customized popup notifications, Google-based auto-completion for internal web browser location bar, ability to cleanup internal message database with various options, enhanced feed auto-updating with separate time intervals, multiple data backend support, SQLite (in-memory DBs too), MySQL. is able to specify target database by its name (MySQL backend), “portable” mode support with clever auto-detection, feed categorization, drap-n-drop for feed list, automatic checking for updates, ability to discover existing feeds on websites, full support of podcasts (both RSS & ATOM), ability to backup/restore database or settings, fully-featured recycle bin, printing of messages and any web pages, can be fully controlled via keyboard, feed authentication (Digest-MD5, BASIC, NTLM-2), handles tons of messages & feeds, sweet look & feel, fully adjustable toolbars (changeable buttons and style), ability to check for updates on all platforms + self-updating on Windows, hideable main menu, toolbars and list headers, KFeanza-based default icon theme + ability to create your own icon themes, fully skinnable user interface + ability to create your own skins, “newspaper” view, plenty of skins, support for "feed://" URI scheme, ability to hide list of feeds/categories, open-source development model based on GNU GPL license, version 3, tabbed interface, integrated web browser with adjustable behavior + external browser support, internal web browser mouse gestures support, desktop integration via tray icon, localizations to some languages, Qt library is the only dependency, open-source development model and friendly author waiting for your feedback, no ads, no hidden costs. RSS Guard 5.2.0 changelog: Added: Feed auto-fetch can now also be delayed while Feral GameMode is active on Linux and startup auto-fetch is skipped when GameMode is already active. (#2265) WebEngine builds can now use RSS Guard generated proxy auto-config (PAC) rules so article/web browsing follows per-account and per-feed proxy settings more closely. (#2273) Generated PAC rules now also cover related subdomains and use Public Suffix List data, so feeds such as feeds.bbc.co.uk can also proxy resources from images.bbc.co.uk. (#2273) Standard feeds can now define extra proxy domains, useful when article images, stylesheets or other page resources are loaded from a CDN or another domain that should use the same feed proxy. (#2273) RSS Guard now asks for proxy credentials when a WebEngine page needs proxy authentication and can fill credentials from the current feed proxy when available. (#2273) Network settings again include an option to ignore all cookies, which clears stored cookies and prevents new cookies from being accepted. Standard RSS/ATOM feeds can now individually ignore cookies while downloading feed data. Stored cookies can now be deleted from the Tools menu. Custom skin colors can now override the feed list article count color separately from feed titles, including a separate highlighted color. (#2275) Settings dialog can now search across available settings and highlight matching controls. (#1754) Standard RSS/ATOM feeds can now optionally be reported as broken when they are valid but contain no articles. (#2039) Standard RSS/ATOM feeds can now override the application-wide feed connection timeout per feed. (#1023) Tray icon can now use a custom background color and unread-count text color, with an option to reuse the generated icon as the application icon. (#1973) Support for more benevolent parsing of Gemlog entries (#2295). Article list can now show when an article was received by RSS Guard. (#947) Feed deep discovery now actually scrapes all links found in the website and checks if they are feeds or not. This greatly enhances usability of the deep discovery mode and discovers many more feeds than before. (#2306) Search boxes now show a small dot when the feed or article list is hiding some items because of active filtering. (#873) Articles now have a shortcut-assignable action to open the homepage of the feed they belong to. (#2060) Fixed: Parallel feed updates no longer crash when multiple update results are processed at the same time. (64cf521) Links in WebEngine articles opened from feeds such as Kill the Newsletter now open correctly instead of being swallowed by the embedded page. (#2272) Relative article URLs resolution was kinda broken. (#2282) Clicking article URL did not work when the URL had "fragment" set. (#2293) The default proxy setting now uses Qt/system default proxy behavior instead of forcing no proxy. (e0263ad) WebEngine article loading now keeps the current feed context, so feed-specific proxy credentials remain available while the article page loads. (fdd0f00) Download: RSS Guard 5.2.0 (64-bit) | Portable | ~ 130.0 MB (Open Source) Link: RSS Guard Home Page | Other Operating Systems | Screenshot Get alerted to all of our Software updates on Twitter at @NeowinSoftware
  • Recent Achievements

    • Rookie
      DaviKar went up a rank
      Rookie
    • Dedicated
      HidekoYamamoto94 earned a badge
      Dedicated
    • One Month Later
      timbobit earned a badge
      One Month Later
    • One Month Later
      nates earned a badge
      One Month Later
    • Week One Done
      Almohandis earned a badge
      Week One Done
  • Popular Contributors

    1. 1
      +primortal
      461
    2. 2
      +Edouard
      161
    3. 3
      PsYcHoKiLLa
      110
    4. 4
      Michael Scrip
      83
    5. 5
      Steven P.
      69
  • Tell a friend

    Love Neowin? Tell a friend!