Skynet Skynet v8 - Router Firewall & Security Enhancements

[Ripshod]

8.0.2 running smooth with Viktor Jaep's list. Also good with somewhereovertherainbow's list.
Thank you!

 

[John Fitzgerald]

@Adamm

Still failing reboots.

Nov 16 06:05:14 Skynet: [i] Startup Initiated... ( skynetloc=/tmp/mnt/EXT4J/skynet )
Nov 16 06:05:14 Skynet: [✘] Configuration File Not Detected - Please Use ( sh /jffs/scripts/firewall install ) To Continue

 

[Adamm]

@Adamm

Still failing reboots.
View attachment 68963

Nov 16 06:05:14 Skynet: [i] Startup Initiated... ( skynetloc=/tmp/mnt/EXT4J/skynet )
Nov 16 06:05:14 Skynet: [✘] Configuration File Not Detected - Please Use ( sh /jffs/scripts/firewall install ) To Continue

What happens when you run the command it asks?

 

[John Fitzgerald]

What happens when you run the command it asks?

I had Skynet uninstalled since yesterday, woke up early and saw you pushed 8.0.2, so I reloaded via AMTM and the above result is what happened.
I've now followed your steps with the wan cable unplugged and rebooted and the result is the same. This is after your instruction to reboot and another reboot.
Diversion Large Block List and Skynet Stock, (no country bans)

Thank you.

 

[John Fitzgerald]

I now followed the router log instruction and it walks you through the load procedure where for the swap, log stats, ect. choosing #1 at each step.
It starts to work, then I reboot and it stops with the "failed" as shown in my picture in Post#42.
This is not surviving a reboot.

Thanks.

 

[Adamm]

I now followed the router log instruction and it walks you through the load procedure where for the swap, log stats, ect. choosing #1 at each step.
It starts to work, then I reboot and it stops with the "failed" as shown in my picture in Post#42.
This is not surviving a reboot.

Thanks.

Post output of;

firewall debug info extended

 

[John Fitzgerald]

Post output of;

I just uninstalled via option #15 and rebooted.

I will reload and post output, right now it returns "not found"

 

[John Fitzgerald]

After fresh reload, without reboot:

 

[John Fitzgerald]

After reboot:

 

[Mogsy]

I had problems connecting Adguard iOS app's pseudo VPN. Updated Skynet and reset blocklist to default. No problem connecting now. Plenty of blocked local IP addresses in Skynet's stats.

Adguard VPN setting:
Server 127.0.0.1
Server Address 127.1.1.1
Address 172.16.209.5

Edit:

Rebooted router and got this error, but option 8 Restart Skynet fixed that

Router Model; RT-AX86U
Skynet Version; v8.0.2 (16/11/2025) (b2cba12296a1d426e1181cf214c44b2e)
iptables v1.4.15 - (eth0 @ 192.168.50.1)
ipset v7.6, protocol version: 7
IP Address; (xxx.xxx.xxx.xxx)
FW Version; 388.10_2 (Oct 31 2025) (4.1.52)
Install Dir; /tmp/mnt/ax86u/skynet (101.1G / 112.3G Space Available)
SWAP File; /tmp/mnt/ax86u/myswap.swp (5.0G)

Cron Jobs                           | [Failed]
IPSets                              | [Failed]
IPTables Rules                      | [Failed]

Select Menu Option
[1]  --> Unban
[2]  --> Ban
[3]  --> Malware Blacklist
[4]  --> Whitelist
[5]  --> Import IP List
[6]  --> Deport IP List
[7]  --> Save
[8]  --> Restart Skynet
[9]  --> Temporarily Disable Skynet
[10] --> Update Skynet
[11] --> Settings
[12] --> Debug Options
[13] --> Stats
[14] --> Install Skynet
[15] --> Uninstall

[e]  --> Exit

 

[Mutzli]

After updating to Skynet 8.02, I encountered the following error:

IPTables Rules | [Failed]

A few minutes later, this followed:

IPSets | [Failed]

After some troubleshooting, I traced the issue to my long country blocking list:

 Banned Countries; cn ru sc ua ee ls gr ba bg hr cz ge hu kg lv lt mc kp ro sk vn uz lk br ar cl co pa py uy iq ir jm

It seems the update may have introduced a change in how large IP sets are handled.
Solution:

1. I manually removed the country block list.
2. Reloaded Skynet.
3. Then, I re-added the countries gradually, starting with just a few to confirm stability.
4. Once confirmed, I reloaded the full list.

Since then, everything has been stable and working as expected.

 

[John Fitzgerald]

After updating to Skynet 8.02, I encountered the following error:

IPTables Rules | [Failed]

A few minutes later, this followed:

IPSets | [Failed]

After some troubleshooting, I traced the issue to my long country blocking list:

 Banned Countries; cn ru sc ua ee ls gr ba bg hr cz ge hu kg lv lt mc kp ro sk vn uz lk br ar cl co pa py uy iq ir jm

It seems the update may have introduced a change in how large IP sets are handled.
Solution:

1. I manually removed the country block list.
2. Reloaded Skynet.
3. Then, I re-added the countries gradually, starting with just a few to confirm stability.
4. Once confirmed, I reloaded the full list.

Since then, everything has been stable and working as expected.

Now try rebooting the router and see if it sticks!

 

[Viktor Jaep]

After updating to Skynet 8.02, I encountered the following error:

IPTables Rules | [Failed]

A few minutes later, this followed:

IPSets | [Failed]

After some troubleshooting, I traced the issue to my long country blocking list:

 Banned Countries; cn ru sc ua ee ls gr ba bg hr cz ge hu kg lv lt mc kp ro sk vn uz lk br ar cl co pa py uy iq ir jm

It seems the update may have introduced a change in how large IP sets are handled.
Solution:

1. I manually removed the country block list.
2. Reloaded Skynet.
3. Then, I re-added the countries gradually, starting with just a few to confirm stability.
4. Once confirmed, I reloaded the full list.

Since then, everything has been stable and working as expected.

@Adamm this brings up a great point I keep forgetting to mention... my country list is so long, it goes off the screen and reverts to saying "multiple countries" in the main UI. I'm not even quite sure where it now stores this list of country codes, as it's no longer visible in the cfg either. It would be great if the actual list of country blocks could be displayed for transparency sake and being able to see what countries I'm actually blocking should I need to make a change. Could you please consider this as a change request?

 

[Mutzli]

One more issue came up, when adding an IOT block to one of my devices I get the following error message:

ipset v7.6: Error in line 1: Syntax error: cannot parse comment: resolving to IPv4 address failed
[i] IOT Blocking List Cleared
[i] Saving Changes

After that the IOT Blocking is set to [Disable] and all of my previous blocked devices i had configured under Skynet 7.6.5 have been cleared.

 

[Mutzli]

Now try rebooting the router and see if it sticks!

Rebooting worked without any issues.

 

[John Fitzgerald]

Rebooting worked without any issues.

Adamm has a GT- BE98. I'm assuming he's on 3006 code base.
So I'm wondering if this is 3004 code base related?