How to setup your SafeStream router in standalone mode
TL-ER7206 , TL-R600VPN , TL-R605 , ER7206 , TL-ER6120 , TL-ER6020 , TL-ER5120 , TL-R480T+ , ER605 , TL-R470T+
Recent updates may have expanded access to feature(s) discussed in this FAQ. Visit your product's support page, select the correct hardware version for your device and check either the Datasheet or the firmware section for the latest improvements added to your product.
Step 1. Connect the network lines
Please refer to the QIG in the packet to connect the hardware.
It is noteworthy that please connect the modem to the WAN port (the first port) on the router, and connect the computer to the LAN port (the last one) with high-quality Ethernet cables (CAT5 for not exceeding 100 Mbps network connection, CAT5E and above for Gigabyte network).
Note: please make sure you are able to access the internet with a direct connection from your computer to the cable modem. If the direct connection doesn’t work, please contact your Internet Service Provider (ISP).
Step 2. Log in to the management page
Please open a browser and input “192.168.0.1” to the address bar to visit the management page of the router. You will be asked to set up the Username and Password for management, after that please enter the Username and Password again to log in the page.
If you have ever setup a static IP for IPv4 Properties, please change it to “Obtain an IP address automatically” mode, and you may follow this link to do the configuration https://www.tp-link.com/support/faq/14/.
When you successfully log in to the management page, you will be on the system status page.
Step 3. Set up the WAN Mode
Please go to Network -> WAN to choose WAN Mode. The default mode is 2, which means the first two ports are in WAN mode, used to connecting ISP lines, and the other ports are in LAN mode, used to connecting network devices.
If you have one ISP line, please click 1 and save, then the router will restart. After restarting, the Power, System, as well as the port LEDs, will be on, then the other four ports can be used to connect terminal devices.
Similarly, 3/4 modes are used to connecting more ISP lines.
Step 4. Set up the Connection Type for each WAN
Please go to Network -> WAN -> WAN1, choose Connection Type according to your ISP information.
For most scenarios, the connection type is Dynamic IP, which is also the default option. There is no need to change the configurations.
If your ISP gives a Username and Password, please change the Connection type as PPPoE, put in the provided account to the corresponding box and click save to enable the configuration. ISPs might provide a router with PPPoE or static IP set. If your PC can obtain a private IP from the ISP router, you may keep using Dynamic IP here.
If your ISP provides a set of IP address, subnet mask, default gateway and DNS addresses, please use Static IP as the connection type. You can use either the DNS addresses provided by your ISP or public DNS addresses.
Apart from connection type, please confirm whether VLAN tag is needed or not. You may enable VLAN and put in the corresponding VLAN ID according to your ISP’s guidance. Don’t enable it if not requested.
If necessary please go to the other WAN to do the configurations.
Step 5. Check the WAN status
Through the above steps, the basic configurations of the router have been finished. You may go to Status -> System Status to check the WAN status of the router. Please refer to WAN IPv4, the connection status indicates the working status for each WAN, and others indicate the IPv4 parameters.
If the connection status is link down, and there is still no IP address, please do the following:
- Restart the router first, wait for about 10 seconds, and connect your device to the router.
- Power off the modem, and unscrew the coaxial cable
- Power on the modem, Check LEDs on the Router, make certain the WAN LED is on.
- Reconnect the coaxial cable to the modem and check if you have access to the internet.
Note: Some cable modem has a backup battery inside. To completely restart the cable modem, please take the battery out, and then unplug the power supply.
If Omada router’s front-end device is another router, it causes IP conflict when front-end subnet is also 192.168.0.1/24. You can check that by connecting a PC to the front-end device and look into its IP address. When the IP is one amongst 192.168.0.2-254, an IP conflict is confirmed. The solution is to change the LAN subnet of either routers. Here is an example with Omada gateways:
Step 1: Navigate to Network -> LAN -> LAN(Tab)
Step 2: Set the IP address as 192.168.10.1(a private IP other than 192.168.0.1) and change the Starting and Ending IP address accordingly.
Step 3: Click “OK” to save the settings.
Re-plug your PC for IP renewing, access the management page again with new LAN IP, 192.168.10.1, and double check if there is a valid WAN IP.
If none of the above helps, please refer to the following to do a MAC clone on the router:
Step 1: Disconnect the router, connect the computer to the modem which used to dial up the modem. Make certain the computer has internet access to the modem.
Step 2: Disconnect the computer from the modem, connect the modem to the WAN/Internet port of the router, and connect the computer to the LAN/Ethernet port of the router.
Step 3: Log in to the router’s web-based interface
Step 4: Click Network->MAC>WAN1, choose Use Current Computer MAC Address.
Step 5: Click Save to save the settings.
Step 6: If the MAC Clone succeeds, the WAN1 MAC Address in the Network->MAC>WAN1 page will be the same as the MAC Address on the computer when it is connected to the modem directly.
Looking for More
Is this faq useful?
Your feedback helps improve this site.
What’s your concern with this article?
- Dissatisfied with product
- Too Complicated
- Confusing Title
- Does not apply to me
- Too Vague
- Other
We'd love to get your feedback, please let us know how we can improve this content.
Thank you
We appreciate your feedback.
Click here to contact TP-Link technical support.
Recommend Products
TP-Link Community
Still need help? Search for answers, ask questions, and get help from TP-Link experts and other users around the world.
We have updated our Policies. Read Privacy Policy and Terms of Use here.
This website uses cookies to improve website navigation, analyze online activities and have the best possible user experience on our website. You can object to the use of cookies at any time. You can find more information in our privacy policy .
We have updated our Policies. Read Privacy Policy and Terms of Use here.
This website uses cookies to improve website navigation, analyze online activities and have the best possible user experience on our website. You can object to the use of cookies at any time. You can find more information in our privacy policy .
Basic Cookies
These cookies are necessary for the website to function and cannot be deactivated in your systems.
TP-Link
accepted_local_switcher, tp_privacy_base, tp_privacy_marketing, tp_smb-select-product_scence, tp_smb-select-product_scenceSimple, tp_smb-select-product_userChoice, tp_smb-select-product_userChoiceSimple, tp_smb-select-product_userInfo, tp_smb-select-product_userInfoSimple, tp_top-banner, tp_popup-bottom, tp_popup-center, tp_popup-right-middle, tp_popup-right-bottom, tp_productCategoryType
Livechat
__livechat, __lc2_cid, __lc2_cst, __lc_cid, __lc_cst, CASID
Youtube
id, VISITOR_INFO1_LIVE, LOGIN_INFO, SIDCC, SAPISID, APISID, SSID, SID, YSC, __Secure-1PSID, __Secure-1PAPISID, __Secure-1PSIDCC, __Secure-3PSID, __Secure-3PAPISID, __Secure-3PSIDCC, 1P_JAR, AEC, NID, OTZ
Analysis and Marketing Cookies
Analysis cookies enable us to analyze your activities on our website in order to improve and adapt the functionality of our website.
The marketing cookies can be set through our website by our advertising partners in order to create a profile of your interests and to show you relevant advertisements on other websites.
Google Analytics & Google Tag Manager
_gid, _ga_<container-id>, _ga, _gat_gtag_<container-id>
Google Ads & DoubleClick
test_cookie, _gcl_au
Meta Pixel
_fbp
Crazy Egg
cebsp_, _ce.s, _ce.clock_data, _ce.clock_event, cebs
Hotjar
OptanonConsent, _sctr, _cs_s, _hjFirstSeen, _hjAbsoluteSessionInProgress, _hjSessionUser_14, _fbp, ajs_anonymous_id, _hjSessionUser_<hotjar-id>, _uetsid, _schn, _uetvid, NEXT_LOCALE, _hjSession_14, _hjid, _cs_c, _scid, _hjAbsoluteSessionInProgress, _cs_id, _gcl_au, _ga, _gid, _hjIncludedInPageviewSample, _hjSession_<hotjar-id>, _hjIncludedInSessionSample_<hotjar-id>
lidc, AnalyticsSyncHistory, UserMatchHistory, bcookie, li_sugr, ln_or