> On Aug 26, 2025, at 15:33, Marcin Cieslak <[email protected]> wrote:
>
> On Tue, 26 Aug 2025, Marcin Cieslak wrote:
>
>> On Tue, 26 Aug 2025, Mark Felder wrote:
>>
>>> If someone could figure out a way to dynamically patch the class in the jar
>>> file -- either manually with a script the porter needs to run or as part of
>>> the port itself -- I'll pay out a $200 bounty. It would remove a lot of
>>> tedious pain when doing updates. I don't think it's possible though.
>>
>> What about something like the below. Requires xxd and jar.
>>
>> JARFILE=../Omada_SDN_Controller_v5.15.24.19_linux_x64/lib/omada-common-5.15.24.19.jar
>> ISLINUXOS_CLASS="com/tplink/smb/omada/common/util/S.class"
>
> [...]
>> Can't test if this really works at the moment, should update the
>> omada-common-5.15.24.19.jar file in place. If "check" fails, we need to
>> figure out whether the Linux-checking function has been moved, renamed or
>> discarded.
>
> This seems to let me go past the following message:
>
> 08-26-2025 22:28:52.159 ERROR [main] [] c.t.s.o.s.OmadaLinuxMain(): Error:
> system is not linux, should not call this founction
>
>
That's looking promising. Does it ever listen on these ports? If so, it started
up correctly. Might take 30 seconds or so.
# netstat -an | grep LISTEN
tcp4 0 0 *.29816 *.* LISTEN
tcp4 0 0 *.29815 *.* LISTEN
tcp4 0 0 *.29814 *.* LISTEN
tcp4 0 0 *.29813 *.* LISTEN
tcp4 0 0 *.29811 *.* LISTEN
tcp4 0 0 *.29812 *.* LISTEN
tcp4 0 0 *.9098 *.* LISTEN
tcp4 0 0 *.8843 *.* LISTEN
tcp4 0 0 *.8043 *.* LISTEN
tcp4 0 0 *.8088 *.* LISTEN
Mark
