FXP.One: Difference between revisions

Latest revision as of 08:01, 28 March 2018

There are further settings that will modify FXP.One's engine behavior which are not part of the definition of a site. Since we are allowed to define any variable name, which is automatically stored, some extra definitions have been created.

Since essentially Extra Site and Client Site commands are the same thing, they are separated because Extra Site lists additional commands which the FXP.One engine will act on. Where as Client Site commands are stored by clients, for clients. The FXP.One engine does not parse these key/value pairs.

USE_XDUPE
STARTDIR
FXP_TLS
IMPLICIT_TLS
LISTARGS
FEAT_CCSN
FEAT_SSCN
FEAT_PRET

Details

 USE_XDUPE=<yna>
 * Auto - If XDUPE is reported in the FEAT reply code, it will be enabled and used.
 * Yes  - Forced on, regardless of FEAT reply.
 * No   - Forced off, regardless of FEAT reply.

 STARTDIR=<str>
 * Optional extra for clients to issue CWD to <str> upon connection, instead of staying in default root "/".

 FXP_TLS=<yna>
 * Auto - Use secure (SSL) data transfers if possible, otherwise plain-text, using CCSN or SSCN.
 * Yes  - Always attempt secure (SSL) data transfers, fail if not possible.
 * No   - Do not attempt secure data transfers, always use plain-text.

The FXP_TLS option is added in addition to data_TLS as it was deemed insufficient for those who would like to force directory listings to use secure methods, but disable secure data transfers, even if sites supported such transfers. If FXP_TLS is not defined, FXP.One engine will use the default behavior as specified by data_TLS.

 IMPLICIT_TLS=<yna>
 * Auto - Do not use Implicit SSL/TLS 
 * No   - Do not use Implicit SSL/TLS
 * Yes  - Attempt implicit SSL challenge immediately upon connecting, before FTP commands.

 LISTARGS=<str>
 * Usually, FXP.Ones uses default LIST arguments ("-lL") but you can over-ride that per site by setting LISTARGS.
 * For example, LISTARGS=-sl, or even "LISTARGS= " for no arguments.

FEAT_CCSN=<str>
FEAT_SSCN=<str>
FEAT_PRET=<str>
* Allow to override the value received in reply to CCSN, SSCN, and PRET.
* If a site replies it supports SSCN, but its FTPD is faulty, you can set
* FEAT_SSCN=n to tell FXP.Oned to ignore it.

Future

 MAX_SESSIONS=<int>
 * Limit number of sessions allowed for one site. Attempts to create another session will be presented with an error.

 MAX_QUEUES=<int>
 * Limit the number of active queues a site is allowed to be involved with. When GO commands are received
 * check the total active queues, and if already over the limit, leave queue in IDLE state. Automatically start queue
 * once an active queue goes to IDLE.

