Re: Networking FAQ: VMM internet access

2018-06-02 Thread Mike Larkin
On Sat, Jun 02, 2018 at 06:26:16PM +0300, Leonid Bobrov wrote: > Thanks for updating. > > I don't understand the necessity of vether(4) interface in fourth > option, I tested without it and didn't notice any change. But I would > fail without your warning about DHCP, thank you :) > Hm, it

Re: Networking FAQ: VMM internet access

2018-06-02 Thread Leonid Bobrov
Thanks for updating. I don't understand the necessity of vether(4) interface in fourth option, I tested without it and didn't notice any change. But I would fail without your warning about DHCP, thank you :)

Re: Networking FAQ: VMM internet access

2018-06-01 Thread Mike Larkin
On Fri, Jun 01, 2018 at 09:19:54AM -0700, Mike Larkin wrote: > On Fri, Jun 01, 2018 at 03:24:53PM +0300, Leonid Bobrov wrote: > > Can anyone update www/faq/faq6.html? That fourth option doesn't work at > > Ethernet device: > > > > mazocomp# echo 'dhcp' > /etc/hostname.vether0 > > mazocomp# sh

Re: Networking FAQ: VMM internet access

2018-06-01 Thread Mike Larkin
On Fri, Jun 01, 2018 at 03:24:53PM +0300, Leonid Bobrov wrote: > Can anyone update www/faq/faq6.html? That fourth option doesn't work at > Ethernet device: > > mazocomp# echo 'dhcp' > /etc/hostname.vether0 > mazocomp# sh /etc/netstart vether0 > vether0: no lease .. sleeping > mazocomp# >

Re: Networking FAQ: VMM internet access

2018-06-01 Thread Leonid Bobrov
I'm taking my words back about options 2 and 3. But couldn't option 2 mention that I have to manually choose DNS? Anyway, I prefer option 3 (but would like option 4 too). Also option 3 required me to choose router's DNS, but still I love how simple things really are: vmmnet.tar.gz Description:

Re: Networking FAQ: VMM internet access

2018-06-01 Thread Leonid Bobrov
Can anyone update www/faq/faq6.html? That fourth option doesn't work at Ethernet device: mazocomp# echo 'dhcp' > /etc/hostname.vether0 mazocomp# sh /etc/netstart vether0 vether0: no lease .. sleeping mazocomp#

Re: Networking FAQ: VMM internet access

2018-06-01 Thread Leonid Bobrov
On Fri, Jun 01, 2018 at 11:22:25AM +0200, Bruno Flueckiger wrote: > On 01.06.2018 10:54, Leonid Bobrov wrote: > > # cat /etc/resolv.conf > > # Generated by vio0 dhclient > > nameserver 100.64.2.2 > > nameserver 100.64.2.2 > > # ping 192.168.1.1 > > PING 192.168.1.1 (192.168.1.1): 56 data bytes > >

Re: Networking FAQ: VMM internet access

2018-06-01 Thread Bruno Flueckiger
On 01.06.2018 10:54, Leonid Bobrov wrote: # cat /etc/resolv.conf # Generated by vio0 dhclient nameserver 100.64.2.2 nameserver 100.64.2.2 # ping 192.168.1.1 PING 192.168.1.1 (192.168.1.1): 56 data bytes 64 bytes from 192.168.1.1: icmp_seq=0 ttl=63 time=0.938 ms 64 bytes from 192.168.1.1:

Re: Networking FAQ: VMM internet access

2018-06-01 Thread Leonid Bobrov
# cat /etc/resolv.conf # Generated by vio0 dhclient nameserver 100.64.2.2 nameserver 100.64.2.2 # ping 192.168.1.1 PING 192.168.1.1 (192.168.1.1): 56 data bytes 64 bytes from 192.168.1.1: icmp_seq=0 ttl=63 time=0.938 ms 64 bytes from

Re: Networking FAQ: VMM internet access

2018-06-01 Thread Leonid Bobrov
Hm, I tried option 2 again: # ping -c 1 www.google.com ping: no address associated with name # ping -c 1 74.125.205.147 PING 74.125.205.147 (74.125.205.147): 56 data bytes 64 bytes from 74.125.205.147: icmp_seq=0 ttl=46 time=24.059 ms --- 74.125.205.147 ping statistics --- 1 packets transmitted,