one for the linux router experts
carlyos at Buffalo.com
Wed Jun 13 16:10:30 EDT 2001
other thing I would try would be take out the 0.0.0.0 and put in the exact IP for that port out on that route. I honestly never set up a linux box as a router and only work on Cisco :(
---------- Original Message ----------------------------------
From: Darin Perusich <Darin.Perusich at cognigencorp.com>
Reply-To: nflug at nflug.org
Date: Wed, 13 Jun 2001 19:06:56 +0000
>i've setup a network and i'm running problems with the router i've setup
>with LRP, here's what i have.
>a logical representation of my companies network from internal, to DMZ,
>to our ISP. for routing i have 2 cisco routers, 1 lrp. on the internal
>network there's 1 dns server, 1 smtp server, and one client for checking
>email. on the DMZ network there's 1 dns server, 1 smtp gateway that
>routes all email to internal server, both these machine are in different
>network. on the ISP side i have a dns server, to test doing a zone
>transfer between the dmz dns server which is authoritative.
>from the internal network i'm able to ping out to the 184.108.40.206
>address, i think this is because 220.127.116.11 knows where that address
>is but not beyond that. from ns.isp.net i can't get past 18.104.22.168.
>this leads me to be believe that it has something to do with the routing
>table in the linux router. which is
>22.214.171.124 0.0.0.0 255.255.255.250 U eth0
>126.96.36.199 0.0.0.0 255.255.255.0 U eth1
>0.0.0.0 188.8.131.52 0.0.0.0 UG eth0
>i've tried adding other static network routes but that hasn'e helped.
>i'm pretty sure thr problem lies in the linux router, but this is the
>first time i've played with one like this.
>i've include a picture, ip's and names have been changed to protect the
>darinper at cognigencorp.com
More information about the nflug