randall wrote:
turns out that it is being blocked by my firewall.
i am running Debian Etch vservers with a private ip address like 192.168.1.* in a DMZ and ido the routing via shorewall 4.08
Except in very limited circumstances (Entry in /etc/shorewall/proxyarp with HAVEROUTE set to No or entries in /etc/shorewall/providers), Shorewall has nothing to do with routing.
Shorewall:fw2dmz:REJECT:IN= OUT=dummy0 SRC=192.168.1.88 DST=192.112.***.** and also Jun 4 18:54:38 host kernel: martian source 192.168.1.88 from 192.112.***.**, on dev eth0
Which means that there is a route to 192.112.***.*** out of an interface other than eth0.
Hint: When you claim to have a routing problem, the output of 'ip route ls' is pretty much manditory. Better yet, when reporting a problem, follow the guidelines at http://www.shorewall.net/support.htm#Guidelines.
-Tom -- Tom Eastep \ Nothing is foolproof to a sufficiently talented fool Shoreline, \ http://shorewall.net Washington USA \ [EMAIL PROTECTED] PGP Public Key \ https://lists.shorewall.net/teastep.pgp.key
signature.asc
Description: OpenPGP digital signature
------------------------------------------------------------------------- Check out the new SourceForge.net Marketplace. It's the best place to buy or sell services for just about anything Open Source. http://sourceforge.net/services/buy/index.php
_______________________________________________ Shorewall-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/shorewall-users
