# Weird problem how should I proceed?

**URL:** <https://community.ipfire.org/t/weird-problem-how-should-i-proceed/10792>\
**Category:** Community\
**Created:** [31 December 2023 02:08 UTC](https://community.ipfire.org/t/weird-problem-how-should-i-proceed/10792 "2023-12-31T02:08:02Z")\
**Posts on this page:** 1\
**Showing post:** 4

<div class="post-metadata">

**Author:** ![ummeegge](https://community.ipfire.org/user_avatar/community.ipfire.org/ummeegge/32/16602_2.png) [@ummeegge](https://community.ipfire.org/u/ummeegge)\
**Post date:** [2 January 2024 09:06 UTC](https://community.ipfire.org/t/weird-problem-how-should-i-proceed/10792/4 "2024-01-02T09:06:20Z")

</div>

Hello @mumpitz ,  
OK, let´s try to solve them step by step.

> [@mumpitz](#):
>
> ```bash
> > #!/bin/sh
> > # Used for private firewall rules
> > IPSETCOMPANY="/sbin/iptables"
> > 
> > # See how we were called.
> > case "$1" in
> > start)
> > # --> Automatic generated IPSET COMPANY FW entries in start section BEGIN
> > ${IPSETCOMPANY} -I CUSTOMFORWARD -m set --match-set companies dst -j REJECT
> > ${IPSETCOMPANY} -I CUSTOMINPUT -m set --match-set companies dst -j REJECT
> > ${IPSETCOMPANY} -I CUSTOMOUTPUT -m set --match-set companies dst -j REJECT
> > # --> Automatic generated IPSET COMPANY FW entries in start section END
> > ## add your 'start' rules here
> > ;;
> > stop)
> > # --> Automatic generated IPSET COMPANY FW entries in stop section BEGIN
> > ${IPSETCOMPANY} -F CUSTOMFORWARD
> > ${IPSETCOMPANY} -F CUSTOMINPUT
> > ${IPSETCOMPANY} -F CUSTOMOUTPUT
> > # --> Automatic generated IPSET COMPANY FW entries in stop section END
> > ## add your 'stop' rules here
> > ;;
> > reload)
> > $0 stop
> > $0 start
> > ## add your 'reload' rules here
> > ;;
> > *)
> > echo "Usage: $0 {start|stop|reload}"
> > ;;
> > esac
> 
> ```

this entries are from my script from this topic → [Blocking Reverse Proxys from cloudflare - #17 by ummeegge](https://community.ipfire.org/t/blocking-reverse-proxys-from-cloudflare/10040/17) . There was a bug in it that´s why i loaded a fixed version at that time up and left a note → [Blocking Reverse Proxys from cloudflare - #43 by ummeegge](https://community.ipfire.org/t/blocking-reverse-proxys-from-cloudflare/10040/43) which fixed the

```bash
Try `iptables -h’ or ‘iptables --help’ for more information.
iptables v1.8.9 (legacy): Set companies doesn’t exist.

```

problem. It seems that you used the old version and/or never deleted those entries which should be done via the CLI helper →

 ![Bildschirmfoto vom 2024-01-02 09-47-16](https://community.ipfire.org/uploads/default/original/2X/8/87c1d2111986c2bf9852f642710425814e64be26.png)  
just use ‘d’ and [ENTER] .

> [@mumpitz](#):
>
> I see in my research you already know the script … [ASN\_Script](https://notabug.org/maloe/ASN_IPFire_Script/src/master/asn_ipfire.sh)  
> this is the error message on boot and after execute the script →

This ASN script from maloe and Mike Kuketz differs to my script so the firewall.local entries are related to my script and have nothing to do with their script since they use firewall groups for this.  
My concern at that time was that to many entries in the IPTable chains (vast lists) can bring the system down that´s why i used IPSet for this but also only firewall.local which have a better overview and not too much work to delete it manually.

> [@mumpitz](#):
>
> Hi 😃  
> Yes I wish you too a happy new year.
> 
> I see in my research you already know the script … [ASN\_Script](https://notabug.org/maloe/ASN_IPFire_Script/src/master/asn_ipfire.sh)  
> This is the file mention at boot /etc/rc.d/rc3.d/S98rc.local–\>
> 
> ```bash
> > #!/bin/sh
> > ###############################################################################
> > # #
> > # IPFire.org - A linux based firewall #
> > # Copyright (C) 2007 Michael Tremer & Christian Schmidt #
> > # #
> > # This program is free software: you can redistribute it and/or modify #
> > # it under the terms of the GNU General Public License as published by #
> > # the Free Software Foundation, either version 3 of the License, or #
> > # (at your option) any later version. #
> > # #
> > # This program is distributed in the hope that it will be useful, #
> > # but WITHOUT ANY WARRANTY; without even the implied warranty of #
> > # MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the #
> > # GNU General Public License for more details. #
> > # #
> > # You should have received a copy of the GNU General Public License #
> > # along with this program. If not, see <http://www.gnu.org/licenses/>. #
> > # #
> > ###############################################################################
> > # Used for private calls after boot #
> > ###############################################################################
> > ipset restore < /etc/ipset/ipset.conf && /etc/sysconfig/firewall.local reload;
> 
> ```

this entry is a restore command for IPSet sets and i use it also in my script but not in this location but in ‘/etc/sysconfig/rc.local’ so i don´t know where it comes from.  
Also, i currently can not say much to this ASN\_IPFire script (haven´t used it) and i would also use it for the first only in a VM to test or debug it.

According to the Tor problem, i would fix for the first the company\_blocker (delete both of them) and check your system if it runs again.

According to the kernel message, this jumps in my eyes

> [@mumpitz](#):
>
> > |02:13:24|kernel: |BUG: kernel NULL pointer dereference, address: 0000000000000090|

. I would try to split the problems in different parts and use the problem substitution step by step to see how the system reacts.

Hopefully some light comes into this.

Best,

Erik

P.S.: Am on the road without net the next days so some days needed to answer again if needed, or may some others jump in…

---

_[View the full topic](https://community.ipfire.org/t/weird-problem-how-should-i-proceed/10792)._