Planet Replay Forum Index Planet Replay
The Destination for ReplayTV Owners and TV Enthusiasts
Back to the home page
 
 FAQFAQ   SearchSearch   7 days of topics7 Days  30 days of topics30 Days  MemberlistMemberlist   UsergroupsUsergroups   RegisterRegister 
 ProfileProfile   Log in to check your private messagesLog in to check your private messages   Log inLog in 

WiRNS Help Tidbits

 
Post new topic   This topic is locked: you cannot edit posts or make replies.    Planet Replay Forum Index -> WiRNS
View previous topic :: View next topic  
Author Message
na9d
Moderator
Moderator


Joined: 27 May 2005
Posts: 3353
Location: Algonquin, IL

PostPosted: Wed Mar 08, 2006 11:38 am    Post subject: WiRNS Help Tidbits Reply with quote

Among those contributing to this list are: Rbolen70, TakeTheActive, The Dreamer and many other members of the community

Below are a few descriptions and tidbits and hints and kinks for using WiRNS. These have been compiled from various sources. If you have any additional hints or kinks let us know and they can be added to this sticky.



=====================

WiRNS Plug-In Descriptions:

Code:

Plugin Descriptions:

ChannelGuideProvider.dll - Serves guide info to your Replay(s) - Not required.
GetNextCall.dll          - Used to set the time after WiRNS does a guide update when the Replays will Net-Connect - Not required.
GetShellCommands.dll     - Used for executing shell commands - Not required.
GuideServer.dll          - Used to View the Web-based Channel Guide - Not required.
HeadendProvider.dll      - Serves channel info for the lineup(s) provided by ZipcodeProvider - Not required.
IVSProvider.dll          - Provide IVS RDDNS lookups locally, then proxies to rddns-production - Not required.
NoPhoneNumbers.dll       - Intercepts phone number updates during a net connect - Not required.
NoReplayZones.dll        - Intercepts ReplayZone updates during a net connect - Not required.
NoSoftwareUpdate.dll     - Intercepts software updates during a net connect - Not required.
PutSyslogProvider.dll    - Intercepts syslog uploading during a net connect - Not required.
ServerManagment.dll      - Manages the WiRNS Server - Required
ZipcodeProvider.dll      - Serves lineup info (i.e. DirecTV, National or DISH, National, etc)- Not required.
LoginAuthLogout.dll      - If the ReplayTV servers are unreachable, this will return a 304 not modified. (This does NOT bypass service activation NOR let you "Steal" service)



Plug-In Usage:

1. ServerManagement.dll must always be enabled. It is what runs the WiRNS webserver.

2. HeadendProvider.dll & ZipcodeProvider.dll must be enabled together in order to provide channel guide info to the Replay.

Additionally, the three plugins listed below provide additionally functionality for channel guide information and can be individually enabled or disabled when using the above two plugins.

* ChannelGuideProvider.dll
* ChannelRemap.dll
* GuideServer.dll


NoReplayZones.dll and ReplayZones.dll are mutually exclusive and either one may be enabled (or neither enabled) when using Headend and Zipcode Providers.

If you want true Replay Zone functionality, you want to run neither Zones plugin and instead select "Proxy Guide Data to DNNA" from within WiRNS in either the DataDirect setup page or on the configuration page for each individual Replay.

3. The following list of Plugins are all optional and may be enabled or disabled as the user chooses.

* GetNextCall.dll
* GetShellCommands.dll
* IVSProvider.dll
* LoginAuthLogout.dll
* NoPhoneNumbers.dll
* NoSoftwareUpdate.dll
* PutSyslogProvider.dll
* RemoteControl.dll


=====================================

Other Hints/Registry Commands:


1. Enable Commercial Advance on a 55xx running a software version < 144:
Code:

      regedit setval SysConfig/DefaultPlayback CommercialSkipEnabled 1


2. Enable Internet Video Sharing on a 55xx running a software version < 144:
Code:

       regedit setval Software/Apps/Internet InternetEnabled 1


