Easy Smart 108 fix for Java application
This thread has been locked for further replies. You can start a new thread to share your ideas or ask questions.
Easy Smart 108 fix for Java application
Model :
Hardware Version : Not Clear
Firmware Version :
ISP :
I just got my Easy Smart 108E switch and was disappointed as others that the web interface had been removed.
To add insult to injury, the software (which is Java based) has a windows installer and only works under Windows.
Some folk have managed to use WINE to run the software, which does work (although a bug in my Crossover means that all the text is white)
I decided instead to find out why the Java DIDN'T work under OSX.
It turns out that the code binds the listening socket to a specific IP address. At least OS X and possibly others will only receive broadcast traffic when the socket is bound to INADDR_ANY (0.0.0.0). I fixed this in my own version and can now run the software from OS X.
With my white hat on, would TP Link object to my attaching my fixed jar file here? Obviously we all hope that TP-Link would incorporate the fix into their official distribution soon.
I'm also working on a little utility to expose the monitoring in a way suitable for graphing. I think I could make a java class which could be deployed standalone and call into the Easy Smart jar for the protocol handling. Any thoughts? Obviously there'd be a level of knowledge required, but you're probably going to need to have some skill to want to graph your network traffic anyhow :D
Hardware Version : Not Clear
Firmware Version :
ISP :
I just got my Easy Smart 108E switch and was disappointed as others that the web interface had been removed.
To add insult to injury, the software (which is Java based) has a windows installer and only works under Windows.
Some folk have managed to use WINE to run the software, which does work (although a bug in my Crossover means that all the text is white)
I decided instead to find out why the Java DIDN'T work under OSX.
It turns out that the code binds the listening socket to a specific IP address. At least OS X and possibly others will only receive broadcast traffic when the socket is bound to INADDR_ANY (0.0.0.0). I fixed this in my own version and can now run the software from OS X.
With my white hat on, would TP Link object to my attaching my fixed jar file here? Obviously we all hope that TP-Link would incorporate the fix into their official distribution soon.
I'm also working on a little utility to expose the monitoring in a way suitable for graphing. I think I could make a java class which could be deployed standalone and call into the Easy Smart jar for the protocol handling. Any thoughts? Obviously there'd be a level of knowledge required, but you're probably going to need to have some skill to want to graph your network traffic anyhow :D