[RndTbl] Routing questions

Dan Keizer ve4drk at gmail.com
Tue Jun 16 19:37:06 CDT 2009

yeah -- like Bill says -- you want to use a customized firmware to
perform that function.

Check out a few micro builds ... a couple I've used are below -- you
didn't say what hardware you have, but check the following:

dd-wrt:  http://www.dd-wrt.com/wiki/index.php/Supported_Devices
openwrt: http://oldwiki.openwrt.org/TableOfHardware.html

you would probably like dd-wrt -- it is very user friendly and
provides alot of functionality ... a small screenshot of one of my
dd-wrt router configs is attached -- (I don't have that service

openwrt has a large collection (and I mean large!) of downloadable
programs cross-compiled for the various supported platforms... both
have ssh and http control.


On Tue, Jun 16, 2009 at 7:00 PM, Bill Reid<billreid at shaw.ca> wrote:
> Hi Mike,
> What you want to do goes way beyond what most low end routers are
> designed to do. As you suggest the rules are applied to traffic coming
> into the WAN port and not local traffic. Your proposal also is not just
> IP routing but is also URL routing(i.e more like a proxy).
> The port 80 redirect is available in the mods to the Linksys router via
> firmware replacement(an exmaple is openwrt.org)
> -- Bill
> Mike Pfaiffer wrote:
>>       The set-up to the question is I picked up a decently modern wireless
>> router to play with. I allow no connection to the internet (nothing in
>> the WAN port). I have a couple of computers I can connect to the wired
>> ports of the router (assign static IPs within the subnet but outside the
>> DHCP range). These machines (both *NIX boxes) will provide services such
>> as a web server and a mud/game server. The router will allow open access
>> to anyone who wants to connect (I want to provide my own content for
>> experimentation). Since I have physical control of the hardware I'm not
>> too worried about security.
>>       Initially I'd like to be able to redirect all http traffic not bound
>> for my web server to my web server. For example someone trying to get to
>> Google will get my info page instead. But if someone were trying to
>> access a different page on the same machine would still be able to connect.
>>       I've done the RTFM thing and got confused. The manual seems to dance
>> around the issue but doesn't seem to say anything which looks to be
>> appropriate. The firewall is used mainly to filter incoming (from the
>> WAN port) traffic. IP filters control the outbound (to the WAN port)
>> filtering. The routing page talks about routing requests to a specific
>> IP outside the LAN side. Virtual servers route requests from the WAN
>> side to a specific LAN address. The port forwarding section looked more
>> like an extension to the firewall page.
>>       Here is what I'd like to do graphically.
>> Rule 1:
>> LAN requests non-192.168.X.Y web page --> Router says "You must mean
>> 192.168.X.Y" --> Router sends traffic to 192.168.X.Y/index.html
>> Rule 2:
>> LAN requests 192.168.X.Y/whatever.html --> Router passes along the
>> request to 192.168.X.Y web server
>>       The question is how can I do this? I know I've missed something, but
>> the manual didn't seem to help. I'll admit to not checking Google, but
>> I'm not sure what search terms to use.
>>       This ties in with the wireless questions I was asking a couple of
>> months ago. After I get this working I'll be looking at authentication
>> for other services and extending the range of coverage.
>>                               Later
>>                               Mike
>> _______________________________________________
>> Roundtable mailing list
>> Roundtable at muug.mb.ca
>> http://www.muug.mb.ca/mailman/listinfo/roundtable
> _______________________________________________
> Roundtable mailing list
> Roundtable at muug.mb.ca
> http://www.muug.mb.ca/mailman/listinfo/roundtable
-------------- next part --------------
A non-text attachment was scrubbed...
Name: SS-20090616192547.png
Type: image/png
Size: 36508 bytes
Desc: not available
Url : http://www.muug.mb.ca/pipermail/roundtable/attachments/20090617/a9a1fc8a/attachment.png 

More information about the Roundtable mailing list