Differences

This shows you the differences between two versions of the page.

--- en:netzer:networksettings [2011/12/12 09:33] – created holtmann
+++ en:netzer:networksettings [2025/06/11 20:42] (current) – external edit 127.0.0.1
@@ Line 2: / Line 2: @@
 All network settings are changeable via the website.
 Amendments will become effective only after restart, so that it is possible to correct incorrect entries.
+<note important>
+Some settings are available since Version 1.4 or 1.5.
+You should consider updating to the latest Release.
+</note>
+{{networksettings.gif?nolink& |Settings on website}}
-{{:de:netzer:networksettings.gif?nolink& |}}
 ===== IP modes =====
-{{ :de:netzer:ipmode.gif?nolink& |}}
+{{ ipmode.gif?nolink& |IP Modes}}
 IP mode determines how Netzer allocates its IP address, the subnetwork mask and the gateway.
-==== DHCP (from Version 1.4 pro) ====
+==== DHCP ====
 In this mode, Netzer receives the IP address from a DHCP server. After restart, Netzer tries to contact the DHCP server via DHCP broadcast. If a DHCP server is available and prepared to provide an IP address, Netzer will receive its IP address in this way.
 <note important>In this mode, Netzer remains without IP address until it has found a DHCP server.</note>
@@ Line 24: / Line 31: @@
 In this mode, Netzer receives the IP address from a DHCP server. After restart, Netzer tries to contact the DHCP server via DHCP broadcast. If a DHCP server is available and prepared to provide an IP address, Netzer will receive its IP address in this way.
-Should Netzer fail to find a DHCP server after some attempts, it will automatically select an IP address from the AutoIP area (see mode [[de:netzer:networksettings#Auto IP (from version 1.4 pro)|Auto IP]])
-==== DHCP -> Manual IP (from Version 1.4 pro) ====
+Should Netzer fail to find a DHCP server after some attempts, it will automatically select an IP address from the AutoIP area (see mode [[networksettings#Auto IP (from version 1.4 pro)|Auto IP]])
-Analog to mode [[de:netzer:networksettings#DHCP -> AutoIP (Default)|DHCP -> AutoIP]] Netzer tries to contact the DHCP server. Should the attempt fail, the IP data configured manually will be used (refer to mode [[de:netzer:networksettings#manual IP|manual IP]]).
-==== Auto IP (from Version 1.4 pro) ====
+==== DHCP -> Manual IP ====
-In this mode, Netzer selects an IP address from AutoIP area 169.254.1.0 - 169.254.254.255 directly upon restart. The subnetwork mask is 255.255.0.0, a gateway address is not provided. Selection and provision of the AutoIP address is done following the [[wpde>Zeroconf]] protocol. This guarantees tha the IP address is well-defined in the network.
+Analog to mode [[networksettings#DHCP -> AutoIP (Default)|DHCP -> AutoIP]] Netzer tries to contact the DHCP server. Should the attempt fail, the IP data configured manually will be used (refer to mode [[networksettings#manual IP|manual IP]]).
-In AutoIP mode, the IP address has a minor role. Accordingly, the IP address actually used is not very easy to determine (exception: [[de:netzer:spislave|SPI Slave mode]]). Instead, other mechanisms are used to access devices in such a network, e.g. via the name of the device.
+==== Auto IP ====
+In this mode, Netzer selects an IP address from AutoIP area 169.254.1.0 - 169.254.254.255 directly upon restart. The subnetwork mask is 255.255.0.0, a gateway address is not provided. Selection and provision of the AutoIP address is done following the [[wp>Zeroconf]] protocol. This guarantees tha the IP address is well-defined in the network.
+The starting AutoIP is chosen in format 169.254.X.Y. X is the 5th number and Y the 6th number of the MAC address. If for example Netzer has the MAC address //00-04-a3-2c-3d-9f// than the IP address is //169.254.61.159//.
+In AutoIP mode, the IP address has a minor role. Accordingly, the IP address actually used is not very easy to determine (exception: [[spislave|SPI Slave mode]]). Instead, other mechanisms are used to access devices in such a network, e.g. via the [[networksettings#Network name|name of the device]].
@@ Line 41: / Line 53: @@
 In this mode, after restart Netzer uses the manuall IP data previously configured.
-{{ :de:netzer:manualip.gif?nolink& |}}
+{{ manualip.gif?nolink& |}}
 Prior to the IP address being used by Netzer it investigates whether the IP address is not already occupied in the network by another device. In this event, Netzer will enter the state "address conflict" which is indicated by the fast blinking of the connection LED at the network connector of Netzer.
 This address conflict can be solved as follows
   - removing other device from the network or chaning IP address or
   - resetting Netzer to factory settings [[de:netzer:resettofactory#reset to factory settings at Netzer]]
@@ Line 51: / Line 64: @@
 ===== Network name =====
-This name is used to find Netzer in a so-called local network via the [[wpde>Zeroconf#Multicast_DNS|Multicast DNS]] protocol.
+This name is used to find Netzer in a so-called local network via the [[wp>Zeroconf#Service_discovery|Multicast DNS]] protocol.
 The network name may have up to eight characters. The name is required to be unambiguous in the network. In the event of a duplicate, the network service cannot be started and Netzer can only be contacted via the IP address. The name is only valid in the local domain, i.e. .local belongs to the name and must not be left out.
@@ Line 59: / Line 74: @@
-===== HTTP Port (from Version 1.4 pro) =====
+===== HTTP Port =====
 If required (for Firewall reasons or for port forwarding) the port of the Netzer web interface can be changed. The port is published by the name service in the network, so that calls via Bonjour plug-ins are correctly switched to the appropriate port. If calling up the website via the IP address, the port is required to be coded into the URL. An example for port 8080:
 <code>
 http://ne123456.local:8080
 </code>