Tom Eastep wrote: > c) ping 210.0.214.1. If that fails, look at the traffic with tcpdump; if > you are pinging from 192.168.0.14, then: > > tcpdump -nei eth2 host 210.0.214.127 > > If you see traffic going out but no traffic coming in, contact your ISP > for assistance. If you see traffic in both directions, check the link > layer (MAC) destination address in the response packets; is it the same > as the source MAC in the outgoing requests? If not, you have an > ARP/bridging issue.
Note that http://www.shorewall.net/3.0/NAT.htm#id2479684 includes an example which shows you how to find the source and destination MAC addresses (the destination comes first followed by the source). -Tom -- Tom Eastep \ When I die, I want to go like my Grandfather who Shoreline, \ died peacefully in his sleep. Not screaming like Washington, USA \ all of the passengers in his car http://shorewall.net \________________________________________________
signature.asc
Description: OpenPGP digital signature
------------------------------------------------------------------------------ The Planet: dedicated and managed hosting, cloud storage, colocation Stay online with enterprise data centers and the best network in the business Choose flexible plans and management services without long-term contracts Personal 24x7 support from experience hosting pros just a phone call away. http://p.sf.net/sfu/theplanet-com
_______________________________________________ Shorewall-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/shorewall-users
