Yes, I basically started from scratch once I renamed the USB drive.Did you re-format the drive?
sh /jffs/scripts/firewall debug swap uninstall
sed -i '\~swapon ~d' /jffs/scripts/post-mount
swapoff /tmp/mnt/USBDrive/myswap.swp
rm -rf /tmp/mnt/USBDrive/myswap.swp
swapoff /myswap.swp
rm -rf /myswap.swp
cat /proc/swaps
sh /jffs/scripts/firewall debug swap install
Have you tried disabling the disk check script if you are running it with amtm?Uninstalling and installing the swap file through Skynet fixes the issue again. But it's right back to the missing swap file error once I reboot the router.
Okay so I'm not going crazy, there are two swap files loaded (or the same one loaded twice?), so Skynet has been grabbing the wrong info. I'm not even sure how its mounting twice successfully but it explains all the issues unique to your system.
So this in theory should fix it (and really make sure its gone ).
Code:sh /jffs/scripts/firewall debug swap uninstall sed -i '\~swapon ~d' /jffs/scripts/post-mount swapoff /tmp/mnt/USBDrive/myswap.swp rm -rf /tmp/mnt/USBDrive/myswap.swp swapoff /myswap.swp rm -rf /myswap.swp
Then reboot to make sure any lingering swap file is unloaded.
Verify on boot that there is no swap file listed;
Code:cat /proc/swaps
Install a fresh swap file
Code:sh /jffs/scripts/firewall debug swap install
Excellent!! Another well supported problem fixed.I had to remove the partition on the USB drive, a simple format didn't delete the swap file either.
Now it's works again. I rebooted the router a couple of times and Skynet doesn't complain any more about the missing swap file.
Sorry for the commotion...
I had to remove the partition on the USB drive, a simple format didn't delete the swap file either.
Now it's works again. I rebooted the router a couple of times and Skynet doesn't complain any more about the missing swap file.
Sorry for the commotion...
Hi Adamm,
I have only been using Skynet for a couple of weeks, and I'm grateful that it has been keeping a ton of traffic looking for open ports on our server off of our network. Last night I flashed my Asus RT-AC88U with Merlin's 384.8 Beta 2, and reinstalled Skynet. Of course, the install complained that there was no ext formatted usb partition. It took me a goodly while (longer than I care to admit) to figure out that this version of Skynet really is looking for an ext* formatted partition on the USB port. While I found in the changelog where the other filesystems were disallowed, I could not find any reason why they were disallowed.
The main page of this thread describes Skynet as "All that's required is a USB drive that's at-least 500MB, After downloading it just works." Problem though is that no off the shelf USB drives come partitioned and formatted with an ext* filesystem.. If there is no reason why the new version of Skynet CAN'T work with an off-the-shelf, Windows formatted memory stick, other than maybe a performance hit, would it be possible to re-enable the other file system types and maybe just post a warning during installation that not having an ext* filesystem might result in a performance hit? (or whatever the detrimental effect would be) so that it could go back to being "After downloading it just works"?
I really appreciate the work you've put in. In the first couple of days it was running it blocked multiple thousands of connection attempts that would have gunked up our office network and our server. I can honestly say that now that I DON'T have this running, I'm a little uneasy about our network. Thanks, in advance, for your consideration.
Vinny
You're right, my approach to the situation was wrong. I've re-added support in a hotfix for fat (but will add warnings in a future update).
With that being said, I highly suggest formatting ext for both compatibility and performance reasons, but each to their own.
While it is kind of @Adamm to re-instate support of the FAT filesystem, ultimately anyone running Skynet will lilely want a USB drive formatted to one of the ext variants if they ever want to run the excellent companion programs like Diversion and amtm.Adamm, you ROCK.. THANK YOU! I prefer ext, although I kinda got bit in the behind because I didn't think I'd have to do more than flash the update and go. The thing is though, having to partition and format the stupid thing is far from just download and go. I'm hoping that sometime this weekend I'll have time to partition and format a USB stick, and compare CPU load and performance between ext and fat.
Even though it's well after midnight, I'm going to load the hotfix.. I'll sleep better knowing it's there.
V.
I prefer to minimize unnecessary syslog activity since it is copied to jffs so frequently.
I was going to point this out too. In that respect @Adamm does a disservice to the users as the majority use Skynet along with Diversion. I wish I had a foolproof script to format FAT or any other formatted device reliably and automated to ext* directly in the router and still have it compatible with amtm's disk checker.While it is kind of @Adamm to re-instate support of the FAT filesystem, ultimately anyone running Skynet will lilely want a USB drive formatted to one of the ext variants if they ever want to run the excellent companion programs like Diversion and amtm.
I'm not sure if this helps or just postpones the eventual need to move to one of the native linux/unix formats...
Gang, quick question. My router died; a new one has arrived. I'm not surprised that it's not plug-and-play in the replacement; do I need to re-format the drive? Can I just wipe it? Is there a way to back-up the "unbanned" domains before I do that? Thanks!
Welcome To SNBForums
SNBForums is a community for anyone who wants to learn about or discuss the latest in wireless routers, network storage and the ins and outs of building and maintaining a small network.
If you'd like to post a question, simply register and have at it!
While you're at it, please check out SmallNetBuilder for product reviews and our famous Router Charts, Ranker and plenty more!