- Newest
- Most votes
- Most comments
Hello all, I ended up figuring out my issue here. For some reason, it was using our "backup" tunnel setup in AWS. It was using Tunnel2 rather than Tunnel1. After doing some packet captures on our FortiGate itself, it showed me this. After finding this out, I had to update the subnet on the Tunnel2 on the Firewall and then add the policy. After that, everything started kicking along. I do not know why it started using the other tunnel though.
By performing packet captures on your FortiGate firewall, you were able to identify this discrepancy. To fix the issue, you updated the subnet on Tunnel2 and added the necessary policy. After making these changes, everything started functioning properly.
As for why the system started using the other tunnel, it could be due to various factors such as configuration changes, routing issues, or automatic failover mechanisms. Without more information, it is difficult to pinpoint the exact cause. However, the important thing is that you were able to troubleshoot and resolve the issue successfully.
If you have any further questions or need assistance with anything else, feel free to ask. I'm here to help!
Do you have the ip routes on your network and vpc configured correctly?
Are the NACLs configured to allow bi directional traffic?
Does the security group on the ec2 allow outbound traffic to the subnet assigned to your WiFi network?
Do you have same routing and firewall rule in AWS VPC/ EC2 sg/acl/ VPN encryption / Fortigate, for WIFI and WIRED network CIDR IP Address of your printer ?
Relevant content
AWS OFFICIALUpdated a year ago- AWS OFFICIALUpdated 8 months ago
- AWS OFFICIALUpdated 3 years ago
- AWS OFFICIALUpdated a year ago
You mentioned that you have configured static routes and have allowed the necessary port (9100) for inbound rules on your FortiGate firewall. Additionally, the firewall rules allow all traffic, and the communication is taking place over a private VPC. However, you are still experiencing connectivity problems.
To troubleshoot the issue, here are a few suggestions:
Verify Wi-Fi connectivity: Ensure that the Wi-Fi network is functioning properly and that the EC2 instance hosting the print server has a stable and reliable connection to the Wi-Fi network.
Check security group settings: Confirm that the security group associated with the EC2 instance allows inbound and outbound traffic on the necessary ports (e.g., port 9100) for printer communication.