Nope, assuming host a talks to web server b, here is what happens:
Host a sends a packet with source of its IP and a source port of an available port higher than 1024. Let's say it chooses port 6000. B receives the request on port 80, and sends the reply _from_ port 80 to host A on port 6000.
a(6000) ---> b(80)
b(80) ---> a(6000)
The next http request packet may use 6001, so it would be:
You can do that, but most firewalls do that automatically per traffic flow. If you are using a router, it might be easiest to do that. If you are using a PIX/ASA, that is all automatic. The reason you would want to avoiod doing that if possible is that it also allows external hosts to send inbound traffic to any port as long as they source it from port 80 (which is possible to do using special software). Furthermore, if you are doing PAT on the firewall (likely) then your traffic probably goes out as another source port altogether.
The automatic rules are more specific so in the example I listed in the above post, the firewall sees the request from a(6000) to b(80) and it temporarily allows traffic from b(80) to a(6000) to allow the return traffic.
Sorry if I wasn't clear. The firewall monitors the traffic (inspect), and if your traffic is sourced from 6001, it opens up traffic back to 6001. If you then send traffic sourced from 6002, it will also allow the traffic back to 6002.
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...