3. Enable ShowGuard on a 50xx or 55xx:
Code:

      regedit setstr Software/Apps/ReplayChannels EnableShowGuard TRUE
      regedit setstr Software/Apps/ReplayChannels ShowGuardTime 5


4. Enable SportsGuard on a 50xx or 55xx:
Code:

      regedit setstr Software/Apps/ReplayChannels EnableSportsGuard TRUE
      regedit setstr Software/Apps/ReplayChannels SportsGuardTime 90


5. Revert to a previous software version on a 50xx or 55xx:
Code:

      cdsys
      mv boot.state boot.state.bak
      reboot


WARNING: Be sure there is a previous version of software on your Replay before doing this otherwise your Replay will be a doorstop until you reimage your drive from scratch.

EXPLANATION:

Whenever the Replay receives a firmware update, a backup copy of the old firmware is stored on a backup partition on the Replay's hard drive. That way if something is corrupted with the firmware download the Replay can revert to the old version w/o becomming a doorstop.

* The "cdsys" command changes to whatever sys directory the ReplayTV is currently running from (i.e. sys1 or sys2).
* The "mv boot.state boot.state.bak" command renames the boot file, which causes the ReplayTV to think the current software is corrupt and revert to the backup software.

*-> When doing this be sure that NO other Replays will net connect during this time. When completed with the revert, shut down WiRNS, edit the shellcmds file to remove these commands and restart WiRNS. Not doing so will turn your newly reverted Replay into the doorstop mentioned above!


6. Copy the ReplayTV Registry values to the Photo Partition to allow d/l and inspection via a PC:
Code:

      cp /name/system/user/Registry/ /name/storage/Photo/


7. Reset Parental Control:
Code:

      regedit setval Software/Apps/ParentalControl UserPin xxxx


8. Turn on power to USB port:
Code:

      IRMTS
      usb_enumerate


9. Prevent Net Connects from happening whenever the Replay sees fit:
Code:

       regedit setval SysConfig/NetworkUpdateTime Anytime 0

This should be used with the GetNextCall plugin or scheduled net-connects in WiRNS. GetNextCall will suggest that the ReplayTV connect in a 12 minute window starting the number of minutes specified after the next guide update time....staggering the known units by 8 minute increments. (all) Unknown units get the same time outside the range of the known units. Forced NetConnects are scheduled inside WiRNS on the schedule and time of the users choosing.

======================

Tips for Setting Up the Replay and Router for proper operation through WiRNS

1.) DNS1 must point to the IP of the computer running WiRNS. DNS2 may be blank or the same as DNS1. Under NO circumstances should either DNS entry be that of your Router or the DNS address of your ISP. This is essential for WiRNS to fully proxy all the Replay data.

2.) The GATEWAY IP on your Replay MUST be set to the IP of your Router. DO NOT set this IP to that of the PC running WiRNS. If you do, you will not be able to do IVS transfers.

3.) If you are using the WiRNS IVSTracker to track send progress of shows, you must configure the port forwarding in you router for each Replay you want to track to that of the PC running WiRNS. If you port forward to each Replay instead, the IVSTracker will not work.

4.) The PC MUST be on and WiRNS running in order to receive shows via IVS if you have your router configured as per step 3.

===================
Back to top
View user's profile Send private message Send e-mail Visit poster's website AIM Address Yahoo Messenger
na9d
Moderator
Moderator


Joined: 27 May 2005
Posts: 3353
Location: Algonquin, IL

PostPosted: Sun Apr 16, 2006 4:26 pm    Post subject: Reply with quote

Tips for IVS and Using the IVS Tracker within WiRNS

WiRNS can track the progress of IVS sends and receives. WiRNS can also send shows from your local show directory. This tidbit will hopefully make these operations more clear.

- WiRNS does NOT have the capability to receive shows via IVS. It can only send them.

To enable WiRNS to send shows:

