This is a bit OT.
> OK one factor that I had not mentioned previously is this is my first
> time running Debian (yes I managed to do that since 1997...). Yesterday
> I found /etc/network/interfaces and understood what it does!
>
> My system is like the "About My Network" example except that I
have 2
> class Cs in the DMZ.
>
> >From what I understand I use the same IP on the NET and DMZ interfaces.
> I don''t want to use proxy-arp on 400 server IPs working from the
> example:
>
> # DMZ interface -- After the interface is up, add a route to the server.
> This allows the ''Yes'' setting
> # in the HAVEROUTE column of /etc/shorewall/proxyarp
above.>
> auto eth1
> iface eth1 inet static
> address 206.124.146.176
> netmask 255.255.255.255
> broadcast 0.0.0.0
> up ip route add 206.124.146.177 dev eth1
>
You need to use gateway here, that is where it is connected.
> # Internet interface -- After the interface is up, add a route to the
Westell 2200 DSL "Modem">
> auto eth2
> iface eth2 inet static
> address 206.124.146.176
> netmask 255.255.255.0
> gateway 206.124.146.254
> up ip route add 192.168.1.1 dev eth2
>
> I could use "up ip route add 206.124.146.0/24 dev eth1" on the
DMZ?
> And can the gateway and route be the same on the NET interface?
>
You should use that route statement, but with no gateway, for the dmz.
The kernel may use the wrong interface to contact the gateway.
Think that is what your running in too.
Jerry