I've also added a static route in the router on E0 as destination IP that of E1 and gateway IP that of E0 with a metric of 1 (no other router in between either interface) and a subnet first tried 255.255.255.255 which I thought means connection to host only and then 255.255.255.0 but unable to ping anything on E0 nor does the PC connect to the internet when the router is on E0. It only works when router's on E1 but I suppose that defeats the purpose of the PIX.
From the console I am able to ping both interfaces.
Secondly, the access-list on the inside interface only allows icmp originating to the outside. All other traffic is implicitly dropped. Is that really what you want? By default all traffic from the inside to the outside is allowed, so you should not have to apply an access-list to the inside interface if you want to allow all traffic from the inside to the outside.
for icmp connectivity, there should only be an access-list applied to the outside interface of the pix. This access-list should allow icmp reply traffic. Did you also remove the NAT0 statement? The static command should replace the nat0 command.
Could you try a traceroute on an inside host and on the router to see that the correct route is followed.
Login to the FXOS chassis manager.
Direct your browser to https://hostname/, and log-in using the user-name and password.
Go to Help > About and check the current version:
Check the current version availa...
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...