At 10:42 AM 12/5/2002 -0800, Charles Gray wrote:
We have the T1 and the DSL connected to the firewall. The T1 works just fine, but the DSL does NOT work.this really isn't the firewall's job. here's what i'd do: point the gnatbox at the t1 router. have the router (depends on the
The firewall is using the T1 addresses for the DNS and the default route. From behind the firewall I can see the DSL external addresses. (Aliases on the external interface)
Remotely, I can only see the lan side of the DSL router. I cannot ping or traceroute to any of the Aliases servers.
Yep I bet you want to know how the DSL, and T1 routers are connected to the firewall. We are using a common hub between the DSL router, the T1 router and the gb-100 firewall.
I liked Dan's idea to use the gateway feature, but it would be nice if the DSL could be accessed or available all of the time. Any ideas? Is there a way to setup a second default route for the aliased network?
make&model, i know ciscos well but can't comment on others) selectively either route outbound packets out the T1 or
redirect them to the DSL router. this can be used in a number of ways:
1. the t1 router uses the dsl router as a failover.
2. the t1 router uses the dsl router to reach certain sites/IP ranges.
3. the t1 router does some kind of outbound load-balancing so that outbound traffic either
takes the t1 or the DSL depending on whatever the t1 router is programmed to do.
it would be cleaner if the t1 router had a second enet interface for the dsl router, but that isn't
a show-stopper...
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
To subscribe to the digest version first unsubscribe, then
e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Archive of the last 1000 messages:
http://www.mail-archive.com/[email protected]
