tampler opened a new issue, #8349:
URL: https://github.com/apache/cloudstack/issues/8349
<!--
Verify first that your issue/request is not already reported on GitHub.
Also test if the latest release and main branch are affected too.
Always add information AFTER of these HTML comments, but no need to delete
the comments.
-->
##### ISSUE TYPE
<!-- Pick one below and delete the rest -->
* Networking
* Debug
* Documentation Report
##### COMPONENT NAME
<!--
Categorize the issue, e.g. API, VR, VPN, UI, etc.
-->
~~~
Core, Network, Debug, UI
~~~
##### CLOUDSTACK VERSION
<!--
New line separated list of affected versions, commit ID for issues on main
branch.
-->
~~~
4.19.0.0
~~~
##### CONFIGURATION
<!--
Information about the configuration if relevant, e.g. basic network,
advanced networking, etc. N/A otherwise
-->
Advanced zone with VPC
Bridge config
```sh
br1:
interfaces: [enp1s0f1]
addresses: [192.168.1.4/24]
routes:
- to: 0.0.0.0/0
via: 192.168.1.1
on-link: true
nameservers:
addresses:
- xxx.yyy.93.93
- xxx.yyy.92.92
```
##### OS / ENVIRONMENT
<!--
Information about the environment if relevant, N/A otherwise
-->
Ubuntu 22.04
##### SUMMARY
<!-- Explain the problem/feature briefly -->
Using an external `router` device to route traffic in ACS. CloudStack is
running on the private network `192.168.1.0/24` with Source NAT enabled.
Hypervisor is using only `one` bridge `br1` to route all traffic types in
the `192.168.1.0/24` network.
```
> cat ./agent.properties
private.network.device=br1
guest.network.device=br1
public.network.device=br1
```
I was able to successfully config VPC and a private subnet and launch
`Alpine Linux` VM. Now I need to route traffic into it to proceed with my VM
##### STEPS TO REPRODUCE
<!--
For bugs, show exactly how to reproduce the problem, using a minimal
test-case. Use Screenshots if accurate.
For new features, show how the feature would be used.
-->
<!-- Paste example playbooks or commands between quotes below -->
~~~
1. Install ACS 4.19.0.0 with an Advanced Zone
2. Create a VPC and a subnet
3. Launch `Alpine Linux` VM in the private subnet
4. Click on `Console Proxy` to allow VNC screen
5. Enable port forwarding to console proxy: `ssh -L 2220:<remote public
IP>:<80>
6. Check VNC connection:
> curl
http://localhost:2220/resource/noVNC/vnc.html\?autoconnect\=true\&port\=8080\&token\=MSY5R/tXOxtp7MKoxOTiZJTG1cwTmWhzj3JVqvwmy1aBBGYLS04sfwYGGX70Yh6w8JT1EBqr7ZavvYLnIeK4CJsmDrhoCn1EHAKhR1U/XZ2cIcT7mKjzw9wkcQIi3YAQXhmqRFPJ41EskEdcBE40+qouQYchsrG397c7HEyzg+t2ITknryu5IJNMEY3QfrkMmkN5ag2H/0t+d19cRI1jUNbOAGdchYFbExR2d2xqkwtvCn8awehXwC3xsuPxPk+y/5Ec+AArtMKW5P8uqPsBJ2xmzaJ+PfmgT+niDDuz8XmRBOKCOYnyC31CDf2JXMOpX4S56F0duIjDUDhYKR0y8ETQ4rs1LsEJPglWvz+Md4dareUMzjqbeYvnOTiEmYjmXkERTQi/O6l5cyJN0tyDgeIvQRI6PHWmq7UaULsyj2UDHPFQO1qJEn+UTXGW3lvMqQCbtb/NwGlfWFvwhoS/4w44ewd5N/oLFN6PsSnNMmmPPdXxlwK3Ut++9XpvyhIzvdqyX5OuH5gUNCxWxwzZKsPdqA\=\=
curl: (7) Failed to connect to localhost port 2220 after 0 ms: Connection
refused
~~~
<!-- You can also paste gist.github.com links for larger files -->
##### EXPECTED RESULTS
<!-- What did you expect to happen when running the steps above? -->
~~~
Login via Console Proxy to my VM
~~~
##### ACTUAL RESULTS
<!-- What actually happened? -->
<!-- Paste verbatim command output between quotes below -->
~~~
Error in connection establishment: net::ERR_CONNECTION_REFUSED
~~~
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
