You don't - not easily, at least.
iptables allows you to configure rules by IP.
Blocking e.g. *.youtube.com/* [to say nothing of aliases thereof] is
hostname-based, not IP-based. And I would imagine, at a glance, that
Youtube has a lot of IPs.
Your easiest answer would be to do HTTP proxying
On Wed, Oct 3, 2012 at 4:03 PM, Konstantin Olchanski olcha...@triumf.ca wrote:
On Wed, Oct 03, 2012 at 07:00:00AM -0400, Tom H wrote:
On Mon, Oct 1, 2012 at 6:53 PM, Konstantin Olchanski olcha...@triumf.ca
wrote:
On Sat, Sep 29, 2012 at 04:28:22PM +0200, Gerhard Schneider wrote:
After
RAID0: LOL. If I suggested using RAID0, even on a simple dev box, I'd
either be asked to clear my desk on the spot or my name would rise
immediately to #1 on the headcount-reduction list...
That is supposed to be RAID1, I think Konstantin has a buggy keyboard
as well ;-)
Cheers
Sean
On 10/4/12 3:27 AM, vivek chalotra wrote:
And now i want to block youtube on my network.
It can be done with iptables however it's not for the faint of heart. I
did some reading about it on a dd-wrt website and it wasn't something I
found as an easy solution to a single problem such as this.
Have you looked into setting up a Squid proxy/filter? Much less of a
headache than doing it at the iptables level.
On 10/04/2012 08:26 AM, Michael Tiernan wrote:
On 10/4/12 3:27 AM, vivek chalotra wrote:
And now i want to block youtube on my network.
It can be done with iptables however it's
Content filtering would be the way to go.
For an interim solution, if you control your DNS servers, block it at the DNS
level.
From: owner-scientific-linux-us...@listserv.fnal.gov
[mailto:owner-scientific-linux-us...@listserv.fnal.gov] On Behalf Of Trenton Ray
Sent: Thursday, October 04, 2012
To start a little bash-fu:
dig youtube.com | egrep youtube.com | awk '{ print $5 }' | grep . | grep
-v '' yt.dig
From here it isn't hard to append your blocking rules.
If you need more help I'm sure myself or others on the list can further
script this and you can choose how often you'd want
On 10/04/2012 09:58 AM, Steven Miano wrote:
dig youtube.com http://youtube.com | egrep youtube.com http://youtube.com | awk '{
print $5 }' | grep . | grep -v '' yt.dig
You'd block google's DNS servers with that, which might not be a problem on the client,
but may I suggest a new and
I've run into problems trying to use desktop disks in a RAID array with a
MegaRAID 9260-8i. I built 2 previous systems with desktop disks and did not
have any problems but I've been unable to get this 3rd system to function
stably. Disks dropped from the array except the disks are fine which
Sorry for the low level questions but I have two point which I need to
better understand:
SO : SCIENTIFIC LINUX 5.5
a) yum
In /etc/cron yum.cron correspond to the orginal.yum.cron
so some autoupdates are enabled
in yum.excludes are defined the packages which are not updatet
in mine
a.) yes if you list kernel* in your excludes list it should not update any
package starting with kernel
b.) /var/log/maillog should have some information about any messages you
attempt to send. There could be, literally, 100s of reasons it didn't work.
On Thu, Oct 4, 2012 at 11:49 AM, O.D.
My understanding is that the main difference between desktop drives
and enterprise raid array drives in this regard is that the drive firmware
is configured to retry errors a lot longer on the desktop drives.
It is also my experience, although it was a few years ago on older
model WD drives, that
Greetings,
I have built many RAID systems using desktop disks and they are
generally quite stable. One of the issues with WD drives are with their
Green drives. By default, they park the heads after ~8 seconds of
inactivity. This will cause them to drop out of the array. The disk
firmware can be
I'm confused as to why it would block the Google DNS servers (which I
believe are 8.8.8.8 and 8.8.4.4 unless they have more? resolve to):
8.8.8.8.in-addr.arpa. 43194 IN PTR
google-public-dns-a.google.com.
My results to both of our suggestions seem to be identical. Very
interesting that
Disregard this. You can not stop youtube at Layer 3. Or you will lose
Google pretty much.
Sorry.
On Thu, Oct 4, 2012 at 1:12 PM, Steven Miano mian...@gmail.com wrote:
I'm confused as to why it would block the Google DNS servers (which I
believe are 8.8.8.8 and 8.8.4.4 unless they have more?
On Thu, Oct 4, 2012 at 8:01 AM, Sean Murray mur...@tlabs.ac.za wrote:
RAID0: LOL. If I suggested using RAID0, even on a simple dev box, I'd
either be asked to clear my desk on the spot or my name would rise
immediately to #1 on the headcount-reduction list...
That is supposed to be RAID1, I
I found that especially bad via USB adapters for the WD Green disks. For a 6
disk array. For 2 Disk via eSATA, works OK so far, but I really would stay away
from the green disks for RAID.
--
James Pulver
LEPP Computer Group
Cornell University
-Original Message-
From:
Similar findings here, where the first batch of drives in our hadoop
clusters were WD greens. smartctl shows huge Load_Cycle_Count numbers
for those drives which have been in service for a while (and they do
indeed keep us busy with RMAs). Eventually we found this utility which
can disable the
On Thu, Oct 04, 2012 at 12:57:00PM +0530, vivek chalotra wrote:
And now i want to block youtube on my network. kindly suggest iptable rules
to do that.
block youtube on my network is not a very well defined wish.
If you want to merely block the well known youtube IP and DNS addresses,
you
Maybe you should take a look at ClearOS[1].
It is a RHEL based distribution from a company that, now, develops
layer7-filter. In a simple way I was able to block all FLV videos (even if the
users are still able to reach youtube.com, they can not see any videos).
[1] -
On Thu, Oct 04, 2012 at 01:22:21PM -0400, Tom H wrote:
On Thu, Oct 4, 2012 at 8:01 AM, Sean Murray mur...@tlabs.ac.za wrote:
RAID0: LOL. If I suggested using RAID0, even on a simple dev box, I'd
either be asked to clear my desk on the spot or my name would rise
immediately to #1 on the
21 matches
Mail list logo
