Re: HOWTO: Graphical IP Blocker
hi if your using ubuntu download the .deb file. :) it's already ready to go and then double click on it - and in the upper right hit install - in other words it is pre-packaged... :)
but it will connect you to the internet to download the needed dependency files tho..
edit - yes deb is debian and ubuntu is debian based so just about anything .deb is installable to ubuntu.. ;)
pick the .deb file that corresponds to your computer
1386 for x86 computers - 32 bits
amd64 for 64 bit computers
and choose whether you have Gutsy or Feisty - gutsy is in development you prob have feisty..
edit2/3: i had to download iplist_0.15-0feisty1_i386.deb for my computer...
Re: HOWTO: Graphical IP Blocker
Quote:
Originally Posted by
nowshining
okay i got it working to startup on reboot :)
Great tutorial! It now starts on boot up and works good!!
One question, if I need to how do I start up the GUI?
I used "$ sudo ipblock stop" to stop the app and then started it up with $ sudo ipblock start -g". It runs, but not in GUI mode. Any ideas?
Thanks from a nOOb who's learning!
Re: HOWTO: Graphical IP Blocker
Quote:
Originally Posted by
onestep
One question, if I need to how do I start up the GUI?
I used "$ sudo ipblock stop" to stop the app and then started it up with $ sudo ipblock start -g". It runs, but not in GUI mode. Any ideas?
This stops the already running session and starts the GUI.
Those "start" or "stop" parameters are just shortcuts and only useful if ipblock is used as an init-script.
At the moment only the GUI has an auto-update functionality. But it's possible to force an update "$ sudo ipblock -u" if ipblock is used only via command-line.
Re: HOWTO: Graphical IP Blocker
Quote:
Originally Posted by
uljanow
This stops the already running session and starts the GUI.
When I do that, it stops the running session but does not display the GUI. This is what the terminal shows;
Code:
~$ sudo ipblock -dg
Stopping ipblock...done.
Xlib: connection to ":0.0" refused by server
Xlib: No protocol specified
Exception in thread "main" java.lang.InternalError: Can't connect to X11 window server using ':0.0' as the value of the DISPLAY variable.
at sun.awt.X11GraphicsEnvironment.initDisplay(Native Method)
at sun.awt.X11GraphicsEnvironment.access$100(X11GraphicsEnvironment.java:52)
at sun.awt.X11GraphicsEnvironment$1.run(X11GraphicsEnvironment.java:155)
at java.security.AccessController.doPrivileged(Native Method)
at sun.awt.X11GraphicsEnvironment.<clinit>(X11GraphicsEnvironment.java:131)
at java.lang.Class.forName0(Native Method)
at java.lang.Class.forName(Class.java:169)
at java.awt.GraphicsEnvironment.getLocalGraphicsEnvironment(GraphicsEnvironment.java:68)
at sun.awt.X11.XToolkit.<clinit>(XToolkit.java:91)
at java.lang.Class.forName0(Native Method)
at java.lang.Class.forName(Class.java:169)
at java.awt.Toolkit$2.run(Toolkit.java:836)
at java.security.AccessController.doPrivileged(Native Method)
at java.awt.Toolkit.getDefaultToolkit(Toolkit.java:828)
at java.awt.Toolkit.getEventQueue(Toolkit.java:1678)
at java.awt.EventQueue.invokeLater(EventQueue.java:954)
at org.ipblock.gui.ipblockUI.main(Unknown Source)
Re: HOWTO: Graphical IP Blocker
Sometimes security settings prohibit to connect to another user's X-screen.
I suggest to stop it (sudo ipblock -d) and start it through Applications -> Internet -> ipblock as usual.
Re: HOWTO: Graphical IP Blocker
Quote:
Originally Posted by
uljanow
I suggest to stop it (sudo ipblock -d) and start it through Applications -> Internet -> ipblock as usual.
I can stop ipblock as instructed, but starting it through Applications -> Internet -> ipblock does not work. It has not worked since I followed the instructions on post #28 to make ipblock run in the background, and automatically start up at boot.
The only reason I want to have GUI access is to do a manual update of the filters.
I've added the command "sudo ipblock -u" to Gnome Schedule 1.0.0 If I set it up correctly it will update every 2 days. Any idea how can I check if the update actually takes place?
Re: HOWTO: Graphical IP Blocker
Quote:
Originally Posted by
onestep
I can stop ipblock as instructed, but starting it through Applications -> Internet -> ipblock does not work. It has not worked since I followed the instructions on post #28 to make ipblock run in the background, and automatically start up at boot.
The only reason I want to have GUI access is to do a manual update of the filters.
I've added the command "sudo ipblock -u" to Gnome Schedule 1.0.0 If I set it up correctly it will update every 2 days. Any idea how can I check if the update actually takes place?
I've tried the instructions from post #28 and I get the same behavior / error you've posted. To fix this I would undo the changes (the sudoers entry and the gnome session manager entry).
To start ipblock at boot just add this line to /etc/rc.local (as root)
Code:
/usr/sbin/ipblock -s
The line should be before "exit 0".
Now you should be able to stop ipblock and start the GUI in both ways.
I think updating with Gnome Scheduler might not work. But adding this line to /etc/crontab (as root) will do it
Quote:
30 18 * * * root /usr/sbin/ipblock -u
Lists are updated daily (18:30).
The GUI shows the last update time regardless of how the update took place. Alternatively check the last modified time:
Code:
ls -l /var/cache/iplist/.update-stamp
Re: HOWTO: Graphical IP Blocker
Thank you!
ipblock now loads at boot to run in the background and I'm able to run it's GUI when I want to!
This is why the Ubuntu Linux community is so GREAT!
Re: HOWTO: Graphical IP Blocker
by the way to do an update of the filters open up a terminal and do the following
sudo ipblock -u
or
sudo ipblock update
:)
edit:
to also see the logs
do the following
sudo ipblock status
Re: HOWTO: Graphical IP Blocker
Bluetack.co.uk has been down for several days now, I have been wondering whats going on. Then I realized my ISP is blocking my connection to them. I can access the site fine and manually download the files using tor. Would it be too much trouble to be able to have IPBlock use tor to update the lists?
I can manually update using a web browser and TOR