All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ed Wildgoose <lists@wildgooses.com>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] Slashdot on WRT54G
Date: Wed, 02 Jun 2004 18:14:11 +0000	[thread overview]
Message-ID: <40BE18F3.20007@wildgooses.com> (raw)
In-Reply-To: <40BD8F05.2050800@wildgooses.com>


>I do have one of the WRT54Gs and did contribute some scripts to James,
>the head developer of the sveasoft firmware. I do not have the most
>recent firmware since I had a few issues "subscribing" to the
>development process but I still am thinking about getting more involved.
>
>The web admin interface on the version of the firmware that I'm using
>offers very little in the way of customizing the tc rules. 
>

It sounds excellent.  The web interface is not interesting at all, ssh 
is the only way I intend to access it anyway.

Having l7 compiled in, but at least traffic control, sounds absolutely 
excellent.  If you can get it to run a vpn, then this is just superb

I assume you have a US model?  Can you tell me what sort of power supply 
it has?  I am thinking about getting one imported to the UK since they 
don't sell them here (and will probably be overpriced when they 
arrive).  Will a universal power adaptor work?  Also, any other issues 
with a uk ADSL line that might prevent this working...?

Thanks

Ed W
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/

  parent reply	other threads:[~2004-06-02 18:14 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-06-02  8:25 [LARTC] Slashdot on WRT54G Ed Wildgoose
2004-06-02 15:07 ` Patrick Nehls
2004-06-02 18:14 ` Ed Wildgoose [this message]
2004-06-02 19:51 ` Patrick Nehls
2004-06-03 17:45 ` james jones
2004-06-03 19:01 ` Ed Wildgoose

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=40BE18F3.20007@wildgooses.com \
    --to=lists@wildgooses.com \
    --cc=lartc@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.