Hello eBlocker-Fans,
When I start my eBlocker on above named Raspi4, the eBlocker kickes away the Fritz!Box and overtakes its place - no Internet any more. If I take my PI400, the eBlocker works fine. The Raspi4 itself with Bullseye works fine but homenet crashes, if it is connected to. As a workaround i connected the raspi4 with a new eBlocker installed by an USB to Ethernet Adapter, but it doesn't work. The same Raspi4 with Bullseye, is connecting immediatly to the Internet. Is it possible to teach eBlocker (for Example by editing a config-File) to use the adapter instead of the build-in Ethernet-connection?
Regards Thomas
@kalkleiste First of all, external ethernet adapters are not supported. Unless you are a developer with root access to eBlockerOS with deeper knowledge of handling device drivers and IP-tables, this is not feasible.
I'm sure we find a different solution once the problem is fully clear. At the very moment I have not understood the problem. I already don't understand, what "crashes the Internet" mean at all? Please be more specific like "if I try XXX, I get YYY but I expected ZZZ" and describe in detail what you do.
Generally, if I get you right, you have two Raspi 4 - on is working fine with eBlockerOS, the other is not. Correct?
Have you tried a fresh install of eBlockerOS (writing a new SD card with eBlockerOS) and used this in the bogus eBlocker?
If the issue persist with a new SD, please run a "traceroute eblocker.org" with both(!) eBlockers and post results here for comparison.
THX!
Hello and thanks for the qiuck response and, on the other hand, sorry for my late one.
With "crashes the internet" is following behavior meant:
If I connect the "defect Pi4" with inserted eBlocker4 to the internet, using the internal ethernet-connector, it overtakes the IP-Adress of the router, the router is no longer accessable (nor with the IP-Adress, which now belongs to the eBlocker, neither with "fritz.box") and no Internet-connection (with all other devices, too) is possible. I tried this with a new installation of eBlocker4 on a testetd used SD-Card, done with the AppImage with LinuxMint 21.3. The same eBlocker4-SD-Card works fine on a PI400. To make this test with a new SD-Card, I first have to get one (is ordered, but unfortually is missing on mail-delivery).
If I start the "defect PI4" with Bullseye, the same error occurs when connected with the internal ethernet-connector and workes fine with the adapter.
This RasPi4 worked fine in the past, I started with eBlocker 2.8 somewhere in 2022. Then, I guess a year ago, this error occured 2 or 3 times but has always been solved by power-on-reset of the PI4.
Next problem: I don't know how to run the "traceroute eblocker.org" test. And, if I will know, due to the Internet-Problem, it can't be done with the eBloker on the "defect PI4".
So I'm waiting for rmy new SD-Card and some help for the "traceroute eblocker.org" test, which, as named above, can only be done with the PI400.
By the way: I tried to use the AppImage with the PI400 using Bullseye - it didn't even start. Do I need a newer OS?
Thanks and kind regards
Thomas
@kalkleiste Of what I understand is that the NIC (Ethernet adapter) in your Pi is broken. I'd consider buying a new Raspi rather than trying to revive a broken device. Any work-around is time consuming with an unknown and probably not satisfying result. Sorry, but I fear I can not invest more time into this.
THX!