Routing and/or Bridging Problems

[averyb]

I have a router connected over ATM to a field CCTV camera.

10.10.1.226 is a MPEG 4 encoder.

192.168.253.2 is a software MPEG 4 decoder running on Windows XP (firewall is off)

This circuit and these devices are for transporting CCTV video from the field to a central monitoring location.

From the router, I can ping both the encoder (10.10.1.226) and the decoder (192.168.253.2).

From the decoder, I can ping its gateway 192.168.253.254 and the gateway to the field--BVI1 at 10.10.1.254

From the field I can ping BVI1 at 10.10.1.254, the gateway at central 192.168.253.254 and the decoder itself at 192.168.253.2.

Problem is that I can not ping from the decoder to the field.

For a test I associated access-list 107 on the BVI1 interface. When I ping the encoder from the router the acl increments. When I ping the encoder from the decoder, it doesn't. I take that to mean that there is some sort of routing or bridging problem going on.

It seems that the router doesn't know what to with traffic trying to get to 10.10.1.226. Same thing happens when trying to ping the encoder from a machine attached to FE0/0.2.

I can't explain why.

I attached the router configuration. I inherited this router so there are lots of extra statements in the config. Pertinent ones for this problem are FE0/0.1, FE0/0.2, ATM3/0.31, and BVI1.

[a-vazquez]

LLC and SNAP headers use a routed format or a bridged format. A bridged format does not necessarily mean that the encapsulated protocol is not routable. Instead, it is used when one side of the link supports only the bridged-format Protocol Data Units (PDUs), such as in these applications:

Connection between a router and a Catalyst switch in a corporate campus network.

Connection between a router and digital subscriber line (DSL) users that connect through a DSL access multiplexer (DSLAM).