tomii
Posts: 10
Joined: Tue Dec 25, 2018 11:53 pm

Pi 0 Ethernet Gadget can't reach internet - Windows 10

Wed Dec 26, 2018 12:48 am

Lordy, it's been a long day...

Let's start with a solution to the 1st problem I had, because nowhere did I actually find the solution, and just got there out of frustration and spite..

Problem 1 *FIXED*
  1. Followed the steps on the many diff't websites (ex. adafruit) to turn a Pi0 into an Ethernet Gadget (not the first time I've done this, but the first time it took me a day and a half to get it working).
  2. Plug it in, no talky. That is, I could not SSH in using raspberrypi.local.
  3. Connect console cable - am able to log in.
  4. Use "Powershell" to perform an ipconfig. Get local address. Can then ssh directly to address.
  5. notice "stuff" that sends me down many rabbit holes, but also reading lots of forum posts here, and elsewhere.
  6. Cannot touch internet to perform updates (source of this post); cannot use hostname.local to ssh into box.
SOLUTION: in the end, it was bonjour was some how confused. Trick was, I reinstalled it twice along with changing (and unchanging) a million other things. Turns out, and here is the crux - YOU MUST COMPLETELY UNINSTALL BONJOUR before REINSTALLING IT!.

D'oh... Now "DNS" is working on the PC, and I can SSH/VNC into the Pi 0 without having to go to the console and find out what the IP has been set to. Yes, it's still dynamic - not messing with static IPs.

PROBLEM 2:
Using Windows 10. Can't seem to share my internet connection,. My linux-foo is real rusty, as I haven't used it much in the last 15 years...
But, I notice some things. But I woun't put them here, as I don't want to lead someone who might have the answer down thr wrong path (immediately, anyway)

UPDATE:
Getting closer - I just figured out that Windows Defender Firewall is the culprit. Not sure when or what turned it on to block private networks...

So, now the question becomes:
"Should I just turn off firewalls on private networks, or should I try to figure out how to let services through."

I'm hesitant to just shut off private network firewall, as that would include protecting me from some st00pid virus my kids download on their PC (which is on the "private" home network)... But OTOH, it's clearly blocking my PIs.

Looks like I've got some more research to do...


UPDATE 2

Potentially(?) solved.

https://social.technet.microsoft.com/Fo ... networking

I'll have to look and see if this works across multiple PIs, though. Don't particularly want to do this separately for every Pi (I have several)

