You say that Site B has a router behind the LAN interface of the ASA
You say that Site B can ping Site A with no problem
You say that Site A cant ping Site B
On Site B there is no Route for the network 192.168.1.0/24
On Site B you have a Management interface which has the address range 192.168.1.0/24 also?
So I am beginning to think that the router behind the Site B ASA is doing Dynamic PAT for the network 192.168.1.0/24 behind it. This would mean that all traffic from the 192.168.1.0/24 would be PATed to some IP address from network 126.96.36.199/24. This again would enable traffic to flow from Site B to Site A normally. Considering the Dynamic PAT done by the Site B LAN router would mean though that no connection initiation would work from Site A to Site B since you cant form connections through Dynamic PAT from the external side.
So my guess would be that you would have to
Remove the Site B management interface configurations, atleast the IP address. If its in use change the network for the Management interface
Disable any type of NAT on the LAN Router at Site B so Site A can actually see the local network 192.168.1.0/24
Change the VPN and NAT configurations on the ASAs to reflect this change in the Site B network
The above would most likely affect your Site B Static NAT configuration you did just in the other discussion here on the forums.
One other alternative is that you configure Static NAT for the hosts you need on the Site B router from 192.168.0.x to 1.1.2.x so they can be connected from Site A
We have configured the outside and inside Interface with official ipv6 adresses, set a default route on outside Interface to our router, we also have definied a rule , which also gets hits, to permit tcp from inside Interface to any6.
In Syslog I also se...