<
WiFi
EAP-Software: Why not available for Linux / as Docker image
This thread has been locked for further replies. You can start a new thread to share your ideas or ask questions.EAP-Software: Why not available for Linux / as Docker image
Posts: 3
Helpful: 0
Solutions: 0
Stories: 0
Registered: 2017-05-11
EAP-Software: Why not available for Linux / as Docker image
2017-05-11 13:54:18
Tags:
Model :
Hardware Version :
Firmware Version :
ISP :
Hi there,
I am a mac pureplayer and just bought EAP 330 APs.
So far, I am very happy but delivering only windows software seems to be "from the past".
I understand that it's purely java (tomcat) & mongodb and ask myself why there is no linux version publicly available?
If you would just release a docker, this would be really awesome.
Tobias
Hardware Version :
Firmware Version :
ISP :
Hi there,
I am a mac pureplayer and just bought EAP 330 APs.
So far, I am very happy but delivering only windows software seems to be "from the past".
I understand that it's purely java (tomcat) & mongodb and ask myself why there is no linux version publicly available?
If you would just release a docker, this would be really awesome.
Tobias
#1
Options
- Copy Link
- Subscribe
- Bookmark
- Report Inappropriate Content
Thread Manage
68 Reply
Posts: 4334
Helpful: 993
Solutions: 173
Stories: 3
Registered: 2015-12-05
Re:EAP-Software: Why not available for Linux / as Docker image
2017-09-21 03:00:41
jeanphi wrote
this is our fault, we find solution on problem on manual, but not read completely from start to end ;-(
Call me old-school or pedantic, but I read manuals and I really enjoy reading them. At least I always check the prerequisites for any piece of software before even considering installation.
But: even if one doesn't read the manual, it should be clear (at least to network engineers) that although each EAPC can detect all EAPs in the LAN - that's why discovery works - they cannot see wether another EAPC already talks with pending EAPs or has adopted the EAPs. An EAPC could log an error message only if the second EAPC is running on the same computer system; this is indeed detectable and also checked for on startup!
See, if PeterL would have mentioned that he runs a second EAPC in the same LAN, I would have told him to stop the other one and a lot of wasted time trying to reproduce this "error" on other people's systems would have been saved (yes, I did try his "solution" with different IPs to see whether there are some hard-coded IPs in the EAPC software). Indeed I could not imagine that someone is really trying to run two EAPCs in the same network. It's like trying to establish two network default routes or two DHCP servers with overlapping address pools.
But it's ridiculous to blame the software for not detecting what's going on on another system somewhere in the network.
༺ 0100 1101 0010 10ཏ1 0010 0110 1010 1110 ༻
0
We appreciate your feedback. Feel free to let us know more. Log in to submit feedback.
0
We appreciate your feedback. Feel free to let us know more. Log in to submit feedback.
#62
Options
- Copy Link
- Report Inappropriate Content
Thread Manage
Posts: 15
Helpful: 0
Solutions: 0
Stories: 0
Registered: 2017-01-17
Re:EAP-Software: Why not available for Linux / as Docker image
2017-09-21 14:06:32
R1D2 wrote
I disagree. Instead, it is another case of not Reading The Fine Manual. See EAP Controller User's Guide, page 2:
While it's true that the EAP Controller software can be improved in some areas, it has the same RTFM policy as with any other software.
The full quote reads
[quote]
The EAP Controller can be running on only one host in a LAN. When other users in the LAN try to launch EAP
Controller on their own hosts, they will be redirected to the host that is already running EAP Controller.[/quote]
I remove the rest of my comment.
I won't be arguing on the internet ...
0
We appreciate your feedback. Feel free to let us know more. Log in to submit feedback.
0
We appreciate your feedback. Feel free to let us know more. Log in to submit feedback.
#63
Options
- Copy Link
- Report Inappropriate Content
Thread Manage
Posts: 4334
Helpful: 993
Solutions: 173
Stories: 3
Registered: 2015-12-05
Re:EAP-Software: Why not available for Linux / as Docker image
2017-09-22 01:48:21
PeterL. wrote
When other users in the LAN try to launch EAP [B]Controller on their own hosts, they will be redirected to the host that is already running EAP Controller.[/B]
Not applicable to Linux way of starting daemon processes. If you need this, use the Windows version of EAPC.
༺ 0100 1101 0010 10ཏ1 0010 0110 1010 1110 ༻
0
We appreciate your feedback. Feel free to let us know more. Log in to submit feedback.
0
We appreciate your feedback. Feel free to let us know more. Log in to submit feedback.
#64
Options
- Copy Link
- Report Inappropriate Content
Thread Manage
Posts: 13
Helpful: 1
Solutions: 0
Stories: 0
Registered: 2016-01-03
Re:EAP-Software: Why not available for Linux / as Docker image
2017-10-29 00:26:45
Hello,
I try to use the EAPController on an Ubuntu 16.04.3 vm too. But I have the same problems like the others. The daemon starts only with stopped ethernet interface.
I understand, that only on eap controller can manage the network and because of this an second on linux won't start. I've tested the eap controller in the past on my local windows pc, but deinstalled it again.
So I have no active EAPController installation in my network but the linux daemon won't start. Why? I have a Lancom Access Point but no separate controller software for mesh wlans.
There are only this lines in startup.log
[CODE]log4j:WARN No appenders could be found for logger (com.tp_link.eap.util.system.SystemUtil).
log4j:WARN Please initialize the log4j system properly.
========EAP_LINUX_MONGOD_KEY======
mongodPath = "/opt/tplink/EAPController/bin/mongod" --port 27017 --dbpath "/opt/tplink/EAPController/data/db" -pidfilepath "/opt/tplink/EAPController/data/mongo.pid" --logappend --logpath "/opt/tplink/EAPController/logs/mongod.log" --nohttpinterface --bind_ip 127.0.0.1
repairCommand = "/opt/tplink/EAPController/bin/mongod" --repair --dbpath "/opt/tplink/EAPController/data/db" --logappend --logpath "/opt/tplink/EAPController/logs/mongod.log"
"/opt/tplink/EAPController/bin/mongod" --port 27017 --dbpath "/opt/tplink/EAPController/data/db" -pidfilepath "/opt/tplink/EAPController/data/mongo.pid" --logappend --logpath "/opt/tplink/EAPController/logs/mongod.log" --nohttpinterface --bind_ip 127.0.0.1
[/CODE]
and in server.log
[CODE]2017-10-28 18:16:54 [main] [INFO]-[ConfigurationFactory.java:39] - success to load configuration : eap.properties
2017-10-28 18:17:21 [main] [INFO]-[ConfigurationFactory.java:39] - success to load configuration : eap.properties
2017-10-28 18:17:21 [main] [INFO]-[ConfigurationFactory.java:39] - success to load configuration : mongodb.properties
2017-10-28 18:17:21 [main] [INFO]-[ConfigurationFactory.java:39] - success to load configuration : jetty.properties
2017-10-28 18:17:21 [main] [INFO]-[ConfigurationFactory.java:39] - success to load configuration : log4j.properties
2017-10-28 18:17:21 [main] [INFO]-[ConfigurationFactory.java:39] - success to load configuration : device.properties
2017-10-28 18:17:21 [main] [INFO]-[ConfigurationFactory.java:39] - success to load configuration : netty.properties
2017-10-28 18:17:21 [main] [INFO]-[ConfigurationFactory.java:39] - success to load configuration : user.params.properties
[/CODE]
I use the init.d-Script from R1D2.
Where is my error?
Thanks
Ulf
I try to use the EAPController on an Ubuntu 16.04.3 vm too. But I have the same problems like the others. The daemon starts only with stopped ethernet interface.
I understand, that only on eap controller can manage the network and because of this an second on linux won't start. I've tested the eap controller in the past on my local windows pc, but deinstalled it again.
So I have no active EAPController installation in my network but the linux daemon won't start. Why? I have a Lancom Access Point but no separate controller software for mesh wlans.
There are only this lines in startup.log
[CODE]log4j:WARN No appenders could be found for logger (com.tp_link.eap.util.system.SystemUtil).
log4j:WARN Please initialize the log4j system properly.
========EAP_LINUX_MONGOD_KEY======
mongodPath = "/opt/tplink/EAPController/bin/mongod" --port 27017 --dbpath "/opt/tplink/EAPController/data/db" -pidfilepath "/opt/tplink/EAPController/data/mongo.pid" --logappend --logpath "/opt/tplink/EAPController/logs/mongod.log" --nohttpinterface --bind_ip 127.0.0.1
repairCommand = "/opt/tplink/EAPController/bin/mongod" --repair --dbpath "/opt/tplink/EAPController/data/db" --logappend --logpath "/opt/tplink/EAPController/logs/mongod.log"
"/opt/tplink/EAPController/bin/mongod" --port 27017 --dbpath "/opt/tplink/EAPController/data/db" -pidfilepath "/opt/tplink/EAPController/data/mongo.pid" --logappend --logpath "/opt/tplink/EAPController/logs/mongod.log" --nohttpinterface --bind_ip 127.0.0.1
[/CODE]
and in server.log
[CODE]2017-10-28 18:16:54 [main] [INFO]-[ConfigurationFactory.java:39] - success to load configuration : eap.properties
2017-10-28 18:17:21 [main] [INFO]-[ConfigurationFactory.java:39] - success to load configuration : eap.properties
2017-10-28 18:17:21 [main] [INFO]-[ConfigurationFactory.java:39] - success to load configuration : mongodb.properties
2017-10-28 18:17:21 [main] [INFO]-[ConfigurationFactory.java:39] - success to load configuration : jetty.properties
2017-10-28 18:17:21 [main] [INFO]-[ConfigurationFactory.java:39] - success to load configuration : log4j.properties
2017-10-28 18:17:21 [main] [INFO]-[ConfigurationFactory.java:39] - success to load configuration : device.properties
2017-10-28 18:17:21 [main] [INFO]-[ConfigurationFactory.java:39] - success to load configuration : netty.properties
2017-10-28 18:17:21 [main] [INFO]-[ConfigurationFactory.java:39] - success to load configuration : user.params.properties
[/CODE]
I use the init.d-Script from R1D2.
Where is my error?
Thanks
Ulf
0
We appreciate your feedback. Feel free to let us know more. Log in to submit feedback.
0
We appreciate your feedback. Feel free to let us know more. Log in to submit feedback.
#65
Options
- Copy Link
- Report Inappropriate Content
Thread Manage
Posts: 4334
Helpful: 993
Solutions: 173
Stories: 3
Registered: 2015-12-05
Re:EAP-Software: Why not available for Linux / as Docker image
2017-10-29 02:52:54
How did you check that the EAPC is not running? Using ps or by trying to connect to it?
If the latter, please post output of
[CODE]netstat -a | grep 8043[/CODE]
If the latter, please post output of
[CODE]netstat -a | grep 8043[/CODE]
༺ 0100 1101 0010 10ཏ1 0010 0110 1010 1110 ༻
0
We appreciate your feedback. Feel free to let us know more. Log in to submit feedback.
0
We appreciate your feedback. Feel free to let us know more. Log in to submit feedback.
#66
Options
- Copy Link
- Report Inappropriate Content
Thread Manage
Posts: 13
Helpful: 1
Solutions: 0
Stories: 0
Registered: 2016-01-03
Re:EAP-Software: Why not available for Linux / as Docker image
2017-10-29 15:21:29
I have 3 Windows VMs and one Windows workstation. The TP-Link EAP Controller was only installed on the workstation. The I have deinstalled it some times ago. So I doublechecked only, if the software EAPController installed on this machines. It is not. To be sure I was shutting down the 2 Win7-VMs. The third is a server. On my workstation and on the server I doublechecked with "netstat -an". On both machines is no Port 8088 or 8043 open (code shows only tcp lines). Additionally the Linux VM is in a other VLAN separated network (10.0.1.0/24). But in this network i have no MS Windows.
Server:
[CODE]
Proto Lokale Adresse Remoteadresse Status
TCP 0.0.0.0:80 0.0.0.0:0 ABHÖREN
TCP 0.0.0.0:135 0.0.0.0:0 ABHÖREN
TCP 0.0.0.0:443 0.0.0.0:0 ABHÖREN
TCP 0.0.0.0:445 0.0.0.0:0 ABHÖREN
TCP 0.0.0.0:1433 0.0.0.0:0 ABHÖREN
TCP 0.0.0.0:3389 0.0.0.0:0 ABHÖREN
TCP 0.0.0.0:5666 0.0.0.0:0 ABHÖREN
TCP 0.0.0.0:5666 0.0.0.0:0 ABHÖREN
TCP 0.0.0.0:5985 0.0.0.0:0 ABHÖREN
TCP 0.0.0.0:8443 0.0.0.0:0 ABHÖREN
TCP 0.0.0.0:8460 0.0.0.0:0 ABHÖREN
TCP 0.0.0.0:8530 0.0.0.0:0 ABHÖREN
TCP 0.0.0.0:8531 0.0.0.0:0 ABHÖREN
TCP 0.0.0.0:47001 0.0.0.0:0 ABHÖREN
TCP 0.0.0.0:49152 0.0.0.0:0 ABHÖREN
TCP 0.0.0.0:49153 0.0.0.0:0 ABHÖREN
TCP 0.0.0.0:49154 0.0.0.0:0 ABHÖREN
TCP 0.0.0.0:49156 0.0.0.0:0 ABHÖREN
TCP 0.0.0.0:51180 0.0.0.0:0 ABHÖREN
TCP 0.0.0.0:51193 0.0.0.0:0 ABHÖREN
TCP 0.0.0.0:51246 0.0.0.0:0 ABHÖREN
TCP 10.0.2.4:139 0.0.0.0:0 ABHÖREN
TCP 10.0.2.4:3389 10.0.2.205:50017 HERGESTELLT
TCP 10.0.2.4:62123 10.0.2.5:3128 SCHLIESSEN_WARTEN
TCP 10.0.2.4:62124 10.0.2.5:3128 SCHLIESSEN_WARTEN
TCP 10.0.2.4:62129 10.0.2.5:3128 SCHLIESSEN_WARTEN
TCP 10.0.2.4:62134 10.0.2.5:3128 HERGESTELLT
TCP 10.0.2.4:62486 10.0.2.2:3128 HERGESTELLT
TCP 10.0.2.4:62615 10.0.2.2:135 WARTEND
TCP 10.0.2.4:62616 10.0.2.2:1024 WARTEND
TCP 10.0.2.4:62618 10.0.2.2:1024 WARTEND
TCP 10.0.2.4:62620 10.0.2.2:88 WARTEND
TCP 10.0.2.4:62621 10.0.2.2:88 WARTEND
TCP 10.0.2.4:62622 10.0.2.2:88 WARTEND
TCP 10.0.2.4:62624 10.0.2.2:88 WARTEND
TCP 10.0.2.4:62625 10.0.2.2:445 HERGESTELLT
TCP 10.0.2.4:62626 10.0.2.2:88 WARTEND
TCP 10.0.2.4:62627 10.0.2.2:88 WARTEND
TCP 10.0.2.4:62628 10.0.2.2:88 WARTEND
TCP 10.0.2.4:62629 10.0.2.2:1024 WARTEND
TCP 10.0.2.4:62630 10.0.2.2:88 WARTEND
TCP 10.0.2.4:62631 10.0.2.2:1024 WARTEND
TCP 10.0.2.4:62632 10.0.2.2:389 WARTEND
TCP 10.0.2.4:62633 10.0.2.2:389 WARTEND
TCP 10.0.2.4:62634 10.0.2.2:88 WARTEND
TCP 10.0.2.4:62635 10.0.2.2:88 WARTEND
TCP 10.0.2.4:62636 10.0.2.2:1024 WARTEND
TCP 10.0.2.4:62637 10.0.2.2:389 WARTEND
TCP 10.0.2.4:62638 10.0.2.2:88 WARTEND
TCP 10.0.2.4:62639 10.0.2.2:389 WARTEND
TCP 10.0.2.4:62640 10.0.2.2:389 WARTEND
TCP 10.0.2.4:62641 10.0.2.2:389 WARTEND
TCP 10.0.2.4:62642 10.0.2.5:445 HERGESTELLT
TCP 10.0.2.4:62643 10.0.2.2:88 WARTEND
TCP 10.0.2.4:62645 10.0.2.2:3128 WARTEND
TCP 10.0.2.4:62648 10.0.2.2:1024 HERGESTELLT
TCP 10.0.2.4:62649 10.0.2.2:88 WARTEND
TCP 10.0.2.4:62650 10.0.2.2:389 WARTEND
TCP 10.0.2.4:62651 10.0.2.2:88 WARTEND
TCP 127.0.0.1:5939 0.0.0.0:0 ABHÖREN
TCP 127.0.0.1:5939 127.0.0.1:62644 HERGESTELLT
TCP 127.0.0.1:62482 127.0.0.1:62483 HERGESTELLT
TCP 127.0.0.1:62483 127.0.0.1:62482 HERGESTELLT
TCP 127.0.0.1:62644 127.0.0.1:5939 HERGESTELLT
TCP 127.0.0.1:62646 127.0.0.1:62647 HERGESTELLT
TCP 127.0.0.1:62647 127.0.0.1:62646 HERGESTELLT
TCP [::]:80 [::]:0 ABHÖREN
TCP [::]:135 [::]:0 ABHÖREN
TCP [::]:443 [::]:0 ABHÖREN
TCP [::]:445 [::]:0 ABHÖREN
TCP [::]:1433 [::]:0 ABHÖREN
TCP [::]:3389 [::]:0 ABHÖREN
TCP [::]:5666 [::]:0 ABHÖREN
TCP [::]:5985 [::]:0 ABHÖREN
TCP [::]:8460 [::]:0 ABHÖREN
TCP [::]:8530 [::]:0 ABHÖREN
TCP [::]:8531 [::]:0 ABHÖREN
TCP [::]:47001 [::]:0 ABHÖREN
TCP [::]:49152 [::]:0 ABHÖREN
TCP [::]:49153 [::]:0 ABHÖREN
TCP [::]:49154 [::]:0 ABHÖREN
TCP [::]:49156 [::]:0 ABHÖREN
TCP [::]:51180 [::]:0 ABHÖREN
TCP [::]:51193 [::]:0 ABHÖREN
TCP [::]:51246 [::]:0 ABHÖREN[/CODE]
Workstation:
[CODE]
Aktive Verbindungen
Proto Lokale Adresse Remoteadresse Status
TCP 0.0.0.0:135 0.0.0.0:0 ABHÖREN
TCP 0.0.0.0:445 0.0.0.0:0 ABHÖREN
TCP 0.0.0.0:3389 0.0.0.0:0 ABHÖREN
TCP 0.0.0.0:5357 0.0.0.0:0 ABHÖREN
TCP 0.0.0.0:19443 0.0.0.0:0 ABHÖREN
TCP 0.0.0.0:49152 0.0.0.0:0 ABHÖREN
TCP 0.0.0.0:49153 0.0.0.0:0 ABHÖREN
TCP 0.0.0.0:49154 0.0.0.0:0 ABHÖREN
TCP 0.0.0.0:49218 0.0.0.0:0 ABHÖREN
TCP 0.0.0.0:51746 0.0.0.0:0 ABHÖREN
TCP 0.0.0.0:51833 0.0.0.0:0 ABHÖREN
TCP 10.0.2.205:139 0.0.0.0:0 ABHÖREN
TCP 10.0.2.205:51756 169.54.83.37:5938 HERGESTELLT
TCP 10.0.2.205:51765 10.0.2.2:3128 SCHLIESSEN_WARTEN
TCP 10.0.2.205:51775 10.0.2.2:3128 SCHLIESSEN_WARTEN
TCP 10.0.2.205:51779 10.0.2.2:3128 SCHLIESSEN_WARTEN
TCP 10.0.2.205:51782 10.0.2.2:3128 SCHLIESSEN_WARTEN
TCP 10.0.2.205:51792 10.0.2.2:445 HERGESTELLT
TCP 10.0.2.205:51810 10.0.2.5:445 HERGESTELLT
TCP 10.0.2.205:51858 10.0.2.8:5222 HERGESTELLT
TCP 10.0.2.205:52283 149.154.167.51:443 HERGESTELLT
TCP 10.0.2.205:52318 10.0.2.2:389 WARTEND
TCP 10.0.2.205:52319 10.0.2.2:389 WARTEND
TCP 10.0.2.205:52321 10.0.2.2:3128 WARTEND
TCP 10.0.2.205:52322 10.0.2.2:3128 HERGESTELLT
TCP 10.0.2.205:52325 10.0.2.2:3128 HERGESTELLT
TCP 10.0.2.205:52326 10.0.2.2:3128 HERGESTELLT
TCP 10.0.2.205:52328 10.0.2.2:3128 HERGESTELLT
TCP 10.0.2.205:52329 10.0.2.2:3128 HERGESTELLT
TCP 10.0.2.205:52331 194.25.134.115:993 HERGESTELLT
TCP 10.0.2.205:52332 81.169.145.103:993 HERGESTELLT
TCP 10.0.2.205:52333 81.169.145.103:993 HERGESTELLT
TCP 10.0.2.205:52334 81.169.145.103:993 HERGESTELLT
TCP 10.0.2.205:52335 134.119.228.54:993 HERGESTELLT
TCP 10.0.2.205:52336 212.227.17.170:993 HERGESTELLT
TCP 10.0.2.205:52338 134.119.228.54:993 HERGESTELLT
TCP 10.0.2.205:52339 194.25.134.115:993 HERGESTELLT
TCP 10.0.2.205:52340 81.169.145.103:993 HERGESTELLT
TCP 10.0.2.205:52341 10.1.2.2:993 HERGESTELLT
TCP 10.0.2.205:52342 10.1.2.2:993 HERGESTELLT
TCP 10.0.2.205:52343 10.0.2.2:3128 WARTEND
TCP 10.0.2.205:52344 10.0.2.2:3128 WARTEND
TCP 10.0.2.205:52345 10.0.2.2:3128 WARTEND
TCP 10.0.2.205:52346 10.0.2.2:3128 WARTEND
TCP 10.0.2.205:52347 10.0.2.2:3128 WARTEND
TCP 10.0.2.205:52348 10.0.2.2:3128 HERGESTELLT
TCP 10.0.2.205:52349 10.0.2.2:3128 HERGESTELLT
TCP 10.0.2.205:52350 10.0.2.2:3128 HERGESTELLT
TCP 10.0.2.205:52351 10.0.2.2:3128 HERGESTELLT
TCP 10.0.2.205:52352 10.0.2.2:3128 HERGESTELLT
TCP 10.0.2.205:52354 212.227.17.170:993 HERGESTELLT
TCP 10.0.2.205:52358 10.0.2.2:3128 HERGESTELLT
TCP 10.0.2.205:52360 10.0.2.2:3128 HERGESTELLT
TCP 10.0.2.205:52361 81.169.145.103:993 HERGESTELLT
TCP 10.0.2.205:52362 10.0.2.2:3128 WARTEND
TCP 10.0.2.205:52363 81.169.145.103:993 HERGESTELLT
TCP 10.0.2.205:52364 10.0.2.2:3128 WARTEND
TCP 10.0.2.205:52365 10.0.2.2:3128 HERGESTELLT
TCP 10.0.2.205:52366 10.0.2.2:3128 HERGESTELLT
TCP 10.0.2.205:52367 81.169.145.103:993 HERGESTELLT
TCP 10.0.2.205:52368 10.0.2.2:3128 HERGESTELLT
TCP 10.0.2.205:52369 10.0.2.2:3128 HERGESTELLT
TCP 10.0.2.205:52370 81.169.145.103:993 HERGESTELLT
TCP 10.0.2.205:52371 10.0.2.2:3128 WARTEND
TCP 10.0.2.205:52372 81.169.145.103:993 HERGESTELLT
TCP 10.0.2.205:52373 81.169.145.103:993 HERGESTELLT
TCP 10.0.2.205:52374 10.0.2.2:3128 HERGESTELLT
TCP 10.0.2.205:52375 10.0.2.2:3128 HERGESTELLT
TCP 10.0.2.205:52377 10.1.2.2:993 HERGESTELLT
TCP 10.0.2.205:52378 10.0.2.2:3128 HERGESTELLT
TCP 10.0.2.205:52380 10.1.2.2:993 HERGESTELLT
TCP 10.0.2.205:52381 10.0.2.2:3128 HERGESTELLT
TCP 10.0.2.205:52382 10.0.2.2:3128 HERGESTELLT
TCP 10.0.2.205:52383 10.0.2.2:3128 HERGESTELLT
TCP 10.0.2.205:52384 10.0.2.2:3128 WARTEND
TCP 10.0.2.205:52385 134.119.228.54:993 HERGESTELLT
TCP 10.0.2.205:52386 134.119.228.54:993 HERGESTELLT
TCP 10.0.2.205:52387 10.1.2.2:993 HERGESTELLT
TCP 10.0.2.205:52388 10.1.2.2:993 HERGESTELLT
TCP 10.0.2.205:52389 10.0.2.2:3128 HERGESTELLT
TCP 127.0.0.1:5354 0.0.0.0:0 ABHÖREN
TCP 127.0.0.1:5939 0.0.0.0:0 ABHÖREN
TCP 127.0.0.1:5939 127.0.0.1:51823 HERGESTELLT
TCP 127.0.0.1:9990 0.0.0.0:0 ABHÖREN
TCP 127.0.0.1:24271 0.0.0.0:0 ABHÖREN
TCP 127.0.0.1:51823 127.0.0.1:5939 HERGESTELLT
TCP 127.0.0.1:51825 127.0.0.1:51826 HERGESTELLT
TCP 127.0.0.1:51826 127.0.0.1:51825 HERGESTELLT
TCP 127.0.0.1:52314 127.0.0.1:52315 HERGESTELLT
TCP 127.0.0.1:52315 127.0.0.1:52314 HERGESTELLT
TCP 127.0.0.1:52355 127.0.0.1:52356 HERGESTELLT
TCP 127.0.0.1:52356 127.0.0.1:52355 HERGESTELLT
TCP 127.0.0.1:58946 0.0.0.0:0 ABHÖREN
TCP 127.0.0.1:59046 0.0.0.0:0 ABHÖREN
TCP 127.0.0.1:62514 0.0.0.0:0 ABHÖREN
TCP 127.0.0.1:65000 0.0.0.0:0 ABHÖREN
TCP 192.168.56.1:139 0.0.0.0:0 ABHÖREN
TCP [::]:135 [::]:0 ABHÖREN
TCP [::]:445 [::]:0 ABHÖREN
TCP [::]:3389 [::]:0 ABHÖREN
TCP [::]:5357 [::]:0 ABHÖREN
TCP [::]:19443 [::]:0 ABHÖREN
TCP [::]:49152 [::]:0 ABHÖREN
TCP [::]:49153 [::]:0 ABHÖREN
TCP [::]:49154 [::]:0 ABHÖREN
TCP [::]:49218 [::]:0 ABHÖREN
TCP [::]:51746 [::]:0 ABHÖREN
TCP [::]:51833 [::]:0 ABHÖREN
TCP [::]:51833 [::]:0 ABHÖREN[/CODE]
I've tested the the statement:
So I'd shutting down the Linux VM an installed EAP Controller on the Windows Server. After installation there is no redirect to any other instance.
So why the the software don't works on supported OS Ubuntu 16.04 :-( ?
Thanks
Ulf
Server:
[CODE]
Proto Lokale Adresse Remoteadresse Status
TCP 0.0.0.0:80 0.0.0.0:0 ABHÖREN
TCP 0.0.0.0:135 0.0.0.0:0 ABHÖREN
TCP 0.0.0.0:443 0.0.0.0:0 ABHÖREN
TCP 0.0.0.0:445 0.0.0.0:0 ABHÖREN
TCP 0.0.0.0:1433 0.0.0.0:0 ABHÖREN
TCP 0.0.0.0:3389 0.0.0.0:0 ABHÖREN
TCP 0.0.0.0:5666 0.0.0.0:0 ABHÖREN
TCP 0.0.0.0:5666 0.0.0.0:0 ABHÖREN
TCP 0.0.0.0:5985 0.0.0.0:0 ABHÖREN
TCP 0.0.0.0:8443 0.0.0.0:0 ABHÖREN
TCP 0.0.0.0:8460 0.0.0.0:0 ABHÖREN
TCP 0.0.0.0:8530 0.0.0.0:0 ABHÖREN
TCP 0.0.0.0:8531 0.0.0.0:0 ABHÖREN
TCP 0.0.0.0:47001 0.0.0.0:0 ABHÖREN
TCP 0.0.0.0:49152 0.0.0.0:0 ABHÖREN
TCP 0.0.0.0:49153 0.0.0.0:0 ABHÖREN
TCP 0.0.0.0:49154 0.0.0.0:0 ABHÖREN
TCP 0.0.0.0:49156 0.0.0.0:0 ABHÖREN
TCP 0.0.0.0:51180 0.0.0.0:0 ABHÖREN
TCP 0.0.0.0:51193 0.0.0.0:0 ABHÖREN
TCP 0.0.0.0:51246 0.0.0.0:0 ABHÖREN
TCP 10.0.2.4:139 0.0.0.0:0 ABHÖREN
TCP 10.0.2.4:3389 10.0.2.205:50017 HERGESTELLT
TCP 10.0.2.4:62123 10.0.2.5:3128 SCHLIESSEN_WARTEN
TCP 10.0.2.4:62124 10.0.2.5:3128 SCHLIESSEN_WARTEN
TCP 10.0.2.4:62129 10.0.2.5:3128 SCHLIESSEN_WARTEN
TCP 10.0.2.4:62134 10.0.2.5:3128 HERGESTELLT
TCP 10.0.2.4:62486 10.0.2.2:3128 HERGESTELLT
TCP 10.0.2.4:62615 10.0.2.2:135 WARTEND
TCP 10.0.2.4:62616 10.0.2.2:1024 WARTEND
TCP 10.0.2.4:62618 10.0.2.2:1024 WARTEND
TCP 10.0.2.4:62620 10.0.2.2:88 WARTEND
TCP 10.0.2.4:62621 10.0.2.2:88 WARTEND
TCP 10.0.2.4:62622 10.0.2.2:88 WARTEND
TCP 10.0.2.4:62624 10.0.2.2:88 WARTEND
TCP 10.0.2.4:62625 10.0.2.2:445 HERGESTELLT
TCP 10.0.2.4:62626 10.0.2.2:88 WARTEND
TCP 10.0.2.4:62627 10.0.2.2:88 WARTEND
TCP 10.0.2.4:62628 10.0.2.2:88 WARTEND
TCP 10.0.2.4:62629 10.0.2.2:1024 WARTEND
TCP 10.0.2.4:62630 10.0.2.2:88 WARTEND
TCP 10.0.2.4:62631 10.0.2.2:1024 WARTEND
TCP 10.0.2.4:62632 10.0.2.2:389 WARTEND
TCP 10.0.2.4:62633 10.0.2.2:389 WARTEND
TCP 10.0.2.4:62634 10.0.2.2:88 WARTEND
TCP 10.0.2.4:62635 10.0.2.2:88 WARTEND
TCP 10.0.2.4:62636 10.0.2.2:1024 WARTEND
TCP 10.0.2.4:62637 10.0.2.2:389 WARTEND
TCP 10.0.2.4:62638 10.0.2.2:88 WARTEND
TCP 10.0.2.4:62639 10.0.2.2:389 WARTEND
TCP 10.0.2.4:62640 10.0.2.2:389 WARTEND
TCP 10.0.2.4:62641 10.0.2.2:389 WARTEND
TCP 10.0.2.4:62642 10.0.2.5:445 HERGESTELLT
TCP 10.0.2.4:62643 10.0.2.2:88 WARTEND
TCP 10.0.2.4:62645 10.0.2.2:3128 WARTEND
TCP 10.0.2.4:62648 10.0.2.2:1024 HERGESTELLT
TCP 10.0.2.4:62649 10.0.2.2:88 WARTEND
TCP 10.0.2.4:62650 10.0.2.2:389 WARTEND
TCP 10.0.2.4:62651 10.0.2.2:88 WARTEND
TCP 127.0.0.1:5939 0.0.0.0:0 ABHÖREN
TCP 127.0.0.1:5939 127.0.0.1:62644 HERGESTELLT
TCP 127.0.0.1:62482 127.0.0.1:62483 HERGESTELLT
TCP 127.0.0.1:62483 127.0.0.1:62482 HERGESTELLT
TCP 127.0.0.1:62644 127.0.0.1:5939 HERGESTELLT
TCP 127.0.0.1:62646 127.0.0.1:62647 HERGESTELLT
TCP 127.0.0.1:62647 127.0.0.1:62646 HERGESTELLT
TCP [::]:80 [::]:0 ABHÖREN
TCP [::]:135 [::]:0 ABHÖREN
TCP [::]:443 [::]:0 ABHÖREN
TCP [::]:445 [::]:0 ABHÖREN
TCP [::]:1433 [::]:0 ABHÖREN
TCP [::]:3389 [::]:0 ABHÖREN
TCP [::]:5666 [::]:0 ABHÖREN
TCP [::]:5985 [::]:0 ABHÖREN
TCP [::]:8460 [::]:0 ABHÖREN
TCP [::]:8530 [::]:0 ABHÖREN
TCP [::]:8531 [::]:0 ABHÖREN
TCP [::]:47001 [::]:0 ABHÖREN
TCP [::]:49152 [::]:0 ABHÖREN
TCP [::]:49153 [::]:0 ABHÖREN
TCP [::]:49154 [::]:0 ABHÖREN
TCP [::]:49156 [::]:0 ABHÖREN
TCP [::]:51180 [::]:0 ABHÖREN
TCP [::]:51193 [::]:0 ABHÖREN
TCP [::]:51246 [::]:0 ABHÖREN[/CODE]
Workstation:
[CODE]
Aktive Verbindungen
Proto Lokale Adresse Remoteadresse Status
TCP 0.0.0.0:135 0.0.0.0:0 ABHÖREN
TCP 0.0.0.0:445 0.0.0.0:0 ABHÖREN
TCP 0.0.0.0:3389 0.0.0.0:0 ABHÖREN
TCP 0.0.0.0:5357 0.0.0.0:0 ABHÖREN
TCP 0.0.0.0:19443 0.0.0.0:0 ABHÖREN
TCP 0.0.0.0:49152 0.0.0.0:0 ABHÖREN
TCP 0.0.0.0:49153 0.0.0.0:0 ABHÖREN
TCP 0.0.0.0:49154 0.0.0.0:0 ABHÖREN
TCP 0.0.0.0:49218 0.0.0.0:0 ABHÖREN
TCP 0.0.0.0:51746 0.0.0.0:0 ABHÖREN
TCP 0.0.0.0:51833 0.0.0.0:0 ABHÖREN
TCP 10.0.2.205:139 0.0.0.0:0 ABHÖREN
TCP 10.0.2.205:51756 169.54.83.37:5938 HERGESTELLT
TCP 10.0.2.205:51765 10.0.2.2:3128 SCHLIESSEN_WARTEN
TCP 10.0.2.205:51775 10.0.2.2:3128 SCHLIESSEN_WARTEN
TCP 10.0.2.205:51779 10.0.2.2:3128 SCHLIESSEN_WARTEN
TCP 10.0.2.205:51782 10.0.2.2:3128 SCHLIESSEN_WARTEN
TCP 10.0.2.205:51792 10.0.2.2:445 HERGESTELLT
TCP 10.0.2.205:51810 10.0.2.5:445 HERGESTELLT
TCP 10.0.2.205:51858 10.0.2.8:5222 HERGESTELLT
TCP 10.0.2.205:52283 149.154.167.51:443 HERGESTELLT
TCP 10.0.2.205:52318 10.0.2.2:389 WARTEND
TCP 10.0.2.205:52319 10.0.2.2:389 WARTEND
TCP 10.0.2.205:52321 10.0.2.2:3128 WARTEND
TCP 10.0.2.205:52322 10.0.2.2:3128 HERGESTELLT
TCP 10.0.2.205:52325 10.0.2.2:3128 HERGESTELLT
TCP 10.0.2.205:52326 10.0.2.2:3128 HERGESTELLT
TCP 10.0.2.205:52328 10.0.2.2:3128 HERGESTELLT
TCP 10.0.2.205:52329 10.0.2.2:3128 HERGESTELLT
TCP 10.0.2.205:52331 194.25.134.115:993 HERGESTELLT
TCP 10.0.2.205:52332 81.169.145.103:993 HERGESTELLT
TCP 10.0.2.205:52333 81.169.145.103:993 HERGESTELLT
TCP 10.0.2.205:52334 81.169.145.103:993 HERGESTELLT
TCP 10.0.2.205:52335 134.119.228.54:993 HERGESTELLT
TCP 10.0.2.205:52336 212.227.17.170:993 HERGESTELLT
TCP 10.0.2.205:52338 134.119.228.54:993 HERGESTELLT
TCP 10.0.2.205:52339 194.25.134.115:993 HERGESTELLT
TCP 10.0.2.205:52340 81.169.145.103:993 HERGESTELLT
TCP 10.0.2.205:52341 10.1.2.2:993 HERGESTELLT
TCP 10.0.2.205:52342 10.1.2.2:993 HERGESTELLT
TCP 10.0.2.205:52343 10.0.2.2:3128 WARTEND
TCP 10.0.2.205:52344 10.0.2.2:3128 WARTEND
TCP 10.0.2.205:52345 10.0.2.2:3128 WARTEND
TCP 10.0.2.205:52346 10.0.2.2:3128 WARTEND
TCP 10.0.2.205:52347 10.0.2.2:3128 WARTEND
TCP 10.0.2.205:52348 10.0.2.2:3128 HERGESTELLT
TCP 10.0.2.205:52349 10.0.2.2:3128 HERGESTELLT
TCP 10.0.2.205:52350 10.0.2.2:3128 HERGESTELLT
TCP 10.0.2.205:52351 10.0.2.2:3128 HERGESTELLT
TCP 10.0.2.205:52352 10.0.2.2:3128 HERGESTELLT
TCP 10.0.2.205:52354 212.227.17.170:993 HERGESTELLT
TCP 10.0.2.205:52358 10.0.2.2:3128 HERGESTELLT
TCP 10.0.2.205:52360 10.0.2.2:3128 HERGESTELLT
TCP 10.0.2.205:52361 81.169.145.103:993 HERGESTELLT
TCP 10.0.2.205:52362 10.0.2.2:3128 WARTEND
TCP 10.0.2.205:52363 81.169.145.103:993 HERGESTELLT
TCP 10.0.2.205:52364 10.0.2.2:3128 WARTEND
TCP 10.0.2.205:52365 10.0.2.2:3128 HERGESTELLT
TCP 10.0.2.205:52366 10.0.2.2:3128 HERGESTELLT
TCP 10.0.2.205:52367 81.169.145.103:993 HERGESTELLT
TCP 10.0.2.205:52368 10.0.2.2:3128 HERGESTELLT
TCP 10.0.2.205:52369 10.0.2.2:3128 HERGESTELLT
TCP 10.0.2.205:52370 81.169.145.103:993 HERGESTELLT
TCP 10.0.2.205:52371 10.0.2.2:3128 WARTEND
TCP 10.0.2.205:52372 81.169.145.103:993 HERGESTELLT
TCP 10.0.2.205:52373 81.169.145.103:993 HERGESTELLT
TCP 10.0.2.205:52374 10.0.2.2:3128 HERGESTELLT
TCP 10.0.2.205:52375 10.0.2.2:3128 HERGESTELLT
TCP 10.0.2.205:52377 10.1.2.2:993 HERGESTELLT
TCP 10.0.2.205:52378 10.0.2.2:3128 HERGESTELLT
TCP 10.0.2.205:52380 10.1.2.2:993 HERGESTELLT
TCP 10.0.2.205:52381 10.0.2.2:3128 HERGESTELLT
TCP 10.0.2.205:52382 10.0.2.2:3128 HERGESTELLT
TCP 10.0.2.205:52383 10.0.2.2:3128 HERGESTELLT
TCP 10.0.2.205:52384 10.0.2.2:3128 WARTEND
TCP 10.0.2.205:52385 134.119.228.54:993 HERGESTELLT
TCP 10.0.2.205:52386 134.119.228.54:993 HERGESTELLT
TCP 10.0.2.205:52387 10.1.2.2:993 HERGESTELLT
TCP 10.0.2.205:52388 10.1.2.2:993 HERGESTELLT
TCP 10.0.2.205:52389 10.0.2.2:3128 HERGESTELLT
TCP 127.0.0.1:5354 0.0.0.0:0 ABHÖREN
TCP 127.0.0.1:5939 0.0.0.0:0 ABHÖREN
TCP 127.0.0.1:5939 127.0.0.1:51823 HERGESTELLT
TCP 127.0.0.1:9990 0.0.0.0:0 ABHÖREN
TCP 127.0.0.1:24271 0.0.0.0:0 ABHÖREN
TCP 127.0.0.1:51823 127.0.0.1:5939 HERGESTELLT
TCP 127.0.0.1:51825 127.0.0.1:51826 HERGESTELLT
TCP 127.0.0.1:51826 127.0.0.1:51825 HERGESTELLT
TCP 127.0.0.1:52314 127.0.0.1:52315 HERGESTELLT
TCP 127.0.0.1:52315 127.0.0.1:52314 HERGESTELLT
TCP 127.0.0.1:52355 127.0.0.1:52356 HERGESTELLT
TCP 127.0.0.1:52356 127.0.0.1:52355 HERGESTELLT
TCP 127.0.0.1:58946 0.0.0.0:0 ABHÖREN
TCP 127.0.0.1:59046 0.0.0.0:0 ABHÖREN
TCP 127.0.0.1:62514 0.0.0.0:0 ABHÖREN
TCP 127.0.0.1:65000 0.0.0.0:0 ABHÖREN
TCP 192.168.56.1:139 0.0.0.0:0 ABHÖREN
TCP [::]:135 [::]:0 ABHÖREN
TCP [::]:445 [::]:0 ABHÖREN
TCP [::]:3389 [::]:0 ABHÖREN
TCP [::]:5357 [::]:0 ABHÖREN
TCP [::]:19443 [::]:0 ABHÖREN
TCP [::]:49152 [::]:0 ABHÖREN
TCP [::]:49153 [::]:0 ABHÖREN
TCP [::]:49154 [::]:0 ABHÖREN
TCP [::]:49218 [::]:0 ABHÖREN
TCP [::]:51746 [::]:0 ABHÖREN
TCP [::]:51833 [::]:0 ABHÖREN
TCP [::]:51833 [::]:0 ABHÖREN[/CODE]
I've tested the the statement:
When other users in the LAN try to launch EAP [B]Controller on their own hosts, they will be redirected to the host that is already running EAP Controller.[/B]
So I'd shutting down the Linux VM an installed EAP Controller on the Windows Server. After installation there is no redirect to any other instance.
So why the the software don't works on supported OS Ubuntu 16.04 :-( ?
Thanks
Ulf
0
We appreciate your feedback. Feel free to let us know more. Log in to submit feedback.
0
We appreciate your feedback. Feel free to let us know more. Log in to submit feedback.
#67
Options
- Copy Link
- Report Inappropriate Content
Thread Manage
Posts: 4334
Helpful: 993
Solutions: 173
Stories: 3
Registered: 2015-12-05
Re:EAP-Software: Why not available for Linux / as Docker image
2017-10-29 17:32:25
Seems to me that the WebApplicationContext is not initialized for some weird reason.
As can be seen from the EAP firmware download page, TP-Link currently prepares for release of EAPC 2.5.1.
Maybe the new version will have fixes for this problem, too.
As can be seen from the EAP firmware download page, TP-Link currently prepares for release of EAPC 2.5.1.
Maybe the new version will have fixes for this problem, too.
༺ 0100 1101 0010 10ཏ1 0010 0110 1010 1110 ༻
0
We appreciate your feedback. Feel free to let us know more. Log in to submit feedback.
0
We appreciate your feedback. Feel free to let us know more. Log in to submit feedback.
#68
Options
- Copy Link
- Report Inappropriate Content
Thread Manage
Posts: 13
Helpful: 1
Solutions: 0
Stories: 0
Registered: 2016-01-03
Re:EAP-Software: Why not available for Linux / as Docker image
2017-10-30 03:03:36
Ok. Until this I will use it from my Windows Server. Thanks
0
We appreciate your feedback. Feel free to let us know more. Log in to submit feedback.
0
We appreciate your feedback. Feel free to let us know more. Log in to submit feedback.
#69
Options
- Copy Link
- Report Inappropriate Content
Thread Manage
Posts: 3
Helpful: 0
Solutions: 0
Stories: 0
Registered: 2017-05-11
Information
Helpful: 0
Views: 13920
Replies: 68
Voters 0
No one has voted for it yet.
Tags
Related Articles
API or SDK Doc
263
0
Report Inappropriate Content
Transfer Module
New message