Thanks for the advice, everyone. It seems the best option is for me to
simply go request a temporary chunk of addresses through a broker.
I managed to get on with AARNet (a single IP, not a /48, just for
testing) using some linux.sh script, which was much easier than setting
up 6to4, which I did
You may find one of the other free brokers can handle a moving IP4 at
your end. Check out sixxs.net.
--
Christopher Vance
--
SLUG - Sydney Linux User's Group Mailing List - http://slug.org.au/
Subscription info and FAQs: http://slug.org.au/faq/mailinglists.html
On Thu, Oct 09, 2008 at 06:49:06PM +1100, Jeremy Visser wrote:
Thanks for the advice, everyone. It seems the best option is for me to
simply go request a temporary chunk of addresses through a broker.
I managed to get on with AARNet (a single IP, not a /48, just for
testing) using some
iostat can be a bit special.I -think- under linux its the amount
of time spent waiting for pending disk IO to complete. Now,
some chipsets and their drivers seem to spend a lot of time in IOWAIT
compared to others. The traditional difference was polled vs dma'ed
disk IO - with polled IO, the
On Fri, Oct 10, 2008, Adrian Chadd wrote:
Now, you could go groveling through the kernel to try and figure out
whether IOWAIT includes nfs activity (which I believe would be
the disk IO related to NFS, but it could be other things I guess) and
first see if doing userspace disk IO does a lot
Hi everyone
I am running a fedora server and currently using hosts.allow to
only allow ssh accesses from specific ip addresses. I did this because I was
getting
a lot of idiots from eastern Europe and Russia tring to crack my server.
This has been ok but now is prooving to be too
BODY { font-family:Arial, Helvetica, sans-serif;font-size:12px; }Ken
and Dion
today I bought an Intel D945GCLF2 mini-itx mobo with a dual-core
Intel Atom processor for 10180 Yen (on sale).
Last night found reviews for Atom CPU mini boards
http://www.mini-itx.com/reviews/atoms/
and this
2008/10/9 Phill O'Flynn [EMAIL PROTECTED]:
Hi everyone
I am running a fedora server and currently using hosts.allow to
only allow ssh accesses from specific ip addresses. I did this because I was
getting
a lot of idiots from eastern Europe and Russia tring to crack my server.
This has
Phill O'Flynn wrote:
I am running a fedora server and currently using hosts.allow to
only allow ssh accesses from specific ip addresses. I did this because I was
getting
a lot of idiots from eastern Europe and Russia tring to crack my server.
This has been ok but now is prooving to be
On Fri, Oct 10, 2008 at 05:50:52AM +0800, Adrian Chadd wrote:
I've never seen IOWAIT for NFS client traffic (ie, traffic from an
NFS client talking to an NFS server) but who knows, this is linux..
I would say this doesn't count to iowait either; see
fs/nfs/pagelist.c:nfs_wait_on_request() -- it
you can configured your sshd's configuration in /etc/ssh/sshd_config
however in your case you might want to look at denyhosts
http://denyhosts.sourceforge.net/
Dean
Phill O'Flynn wrote:
Hi everyone
I am running a fedora server and currently using hosts.allow to
only allow ssh accesses
On Friday 10 October 2008 07:29:25 [EMAIL PROTECTED] wrote:
I am running a fedora server and currently using hosts.allow to
only allow ssh accesses from specific ip addresses. I did this because I
was getting a lot of idiots from eastern Europe and Russia tring to crack
my server.
This has
Erik de Castro Lopo [EMAIL PROTECTED] writes:
Phill O'Flynn wrote:
I am running a fedora server and currently using hosts.allow to
only allow ssh accesses from specific ip addresses. I did this because I was
getting
a lot of idiots from eastern Europe and Russia tring to crack my server.
On Fri, Oct 10, 2008, jam wrote:
On a non-standard port I've had ZERO login attempts over the last 3+ years,
compared (like you) to 10s and 100s per day. This is trivial to implement
even has the advantage of multiple servers/virtual servers behind a DSL
router (different non standard for
I guess the best approach would be to consider using Port Knock
http://www.portknocking.org/
Cheers,
Brian
On 10/9/08, Phill O'Flynn [EMAIL PROTECTED] wrote:
Hi everyone
I am running a fedora server and currently using hosts.allow to
only allow ssh accesses from specific ip addresses. I
Hi all,
I currenty have a device with the following permissions and ownership:
crw-rw 1 root dialout 4, 64 Oct 10 11:05 /dev/ttyS0
Where and how do I fiddle to changes this so it sticks across reboots?
TIA,
Erik
--
-
Erik
Hi all,
I currenty have a device with the following permissions and ownership:
crw-rw 1 root dialout 4, 64 Oct 10 11:05 /dev/ttyS0
Where and how do I fiddle to changes this so it sticks across reboots?
The short answer is udev (or at least that is the approach I have taken in
Erik de Castro Lopo wrote:
Where and how do I fiddle to changes this so it sticks across reboots?
Here we go:
http://www.debianhelp.org/node/5003#comment-36703
A file in /etc/udev/rules.d/ containing:
SUBSYSTEM==tty, KERNEL==ttyS0, OWNER=lp, GROUP=lp
Erik
--
On Wed, 8 Oct 2008 23:38:33 +1100
Jeremy Visser [EMAIL PROTECTED] wrote:
G'day SLUG,
Hi Jeremy,
I'd actually like to get my hands on a small chunk of address space
that I could play with and make my own. Unfortunately, according to
the APNIC website:
Enjoy playing with IPv6 but don't
Brian Sydney Jathanna [EMAIL PROTECTED] writes:
On 10/9/08, Phill O'Flynn [EMAIL PROTECTED] wrote:
Hi everyone
I am running a fedora server and currently using hosts.allow to
only allow ssh accesses from specific ip addresses. I did this because I
was getting
a lot of idiots from eastern
Jeremy == Jeremy Visser [EMAIL PROTECTED] writes:
Jeremy I'm guessing that ticking the Request a /48 prefix box will
Jeremy give me a few addresses that I can set up my server to route
Jeremy and advertise the scheme via radvd...correct?
Yup, except they're no longer handing out /48s ---
On 10/10/2008, at 10:58 AM, Daniel Pittman wrote:
Personally, I use fail2ban[1] which uses the cruder, but still
effective, technique of reading your logs and blocking people who
try to
guess passwords via iptables.
I use with great success an iptables rule to limit new ssh connections
On Fri, Oct 10, 2008 at 03:41:57PM +1100, Michael Chesterton wrote:
On 10/10/2008, at 10:58 AM, Daniel Pittman wrote:
Personally, I use fail2ban[1] which uses the cruder, but still
effective, technique of reading your logs and blocking people who try
to
guess passwords via iptables.
I
Hi
I was wondering if any one out there uses one of these to do hardware
raid.
I thought I might set it up in raid10 with 4 1Tb drives.
My questions on this is what software do I use to alert me if there any
problems and will it show up as 1 scsi device (or is it a silly software
raid solution
Well, Michael and Alex beat me to it.
That's what I was going to say; use iptables. Though Alex's rules are
somewhat more complex than mine, I think mine do the same.
After setting up the chain, my salient rule is just;
-A INBOUND_FILTER -i eth0 -p tcp -m tcp --dport 22 -m limit --limit
122.116.243.233 has been hitting me today, apparently from Taiwan. I blackholed
him by hand.
Jim Donovan
--
SLUG - Sydney Linux User's Group Mailing List - http://slug.org.au/
Subscription info and FAQs: http://slug.org.au/faq/mailinglists.html
26 matches
Mail list logo
