I assume this is because of the default blocklists loaded with the installation but have no idea how to select blocklists that will protect P2P without blocking internet access.
I hope this post isn't redundant. I've Ixquicked this fairly extensively and searched Ubuntu Forums but to no avail--any advice would be greatly appreciated.
Thanks in advance.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Look in /etc/pgl/blocklists.list
Comment out the iana* and bogon lines.
Then "sudo pglcmd update" or "sudo pglcmd force-update"
-----Original Message-----
From: mlnease [mailto:mlnease@users.sf.net]
Sent: Wednesday, February 12, 2014 2:26 PM
To: [peerguardian:discussion]
Subject: [peerguardian:discussion] Configuring Peerguardian Linux version
2.2.4 for Xubuntu 12.04.4
I assume this is because of the default blocklists loaded with the
installation but have no idea how to select blocklists that will protect P2P
without blocking internet access.
I hope this post isn't redundant. I've Ixquicked this fairly extensively
and searched Ubuntu Forums but to no avail--any advice would be greatly
appreciated.
If it is a blocklist related problem, then of course just use other blocklists.
But let's first make sure whether it is a blocklist related problem or if the basic whitelisting fails:
I don't know how you connect to the internet. But I guess you have a router. Can you ping it?
Alternatively (and in case you don't understand what I'm talking about), you may post your /var/log/pgl/pglcmd.log. I'm interested in lines like these:
..Allowing loopback traffic: INPUT OUTPUT...Allowing OUTPUT traffic to DNS server 192.168.178.1...Allowing FORWARD traffic to DNS server 192.168.178.1...Allowing LAN traffic .......INPUT from 192.168.178.0/24.....OUTPUT to 192.168.178.0/24.....FORWARD from 192.168.178.0/24 to 192.168.178.0/24...LAN traffic allowed.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Are you using Xubuntu as a Server or cuz of need for old Xorg since it's as old as 12.04.04 ?
However, my Ubuntu Server is same version, with same PGL version and no desktop. Never had Internet issues on that computer with PGL, but PGL doesn't auto-update the lists, sometimes causing them to block someone who doesn't need to be blocked.
What comes to figuring out the lists, that's not hard: every blocklist link the program carries with it by default, are served by iBlocklist.com, so you just go there and check every list you got a link for and read the description.
You don't need many lists unless there's a special reason for each of them, and the more lists the higher the chance something innocent gets blocked.
WARNING: 2013-09-24 iBlocklist.com along with PeerBlock, a fork of PeerGuardian, moved to a new line: unless you pay, you can update only once a week. http://www.peerblock.com/news/139.html. Cuz of that, after years, PB has been updated to work correctly with this change. PG has been dead for long, so PB was born, and PG doesn't even work on 64-bit VI$TA+, so ...
Last edit: Jouni Järvinen 2014-02-12
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I dunno what your knowledge nor experience is with blocklists like these, but I need to warn that using blocklists which block unused addresses is very bad idea for 2 reasons: the address space ain't updated in realtime; you can't update fast enough.
Blocklists against hijacked machines is similar issue of a list. Although nice, it's always too slowly updated to be useful.
Now that I checked on the list PGL had, http://list.iblocklist.com/lists/dchubad/hacker seems like good idea, "In the p2p community we have encountered many hackers or people who wish to harm the information on your computer/network, This list contains IP/IP Ranges which we found to belong to known hackers or people who have been found to be sharing hacking tools, viruses or trojans."
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hello,
I've just installed Peerguardian Linux version 2.2.4 (from the PPA). The installation went perfectly--but when 'on', PGL blocks all internet access (as per the warning at http://handytutorial.com/install-peerguardian-in-ubuntu-using-ppa/).
I assume this is because of the default blocklists loaded with the installation but have no idea how to select blocklists that will protect P2P without blocking internet access.
I hope this post isn't redundant. I've Ixquicked this fairly extensively and searched Ubuntu Forums but to no avail--any advice would be greatly appreciated.
Thanks in advance.
Look in /etc/pgl/blocklists.list
Comment out the iana* and bogon lines.
Then "sudo pglcmd update" or "sudo pglcmd force-update"
-----Original Message-----
From: mlnease [mailto:mlnease@users.sf.net]
Sent: Wednesday, February 12, 2014 2:26 PM
To: [peerguardian:discussion]
Subject: [peerguardian:discussion] Configuring Peerguardian Linux version
2.2.4 for Xubuntu 12.04.4
Hello,
I've just installed Peerguardian Linux version 2.2.4 (from the PPA). The
installation went perfectly--but when 'on', PGL blocks all internet access
(as per the warning at
http://handytutorial.com/install-peerguardian-in-ubuntu-using-ppa/).
I assume this is because of the default blocklists loaded with the
installation but have no idea how to select blocklists that will protect P2P
without blocking internet access.
I hope this post isn't redundant. I've Ixquicked this fairly extensively
and searched Ubuntu Forums but to no avail--any advice would be greatly
appreciated.
Thanks in advance.
Configuring Peerguardian Linux version 2.2.4 for Xubuntu
12.04.4
Sent from sourceforge.net because you indicated interest in
https://sourceforge.net/p/peerguardian/discussion/446997/
To unsubscribe from further messages, please visit
https://sourceforge.net/auth/subscriptions/
Yeah, if normal update doesn't resolve in half an hour, try force.
If it is a blocklist related problem, then of course just use other blocklists.
But let's first make sure whether it is a blocklist related problem or if the basic whitelisting fails:
I don't know how you connect to the internet. But I guess you have a router. Can you ping it?
Alternatively (and in case you don't understand what I'm talking about), you may post your /var/log/pgl/pglcmd.log. I'm interested in lines like these:
Are you using Xubuntu as a Server or cuz of need for old Xorg since it's as old as 12.04.04 ?
However, my Ubuntu Server is same version, with same PGL version and no desktop. Never had Internet issues on that computer with PGL, but PGL doesn't auto-update the lists, sometimes causing them to block someone who doesn't need to be blocked.
What comes to figuring out the lists, that's not hard: every blocklist link the program carries with it by default, are served by iBlocklist.com, so you just go there and check every list you got a link for and read the description.
You don't need many lists unless there's a special reason for each of them, and the more lists the higher the chance something innocent gets blocked.
WARNING: 2013-09-24 iBlocklist.com along with PeerBlock, a fork of PeerGuardian, moved to a new line: unless you pay, you can update only once a week. http://www.peerblock.com/news/139.html. Cuz of that, after years, PB has been updated to work correctly with this change. PG has been dead for long, so PB was born, and PG doesn't even work on 64-bit VI$TA+, so ...
Last edit: Jouni Järvinen 2014-02-12
I think I must help more ... The lists I use there:
- http://list.iblocklist.com/lists/bluetack/dshield <- hackers and such
- http://list.iblocklist.com/lists/bluetack/proxy
- http://list.iblocklist.com/lists/bluetack/spyware
- http://list.iblocklist.com/lists/bluetack/web-exploit
- http://list.iblocklist.com/lists/spamhaus/drop <- Spamhaus Don't Route Or Peer, directly owned by malicious persons
I dunno what your knowledge nor experience is with blocklists like these, but I need to warn that using blocklists which block unused addresses is very bad idea for 2 reasons: the address space ain't updated in realtime; you can't update fast enough.
Blocklists against hijacked machines is similar issue of a list. Although nice, it's always too slowly updated to be useful.
Now that I checked on the list PGL had, http://list.iblocklist.com/lists/dchubad/hacker seems like good idea, "In the p2p community we have encountered many hackers or people who wish to harm the information on your computer/network, This list contains IP/IP Ranges which we found to belong to known hackers or people who have been found to be sharing hacking tools, viruses or trojans."