Thread: General Windows 10 Desktop WiFi
View Single Post
Old 27-12-2018, 20:08   #44
jem
cf.addict
 
Join Date: Mar 2005
Location: SE London (Bexley)
Services: None - well none with VM!
Posts: 275
jem is just so famous around these partsjem is just so famous around these partsjem is just so famous around these partsjem is just so famous around these partsjem is just so famous around these partsjem is just so famous around these partsjem is just so famous around these partsjem is just so famous around these partsjem is just so famous around these partsjem is just so famous around these partsjem is just so famous around these partsjem is just so famous around these partsjem is just so famous around these partsjem is just so famous around these partsjem is just so famous around these parts
Re: Windows 10 Desktop WiFi

Well this thread escalated fairly quickly didn't it?

It's a pity nobody asked 'beaker17' what printer he had or if he had direct print (or similar) switched on (probably yes) because in that case it might well create an ad-hoc wifi network and start broadcasting discovery frames which a PC with the proper software installed will find and connect to - over wifi while Windows will quite happily tell you that the wifi is 'Not Connected' because it is looking for an infrastructure-type setup, ie a proper IP address, gateway etc. So it's perfectly possible that his PC is connected 'wirelessly' directly to his printer, completely ignoring the SuperHub and all the while Windows claiming that the wifi is not connected.

Anyhow, back to his original question, can you have wifi and cabled ethernet (although on some levels you can argue that wifi transmissions are a form of ethernet as well) connected at the same time? And the answer is an unequivocal 'YES'. And I know because it drives me nuts with some of my clients who have laptops plugged into docking stations (we'll actually port replicators) and they get two IP addresses (and I hate waste) and it's always a bit vague as to which interface traffic will flow through.

This was actually addressed back in post 13 where it was pointed out that PCs, printers, tablets etc. never, ever have an IP address, it's the network interface which has the address and if you have more than one network interface they can both be connected and both can have their own IP address (and as long as the MAC addresses are different) there won't be any issues at all - no bridging loops etc. It's not ideal from a traffic management point of view, but in a home setup, who cares?

Now it is possible that some PC chipsets 'might' detect two connections to the same subnet and choose one to shutdown but this isn't normal or standard, in fact i'm posting this from an iMac with both wifi and ethernet connected and operational with IP addresses of 172.22.57.150 and 151 (I reserve them in DHCP) and I leave it to sort out which route to take outbound.
__________________
"I believe in an open mind, but not so open that your brains fall out"
Arthur Hays Sulzberger
jem is online now   Reply With Quote