From the PC (on current boot):
ipconfig /all (I've highlighted the adapters of concern for easier grep-ing
Windows IP Configuration

Host Name . . . . . . . . . . . . : Acer-Laptop
Primary Dns Suffix . . . . . . . :
Node Type . . . . . . . . . . . . : Hybrid
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No
DNS Suffix Search List. . . . . . : home

Ethernet adapter Ethernet:

Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Realtek PCIe GBE Family Controller
Physical Address. . . . . . . . . : F0-76-1C-35-58-1D
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes

Ethernet adapter Ethernet 3:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : USB Ethernet/RNDIS Gadget
Physical Address. . . . . . . . . : 3E-51-21-44-BE-8A
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes
Autoconfiguration IPv4 Address. . : 169.254.11.100(Preferred)
Subnet Mask . . . . . . . . . . . : 255.255.0.0
Default Gateway . . . . . . . . . :
NetBIOS over Tcpip. . . . . . . . : Enabled

Wireless LAN adapter Local Area Connection* 5:

Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Microsoft Wi-Fi Direct Virtual Adapter #3
Physical Address. . . . . . . . . : 1E-93-A2-F5-E0-2D
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes

Wireless LAN adapter Local Area Connection* 6:

Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Microsoft Wi-Fi Direct Virtual Adapter #4
Physical Address. . . . . . . . . : 2E-93-A2-F5-E0-2D
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes

Wireless LAN adapter Local Area Connection* 16:

Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Microsoft Hosted Network Virtual Adapter #2
Physical Address. . . . . . . . . : 5E-93-A2-F5-E0-2D
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes

Wireless LAN adapter Wi-Fi:

Connection-specific DNS Suffix . : home
Description . . . . . . . . . . . : Qualcomm Atheros AR956x Wireless Network Adapter
Physical Address. . . . . . . . . : 5C-93-A2-F5-E0-2D
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
IPv4 Address. . . . . . . . . . . : 192.168.68.14(Preferred)
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Lease Obtained. . . . . . . . . . : Tuesday, December 25, 2018 6:09:20 PM
Lease Expires . . . . . . . . . . : Wednesday, December 26, 2018 6:09:19 PM
Default Gateway . . . . . . . . . : 192.168.68.1
DHCP Server . . . . . . . . . . . : 192.168.68.1
DNS Servers . . . . . . . . . . . : 192.168.68.1
NetBIOS over Tcpip. . . . . . . . : Enabled


Ethernet adapter Bluetooth Network Connection:

Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Bluetooth PAN HelpText
Physical Address. . . . . . . . . : 5C-93-A2-F6-7E-39
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
route print:

Code: Select all

===========================================================================
Interface List
  9...f0 76 1c 35 58 1d ......Realtek PCIe GBE Family Controller
20...3e 51 21 44 be 8a ......USB Ethernet/RNDIS Gadget
24...1e 93 a2 f5 e0 2d ......Microsoft Wi-Fi Direct Virtual Adapter #3
 12...2e 93 a2 f5 e0 2d ......Microsoft Wi-Fi Direct Virtual Adapter #4
 21...5e 93 a2 f5 e0 2d ......Microsoft Hosted Network Virtual Adapter #2
  [color=#BF00BF]4...5c 93 a2 f5 e0 2d ......Qualcomm Atheros AR956x Wireless Network Adapter[/color]
  6...5c 93 a2 f6 7e 39 ......Bluetooth PAN HelpText
  1...........................Software Loopback Interface 1
===========================================================================

IPv4 Route Table
===========================================================================
Active Routes:
Network Destination        Netmask          Gateway       Interface  Metric
          0.0.0.0      |    0.0.0.0   |  192.168.68.1  |  192.168.68.14  |   55
        127.0.0.0   |     255.0.0.0     |    On-link     |    127.0.0.1  |  331
        127.0.0.1 | 255.255.255.255      |   On-link     |    127.0.0.1  |  331
  127.255.255.255 | 255.255.255.255   |      On-link     |    127.0.0.1  |  331
      169.254.0.0    |  255.255.0.0     |    On-link  |  169.254.11.100  |  281
   169.254.11.100 | 255.255.255.255     |    On-link  |  169.254.11.100  |  281
  169.254.255.255 | 255.255.255.255    |     On-link |   169.254.11.100  |  281
     192.168.68.0   | 255.255.255.0     |    On-link   |  192.168.68.14  |  311
    192.168.68.14 | 255.255.255.255     |    On-link   |  192.168.68.14  |  311
   192.168.68.255 | 255.255.255.255    |     On-link   |  192.168.68.14  |  311
        224.0.0.0      |  240.0.0.0    |     On-link    |     127.0.0.1  |  331
        224.0.0.0      |  240.0.0.0    |     On-link  |   192.168.68.14  |  311
        224.0.0.0      |  240.0.0.0    |     On-link   | 169.254.11.100  |  281
  255.255.255.255 | 255.255.255.255     |    On-link         127.0.0.1  |  331
  255.255.255.255 | 255.255.255.255     |    On-link     192.168.68.14 |   311
  255.255.255.255 | 255.255.255.255     |    On-link  |  169.254.11.100 |   281
===========================================================================
Persistent Routes:
  None

IPv6 Route Table
===========================================================================
Active Routes:
 If Metric Network Destination      Gateway
  1    331 ::1/128                  On-link
  1    331 ff00::/8                 On-link
===========================================================================
Persistent Routes:
  None
from Pi side:
ifconfig -a

Code: Select all

lo: flags=73<UP,LOOPBACK,RUNNING>  mtu 65536
        inet 127.0.0.1  netmask 255.0.0.0
        inet6 ::1  prefixlen 128  scopeid 0x10<host>
        loop  txqueuelen 1000  (Local Loopback)
        RX packets 1430  bytes 136054 (132.8 KiB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 1430  bytes 136054 (132.8 KiB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

usb0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
        inet 169.254.66.155  netmask 255.255.0.0  broadcast 169.254.255.255
        inet6 fe80::508c:6fdc:2ae3:dce0  prefixlen 64  scopeid 0x20<link>
        ether aa:3d:5f:6f:3a:f7  txqueuelen 1000  (Ethernet)
        RX packets 9428  bytes 754538 (736.8 KiB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 14203  bytes 3921316 (3.7 MiB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0
route

Code: Select all

Kernel IP routing table
Destination     Gateway         Genmask         Flags Metric Ref    Use Iface
default         0.0.0.0         0.0.0.0         U     202    0        0 usb0
link-local      0.0.0.0         255.255.0.0     U     202    0        0 usb0
I won't post images right now, but in device manager, Ethernet Gadget shows up with no errors under network interfaces
I can share and unshare, and then share again the wireless connection to ethernet3 to no avail.
I can successfully ping the IP of the Pi (169.254.66.15, above) from the windows box
I can successfully ping the IP of the Windows box (169.254.11.100, above) from the Pi.

I can reach exterior networks from the Windows box (e.g. Google, Microsoft, this site, etc).
I cannot reach even my local network from the Pi.

ping (from pi):
pi@Pi0-00:~ $ ping www.google.com
ping: www.google.com: Temporary failure in name resolution
PING 8.8.8.8 (8.8.8.8) 56(84) bytes of data.
From 169.254.66.155 icmp_seq=1 Destination Host Unreachable
From 169.254.66.155 icmp_seq=2 Destination Host Unreachable
From 169.254.66.155 icmp_seq=3 Destination Host Unreachable
For clarity's sake, no internet apps (e.g. chromium) work either.
ERR_NAME_RESOLUTION_FAILED
Last edited by tomii on Wed Dec 26, 2018 8:48 pm, edited 2 times in total.

Ernst
Posts: 1191
Joined: Sat Feb 04, 2017 9:39 am
Location: Germany

Re: Pi 0 Ethernet Gadget can't reach internet - Windows 10

Wed Dec 26, 2018 8:51 am

This will never work because 169.254.0.0/16 are local addresses and can/will not be routed.

The simplest method to solve your problem is to configure internet sharing on your PC, you must find out why you are unable to get this to work.
The road to insanity is paved with static ip addresses

tomii
Posts: 10
Joined: Tue Dec 25, 2018 11:53 pm

Re: Pi 0 Ethernet Gadget can't reach internet - Windows 10

Wed Dec 26, 2018 12:53 pm

Ernst wrote:
Wed Dec 26, 2018 8:51 am
This will never work because 169.254.0.0/16 are local addresses and can/will not be routed.

The simplest method to solve your problem is to configure internet sharing on your PC, you must find out why you are unable to get this to work.
reposting from the original...
I won't post images right now, but in device manager, Ethernet Gadget shows up with no errors under network interfaces
I can share and unshare, and then share again the wireless connection to ethernet3 to no avail.
I can successfully ping the IP of the Pi (169.254.66.15, above) from the windows box
I can successfully ping the IP of the Windows box (169.254.11.100, above) from the Pi.
Clearly (I think), this is a windows sharing problem, and not a Pi problem. I guess I should have been more clear that I'm seeking help in getting windows sharing to work properly.

fruitoftheloom
Posts: 20196
Joined: Tue Mar 25, 2014 12:40 pm
Location: Delightful Dorset

Re: Pi 0 Ethernet Gadget can't reach internet - Windows 10

Wed Dec 26, 2018 1:19 pm

tomii wrote:
Wed Dec 26, 2018 12:53 pm
Ernst wrote:
Wed Dec 26, 2018 8:51 am
This will never work because 169.254.0.0/16 are local addresses and can/will not be routed.

The simplest method to solve your problem is to configure internet sharing on your PC, you must find out why you are unable to get this to work.
reposting from the original...
I won't post images right now, but in device manager, Ethernet Gadget shows up with no errors under network interfaces
I can share and unshare, and then share again the wireless connection to ethernet3 to no avail.
I can successfully ping the IP of the Pi (169.254.66.15, above) from the windows box
I can successfully ping the IP of the Windows box (169.254.11.100, above) from the Pi.
Clearly (I think), this is a windows sharing problem, and not a Pi problem. I guess I should have been more clear that I'm seeking help in getting windows sharing to work properly.

If it is indeed a Microsoft Internet Sharing issue, then Microsoft Support would be the ideal place to start:

https://answers.microsoft.com/en-us/win ... ac86d98fb9
adieu

Asus CS10 Chromebit / HP Envy 4500 Wireless Printer / Raspberry Pi Model 2B v1.1 / RealVNC Software...

n67
Posts: 938
Joined: Mon Oct 30, 2017 4:55 pm

Re: Pi 0 Ethernet Gadget can't reach internet - Windows 10

Wed Dec 26, 2018 1:20 pm

Perhaps post to a Windows forum - maybe "stack exchange" or something like that?

BTW, it is perfectly possible to have the PiZero have an IP address of 169.254.x.y and have it be able to see and access the Internet. I do it all the time. I find it the most flexible way to do things - rather than have to set up a "real" IP address.
"L'enfer, c'est les autres"

G fytc hsqr rum umpbq rm qyw rm rfc kmbq md rfgq dmpsk:

Epmu Sn!

J lnacjrw njbruh-carppnanm vxm rb mnuncrwp vh yxbcb!

hippy
Posts: 5613
Joined: Fri Sep 09, 2011 10:34 pm
Location: UK

Re: Pi 0 Ethernet Gadget can't reach internet - Windows 10

Wed Dec 26, 2018 4:37 pm

tomii wrote:
Wed Dec 26, 2018 12:53 pm
Clearly (I think), this is a windows sharing problem, and not a Pi problem. I guess I should have been more clear that I'm seeking help in getting windows sharing to work properly.
I would definitely agree it's a Windows issue; your Pi doesn't seem to be getting a DHCP assigned address. I have no idea how to set that up for Windows 10, I doubt most Pi or Linux users would, so it may be worth hitting a search engine or asking on forums whose focus is on setting up networking and internet sharing for Windows 10.

fruitoftheloom
Posts: 20196
Joined: Tue Mar 25, 2014 12:40 pm
Location: Delightful Dorset

Re: Pi 0 Ethernet Gadget can't reach internet - Windows 10

Wed Dec 26, 2018 5:07 pm

hippy wrote:
Wed Dec 26, 2018 4:37 pm
tomii wrote:
Wed Dec 26, 2018 12:53 pm
Clearly (I think), this is a windows sharing problem, and not a Pi problem. I guess I should have been more clear that I'm seeking help in getting windows sharing to work properly.
I would definitely agree it's a Windows issue; your Pi doesn't seem to be getting a DHCP assigned address. I have no idea how to set that up for Windows 10, I doubt most Pi or Linux users would, so it may be worth hitting a search engine or asking on forums whose focus is on setting up networking and internet sharing for Windows 10.

Yes suggested to use Microsoft Support Forum above :roll:
adieu

Asus CS10 Chromebit / HP Envy 4500 Wireless Printer / Raspberry Pi Model 2B v1.1 / RealVNC Software...

n67
Posts: 938
Joined: Mon Oct 30, 2017 4:55 pm

Re: Pi 0 Ethernet Gadget can't reach internet - Windows 10

Wed Dec 26, 2018 5:59 pm

Problem is that instant anybody on an MS forum hears that a "Raspberry Pi" is involved, they'll wash their hands of it. And point you back to an RPi forum...

It's one of those "neither fish nor fowl" sort of things. Neither side wants to own it.
"L'enfer, c'est les autres"

G fytc hsqr rum umpbq rm qyw rm rfc kmbq md rfgq dmpsk:

Epmu Sn!

J lnacjrw njbruh-carppnanm vxm rb mnuncrwp vh yxbcb!

fruitoftheloom
Posts: 20196
Joined: Tue Mar 25, 2014 12:40 pm
Location: Delightful Dorset

Re: Pi 0 Ethernet Gadget can't reach internet - Windows 10

Wed Dec 26, 2018 6:23 pm

n67 wrote:
Wed Dec 26, 2018 5:59 pm
Problem is that instant anybody on an MS forum hears that a "Raspberry Pi" is involved, they'll wash their hands of it. And point you back to an RPi forum...

It's one of those "neither fish nor fowl" sort of things. Neither side wants to own it.

If ICS is correctly configured then it makes no difference what device is connecting to the MS Windows Desktop Machine, providing the connecting machine is set up as a DHCP Client as most Operating Systems are by default.
adieu

Asus CS10 Chromebit / HP Envy 4500 Wireless Printer / Raspberry Pi Model 2B v1.1 / RealVNC Software...

tomii
Posts: 10
Joined: Tue Dec 25, 2018 11:53 pm

Re: Pi 0 Ethernet Gadget can't reach internet - Windows 10

Wed Dec 26, 2018 7:56 pm

n67 wrote:
Wed Dec 26, 2018 5:59 pm
Problem is that instant anybody on an MS forum hears that a "Raspberry Pi" is involved, they'll wash their hands of it. And point you back to an RPi forum...

It's one of those "neither fish nor fowl" sort of things. Neither side wants to own it.
Indeed. I've been surfing the MS forums, too. I have 2 diff't PIs on 2 diff't PCs - both exhibiting the same issue.

The crux is - I've done this before, and it used to work. And now it doesn't, and I'd like to know WTH...

tomii
Posts: 10
Joined: Tue Dec 25, 2018 11:53 pm

Re: Pi 0 Ethernet Gadget can't reach internet - Windows 10

Wed Dec 26, 2018 8:03 pm

fruitoftheloom wrote:
Wed Dec 26, 2018 1:19 pm

I won't post images right now, but in device manager, Ethernet Gadget shows up with no errors under network interfaces
I can share and unshare, and then share again the wireless connection to ethernet3 to no avail.
I can successfully ping the IP of the Pi (169.254.66.15, above) from the windows box
I can successfully ping the IP of the Windows box (169.254.11.100, above) from the Pi.
Clearly (I think), this is a windows sharing problem, and not a Pi problem. I guess I should have been more clear that I'm seeking help in getting windows sharing to work properly.

If it is indeed a Microsoft Internet Sharing issue, then Microsoft Support would be the ideal place to start:

https://answers.microsoft.com/en-us/win ... ac86d98fb9
[/quote]

Well... I've already been to that forum. Read through it.
  1. Never had to do this before...
  2. But hey, who knows, so I actually followed through all that & did it earlier today...
  3. ...And it still didn't work, and now I have a virtual host adapter in my listings that I never had before, and appears to do nothing... (that kind of thing is worrisome)
Yes, I understand that we're not all necessarily "experts" in things we're not experts at (I'm living proof), but this forum, so far, seems my most likely bet. I'm hoping someone else has come across this (of course), or knows what it is that's (relatively recently) changed in Win10 that needs to be "fixed"

tomii
Posts: 10
Joined: Tue Dec 25, 2018 11:53 pm

Re: Pi 0 Ethernet Gadget can't reach internet - Windows 10

Wed Dec 26, 2018 8:21 pm

UPDATE:

Getting closer - I just figured out that Windows Defender Firewall is the culprit. Not sure when or what turned it on to block private networks...

So, now the question becomes:
"Should I just turn off firewalls on private networks, or should I try to figure out how to let services through."

I'm hesitant to just shut off private network firewall, as that would include protecting me from some st00pid virus my kids download on their PC (which is on the "private" home network)... But OTOH, it's clearly blocking my PIs.

Looks like I've got some more research to do...

hippy
Posts: 5613
Joined: Fri Sep 09, 2011 10:34 pm
Location: UK

Re: Pi 0 Ethernet Gadget can't reach internet - Windows 10

Wed Dec 26, 2018 8:37 pm

tomii wrote:
Wed Dec 26, 2018 8:03 pm
and now I have a virtual host adapter in my listings that I never had before, and appears to do nothing... (that kind of thing is worrisome)
If I recall correctly that's got something to do with setting up a Wi-Fi hotspot, putting a WiFi adapter into AP mode and giving it internet access.

Not sure what rabbit hole you went down there. Good news is it shouldn't be a problem but it's worth checking with a mobile phone or something that your PC isn't advertising itself as an open access point to the internet.

I am not that familiar with W10 ICS but I thought it was just a case of, which ever GUI neteorks are in, selecting ICS and the two or more things to connect; the adapter which goes to the router and the things you want to give access to.

tomii
Posts: 10
Joined: Tue Dec 25, 2018 11:53 pm

Re: Pi 0 Ethernet Gadget can't reach internet - Windows 10

Wed Dec 26, 2018 8:42 pm

No worries.

See update above - problem is with Windows Firewall. Something has turned it on for private networks.

tomii
Posts: 10
Joined: Tue Dec 25, 2018 11:53 pm

Re: Pi 0 Ethernet Gadget can't reach internet - Windows 10

Wed Dec 26, 2018 8:47 pm

UPDATE 2

Potentially(?) solved.

https://social.technet.microsoft.com/Fo ... networking

I'll have to look and see if this works across multiple PIs, though. Don't particularly want to do this separately for every Pi (I have several)

hippy
Posts: 5613
Joined: Fri Sep 09, 2011 10:34 pm
Location: UK

Re: Pi 0 Ethernet Gadget can't reach internet - Windows 10

Wed Dec 26, 2018 8:50 pm

Please don't edit your original post. It just becomes confusing as to what you had, what has changed, where you are now, and whether information included refers to what you had or what you have now.

hippy
Posts: 5613
Joined: Fri Sep 09, 2011 10:34 pm
Location: UK

Re: Pi 0 Ethernet Gadget can't reach internet - Windows 10

Wed Dec 26, 2018 8:54 pm

tomii wrote:
Wed Dec 26, 2018 8:42 pm
See update above - problem is with Windows Firewall. Something has turned it on for private networks.
Or Windows didn't automatically turn it off because you haven't got something right.

Ernst
Posts: 1191
Joined: Sat Feb 04, 2017 9:39 am
Location: Germany

Re: Pi 0 Ethernet Gadget can't reach internet - Windows 10

Wed Dec 26, 2018 9:33 pm

hippy wrote:
Wed Dec 26, 2018 8:54 pm
tomii wrote:
Wed Dec 26, 2018 8:42 pm
See update above - problem is with Windows Firewall. Something has turned it on for private networks.
Or Windows didn't automatically turn it off because you haven't got something right.
which is very likely if the RNDIS interface has an IP address in the 169.254.0.0/16 range instead of 192.168.137.1/24
The road to insanity is paved with static ip addresses

Ernst
Posts: 1191
Joined: Sat Feb 04, 2017 9:39 am
Location: Germany

Re: Pi 0 Ethernet Gadget can't reach internet - Windows 10

Wed Dec 26, 2018 9:42 pm

My apologies that I was offline for a while, I had some work to do.

As I do not have a Windows 10 system available I used a spare Windows 7 notebook and a spare Pi 0 W with g_ether.
After a few tries I got it to work, helps if dtoverly is spelled correctly, and the RNDIS driver is installed, and the ssh keys are generated correctly (failed somehow because of causing a power loss to reboot), after sharing the WiFi interface with the Pi interface the PC has the IP-address 192.168.137.1 while the Pi receives a random address in the same network which can easily be found with arp -a. Did not ssh, used ping to check the connection.
The road to insanity is paved with static ip addresses

tomii
Posts: 10
Joined: Tue Dec 25, 2018 11:53 pm

Re: Pi 0 Ethernet Gadget can't reach internet - Windows 10

Thu Dec 27, 2018 8:19 pm

hippy wrote:
Wed Dec 26, 2018 8:50 pm
Please don't edit your original post. It just becomes confusing as to what you had, what has changed, where you are now, and whether information included refers to what you had or what you have now.
sorry... was just trying to get the answers up top so someone (later) wouldn't have to work through all the mess, unless they really needed/wanted to.

tomii
Posts: 10
Joined: Tue Dec 25, 2018 11:53 pm

Re: Pi 0 Ethernet Gadget can't reach internet - Windows 10

Thu Dec 27, 2018 8:20 pm

Ernst wrote:
Wed Dec 26, 2018 9:33 pm
hippy wrote:
Wed Dec 26, 2018 8:54 pm
tomii wrote:
Wed Dec 26, 2018 8:42 pm
See update above - problem is with Windows Firewall. Something has turned it on for private networks.
Or Windows didn't automatically turn it off because you haven't got something right.
which is very likely if the RNDIS interface has an IP address in the 169.254.0.0/16 range instead of 192.168.137.1/24
Do you know how to change the RNDIS settings for allowed ranges - or have a link to how? It's doing this with both PCs... Never really noticed before, as it was working fine previously.

Ernst
Posts: 1191
Joined: Sat Feb 04, 2017 9:39 am
Location: Germany

Re: Pi 0 Ethernet Gadget can't reach internet - Windows 10

Thu Dec 27, 2018 8:42 pm

tomii wrote:
Thu Dec 27, 2018 8:20 pm
Ernst wrote:
Wed Dec 26, 2018 9:33 pm
hippy wrote:
Wed Dec 26, 2018 8:54 pm

Or Windows didn't automatically turn it off because you haven't got something right.
which is very likely if the RNDIS interface has an IP address in the 169.254.0.0/16 range instead of 192.168.137.1/24
Do you know how to change the RNDIS settings for allowed ranges - or have a link to how? It's doing this with both PCs... Never really noticed before, as it was working fine previously.
RNDIS ranges are automatic, under the normal conditions Windows will assign 192.168.137.x. (see http://www.tomshardware.co.uk/faq/id-19 ... range.html for more information).

169.254.x.x is a private network address that is used by Windows (and Raspbian) when the interface configured for DHCP is unable to obtain an address from the DHCP server.

If, after configuring ICS, the shared interface address does not have a 192.168.137.x address but 169.254.x.x it means that the ICS configuration failed AND the interfaces will tried to obtain an address from DHCP server which failed and the DHCP client assigned a random 169.254.x.x address.

What this means is that ICS on the PC has not been configured properly, if done right there is no need to change the address ranges.
The road to insanity is paved with static ip addresses

tomii
Posts: 10
Joined: Tue Dec 25, 2018 11:53 pm

Re: Pi 0 Ethernet Gadget can't reach internet - Windows 10

Mon Dec 31, 2018 7:48 pm

Ernst wrote:
Thu Dec 27, 2018 8:42 pm
tomii wrote:
Thu Dec 27, 2018 8:20 pm
Ernst wrote:
Wed Dec 26, 2018 9:33 pm


which is very likely if the RNDIS interface has an IP address in the 169.254.0.0/16 range instead of 192.168.137.1/24
Do you know how to change the RNDIS settings for allowed ranges - or have a link to how? It's doing this with both PCs... Never really noticed before, as it was working fine previously.
RNDIS ranges are automatic, under the normal conditions Windows will assign 192.168.137.x. (see http://www.tomshardware.co.uk/faq/id-19 ... range.html for more information).

169.254.x.x is a private network address that is used by Windows (and Raspbian) when the interface configured for DHCP is unable to obtain an address from the DHCP server.

If, after configuring ICS, the shared interface address does not have a 192.168.137.x address but 169.254.x.x it means that the ICS configuration failed AND the interfaces will tried to obtain an address from DHCP server which failed and the DHCP client assigned a random 169.254.x.x address.

What this means is that ICS on the PC has not been configured properly, if done right there is no need to change the address ranges.
Followed the link (to Tom's Hardware). My settings are correct (i.e. 192.168.x.x)

Interesting bit - on one PC, I turned off the Domain section, and everything started to (seem to) work. (I haven't checked the IPs, yet). What makes it even more interesting is that when I turned the domain rules back on, it continued to work. Even after a reboot of both thw Windows box and the pi.

truly confuzzled.

Return to “Troubleshooting”