1.) Enter the IVS Port you want to use as the Secondary Web Port in the main WiRNS configuration page.
2.) On the Replays configuration page, there is a config page for your "WiRNS" Replay. Go into that page. There, make the IVS port the SAME as the secondary web port you selected in step 1.
3.) If you wish to upload your local show data to Poopli and/or IVSBase, click on the appropriate boxes.
4.) Stop and Restart WiRNS
5.) Once WiRNS has restarted go back to the WiRNS Replay configuration page and change the IVS nickname to something other than WiRNS or Server, etc. Make it an IVS nickname like you would your regular Replays.
6.) Set port forwarding on your router for the WiRNS IVS port to direct to the WiRNS IP.
7.) You are set to go!

To add WiRNS as a Replay on Poopli

You add WiRNS as a Replay on Poopli like you would any other Replay. You need to create it on Poopli and add the serial number and ISN. Copy these from Replay Configuration page for the WiRNS Replay in WiRNS. Set the Replay type to be whatever you want it to be. Just make sure that if you are sharing 4000/4500 shows you set it as that and if you are sharing 5000/5500 shows you set it as that.

WiRNS Tracker Configuration

To set up the WiRNS tracker you must first enable it in WiRNS. But this is not enough. You must then configure the port forwarding settings in your router to forward the IVS ports for ALL Replays you wish to track to the IP for WiRNS. WiRNS will then intercept the traffic and process it and send it on to the Replays.

More to come on how IVS transfers work and how WiRNS can track them....
_________________
See my Poop! (5XXX)
See my IVS activity LIVE
Do you Vudu? I do!
Back to top
View user's profile Send private message Send e-mail Visit poster's website AIM Address Yahoo Messenger
na9d
Moderator
Moderator


Joined: 27 May 2005
Posts: 3353
Location: Algonquin, IL

PostPosted: Mon Apr 17, 2006 4:58 pm    Post subject: Using WiRNS with a Windows Server 2003 DC Reply with quote

Thanks to user schwab for this tip

Using WiRNS with a Windows Server 2003 Domain Controller

1) Add new IP Addr
Control Panel->Network Connections->Right Click your internal network->Properties->Double Click TCP/IP Properties->Advanced Tab->Add IP Address->OK out of all of those

2) Modify DNS
Control Panel-DNS->Right Click Forward Lookup Zones->New Zone->Defaults Next->Defaults Next->Zone Name: replaytv.net->Do not allow dynamic Updates->Finish

Click the + next to replay.net->Right click on replay.net->Properties->Name Servers tab->Click the FQDN of your box->Edit->Type in new ip addr you entered in 1), click Add->Remove other IP addr in there->Ok->Yes you want to delete that old host record

Right click on replay.net again->New Host (A)->enter all the servers listed in WiRNS\ReadMeDNS.txt (just the prefix.. i.e., production) and point them to the new ip addr from 1->Add Host

Modify WiRNS to use the new IP address for itself and use the original IP as the DNS server.

And don't forget to set doDNS = 0 in the registry.. look at that ReadMeDNS.txt file for info there.
_________________
See my Poop! (5XXX)
See my IVS activity LIVE
Do you Vudu? I do!
Back to top
View user's profile Send private message Send e-mail Visit poster's website AIM Address Yahoo Messenger
hdonzis
Planet Overlord


Joined: 05 Jan 2005
Posts: 9021
Location: San Antonio, TX

PostPosted: Sun Jun 07, 2009 1:05 pm    Post subject: Using WiRNS with ICS Reply with quote

Using WiRNS with ICS:

bluesloth wrote:
Scenario: You have a single computer that is connecting to the Internet either via a dial-up connection, wi-fi connection, or some other temporary connection that is directly connected to your computer, and you have a Replay TV connected to a separate Ethernet port via hub, switch, or cross-patch cable.

Solution: Enable TCP/IP routing between your Internet connection and your secondary NIC without enabling Internet Connection Sharing (ICS).

Procedure:

1. Verify that your Internet connection is properly configured and you're able to connect to the Internet.

2. Assign your secondary NIC to have a static IP of '192.168.0.1' (or whatever you would like to assign as an IP). use a subnet mask of '255.255.255.0'. Leave the Default Gateway Blank (unless you have a statically assigned IP from your ISP, then you can enter this as your gateway). Add the DNS server IP's from your local ISP.

