Routing problem on a Masquerading Firewall

[Guus Sliepen]

On Wed, Oct 05, 2005 at 06:27:07PM +0200, Martijn Jacobs wrote:

> Connection is succesfull, the Masq firewall / Tinc Host "oeoe" can 
> connect(ping) to Tinc Host "50K" as well as to Workstation A.
> -
> Workstation A can connect (ping) to Masq firewall / Tinc Host "oeoe" as 
> well as to Workstation B. And Tinc Host "50K" is able to connect to 
> Workstation B
> -
> The problem : Workstation B cannot connect to Tinc Host "50K" nor to 
> Workstation A. It could be that the Workstation B packets are not 
> correctly routed, however : When I run both tinc daemons in debug mode, 
> I see packets logged, so the packets are arriving via the virtual 
> network. Because Workstation A can connect to Workstation B , routing 
> should be ok right? Has this something to do with the unknown firewall? 
> And if so, why are the packets then arriving on the other subnet (logged 
> in tincd debug mode)?

I suspect it is a firewall issue on host 50K. Can you send the output
of "iptables -L -v -x -n" and "iptables -t nat -L -v -x -n"?

-- 
Met vriendelijke groet / with kind regards,
    Guus Sliepen <guus at sliepen.eu.org>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: Digital signature
Url : http://brouwer.uvt.nl/pipermail/tinc/attachments/20051005/291437eb/attachment.pgp