In the ThinPrint Hub’s web console under the menu item Network, you will find the following options:
- Identification: Functions to better identify the device in the network
- IPv4 Settings: Functions for addressing the device in the network
- IPv6 Settings: Displays the Hub’s automatically generated IPv6 address
- IEEE 802.1x authentication: Enable the IEEE 802.1X authentication for the Hub logging on to other devices (typically in conjunction with a Radius server)
- Proxy: For the use of a proxy (server) to increase the security in the company network
- Hub Monitoring: Configure which version of the SNMP protocol should be used to monitor the ThinPrint Hub
- Remote Management→ Cloud Management: Centrally manage ThinPrint Hubs or Personal Printing Release Stations in the ezeep Cloud
- Remote Management→ Central Remote Management: Centrally manage ThinPrint Hubs or Personal Printing Release Stations with Stratodesk NoTouch Center
- Cloud Connect: Publish printers (of a Hub) for cloud printing with ezeep Blue
Note:
Starting with firmware version 1.8 it is possible to remotely configure ThinPrint Hubs using the (on premises installed) Stratodesk NoTouch Center. On this, use Remote Management→ Central Remote Management.
As of firmware version 1.16 you can also manage ThinPrint Hubs via the cloud-based ezeep Blue portal; to do so, log in to ezeep Blue and assign the Hub to your Organization there. Then select Remote Management→ Cloud Management.
Identification
The Identification menu in the ThinPrint Hub’s web console offers the following functions to better identify the device in the network:
| Menu | Function |
| Hostname | the ThinPrint Hub’s hostname (contains the last six digits of the MAC address by default) |
| Comments | field for comments on the hostname |
| MAC address | MAC address display |
| Location | the location information for the ThinPrint Hub |
| Save | saves the entries |
| Cancel | cancels the operation |
IPv4 Settings
This web console menu offers the following functions for addressing the device in the network:
| Menu | Function |
| Use DHCP | a dynamic IPv4 address is assigned automatically from a DHCP server |
| a static IPv4 address will be entered manually Note: In this case, remember to maintain your DNS. |
|
|
Address |
the ThinPrint Hub’s IP address or hostname |
|
Subnet mask |
the subnet mask for the IPv4 address |
|
Gateway |
the gateway address of the subnet |
|
DNS server 1 |
the IPv4 address of the first-requested DNS server |
|
DNS server 2 |
the IPv4 address of the second-requested DNS server |
|
DNS search domain |
• Domain name • Suffix for generating the Fully Qualified Domain Names (FQDN) – usually from the hostname and domain name |
| Save | saves the entries |
| Cancel | cancels the operation |
IPv6 Settings
This web console menu displays the Hub’s automatically generated IPv6 address.
IEEE 802.1x authentication
In this website console menu you can enable the IEEE 802.1X authentication for the Hub logging on to other devices (typically in conjunction with a Radius server). You can choose between the following authentication methods:
- MD5
- TLS
- TTLS
- PEAP
Note! If you need certificates for the authentication you have to upload them first in the certificates store using the web console menu Certificates.
MD5 (only for test purposes)
| Menu | Function |
| User name | user name which will be used for identification at RADIUS server |
| Password | password which will be used for authentication at the RADIUS server |
TLS
| Menu | Function |
|
Root or intermediate certificate |
You have to choose a root or intermediate certificate which you’ve already uploaded to the certificate store of the hub.
Note! If you choose an intermediate certificate, the root certificate has to be uploaded to the certificate store as well. |
|
Client certificate |
A user certificate matching the root or intermediate certificate must be specified. See the section Creating an IEEE 802.1x certificate for the Hub. |
TTLS
| Menu | Function |
| User name | user name which will be used for identification at RADIUS server |
| Password | password which will be used for authentication at the RADIUS server |
| Outer authentication | You can choose between the following authentication methods: • PEAP label 0 • PEAP label 1 • PEAPv0 • PEAPv1 |
| Inner authentication | You can choose between the following authentication methods: • PAP • CHAP • MS-CHAPv2 • EAP-MD5 (only for test purposes) |
| Root or intermediate certificate | You have to choose a root or intermediate certificate which you’ve already uploaded to the certificate store of the hub.
Note! If you choose an intermediate certificate, the root certificate has to be uploaded to the certificate store as well. |
| Client certificate | password which will be used for authentication at the RADIUS server |
PEAP
| Menu | Function |
|
User name |
user name which will be used for identification at RADIUS server |
| Password | password which will be used for authentication at the RADIUS server |
| Outer authentication | You can choose between the following authentication methods: • PEAP label 0 • PEAP label 1 • PEAPv0 • PEAPv1 |
| Inner authentication | You can choose between the following authentication methods: • PAP • CHAP • MS-CHAPv2 • EAP-MD5 (only for test purposes) |
| Root or intermediate certificate | You have to choose a root or intermediate certificate which you’ve already uploaded to the certificate store of the hub.
Note! If you choose an intermediate certificate, the root certificate has to be uploaded to the certificate store as well. |
Note! If you wish to use more authentication methods than given or experiencing problems with the implemented methods, please do not hesitate to contact our support team.
Proxy
If you want to place a proxy (server) in front of the Hub, you can enter its address information here.
| Menu | Function |
| Address | proxy’s IP address |
| Port | TCP port for connecting the proxy |
| Save | saves your settings |
| Cancel | cancels the operation |
Hub Monitoring
In this web console menu you can configure which version of the SNMP protocol should be used to monitor the ThinPrint Hub itself. But this time you don’t have to choose which protocol you want to use. You can configure both and decide later which matter suits you better.
| Menu | Function |
| SNMP version 1 & 2c Community name |
Default: “public” Setup the community which should be used for printer monitoring. You have to setup this community name at all printers you want to monitor. |
| SNMP version 3 User name |
user name which will be used for identification at the printer |
| Authentication type | you can choose between 2 encryption algorithms • MD5 (Use only for test purposes) • SHA |
| Authentication passphrase | password which will be used for authentication at the printer |
| Privacy type | You can choose between 2 encryption algorithms: • DES • AES (Optional) |
| Privacy passphrase | password which will be used for encrypting your SNMP queries (Optional) |
| Save | saves your settings |
| Cancel | cancels the operation |