|
Hardware Support Discussions related to using various hardware setups with SageTV products. Anything relating to capture cards, remotes, infrared receivers/transmitters, system compatibility or other hardware related problems or suggestions should be posted here. |
|
Thread Tools | Search this Thread | Display Modes |
#41
|
||||
|
||||
Quote:
__________________
Server: Ryzen 2400G with integrated graphics, ASRock X470 Taichi Motherboard, HDMI output to Vizio 1080p LCD, Win10-64Bit (Professional), 16GB RAM Capture Devices (7 tuners): Colossus (x1), HDHR Prime (x2),USBUIRT (multi-zone) Source: Comcast/Xfinity X1 Cable Primary Client: Server Other Clients: (1) HD200, (1) HD300 Retired Equipment: MediaMVP, PVR150 (x2), PVR150MCE, HDHR, HVR-2250, HD-PVR |
#42
|
|||
|
|||
pj
Why don't you take the tp-link out of the equation temporarily. See if your new modem/router will let you access the way you want. If if does then add your tp-link back in as a wireless access point only. Move the cables from the tp-link to the empty ports on the new modem/router or switch as required. The empty ports on the modem will act as a switch and or connect one cable from the new router to the switch. Sounds like you have enough ports to handle it. If it works the wAy you want the reinstall the tp-link and disable it's dhcp capabities. |
#43
|
|||
|
|||
Quote:
I grabbed a bunch of screenshots of the WAN stuff as requested above but last night I wasn't able to get on this forum because the "server was too busy" (I was hoping the board was blowing up because Google had announced a Sage-compatible extender device, but alas, no such luck). I will try to post later this evening when I get home.
__________________
Server: AMD Athlon II x4 635 2.9GHz, 8 Gb RAM, Win 10 x64, Java 8, Gigabit network Drives: Several TB of internal SATA and external USB drives, no NAS or RAID or such... Software: SageTV v9x64, stock STV with ADM. Tuners: 4 tuners via (2) HDHomeruns (100% OTA, DIY antennas in the attic). Clients: Several HD300s, HD200s, even an old HD100, all on wired LAN. Latest firmware for each. |
#44
|
||||
|
||||
I doubt your DSL is > 100Mbps, so it really doesn't matter if it's only 100. You still have you gigabit switch downstream for int in-house networking.
__________________
Buy Fuzzy a beer! (Fuzzy likes beer) unRAID Server: i7-6700, 32GB RAM, Dual 128GB SSD cache and 13TB pool, with SageTVv9, openDCT, Logitech Media Server and Plex Media Server each in Dockers. Sources: HRHR Prime with Charter CableCard. HDHR-US for OTA. Primary Client: HD-300 through XBoxOne in Living Room, Samsung HLT-6189S Other Clients: Mi Box in Master Bedroom, HD-200 in kids room |
#45
|
|||
|
|||
The cable to the Sage server (which is the bottleneck through which all incoming HD streams from HDHRs and all outgoing streams to extenders must pass) is plugged into the router. If I moved everything to the new Westell (as firenice suggested), everything would be passing through it into that one single 100-Mbps port. It's not about the DSL, it's about the router ports on the unit....
__________________
Server: AMD Athlon II x4 635 2.9GHz, 8 Gb RAM, Win 10 x64, Java 8, Gigabit network Drives: Several TB of internal SATA and external USB drives, no NAS or RAID or such... Software: SageTV v9x64, stock STV with ADM. Tuners: 4 tuners via (2) HDHomeruns (100% OTA, DIY antennas in the attic). Clients: Several HD300s, HD200s, even an old HD100, all on wired LAN. Latest firmware for each. Last edited by pjpjpjpj; 03-14-2014 at 06:35 PM. |
#46
|
|||
|
|||
Quote:
|
#47
|
|||
|
|||
Screenshots from the "Advanced>WAN" tabs. I included the first one just because I pulled down the WAN tab and grabbed it with the options showing.
I'm hoping someone will tell me that the "WAN detection" screen indicates I don't have PPPoE and therefore don't need a password from the ISP.
__________________
Server: AMD Athlon II x4 635 2.9GHz, 8 Gb RAM, Win 10 x64, Java 8, Gigabit network Drives: Several TB of internal SATA and external USB drives, no NAS or RAID or such... Software: SageTV v9x64, stock STV with ADM. Tuners: 4 tuners via (2) HDHomeruns (100% OTA, DIY antennas in the attic). Clients: Several HD300s, HD200s, even an old HD100, all on wired LAN. Latest firmware for each. |
#48
|
|||
|
|||
A couple more screenshots from the TP-Link router page, possibly pertaining to the stuff in the Westell screenshots posted above.
__________________
Server: AMD Athlon II x4 635 2.9GHz, 8 Gb RAM, Win 10 x64, Java 8, Gigabit network Drives: Several TB of internal SATA and external USB drives, no NAS or RAID or such... Software: SageTV v9x64, stock STV with ADM. Tuners: 4 tuners via (2) HDHomeruns (100% OTA, DIY antennas in the attic). Clients: Several HD300s, HD200s, even an old HD100, all on wired LAN. Latest firmware for each. |
#49
|
|||
|
|||
Regarding the gigabit router issue, there are times when we have 4 HD shows recording and three extenders running with HD content being watched. My system is all OTA and the HD streams being recorded are in the 12-15 Mbps range, so worst-case that's 60 total incoming. If three extenders are watching the same shows, that would put me near, at, or over 100 Mbps. I have a few files that I have downloaded, as well as our home videos from a camcorder, which are 1080p, and those are even more bandwidth when streaming to an extender. Plus it's a future-proofing thing since my 2-year-old will someday be old enough that we might have four extenders running at once.
Before I went all gigabit, I did occasionally see hiccups with watching shows when I had four shows recording at once and several extenders running, so, at the very least, it's worth this hassle to get it fixed once and be done with it. Plus I'm learning a LOT from y'all!
__________________
Server: AMD Athlon II x4 635 2.9GHz, 8 Gb RAM, Win 10 x64, Java 8, Gigabit network Drives: Several TB of internal SATA and external USB drives, no NAS or RAID or such... Software: SageTV v9x64, stock STV with ADM. Tuners: 4 tuners via (2) HDHomeruns (100% OTA, DIY antennas in the attic). Clients: Several HD300s, HD200s, even an old HD100, all on wired LAN. Latest firmware for each. |
#50
|
|||
|
|||
Quote:
The 74.215.xxx.xx address looks to be the IP address that would be assign by your ISP. The tp-link router would have the same 192.168.x.x ip as the other equipment on your subnet. When you access the tp-link router what IP address do you use? |
#51
|
|||
|
|||
The TPLink access is 192.168.1.1. I believe you are correct that my internet IP address is the 74.215.xx.xx one. I have seen that in several instances when I was trying to get this to work before y'all discovered the "two routers fighting" issue.
So what do I do with that?
__________________
Server: AMD Athlon II x4 635 2.9GHz, 8 Gb RAM, Win 10 x64, Java 8, Gigabit network Drives: Several TB of internal SATA and external USB drives, no NAS or RAID or such... Software: SageTV v9x64, stock STV with ADM. Tuners: 4 tuners via (2) HDHomeruns (100% OTA, DIY antennas in the attic). Clients: Several HD300s, HD200s, even an old HD100, all on wired LAN. Latest firmware for each. |
#52
|
|||
|
|||
Quote:
I now know why you don't use a username and password for a ppoe connection. Your connection is a routed IP which means you do not authenicate each time you go to the internet. First thing you need to do is change the tp-link routers IP address. Then disable the DHCP service under WAN. See this: http://www.tp-link.com/en/article/?faqid=417 This will set the tp-link to an access point without DHCP service since the Westell will handle the DHCP. Be sure not to duplicate an existing IP address. Log on to the Westell and under My Network view the Device Details. This should give you a list of all equipment attached to your network and the IP adresses assigned to them. By the way most dumb, non-smart, switches are not assigned an IP address. From your screen shot of the adv-WAN above your IP addresses would be ISP IP > 74.215.xx.xx >tp-link 192.168.x.x > Westell 192.168.x.x > local ip 27.0.0.1. IP address 27.0.0.1 is used for local host and may be the computer you used to set up the Westell. I see also that the that a private LAN2 is setup. The Westell is seeing the tp-link as a private network. Last edited by firenice; 03-15-2014 at 09:07 AM. Reason: One thing |
#53
|
|||||
|
|||||
Quote:
Quote:
Quote:
Quote:
Quote:
Finally, do I need (would it be recommended) to turn off everything on the entire network when I do this? When I disable the DHCP on the TPLink, will the Westell reassign new IP addresses to everything? Or will the devices' existing IP addresses be detected by the Westell?
__________________
Server: AMD Athlon II x4 635 2.9GHz, 8 Gb RAM, Win 10 x64, Java 8, Gigabit network Drives: Several TB of internal SATA and external USB drives, no NAS or RAID or such... Software: SageTV v9x64, stock STV with ADM. Tuners: 4 tuners via (2) HDHomeruns (100% OTA, DIY antennas in the attic). Clients: Several HD300s, HD200s, even an old HD100, all on wired LAN. Latest firmware for each. |
#54
|
|||
|
|||
Also - if I am taking the DHCP off the TPLink, should I have the cable fron the Westell running into the WAN or LAN on the TPLink? It currently runs to the WAN. If I take it off the WAN, will the TPLink wireless work or will I be forced to use the slower Westell wireless?
__________________
Server: AMD Athlon II x4 635 2.9GHz, 8 Gb RAM, Win 10 x64, Java 8, Gigabit network Drives: Several TB of internal SATA and external USB drives, no NAS or RAID or such... Software: SageTV v9x64, stock STV with ADM. Tuners: 4 tuners via (2) HDHomeruns (100% OTA, DIY antennas in the attic). Clients: Several HD300s, HD200s, even an old HD100, all on wired LAN. Latest firmware for each. |
#55
|
|||
|
|||
Quote:
The link I posted was for setting the tp-link up as an wireless access point. The purpose for changing the IP address is to not interfere with the Westell. Most all routers are accessed with the IP of 192.168.1.1. If the Westell's is different then you do not have to change it. Connect the Westell to a LAN port, not the WAN port, as in step 1. Once you have disabled the DHCP on the tp-link the Westell will take over that duty and assign IP addresses to everything attached. At this point you will not see the private LAN2 listed on the Westell because now everything will be on the main LAN and will show up in the device list. |
#56
|
||||
|
||||
Here a idea you could always get a 10/100/1000 Ethernet hub and make use of the Uplink on the Westell Router and set the other router a side or see if you can use you own DSL Modem and order used one from ebay or new like a TP-LINK TD-8616 ADSL2 or D-Link DSL-520B or Actiontec GEU003AD3B-01 Modem.
That or ask the phone people to sent you a reg DSL Modem which is a non Combo DSL Modem Router Last edited by SHS; 03-15-2014 at 06:08 PM. |
#57
|
||||
|
||||
Quote:
If none else pjpjpjpj Look up westell a90 bridge mode maybe you find something here http://www.dslreports.com/forum/r241...7500-rebooting here http://mrwhatis.net/a90-750060-07.html Your Modem/Router http://www.westell.com/support/versalink/a90-750060-07 Last edited by SHS; 03-15-2014 at 04:02 PM. |
#58
|
|||
|
|||
pj
We have gone full circle on this one. SHS is correct. Even if you disable the DHCP on the tp-link and use it as an wireless access point you will lose the gigabit routing capablities of the tp-link. The Westell is only 10/100 as well as any routing it would do. The network will only be as fast as it slowest component. The Westell will have to be brigded, basically making it just a modem, and the tp-link will have to be setup as the router. Your best bet is to call your ISP and request a modem only. Tell them you have your own router. |
#59
|
|||
|
|||
So if I have the Westell running the DHCP but there is only one cable from it which runs to the TPLink (the only thing ever passing through that one cable being internet connection), and the Westell is in bridge mode, and throughput to/from the Sage server runs into and out of the TPLink, the Westell still dictates to everything downstream that it must only operate at 10/100? I thought the throughput was determined by the device through which the data stream entered and left ( i.e. the data from an HDHR running through the TPLink, into the cable to my server, would be subject to the TPLink's bandwidth limitation because it didn't have to run through the Westell).
__________________
Server: AMD Athlon II x4 635 2.9GHz, 8 Gb RAM, Win 10 x64, Java 8, Gigabit network Drives: Several TB of internal SATA and external USB drives, no NAS or RAID or such... Software: SageTV v9x64, stock STV with ADM. Tuners: 4 tuners via (2) HDHomeruns (100% OTA, DIY antennas in the attic). Clients: Several HD300s, HD200s, even an old HD100, all on wired LAN. Latest firmware for each. |
#60
|
|||
|
|||
Quote:
An example for this was stated earlier. A Sage extender only has a 10/100 port but when you run 2 at the same time you need 20/200 bandwidth requirement on your router if both are running full speed. I know this is a simplistic way of stating it but with a 10/100/1000 router you get more bandwidth for the route. While surfing the web or as with some wireless devices bandwidth only comes in to play when more devices have an active connection. Most all modem only devices only require a 10/100 port since the bandwidth would never exceed the actual bandwidth supplied by the ISP. In your case, you know that your LAN requires more bandwidth and the tp-link solved that with your other ISP which had provided a modem only. This is why when setting up a gigabit network all equipment needs to be gigabit capable with the exception of the modem. |
Currently Active Users Viewing This Thread: 1 (0 members and 1 guests) | |
|
|
Similar Threads | ||||
Thread | Thread Starter | Forum | Replies | Last Post |
Caller I.D. Modem | Steve52 | Hardware Support | 3 | 02-19-2012 07:56 PM |
Creativev.92 Modem and Caller I.D. | Steve52 | Hardware Support | 5 | 01-24-2012 12:19 PM |
Caller ID modem for voip | tawd1992 | Hardware Support | 11 | 10-22-2009 06:17 PM |
hd200 connected to modem? | ttiell | SageTV HD Theater - Media Player | 8 | 10-09-2009 12:13 PM |
Help with choosing DSL Modem/Router! | JUC | Hardware Support | 3 | 05-04-2006 10:46 AM |