Hi, i have a rasp pi 3 and 4 and with both I get the same behaviour on my network once I connect the blocker software to my velop router setup. My velop nodes constantly reset themselves. Once I go back to my old pi-hole setup all works normally again. Any suggestions or ideas why this is happening?
I assume you are running eBlocker in "automatic network mode". This results in ARP responses to be sent frequently which your router apparently doesn't handle well.
Just switch eBlocker to manual network mode and issue will be gone.
For more tech. background regarding ARP, pls check here: https://eblocker.org/community/bugs-features/internet-radio-playback-stops-after-a-short-time/#post-1362
It would be great if you would share the exact vendor and model of your router for the compatibility list.
Feedback if the issue is gone would be great too 😉
THX!
Hi @random I which it was that simple 😪 . I tried all tree options, so automatic, individual and expert in where I kept my router as beeing the dhcp server.
All with the same result; my velop setup (consisting out of three linksys mesh router) becomes unstable as soon as eblocker has started up.
What I see is blue light on router (good) 10 sec later red blinking, blue again for 10 sec, red again and on and on....
in my devices all is setup automatic, so dhcp from router and dns also set to automatid. Dns is shown on individual device to gateway (which is my router) and on my router dns is pointing to eblocker.
I spend now my complete free friday in setting up something which should be easy in 10 min, but I am about to quit which I find really pitty as it looks so great
@rpvrpv If ARP (automatic) is turned off eBlocker just sits next to your router - and does nothing to it - nor touches the traffic unless configured as gateway. I wonder why this happens. Very odd. Are you using eOS 2.5.x? If not: please upgrade as it has lots of fixes.
Have you tried reducing components? So just you client, your router and eBlocker all wired by LAN cable or even just router and eBlocker as first step?
Another source of error: Mash Networks (depending on vendor) can cause interference in rare cases. But then eBlocker is not working well - not the router/Mash. Hm. Anyhow, make sure your Mash is in Bridge Mode (what's it's called most) as that usually fixes some issues.
If it doesn't work, I would like to take note of the models in use for adding them as "incompatible".
THX very much for your time and efforts!
@Random I tried your suggestions connected only my first Linksys Velop node directly to my isp router and my rasp-pi 4 with eblocker v2.5.2 directly to my velop node (in bridge mode) This seems to be working fine.
As soon as I connect my second velop node the problem start again. Although my first node seems stable, my second node is unstable again and light switches from blue to red as described earlier. I kept the setup for 10/15 min to see maybe if things maybe stabilized, but unfortunately not 🙁
I have a Linksys Velop model WHW03. Hope that helps.
Do you think maybe future release on eblocker can solve this issue?
@rpvrpv Any news on this?
I fear this issue is related to your specific router only, as other routers do not show this behavior.
Of course there is a low chance this might get fixed in future, but honestly I'd rather recommend a different router as this seems to be a router bug (which is generally not a good sign).
In any case I'll add your router to the compatibility note.
THX!