@@ Line 1: / Line 1: @@
-== Hikari TV ひかりTV ==
+There are further settings that will modify '''FXP.One''''s engine behavior which are not part of the definition of a site. Since we are allowed to define any variable name, which is automatically stored, some extra definitions have been created.
-After going through the typical Japanese signup protocol of calling, giving name and address, so they can mail you a form that you write name and address on, to get the service.
+Since essentially '''Extra Site''' and '''Client Site''' commands are the same thing, they are separated because [[Extra Site]] lists additional commands which the '''FXP.One''' engine will act on. Where as [[Client Site]] commands are stored by clients, for clients. The '''FXP.One''' engine does not parse these key/value pairs.
-I got the tuner in the mail ok, as well as the signup code. There was also a NTT flets COP code I needed, so I called NTT to get that.
+* USE_XDUPE
+* STARTDIR
+* FXP_TLS
+* IMPLICIT_TLS
+* LISTARGS
+* FEAT_CCSN
+* FEAT_SSCN
+* FEAT_PRET
-Lots of channels, and the tuner is all in Japanese, but pretty easy to navigate. As always, it is a little sluggish when using the GUI, changing channels and so on. About the same as the satellite and cable STBs I have used before. One would hope they'd made it faster over the years though.
-These are things I want to find an answer for:
+==Details==
-* Hackable? Can I get in, if so, can I add English myself? only port 20000 open so far. (upnp?)
+  USE_XDUPE=<yna>
-* Quick channel list. I want a fast way to get to a more scrollable channel list. Right now you either get full guide (slow) or large icons (slow), or deep in the menus (slow)
+  * Auto - If XDUPE is reported in the FEAT reply code, it will be enabled and used.
-* Quick channels, can I set my preferred channels on the number keys, and quick jump? Looks like I can, but it sure don't work.
+  * Yes  - Forced on, regardless of FEAT reply.
-* Output is 1080i, why not 1080p.
+  * No   - Forced off, regardless of FEAT reply.
-* Can I get it to work with XBMC and remove tuner? (IPV6 etc)
+  STARTDIR=<str>
+  * Optional extra for clients to issue '''CWD''' to <str> upon connection, instead of staying in default root "/".
-=== Networking ===
+  FXP_TLS=<yna>
+  * Auto - Use secure (SSL) data transfers if possible, otherwise plain-text, using CCSN or SSCN.
+  * Yes  - Always attempt secure (SSL) data transfers, fail if not possible.
+  * No   - Do not attempt secure data transfers, always use plain-text.
-I had a fair bit of trouble getting HikariTV to work well. It would sometimes start glitching like crazy, I thought it was the wifi router, or maybe the two switches connected in chain.
+The '''FXP_TLS''' option is added in addition to '''data_TLS''' as it was deemed insufficient for those who would like to force directory listings to use secure methods, but disable secure data transfers, even if sites supported such transfers. If '''FXP_TLS''' is not defined, '''FXP.One''' engine will use the default behavior as specified by '''data_TLS'''.
-But eventually it turns out the be the Win7 PC going into hibernation (sleep). The switch appears to think it still should get multicast packets (wake on lan is on) and something goes weird there. Shutdown has no side effects.
+  IMPLICIT_TLS=<yna>
+  * Auto - Do not use Implicit SSL/TLS
+  * No   - Do not use Implicit SSL/TLS
+  * Yes  - Attempt implicit SSL challenge immediately upon connecting, before FTP commands.
+  LISTARGS=<str>
+  * Usually, FXP.Ones uses default LIST arguments ("-lL") but you can over-ride that per site by setting LISTARGS.
+  * For example, LISTARGS=-sl, or even "LISTARGS= " for no arguments.
+ FEAT_CCSN=<str>
+ FEAT_SSCN=<str>
+ FEAT_PRET=<str>
+ * Allow to override the value received in reply to CCSN, SSCN, and PRET.
+ * If a site replies it supports SSCN, but its FTPD is faulty, you can set
+ * FEAT_SSCN=n to tell FXP.Oned to ignore it.
-=== NEC Aterm WR9500N ===
-I picked up an Aterm WR9500N Wifi router. Fairly easy to setup, defaults were all good. Testing HikariTV with this router now.
+=== Future ===
+  MAX_SESSIONS=<int>
+  * Limit number of sessions allowed for one site. Attempts to create another session will be presented with an error.
+  MAX_QUEUES=<int>
-=== Buffalo ===
+  * Limit the number of '''active queues''' a site is allowed to be involved with. When '''GO''' commands are received
+  * check the total active queues, and if already over the limit, leave queue in IDLE state. Automatically start queue
-I signed up for HikariTV recently, to see what that is like to use. I went for the "double" tuner rental.
+  * once an active queue goes to IDLE.
-Initially I was using an old Buffalo G54 wifi router. It could technically handle it, but all wifi communication stopped when watching tv.
-I went and picked up a WZR-450HP. You have to enable the "Movie engine" and then IPV6 option. Then HikariTV worked.
-However, I noticed you could only watch for 2-3 minutes, then channels would go blocky, corrupt and generally be unplayable. Some channels did not play at all.
-It turns out that you can set the "multicast rate", for which the default is "11 mbps", on the Buffalo WIFI router.
-However, with HD channels, it is sending at about 8-16mbps. I changed the "multicast rate" to 22mbps and it is currently working well.