From f14a6c30cc7cb82775c337e09946bfcb41aab07f Mon Sep 17 00:00:00 2001 From: Samuel Thibault Date: Sat, 5 Jan 2019 15:48:07 +0100 Subject: Fix using netdde's eth0 --- hurd/running/qemu.mdwn | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) (limited to 'hurd/running') diff --git a/hurd/running/qemu.mdwn b/hurd/running/qemu.mdwn index 369ceab6..48ab872a 100644 --- a/hurd/running/qemu.mdwn +++ b/hurd/running/qemu.mdwn @@ -240,7 +240,7 @@ Some further notes about [[networking]] and home hints about If you just want to access the internet from within QEMU, you can setup pfinet for QEMU's user-networking: - # settrans -afgp /servers/socket/2 /hurd/pfinet -i eth0 -a 10.0.2.15 -g 10.0.2.2 -m 255.255.255.0 + # settrans -afgp /servers/socket/2 /hurd/pfinet -i /dev/eth0 -a 10.0.2.15 -g 10.0.2.2 -m 255.255.255.0 # echo "nameserver 10.0.2.3" > /etc/resolv.conf If you are on [[Debian GNU/Hurd|debian]], you can even use [[debian/DHCP]]. @@ -348,7 +348,7 @@ Now it is time to start-up your QEMU Hurd system and get networking going in the Once you have logged in as `root` run the `pfinet` translator with values that apply to your network. Think of your QEMU client as another computer in your network. - # settrans -fgap /servers/socket/2 /hurd/pfinet -i eth0 -a xxx.xxx.xxx.xxx -g xxx.xxx.xxx.xxx -m xxx.xxx.xxx.xxx + # settrans -fgap /servers/socket/2 /hurd/pfinet -i /dev/eth0 -a xxx.xxx.xxx.xxx -g xxx.xxx.xxx.xxx -m xxx.xxx.xxx.xxx That should do it! Do not forget to edit/update `/etc/resolv.conf` to get DNS working. -- cgit v1.2.3