Mark Royds

Another frustrated admin here. Why did this even have a time-limited license in the first place?

I have the same issue but with different vendors. My environment has 3com switches (don't ask!) and UniFi access points. The UniFi access point sends two management addresses: - a...

I don't think even the perexg builds do quite what I'm asking for. The dist/minisatip.md file included in the perexg build mentions an "-X / -9" option that deals with...

> In any case, the perexg patches that enable the above functionality were introduced in build 11 which so far as I can tell (I'm not a git expert) had...

Hi @lars18th Thanks for the suggestion. I've just tried the solution you proposed. Unfortunately, ommitting the `fe=` from the request doesn't solve the problem. You can see below that the...

> But in any case, I suggest a more complex alternative: put DiseqC 1.0 switchess before the unicable cables. Then instead of two tuners fixed for each sat position, you'll...

My understanding is that `-A 0:0:0.1:3:0` instructs minisatip that: `src=1` is on adapter 0, DiSEqC position 0 `src=2` is on adapter 3, DiSEqC position 0 I think that's the crux...

Perhaps what we need is ``` -I --input-map SRC:INPUT:UB-FREQ,[SRC:INPUT:UB-FREQ] * SRC: satellite position being requested by clients * INPUT: physical input (0-3) * UB: Unicable userband * FREQ: Unicable frequency...

Is the `fe=` limitation of `-A` definitely relevant to the issue? When I [tested using curl ](https://github.com/catalinii/minisatip/issues/1174#issuecomment-2318166422)I ommitted the `fe=` parameter completely and only included `src=` in the request. In...

> Hi @mark-royds , > > I feel you need to try the @Jalle19 version of AXE: https://github.com/Jalle19/satip-axe > > Please read: https://github.com/Jalle19/satip-axe/blob/master/dist/minisatip.md#multiple-unicable-groups I have seen that version but there...