BINDADDR (JANUS DEFINE parameter) - Revision history

JAL: /* Syntax */ add link

2016-09-19T17:28:48Z

Syntax: add link

← Older revision		Revision as of 17:28, 19 September 2016
Line 13:		Line 13:

	<li>IPV6 addresses are 128-bit integers, represented with eight, colon-separated, 16-bit (four hex-digit) groups, which may be abbreviated and represented with fewer groups. For example,		<li>IPV6 addresses are 128-bit integers, represented with eight, colon-separated, 16-bit (four hex-digit) groups, which may be abbreviated and represented with fewer groups. For example,
	<code>fe80:0000:0000:0000:0200:0000:0300:0016</code> or <code>fe80::200:0:300:16</code>. </li>		<code>fe80:0000:0000:0000:0200:0000:0300:0016</code> or <code>fe80::200:0:300:16</code>.
			<p>
			For more information about the supported format, see [https://en.wikipedia.org/wiki/IPv6_address Recommended representation as text]. </p></li>
	</ul>		</ul>

JAL: IPV4 must be dotted decimal

2016-09-15T19:17:21Z

IPV4 must be dotted decimal

← Older revision		Revision as of 19:17, 15 September 2016
Line 8:		Line 8:
	<p class="syntax">BINDADDR <span class="term">address</span> </p>		<p class="syntax">BINDADDR <span class="term">address</span> </p>

	Where: <var class="term">address</var> is a host IP address. Address formats for IPV4 and (as of version 7.7 of Model 204) IPV6 are supported.		Where: <var class="term">address</var> is a string containing the host IP address. Address formats for IPV4 and (as of version 7.7 of Model 204) IPV6 are supported:
			<ul>
			<li>IPV4 addresses are 32-bit integers, commonly displayed as "dotted decimal" 8-bit groups. For example, the IP address X'C6F2F40D' is commonly displayed (and must be specified for <var class="term"> address</var>) as <code>198.242.244.13</code>. </li>

	~~IPV4 addresses are 32-bit integers, commonly displayed as "dotted decimal" 8-bit groups. For example, the IP address X'C6F2F40D' is commonly displayed as~~ <~~code~~>~~198.242.244.13</code>.~~		<li>IPV6 addresses are 128-bit integers, represented with eight, colon-separated, 16-bit (four hex-digit) groups, which may be abbreviated and represented with fewer groups. For example,
			<code>fe80:0000:0000:0000:0200:0000:0300:0016</code> or <code>fe80::200:0:300:16</code>. </li>
	IPV6 addresses are 128-bit integers, represented with eight, colon-separated, 16-bit (four hex-digit) groups, which may be abbreviated and represented with fewer groups. For example,		</ul>
	<code>fe80:0000:0000:0000:0200:0000:0300:0016</code> or <code>fe80::200:0:300:16</code>.

	==Usage==		==Usage==

JAL: add IPV6 address format

2016-09-14T21:35:53Z

add IPV6 address format

← Older revision		Revision as of 21:35, 14 September 2016
Line 10:		Line 10:
	Where: <var class="term">address</var> is a host IP address. Address formats for IPV4 and (as of version 7.7 of Model 204) IPV6 are supported.		Where: <var class="term">address</var> is a host IP address. Address formats for IPV4 and (as of version 7.7 of Model 204) IPV6 are supported.

	IPV4 addresses are 32-bit integers, commonly displayed as "dotted decimal." For example, the IP address X'C6F2F40D' is commonly displayed as 198.242.244.13.		IPV4 addresses are 32-bit integers, commonly displayed as "dotted decimal" 8-bit groups. For example, the IP address X'C6F2F40D' is commonly displayed as <code>198.242.244.13</code>.

	IPV6 addresses are 128-bit integers~~. An IPV6 address is formally~~ represented with eight, colon-separated, 16-bit (four hex-digit) groups. For example:		IPV6 addresses are 128-bit integers, represented with eight, colon-separated, 16-bit (four hex-digit) groups, which may be abbreviated and represented with fewer groups. For example,
	<~~p class="~~code">~~2011~~:~~0ab4~~:~~15a1~~:0000:0000:~~4a0e~~:~~0280~~:~~5274~~ </p>		<code>fe80:0000:0000:0000:0200:0000:0300:0016</code> or <code>fe80::200:0:300:16</code>.

	==Usage==		==Usage==

JAL: add IPV6 address format

2016-09-14T19:21:21Z

add IPV6 address format

← Older revision		Revision as of 19:21, 14 September 2016
Line 1:		Line 1:
	<span class="pageSubtitle">~~BINDADDR xxx.xxx.xxx.xxx —~~ Bind port to a particular IP address</span>		<span class="pageSubtitle">Bind port to a particular IP address</span>

	<var>BINDADDR</var> is a parameter on <var>[[JANUS DEFINE]]</var>, which defines and sets characteristics of a Janus port.		<var>BINDADDR</var> is a parameter on <var>[[JANUS DEFINE]]</var>, which defines and sets characteristics of a Janus port.

	This parameter specifies the IP address to which the port will be bound, if the host (machine) on which <var class="product">Model 204</var> is running supports multiple IP addresses. The IP address must be an IP address of the host. If <var>BINDADDR</var> is not specified, the port binds the port number for all IP addresses associated with the host; that is, it can be accessed via any IP address associated with the host.		This parameter specifies the IP address to which the port will be bound, if the host (machine) on which <var class="product">Model 204</var> is running supports multiple IP addresses. The IP address must be an IP address of the host. If <var>BINDADDR</var> is not specified, the port binds the port number for all IP addresses associated with the host; that is, it can be accessed via any IP address associated with the host.

	~~This parameter only really makes sense on a host with more than one IP~~ address~~. For example, if a host on which an Online is running has IP addresses 198.242.244.47 and 198.242.244.130, a~~ <~~code~~>~~BINDADDR 198.242.244.47~~</~~code~~> ~~specification indicates that the port can only be reached through IP address 198.242.244.47.~~		==Syntax==
			<p class="syntax">BINDADDR <span class="term">address</span> </p>

	This parameter is especially useful for allowing a single mainframe host or even an Online to act as more than one web server without the inconvenience of having port numbers on URLs. This can be done because there can be multiple port 80's (the default web port number) on the host, each accessed by its indicated <var>~~BINDADDR~~</var>. ~~The separate IP addresses could, in turn, be associated with different DNS host names even though these separate names refer to the same underlying machine~~.		Where: <var class="term">address</var> is a host IP address. Address formats for IPV4 and (as of version 7.7 of Model 204) IPV6 are supported.

	~~Note~~ that there is not likely to be much, if any, performance benefit to having multiple Janus ports with the same port number but different <var>BINDADDR</var>s in the same Online. ~~There~~ might certainly be~~, however,~~ some organizational advantages to running such a configuration.		IPV4 addresses are 32-bit integers, commonly displayed as "dotted decimal." For example, the IP address X'C6F2F40D' is commonly displayed as 198.242.244.13.

			IPV6 addresses are 128-bit integers. An IPV6 address is formally represented with eight, colon-separated, 16-bit (four hex-digit) groups. For example:
			<p class="code">2011:0ab4:15a1:0000:0000:4a0e:0280:5274 </p>

			==Usage==
			<ul>
			<li>This parameter only really makes sense on a host with more than one IP address. For example, if a host on which an Online is running has IP addresses 198.242.244.47 and 198.242.244.130, a <code>BINDADDR 198.242.244.47</code> specification indicates that the port can only be reached through IP address 198.242.244.47. </li>

			<li><var>BINDADDR</var> is especially useful for allowing a single mainframe host or even an Online to act as more than one web server without the inconvenience of having port numbers on URLs. This can be done because there can be multiple port 80's (the default web port number) on the host, each accessed by its indicated <var>BINDADDR</var>. The separate IP addresses could, in turn, be associated with different DNS host names, even though these separate names refer to the same underlying machine. </li>

			<li>There is not likely to be much, if any, performance benefit to having multiple Janus ports with the same port number but different <var>BINDADDR</var> specifications in the same Online. However, there might certainly be some organizational advantages to running such a configuration. </li>
			</ul>

	Valid for all port types.		Valid for all port types.

JALWiccan: Automatically generated page update

2013-04-16T21:51:33Z

Automatically generated page update

← Older revision		Revision as of 21:51, 16 April 2013
Line 1:		Line 1:
	<span class="pageSubtitle"~~><section begin="desc" /~~>BINDADDR xxx.xxx.xxx.xxx — Bind port to a particular IP address~~<section end="desc" />~~</span>		<span class="pageSubtitle">BINDADDR xxx.xxx.xxx.xxx — Bind port to a particular IP address</span>

	<var>BINDADDR</var> is a parameter on <var>[[JANUS DEFINE]]</var>, which defines and sets characteristics of a Janus port.		<var>BINDADDR</var> is a parameter on <var>[[JANUS DEFINE]]</var>, which defines and sets characteristics of a Janus port.

JAL2 at 17:29, 2 March 2012

2012-03-02T17:29:37Z

← Older revision		Revision as of 17:29, 2 March 2012
Line 1:		Line 1:
	<span class="pageSubtitle"><section begin="desc" />BINDADDR xxx.xxx.xxx.xxx — Bind port to a particular ip address<section end="desc" /></span>		<span class="pageSubtitle"><section begin="desc" />BINDADDR xxx.xxx.xxx.xxx — Bind port to a particular IP address<section end="desc" /></span>

	<var>BINDADDR</var> is a parameter on <var>[[JANUS DEFINE]]</var>, which defines and sets characteristics of a Janus port.		<var>BINDADDR</var> is a parameter on <var>[[JANUS DEFINE]]</var>, which defines and sets characteristics of a Janus port.

JAL2 at 17:29, 2 March 2012

2012-03-02T17:29:20Z

← Older revision		Revision as of 17:29, 2 March 2012
Line 1:		Line 1:
	<span class="pageSubtitle"><section begin="desc" />BINDADDR xxx.xxx.xxx.xxx — ~~bind~~ port to a particular ip address<section end="desc" /></span>		<span class="pageSubtitle"><section begin="desc" />BINDADDR xxx.xxx.xxx.xxx — Bind port to a particular ip address<section end="desc" /></span>

	<var>BINDADDR</var> is a parameter on <var>[[JANUS DEFINE]]</var>, which defines and sets characteristics of a Janus port.		<var>BINDADDR</var> is a parameter on <var>[[JANUS DEFINE]]</var>, which defines and sets characteristics of a Janus port.

JAL2 at 17:28, 2 March 2012

2012-03-02T17:28:57Z

← Older revision		Revision as of 17:28, 2 March 2012
Line 1:		Line 1:
	~~{{DISPLAYTITLE:BINDADDR}}~~		<span class="pageSubtitle"><section begin="desc" />BINDADDR xxx.xxx.xxx.xxx — bind port to a particular ip address<section end="desc" /></span>
	<span class="pageSubtitle"><section begin="desc" />BINDADDR xxx.xxx.xxx.xxx &~~amp;~~mdash; bind port to a particular ip address<section end="desc" /></span>

	<var>BINDADDR</var> is a parameter on [[JANUS DEFINE]], which defines and sets characteristics of a Janus port.		<var>BINDADDR</var> is a parameter on <var>[[JANUS DEFINE]]</var>, which defines and sets characteristics of a Janus port.

	This parameter specifies the IP address to which the port will be bound, if the host (machine) on which <var class="product">Model 204</var> is running supports multiple IP addresses. The IP address must be an IP address of the host. If <var>BINDADDR</var> is not specified, the port binds the port number for all IP addresses associated with the host; that is, it can be accessed via any IP address associated with the host.		This parameter specifies the IP address to which the port will be bound, if the host (machine) on which <var class="product">Model 204</var> is running supports multiple IP addresses. The IP address must be an IP address of the host. If <var>BINDADDR</var> is not specified, the port binds the port number for all IP addresses associated with the host; that is, it can be accessed via any IP address associated with the host.

JALWiccan: 1 revision

2012-03-01T21:15:14Z

1 revision

← Older revision	Revision as of 21:15, 1 March 2012
(No difference)

JAL2 at 21:15, 1 March 2012

2012-03-01T21:15:13Z

← Older revision		Revision as of 21:15, 1 March 2012
Line 1:		Line 1:
	{{DISPLAYTITLE:BINDADDR}}		{{DISPLAYTITLE:BINDADDR}}
	<span class="pageSubtitle"><section begin="desc" />BINDADDR xxx.xxx.xxx.xxx — bind port to a particular ip address<section end="desc" /></span>		<span class="pageSubtitle"><section begin="desc" />BINDADDR xxx.xxx.xxx.xxx &mdash; bind port to a particular ip address<section end="desc" /></span>

	<var>BINDADDR</var> is a parameter on [[JANUS DEFINE]], which defines and sets characteristics of a Janus port.		<var>BINDADDR</var> is a parameter on [[JANUS DEFINE]], which defines and sets characteristics of a Janus port.

	This parameter specifies the IP address to which the port will be bound, if the host (machine) on which ''Model 204'' is running supports multiple IP addresses. The IP address must be an IP address of the host. If <var>BINDADDR</var> is not specified, the port binds the port number for all IP addresses associated with the host; that is, it can be accessed via any IP address associated with the host.		This parameter specifies the IP address to which the port will be bound, if the host (machine) on which <var class="product">Model 204</var> is running supports multiple IP addresses. The IP address must be an IP address of the host. If <var>BINDADDR</var> is not specified, the port binds the port number for all IP addresses associated with the host; that is, it can be accessed via any IP address associated with the host.

	This parameter only really makes sense on a host with more than one IP address. For example, if a host on which an Online is running has IP addresses 198.242.244.47 and 198.242.244.130, a <code>BINDADDR 198.242.244.47</code> specification indicates that the port can only be reached through IP address 198.242.244.47.		This parameter only really makes sense on a host with more than one IP address. For example, if a host on which an Online is running has IP addresses 198.242.244.47 and 198.242.244.130, a <code>BINDADDR 198.242.244.47</code> specification indicates that the port can only be reached through IP address 198.242.244.47.