@Clive_A 

i could see the packets, but only if i am in the same subnet.

if my pc is in another subnet. i cant see any packets from the other subnets.

with 1.2.4 no problem

 

 

Just to confirm, you have ruled out all the possibilities in this:

mDNS Repeater on the Router Doesn't Take Effect

And with the exact same config, it would work if you downgrade it. Is that a correct understanding?

  @Clive_A 

got it working...

BUT... i had to add another mDNS rule. With only one rule, i can't see multicasts from another subnet

i have to create one rule with ALL Networks as Service and ALL Networks as client AND another rule with the 2 subnets where i want to see the multicasts.

With only one rule, it doesn't work... if i disable one, it stops working too.

  @Clive_A 

i hope thats only a config problem, but i would agree to send you my config. via mail or how would you like to receive it?

Clive_A wrote

  @RBL 

RBL wrote

Clive_A wrote

If you reconnect the fiber module instead of rebooting it, will it work?

What does the LED status when it is down and displayed as "disconnected"?
(Disconnected means the link is down. Either unplugged or local or peer port is disabled/down.)

  @Clive_A Will give it a try if it happens again. Currently it is running. 

There is no code-level change from the last firmware to this pre-release.

So, it should not relate to the firmware.

This might be a problem with the modem, which requires much more investigation.

  @Clive_A this morning same issue, after a nightly reboot fiber connection was gone.

removed and reinserted sfp module same result. not working. Reboot of the devices, no result.

Have not done a Power cycle yet.

Update: did a powercycle and fiber connection is once again working.

Clive_A wrote

What's the difference between a power cycle and a reboot? As for me, if you are talking about the router, I assume it is not a problem with the router because there is no difference between a power cycle and a reboot for the router.

I asked when it is down, the network is gone, what does the SFP LED look like? I don't think that is answered?

 

What do you mean reboot the devices? Which one? Router? Modem?

 

And was this behavior seen on previous firmware?

Downgrade it and test again? Like written before, the dev informed that there is no SFP-related change.

 @Clive 
Apparently there is a difference between a (software) reboot and a power cycle. As a power cycle bring the glasfiber connection back alive whereas a (software) reboot doesn't.

As mentioned before, I have two WAN connections:
1. internetconnection via cable whereas the cable modem is in bridge modus.

2 fiber connection whereas the SFP module is used.

And the fiber connection is having the issue.

When it is down the SFP connection is not working at all (notice the absense of the [CONNECT] button:


When doing a powercycle it starts working again:




I have no idea what you mean with SFP LED, as far as I can see it does not have a led (For your reference the image below is when everything is working):


What I mean with reboot the devices, is  I have a reboot schedule in Omada for the router, switches and access points.


There is no modem as my fiber connection is directly connected to the router (the authentication is done by the ER707-M2)

And to clarify the difference between a reboot and a power cycle:

Reboot: hitting the reboot button in Omada


Power Cycle: removing the power cable from the device (in this case the ER707-M2)



I did not have this behaviour prior to updating it to the this v1.3.0, it worked flawlessly for months.

Have not downgraded the firmware yet, as I first need to check what kind of issues I will be getting when downgrading. (current workaround is doing a power cycle of the ER707-M2 v1). This is a minimal business interuption as the backup internet line takes over when the SFP is not working.

I hope this answers the questions.