Jump to content

Alright, note to self. Do NOT configure Default Gateways on internal networks that do not contain an external route while using Linux. Windows finds it's way around it but Linux goes "Oh, so you want me to use THAT ONE now for all Internet bound traffic even though I already have a functioning link to a router.". Like, no I'm just pointing you to the file server I didn't say shit about taking a different route to the Internet. Then when it finds it doesn't work it just quits like "Yeah this isn't working. I know that other network with a function connection exists but just yea, no. DNS_PROBE_FINISHED_NO_INTERNET"

  1. leadeater

    leadeater

    You're only supposed to configure one default gateway, even on Windows ?

  2. Windows7ge

    Windows7ge

    I know, the only reason I do it is as a kind of GOLR since I address everything by IP if it can't find it for some unknown reason it'll send it to the IP I was trying to address on that network.

     

    In the end as it turns out it didn't matter since I was doing everything wrong. I needed to setup a network bridge and assign an IP to the bridge not the physical interface.

     

    I'm in the process of getting Windows running on QEMU_system using virt-manager for a GUI. I got 16 vcpus which the guest saw as 16 one core CPUs which is a problem for Windows 10 also it shows up as a EYPC processor. Interesting. Now I have the NIC sorted so I can pass data between the virtual network and my physical file server so I can pull it from there to my Linux host. Now I need to figure out GPU pass-through which someone mentioned VFIO & Looking Glass. If I can get this working I can run Windows at near native performance at the same time as Linux and control them with the same keyboard/mouse/monitor(s).

×