Peerguardian official site1/7/2024 Update: Looks like they decrypted the ramdisks now. Now to wait for the inevitable breakage from Apple’s next update. Apparently it was the only software unlock that didn’t brick the iPhone with the 1.1.1 update. Unlocks are still coming, though there have been reports that the IPSF stuff still works. If you’re going to try this, remember that this doesn’t get you the carrier unlock, just 3rd party apps. A list of common applications and their compatibility can be found on this iPhone Dev Wiki page. Summerboard doesn’t work, and neither does Sketch or Customize(apparently Customize does work, thanks Brian), but for the most part, everything runs just fine. But now I have my eBook reader and IM client running again. It’s still a very manual process, but way easier than the downgrade to 1.0.2 then update to 1.1.1 nonsense. I used Niacin’s TIFF exploit to get write access to the filesystem, and then followed the directions from the iPhone Dev Team ( detailed here) to get SSH and AppTapp installed. If it works then MoBlock will go on a diet to use as less ram as possible and cpu too, for example not storing range names.Last night I finally got 3rd party apps running on the phone again after the disastrous 1.1.1 update. Kill it ( kill -TERM moblock-pid) and report here. Generate some traffic that should be blocked and then with another shell into the router have a look at the logfile, it should say that it has blocked something. Then start moblock (supposing binary and blocklist are in the same directory): Since i don't know what are the default rules on openwrt and since you are good in iptables so you know that it is important the ORDER of iptables rules, you will find the right place to put QUEUE rules for the traffic you want to be filtered. Iptables -I FORWARD -p tcp -dport 80 -m state -state NEW -j QUEUE For example if you want to filter all traffic forwarded by the ap on destination port 80 tcp, you will use: Now the difficult part, where your iptables knowledge comes handy: moblock filter traffic that is QUEUEd to it through iptables, so you must use an iptables rule to "send" traffic to moblock. How to test it: create a block list file like guarding.p2p BUT with only few (10) lines, DON'T USE A FULL guarding.p2p FILE! It will use about 16MB of ram and i don't know what happens when the router is low on memory! Upload the small block list file and the binary to the router where you can execute it. You can find the compiled binary here: or compile it yourself, there is nothing to change from the x86 version, just set up a proper cross compile environment. If you want to help you will need a firmware that has the ip_queue kernel module (i don't know if it is already included in the official release) and a good knowledge of iptables. This changed a couple of days ago when beta version r677 of PeerBlock 1.1 was released to the official site. I'm trying to make it run on openwrt but since i don't have an openwrt ap i need someone to test it. It is based on PeerGuardian code, and considered to be the official successor of the application for the Windows platform. I want to underline that it is NOT a simple script to load thousands of rules with iptables but a standalone program that uses a standard kernel interface and an iptables library to do his work. Hi, i'm the developer of MoBlock, a peerguardian-like program.
0 Comments
Leave a Reply.AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |