Open alex404sl opened 2 years ago
Tried to attach the created network interface and run the systemctl start snat, got following error message:
[root@ip-10-1-0-177 bin]# systemctl status snat
● snat.service - SNAT via ENI eth1
Loaded: loaded (/etc/systemd/system/snat.service; enabled; vendor preset: disabled)
Active: failed (Result: exit-code) since Wed 2022-02-09 02:22:50 UTC; 15s ago
Process: 2814 ExecStart=/opt/nat/snat.sh (code=exited, status=2)
Main PID: 2814 (code=exited, status=2)
Feb 09 02:22:50 ip-10-1-0-177.compute.internal snat.sh[2814]: --rpm-requires
Feb 09 02:22:50 ip-10-1-0-177.compute.internal snat.sh[2814]: --restricted
Feb 09 02:22:50 ip-10-1-0-177.compute.internal snat.sh[2814]: --verbose
Feb 09 02:22:50 ip-10-1-0-177.compute.internal snat.sh[2814]: --version
Feb 09 02:22:50 ip-10-1-0-177.compute.internal snat.sh[2814]: Shell options:
Feb 09 02:22:50 ip-10-1-0-177.compute.internal snat.sh[2814]: -irsD or -c command or -O shopt_option (invocation only)
Feb 09 02:22:50 ip-10-1-0-177.compute.internal snat.sh[2814]: -abefhkmnptuvxBCHP or -o option
Feb 09 02:22:50 ip-10-1-0-177.compute.internal systemd[1]: Failed to start SNAT via ENI eth1.
Feb 09 02:22:50 ip-10-1-0-177.compute.internal systemd[1]: Unit snat.service entered failed state.
Feb 09 02:22:50 ip-10-1-0-177.compute.internal systemd[1]: snat.service failed.
Hi! Thank you for the work!
But I am not be able to make this work though. The created nat instance does not have eth1.
Thanks!