All:
I am having a routing issue on a server with 2 interfaces that are
SUPPOSEDLY on 2 different networks:
one being the DMZ
the other being the internal network
So the internal interface (eth0) is also the interface with the
default route(eth0). Now, the other gateways are configured within
the /etc/sysconfig/network/ifcfg-eth-*, respectively.
On my DMZ interface (eth1), I cannot route back through my firewall to
get HTTPS traffic returned to the requestor (as indicated below)
until I change the default route to the DMZ interface (eth1).
Apparently the interface does not know how to route back through the
the eth1 interface to return the HTTPS traffic. But when I am in
traversing the network internally via SSH or HTTP everything
seemingly routes fine with both eth0 and/or eth1 - in other words I do
not have return traffic problems.
The problem above is resolved once I make the DMZ interface (eth1) the
default route, but that causes other problems that I
am not prepared, or more embarrassed to discuss.
How can my be resolved without making the DMZ interface my default
route?
freshcrap:/etc/sysconfig/network # tcpdump -i eth1:0 -vvv "(port 443
and ip host 74.198.149.2) or (dst 74.198.149.2)"
tcpdump: listening on eth1:0, link-type EN10MB (Ethernet), capture
size 96 bytes
15:18:46.102340 IP (tos 0x0, ttl 50, id 2354, offset 0, flags [DF],
proto: TCP (6), length: 60) 2.sub-74-198-149.myvzw.com.19512 >
ripem.poop.org.https: S, cksum 0x905f (correct),
3124559779:3124559779(0) win 5800