Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Capstan DHCP #138

Open
yieldone opened this issue Feb 23, 2015 · 1 comment
Open

Capstan DHCP #138

yieldone opened this issue Feb 23, 2015 · 1 comment

Comments

@yieldone
Copy link

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

@dorlaor
Copy link

dorlaor commented Feb 23, 2015

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

On Mon, Feb 23, 2015 at 12:07 PM, yieldone [email protected] wrote:

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


Reply to this email directly or view it on GitHub
#138.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants