You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This could be a KVM thing, but I've noticed that if I run an OSv image via:
scripts/run.py -n -v
I'll get the same IP address assigned to the instance.
Running via:
capstan run -n bridge
Will give me a different IP address each time. Is this an aspect of using bridge or something else? It would be quite nice to be able to know the IP address ahead of time.
Cheers,
Rowland
The text was updated successfully, but these errors were encountered:
It's because capstan randomly selects a MAC address instead of letting qemu
set it.
You're welcome to remove that from Capstan - check 'util.GenerateMAC' in
hypervisor/qemu/qemu.go
This could be a KVM thing, but I've noticed that if I run an OSv image via:
scripts/run.py -n -v
I'll get the same IP address assigned to the instance.
Running via:
capstan run -n bridge
Will give me a different IP address each time. Is this an aspect of using
bridge or something else? It would be quite nice to be able to know the IP
address ahead of time.
Cheers,
Rowland
—
Reply to this email directly or view it on GitHub #138.
Hi folks,
This could be a KVM thing, but I've noticed that if I run an OSv image via:
scripts/run.py -n -v
I'll get the same IP address assigned to the instance.
Running via:
capstan run -n bridge
Will give me a different IP address each time. Is this an aspect of using bridge or something else? It would be quite nice to be able to know the IP address ahead of time.
Cheers,
Rowland
The text was updated successfully, but these errors were encountered: