From: Christopher Lemmer Webber <cwebber@dustycloud.org>
To: Jan Nieuwenhuizen <janneke@gnu.org>
Cc: help-guix@gnu.org
Subject: Re: Port forwarding and `guix system vm`
Date: Tue, 07 Jul 2020 16:18:53 -0400 [thread overview]
Message-ID: <875zazgjte.fsf@dustycloud.org> (raw)
In-Reply-To: <87h7ujayft.fsf@gnu.org>
Jan Nieuwenhuizen writes:
> You want to add something like
>
> (service dhcp-client-service-type)
... doh, I can't believe I missed that. Thank you!
>
> In our chat on IRC I mentioned that adding this "-nic user,virtio-net-pci bit",
> I mentioned that this gives me two eth devices:
>
> --8<---------------cut here---------------start------------->8---
> eth0 Link encap:Ethernet HWaddr 52:54:00:12:34:56
> inet addr:10.0.2.15 Bcast:10.0.2.255 Mask:255.255.255.0
> UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
> RX packets:3 errors:0 dropped:0 overruns:0 frame:0
> TX packets:9 errors:0 dropped:0 overruns:0 carrier:0
> collisions:0 txqueuelen:1000
> RX bytes:1314 TX bytes:1286
>
> eth1 Link encap:Ethernet HWaddr 52:54:00:12:34:57
> inet addr:10.0.2.15 Bcast:10.0.2.255 Mask:255.255.255.0
> UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
> RX packets:11 errors:0 dropped:0 overruns:0 frame:0
> TX packets:17 errors:0 dropped:0 overruns:0 carrier:0
> collisions:0 txqueuelen:1000
> RX bytes:1784 TX bytes:1706
>
> lo Link encap:Local Loopback
> inet addr:127.0.0.1 Bcast:0.0.0.0 Mask:255.0.0.0
> UP LOOPBACK RUNNING MTU:65536 Metric:1
> RX packets:0 errors:0 dropped:0 overruns:0 frame:0
> TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
> collisions:0 txqueuelen:1000
> RX bytes:0 TX bytes:0
> --8<---------------cut here---------------end--------------->8---
I'm also seeing a duplicate network device as above. (Not sure if it's
causing problems or not.)
> I noticed this yesterday while struggled similarly, and found that
> removing this bit from run-sh; like so:
>
> --8<---------------cut here---------------start------------->8---
> sed 's,-nic user[^ ]* ,,' /gnu/store/j8fqc160diq82da7913gpdlcjca45rhz-run-vm.sh > run-vm.sh
> --8<---------------cut here---------------end--------------->8---
>
> and running "run-vm.sh, will create only eth0. I blamed this second
> eth1 device for my ssh'ing troubles...but I cannot reproduce that
> today...dunno!
>
> Greetings,
> Janneke
It does seem like having two network devices bound to the same address
would be ripe for a heisenbug though, right? So maybe...
next prev parent reply other threads:[~2020-07-07 20:19 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-07 18:16 Port forwarding and `guix system vm` Christopher Lemmer Webber
2020-07-07 19:59 ` Jan Nieuwenhuizen
2020-07-07 20:18 ` Christopher Lemmer Webber [this message]
2020-07-07 23:21 ` Christopher Lemmer Webber
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=875zazgjte.fsf@dustycloud.org \
--to=cwebber@dustycloud.org \
--cc=help-guix@gnu.org \
--cc=janneke@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).