3. Open 'regedit' and modify the following registry key to change the value from '0' to '1' to enable TCP/IP Routing:
HKEY_LOCAL_MACHINE \SYSTEM\CurrentControlSet\Services\Tcpip\Parameters\IPEnableRouter

4. Bind your WIRNS server to the IP '192.168.0.1' (or whatever you assigned to the IP of your NIC).

5. Restart WIRNS, or your entire computer for that matter to enable all settings to be correctly set.

6. Assign your ReplayTV network manually with the following info:

IP: 192.168.0.x (I chose 192.168.0.10).
Subnet Mask: 255.255.255.0
Gateway: 192.168.0.1
DNS1: 192.168.0.1
DNS2: 192.168.0.1

7. Connect to the Internet, and update the guide data on WIRNS. Then manually initiate a 'Net Connect' by going to 243-Zones, and choosing option 7.

Hopefully this will successfuly allow your ReplayTV to connect to WIRNS, and your computer to correctly route/proxy the traffic between your ReplayTV, WIRNS, and the real ReplayTV servers.

_________________
Here's my Poop (I know that's the old Poopli, but I like it that way!)
Back to top
View user's profile Send private message
hdonzis
Planet Overlord


Joined: 05 Jan 2005
Posts: 9021
Location: San Antonio, TX

PostPosted: Sun Feb 13, 2011 7:32 pm    Post subject: Reply with quote

I want to document a couple of recent provisions added to allow circumventing WiRNS serving shellcmds and custom lineups:

Because WiRNS will typically aways create a shellcmds file for you to help control the daily net connect, I have added that creating a file named shellcmds.ignore will cause WiRNS to ignore the shellcmds file and get the information from ReplayTV instead. This is particularly useful after performing a factory reset on a unit and IVS/CA does not get restored when connecting through WiRNS. This also can be corrected by adding the two lines that Jon documented in the first post, which are also contained in shellcmds.example. But, it's probably best after performing a factory reset to allow ReplayTV to reconfigure all the ReplayTV settings, so bypassing the custom shellcmds would probably be best. This file can be created either in the individual ReplayTV's directory folders to bypass the shellcmds for individual ReplayTVs, or in the root WiRNS directory to bypass the shellcmds for all ReplayTVs...

In addition, having WiRNS serve custom lineups can be bypassed by creating a file named lineups.no either in the individual ReplayTV directory folders to bypass serving WiRNS lineups for individual ReplayTVs, or in the root WiRNS directory to bypass serving WiRNS lineups to all ReplayTVs. The main benefit of this is to prevent net connection errors when switching ReplayTVs from proxying through WiRNS to connect direct instead. Because the ReplayTV has been configured with custom WiRNS lineups, it will get a net connect error when it connects directly to ReplayTV because they can't serve those lineups. This is typically corrected by changing ZIP codes or clearing the channel guide (2-4-3-Zones). However, if you configure WiRNS not to serve lineups by creating the lineups.no file, then after net connecting WiRNS will clear the custom lineups from the ReplayTV so it can then connect directly successfully. This also can be used if you simply don't want to serve WiRNS lineups to your ReplayTV(s), like if you are using WiRNS temporarily to upgrade IR Blaster files and have lineups configured...

I basically added both these features to allow upgrading IR Blaster files using a fully configured WiRNS on ReplayTVs that aren't net connecting through WiRNS normally. However, I realized that these features also have several other uses, like taking care of the problem of not being able to restore IVS and CA after a factory reset, so I figured they were worth documenting...

Henry
_________________
Here's my Poop (I know that's the old Poopli, but I like it that way!)
Back to top
View user's profile Send private message
Display posts from previous:   
Post new topic   This topic is locked: you cannot edit posts or make replies.    Planet Replay Forum Index -> WiRNS All times are GMT - 8 Hours
Page 1 of 1

 
Jump to:  
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
Planet Replay topic RSS feed 


Powered by phpBB © 2001, 2005 phpBB Group