John Schmidt wrote:
> <snippage throughout>
>
> fernando.scheid@gmail.com wrote:
> > Hi all,
> >
> > I have one big problem with routing.
>
> Maybe not...
>
> <snip>
>
> >From host OSR506A i can ping to ROUTER-A, ROUTER-B, OSR506B (net0),
> > OSR506B (net1), OSR506C (net0) and OSR506C (net1).
>
> <snip>
>
> > But from host OSR506C i can not ping or traceroute to OSR506A.
>
> A quick glance at your routing tables looks like they're correct.
>
> If ping and traceroute work in one direction but not another, it's
more
> than likely not a routing problem. For OSR506A to recieve the replies

> from OSR506C when querying it, *both* machines have to know how to
get
> to each other. Unless there's a dynamic routing protocol running on
any
> of the boxes in the network path, you probably have a firewall rather

> than a routing problem. From your traceroutes, the most likely
culprit
> is OSR506B.
>
>
> JS

John,

I can guarantee to you that there are no dynamic routing protocol
configured and no firewall in the network path.

The server osr506b does not forward the packages between the interfaces
when it originates from osr506c.

This behavior can be seen by the command traceroute.

The package is directed to interface 192.168.100.1 and dies.

Thanks for your attention.

Fernando