colic

Members
  • Content Count

    8
  • Joined

  • Last visited

  1. Thankyou so much for all your comments and help. I honestly did do my reading, but not what has been pointed out. So I stuffed up. I rebuilt using bionic before reading the last of those comments, but its up and running so Ill see how it goes. The first thing I notice is the CPU is running at 47c instead of 57-60.c I also changed IP address and it instantly changed it without reboot. Two big differences already. In trawling the logs I did notice some DNS messages. Now they make sense. So it looks like pihole was having problems with Jessie as well, just lik
  2. OK, cool. Im happy to do whatever it takes (that doesnt cost me buying another board haha). I thought Id googled the right image to flash for OpiZ - it looks like I stuffed up hahah. Start again.... So let me make sure Ive got this right. Im gong to download Bionic 4.19 from here flash that, and try again. Funnily enough I have a second OPIz with similar problems, but its installed on the other side of the world to me so there's not much I can do about it right now! I cant find the links I used to build the OPIz, but that's where I decided (wrongly) that Je
  3. Thanks for the reply Igor. While Ive been using Linux for a while, Im no expert and very new to Armbian. Your second suggestion first, looks like you're saying to buy a new board as the hardware requirements list this? Is that what you mean? If so, that's probably not going to happen just so I can run pihole!! On your first suggestion, everything tells me I should not edit /etc/network/interfaces directly but use nmtui? Do you mean I should simply edit /etc/network/interfaces ? While this might explain the drops in connectivity it doesnt explain the syslog i
  4. I have a new OPIz running ARMBIAN 5.70 stable Debian GNU/Linux 8 (jessie) 3.4.113-sun8i with Pihole version 4.1 (latest). The Opi is connected only with eth0 with a static IP address. Its running a 32G sandisk Ultra (class 10) with a verified image using Etcher. The CPU is running at around 59c. It's unusable because the OPi keeps losing connectivity. Usually about every 12-24 hours but more frequently at times (sometimes two or three times an hour). So no ping, no ssh, no telnet. Ive implemented some scripts on the OPi to try and track down what's happening. But the
  5. The problem is I cant change the port forward in the router. So having a script with the IP will work, until it changes. Then it's completely useless. I also need to connect to the ethernet, not wifi (which is there only as a backup for access). So its the ethernet, not the wifi, that needs the static IP. So as far as I know nmtui would not help there either. Which is sort og how I ended up where i am !!
  6. Oops, sorry, my browser was open on an old page, didnt see your reply! Well maybe I should change my question then!! The Orange Pi will be located in a physically remote network, accessible by port forward through a router that does not allow reservation of dhcp addresses. So I need a way to know what IP address the Pi will boot up with. How do I do that if not through a static IP in interfaces? I do see plenty of posts with a static ip setup. So I think it works, its just on boot there's a problem if eth0 isnt there.
  7. Thanks manuti. You're right, that was missing but it wasnt the issue (ie I added it but to no avail). I think the issue is more fundamental. As I mentioned, bith ehternet and wifi already work, and nmtui was used to do the wifi. All good there. Is there anyone out there knows the correct way to do this so that wifi and ehternet come up as available, and you can boot with both or just one? Assume Ive added the dns in my examples since that's now in there with no change.
  8. Im not sure if this is the right forum. Ive also Googled and found similar problems, but no solution that works for me. So Im happy to be LMGTFY with some hints, or shown the right forum :-) Im running an OrangePi Zero on Armbian (lsb_release reports Ubuntu 16.04.3 LTS). I have networking set up with both ethernet and wifi. Both work. But I want to have ethernet as static IP, and wireless as dhcp. My config looks like this: allow-hotplug eth0 iface eth0 inet static address 192.168.4.122 netmask 255.255.255.0 gateway 192.168.4.1 broadcast 192.168.4.