search

max-mapper / HyperOS

A 50MB linux distribution that has dat-container for booting live containers on mac OS
120 stars 12 forks source link

have hypercore inherit host OS DNS #3

Open max-mapper opened 8 years ago

max-mapper commented 8 years ago

today on a university network that blocked ports etc, I ran into an issue where having /etc/resolv.conf configured with nameserver 192.168.64.1 worked, but nameserver 8.8.8.8 (google DNS) did not work

on other networks i've experienced the opposite being true -- google DNS fixes dns resolution, but using 192.168.64.1 didn't work

It would be nice to solve this for 100% of cases. I'm not an expert in this area, suggestions appreciated

mafintosh commented 8 years ago

should note that 192.168.64.1 is the static ip of the host on the bridge100 network interface that xhyve creates

bridge100: flags=8863<UP,BROADCAST,SMART,RUNNING,SIMPLEX,MULTICAST> mtu 1500
    options=3<RXCSUM,TXCSUM>
    ether aa:66:7f:50:3d:64
    inet 192.168.64.1 netmask 0xffffff00 broadcast 192.168.64.255
    Configuration:
        id 0:0:0:0:0:0 priority 0 hellotime 0 fwddelay 0
        maxage 0 holdcnt 0 proto stp maxaddr 100 timeout 1200
        root id 0:0:0:0:0:0 priority 0 ifcost 0 port 0
        ipfilter disabled flags 0x2
    member: en3 flags=3<LEARNING,DISCOVER>
            ifmaxaddr 0 port 7 priority 0 path cost 0
    nd6 options=1<PERFORMNUD>
    media: autoselect
    status: active