Try a different ethernet cord and different port on the modem. Unplug modem and computer for at least 10 seconds and restart It must be on the computer itself because other wired and wifi connections to this modem. I’ve seen some evidence that this is due to a missing WINS server, however Microsoft themselves say that WINS is deprecated in favour of DNS (which i have running on the Mikrotik).Title says most of it. On Mikrotik forums, one user says that if there isn’t a gateway or SSID present, Windows will complain. I’m running out of google search terms (and search results), so I’ve created this thread to see if anyone has any ideas as to why Windows insists its an “unidentified network”. None of these make me happy at all, because fundamentally I shouldn’t have to change anything locally on the machine - the network configuration should just work.
I’ve done a bit of googling, and it seems like there are lots of solutions ranging from secpol.msc, regedit.exe hacks, and changing entire global policies on the local machine regarding “public” (or “untrusted”) connections.
Now I just want to teach Windows that this isn’t an “Unidentified connection”. so everything will get routed right (and it does.)
…the right set of routing tables: By omitting the gateway, no route was added to 192.168.88.1 for arbitrary destinations. It does the “right thing”, even with its WiFi adapter: :~ $ cat /etc/nf Now, after all that: The RPI2 is very happy. I believe this makes logical sense, since this particular network has no way out to any other networks, and I don’t want clients adding this path to their routing tables (I had a problem with this on the Linux SBC’s.)Īnd for DNS, I put 8.8.8.8 and 4.4.4.4 as alternative DNS servers, so that if i typed ping, it will fail to resolve on the Mikrotik DNS, and then go away to find where 4.4.4.4 lives, an everything should work. Now, I should stress that I have no gateway defined:
0 kommentar(er)
