The problem was the gateway of device in 10.165.50.X network. I thought
the packet would go back in the same way that they came from, but it
doesn't.....always use the gateway of machine (in this case,
10.165.50.5, with doesn't have any route to 192.168.0.X)....anyway, tks
Jose and Pascal!
Since this is a test enviorment (with 2 gateways), eveything will work
in final project :)
Tks
> What do you mean exactly ? Can you really not send a ping request to
> 10.165.50.X (and there is an error message) or do you just not receive
> any reply ?
>
> Do hosts in 10.165.50.0/24, and specially their gateway which seem to be
> 10.165.50.5, have a proper route to 192.168.0.0/24 via 10.165.50.179 ?
> They need it to be able to send a reply.
>
>
>
--
To UNSUBSCRIBE, email to debian-firewall-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
No comments:
Post a Comment