Jump to content

awef

Members
  • Posts

    43
  • Joined

  • Last visited

Everything posted by awef

  1. well... a few reboots later (no additional file changes) and things are working nicely with "no /etc/network/interfaces" and whatever random is left of network manager nmcli m # Monitoring - shows pretty responsive output to connect/disconnect hardwired eth0 But.. Yeah okay SSHD no longer connecting again with eth0 disconnected... erm after reboot now it works again...
  2. Okay so FYI: removed /etc/network/interfaces used nmtui to disconnect/reconnect interfaces reboot sshd will not connect if only wlan0 online Mac -> OPizero : ARP, respond, picked up by wireshark/tcpdump on both computers OPIZero -> Mac : ARP, respond, wireshark shows ARP response from Mac -> Router; OPiZero does not get ARP response on tcpdump With ethernet plugged in, SSH to wlan0 ip results in 2 ARP replies from OPiZero (#1 with eth0 mac, #2 with wlan0 mac); Mac then connects via OPiZero eth0 but with wlan0's IP address (of course Mac is just confused) Anyways, summary: removing /etc/network/interfaces is "not enough" If wlan0 works with eth0 is connected, it's because eth0 replies to ARP requests for wlan0's IP address with eth0's MAC address
  3. Ah okay, pardon me. I didn't realize I had to go and "empty out" /etc/network/interfaces. I was under the impression that simply using nmtui-connect "first" was sufficient. Let me try an empty interfaces (or something close to that) and see how it goes. (interfaces was never my favorite file anyways)
  4. Hmmm... but that still doesn't answer why connecting wired ethernet to the OPi Zero then allows the macbook to respond to arps... hmmm...
  5. After more checking, it's almost 99% sure that the Macbook is the problem. Doing some packet dumps on both devices, I see that the OPi Zero is requesting ARPs, but the Mac refuses to answer On the other hand, the Mac makes ARP requests and gets responses from the OPi Zero. Disable/Renabling the WiFi on the Mac fixes this problem OSX 10.11.6 (15G1108)
  6. tao - well I guess that automation is always nice in some sense.. but sometimes less automation is nicer for those of us who "know exactly" what we want to do.
  7. tao - Yeah on the OPi Zero size, it was unable to resolve arp for the Mac. Seems the problem has come up again, so I'm looking into it more.
  8. Folks, thanks all for hanging in there with me. I got another device on the wifi network which had no problems being pinged (thanks arox for the idea) So I suspected that perhaps it was my mac that wasn't responding to arp requests correctly. After resetting my mac and reflashing the SD card (non beta) and using nmtui-connect, sshd responds normally as I would expect. So as far as I can tell, the only bug I could find today was my mac not responding to arp Now as far as why connecting wired ethernet to the OPi Zero makes any difference, I have no idea. That is totally beyond me. Any ideas? Could my mac have been so crazy to only answer arp requests from a wired OPi interface? That's just too crazy to believe.
  9. Thanks tkaiser for the suggestion to remove items from network/interfaces. I'll give it a shot and see if that helps NetworkManager. arox: thanks for the comment, I'll see what I can gather from ip *
  10. Downloaded beta: Armbian_5.24.161118_Orangepizero_Ubuntu_xenial_3.4.113.img Imaged with etcher, verified nmtui-connect iwconfig wlan0 power off Same issue, ssh to wlan0 does not connect. Adding a cable to eth0 later enables wlan0 IP to accept ssh.
  11. My goodness... Did I just miss the entire link? Or did it just appear? downloading now. Testing probably in a day.
  12. Is there a planned OPi Zero beta image coming down the pipe? or should I use an "alternate"?
  13. After another reboot, now the OPi zero again refuses ssh connections via wifi, but gets to the internet just fine.
  14. Reimage Armbian_5.24_Orangepizero_Ubuntu_xenial_3.4.113.img root@orangepizero:~# nmtui-connect root@orangepizero:~# ifconfig -a eth0 Link encap:Ethernet HWaddr 2e:2c:9f:81:79:89 inet6 addr: fe80::2c2c:9fff:fe81:7989/64 Scope:Link UP BROADCAST MULTICAST MTU:1500 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:4 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:0 (0.0 TX bytes:580 (580.0 Interrupt:114 lo Link encap:Local Loopback inet addr:127.0.0.1 Mask:255.0.0.0 inet6 addr: ::1/128 Scope:Host UP LOOPBACK RUNNING MTU:16436 Metric:1 RX packets:2 errors:0 dropped:0 overruns:0 frame:0 TX packets:2 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:98 (98.0 TX bytes:98 (98.0 tunl0 Link encap:IPIP Tunnel HWaddr NOARP MTU:1480 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:0 (0.0 TX bytes:0 (0.0 wlan0 Link encap:Ethernet HWaddr 7c:c2:4d:f8:71:bc # Wow yet another MAC? inet addr:192.168.10.123 Bcast:192.168.10.255 Mask:255.255.255.0 inet6 addr: fe80::7ec2:4dff:fef8:71bc/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:34 errors:0 dropped:0 overruns:0 frame:0 TX packets:28 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:12223 (12.2 KB) TX bytes:5086 (5.0 KB) $ ssh root@192.168.10.123 The authenticity of host '192.168.10.123 (192.168.10.123)' can't be established. ECDSA key fingerprint is SHA256:fH/CYJODVoEXuDhCD4FoR8Z/LMT9T+ony4t/fwbiKLI. Are you sure you want to continue connecting (yes/no)? yes Warning: Permanently added '192.168.10.123' (ECDSA) to the list of known hosts. root@192.168.10.123's password: ___ ____ _ _____ / _ \ _ __ __ _ _ __ __ _ ___ | _ \(_) |__ /___ _ __ ___ | | | | '__/ _` | '_ \ / _` |/ _ \ | |_) | | / // _ \ '__/ _ \ | |_| | | | (_| | | | | (_| | __/ | __/| | / /| __/ | | (_) | \___/|_| \__,_|_| |_|\__, |\___| |_| |_| /____\___|_| \___/ |___/ Welcome to ARMBIAN Ubuntu 16.04.1 LTS 3.4.113-sun8i System load: 0.80 Up time: 1 min Memory usage: 7 % of 494Mb IP: 192.168.10.123 CPU temp: 36°C Usage of /: 16% of 7.2G Last login: Mon Nov 14 07:45:07 2016 root@orangepizero:~# -- So looks like nmtui-connect worked once, and didn't work once. wlan0 MAC address continues to change after imaging. So interesting
  15. Did brand new flash of Armbian_5.24_Orangepizero_Ubuntu_xenial_3.4.113.img Used nmtui-connect to connect to Wifi wlan0 up wlan0 Link encap:Ethernet HWaddr 1c:93:63:d0:e6:17 inet addr:192.168.10.122 Bcast:192.168.10.255 Mask:255.255.255.0 inet6 addr: fe80::1e93:63ff:fed0:e617/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:172 errors:0 dropped:0 overruns:0 frame:0 TX packets:140 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:29254 (29.2 KB) TX bytes:15171 (15.1 KB) Routing table looks good: root@orangepizero:~# netstat -rn Kernel IP routing table Destination Gateway Genmask Flags MSS Window irtt Iface 0.0.0.0 192.168.10.1 0.0.0.0 UG 0 0 0 wlan0 192.168.10.0 0.0.0.0 255.255.255.0 U 0 0 0 wlan0 Ping is good root@orangepizero:~# ping 192.168.10.1 PING 192.168.10.1 (192.168.10.1) 56(84) bytes of data. 64 bytes from 192.168.10.1: icmp_seq=1 ttl=64 time=44.8 ms SSHD running root@orangepizero:~# netstat -an |grep LIS tcp 0 0 127.0.1.1:53 0.0.0.0:* LISTEN tcp 0 0 0.0.0.0:22 0.0.0.0:* LISTEN tcp6 0 0 :::22 :::* LISTEN DNS and internet good: root@orangepizero:~# curl google.com <HTML><HEAD><meta http-equiv="content-type" content="text/html;charset=utf-8"> <TITLE>302 Moved</TITLE></HEAD><BODY> <H1>302 Moved</H1> The document has moved <A HREF="http://www.google.co.kr/?gfe_rd=cr&ei=fO4vWJXtPMjC8gfxtY2wBw">here</A>. </BODY></HTML> Arp from another computer is good: $ arp 192.168.10.122 ? (192.168.10.122) at 1c:93:63:d0:e6:17 on en0 ifscope [ethernet] Ping to router from another computer is good: $ ping 192.168.10.1 PING 192.168.10.1 (192.168.10.1): 56 data bytes 64 bytes from 192.168.10.1: icmp_seq=0 ttl=64 time=4.758 ms Ping to OPi Zero fails $ ping 192.168.10.122 PING 192.168.10.122 (192.168.10.122): 56 data bytes Request timeout for icmp_seq 0 Request timeout for icmp_seq 1 SSH to OPi zero fails $ ssh root@192.168.10.122 Interestingly enough after imaging the SD card, each time my wlan0 mac address is different. Is this normal? # wlan0 Link encap:Ethernet HWaddr 4c:3a:0e:8d:84:f0 Debian # wlan0 Link encap:Ethernet HWaddr 0c:2a:42:8b:9a:98 Ubuntu Try 1 # wlan0 Link encap:Ethernet HWaddr 1c:93:63:d0:e6:17 Ubuntu Try 2 Connect ethernet, get NO DHCP root@orangepizero:~# ifconfig eth0 Link encap:Ethernet HWaddr 2e:2c:9f:81:79:89 inet6 addr: fe80::2c2c:9fff:fe81:7989/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:3 errors:0 dropped:0 overruns:0 frame:0 TX packets:4 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:628 (628.0 TX bytes:580 (580.0 Interrupt:114 lo Link encap:Local Loopback inet addr:127.0.0.1 Mask:255.0.0.0 inet6 addr: ::1/128 Scope:Host UP LOOPBACK RUNNING MTU:16436 Metric:1 RX packets:64 errors:0 dropped:0 overruns:0 frame:0 TX packets:64 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:5530 (5.5 KB) TX bytes:5530 (5.5 KB) wlan0 Link encap:Ethernet HWaddr 1c:93:63:d0:e6:17 inet addr:192.168.10.122 Bcast:192.168.10.255 Mask:255.255.255.0 inet6 addr: fe80::1e93:63ff:fed0:e617/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:244 errors:0 dropped:0 overruns:0 frame:0 TX packets:185 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:45849 (45.8 KB) TX bytes:18990 (18.9 KB) root@orangepizero:~# netstat -rn Kernel IP routing table Destination Gateway Genmask Flags MSS Window irtt Iface 0.0.0.0 192.168.10.1 0.0.0.0 UG 0 0 0 wlan0 192.168.10.0 0.0.0.0 255.255.255.0 U 0 0 0 wlan0 Looks like everything still going to wlan0 Try ssh again $ ssh root@192.168.10.122 The authenticity of host '192.168.10.122 (192.168.10.122)' can't be established. ECDSA key fingerprint is SHA256:GxAvZHUQMY7qQRwewozdSF9CVf/VFiCsTrsa2BVARlA. Are you sure you want to continue connecting (yes/no)? yes Warning: Permanently added '192.168.10.122' (ECDSA) to the list of known hosts. root@192.168.10.122's password: ___ ____ _ _____ / _ \ _ __ __ _ _ __ __ _ ___ | _ \(_) |__ /___ _ __ ___ | | | | '__/ _` | '_ \ / _` |/ _ \ | |_) | | / // _ \ '__/ _ \ | |_| | | | (_| | | | | (_| | __/ | __/| | / /| __/ | | (_) | \___/|_| \__,_|_| |_|\__, |\___| |_| |_| /____\___|_| \___/ |___/ Welcome to ARMBIAN Ubuntu 16.04.1 LTS 3.4.113-sun8i System load: 0.00 Up time: 9 min Memory usage: 6 % of 494Mb IP: 192.168.10.122 CPU temp: 37°C Usage of /: 16% of 7.2G Last login: Sat Nov 19 06:12:43 2016 Wow isn't that just a crazy thing? I can ssh to the opi zero wifi IP if my ethernet is plugged in.
  16. thanks for the pointers. I'll give it a shot a little later.
  17. Is anyone else having issues getting incoming ssh to work with their OPI zero? I've tried both: Armbian_5.24_Orangepizero_Debian_jessie_3.4.113.img and Armbian_5.24_Orangepizero_Ubuntu_xenial_3.4.113.img In both cases I was able to get a WiFi connection, and am able to get out to the internet to download new packages (apt-get). However, I can't seem to get incoming ssh or ping to work. It's as if the device is invisible.
×
×
  • Create New...

Important Information

Terms of Use - Privacy Policy - Guidelines