• Content Count

  • Joined

  • Last visited

About Franky66

  • Rank

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. Yes I found one after a hint from another person. This is what I did in changing default iptables usage: After changing iptables usage it worked: Switching to the legacy version: # update-alternatives --set iptables /usr/sbin/iptables-legacy # update-alternatives --set ip6tables /usr/sbin/ip6tables-legacy # update-alternatives --set arptables /usr/sbin/arptables-legacy # update-alternatives --set ebtables /usr/sbin/ebtables-legacy
  2. The corresponding entry in syslog in long: dockerd[3322]: time="2020-05-04T19:34:03.278587409+02:00" level=error msg="Handler for POST /v1.40/networks/create returned error: Failed to program FILTER chain: iptables failed: iptables --wait -I FORWARD -o br-c723c76c6721 -j DOCKER: iptables v1.8.2 (nf_tables): RULE_INSERT failed (Invalid argument): rule in chain FORWARD\n (exit status 4)"
  3. Hi there, I have just do a fresh install of armbian (Armbian_20.02.5_Odroidn2_buster_legacy_4.9.216) on odroid n2 and installed omv 5 via armbian softy tool. Docker was installed via omv gui - omv extras - docker / portainer. When I now try to setup a separate network in docker / bridged mode I get the following error: docker network create --driver=bridge --subnet= --gateway= home Error response from daemon: Failed to program FILTER chain: iptables failed: iptables --wait -I FORWARD -o br-7a5194cdef64 -j DOCKER: iptables v1.8.2 (nf_tables): RULE_INSERT failed (Invalid argument): rule in chain FORWARD (exit status 4) Searching google doesn't find a possible solution. Anyone here that have a hint for this?
  4. @maxlinux2000 the actual setup is working fine for me. Igor give the right hint for tuning the log destination. I will check this. If I understand right, armbian is configured for delay write the log files to disk (specially sd cards) so that the sd cards are longer usable during less writing. Removing the partitions is not useful as a lot of linux services need this standard locations :-) @Igor Thankx for your hint. I was not sure were armbian is configured for the ram log disk. So will have a look and tune.
  5. I went into a problem after setting up mariadb / nextcloud installation nativ on my armbian installation odroid n2. per default the logfiles for mariadb (bin files) are logged to /var/log which is only 50 mb because of in memory usage (zram). So after some usage the whole installation stucked because of "out of disk usage" in /var/log. So I stopped nginx, php and mariadb and created a new logfile location in /var/log.mariadb and changed the necessary entries in /etc/mysql/my.conf and started the necessary services again. For now the usage is propper again in /var/log. Maybe this is useful for other people or other had another solution for this. Regards
  6. @Igor My big thank to you for your work. I will check the images and will give feedback for errors etc.
  7. Hello Igor, sorry for asking but did you find some time for fixing the buster image for the odroid n2?
  8. Ok no problem I will just wait until you can fix it.
  9. I would like to test the buster image on my odroid n2 but in the download sections the older image stretch is still available. Did I look wrong?
  10. After waiting for a long time and discussing with my local reseller I got today a new odroid n2 with mac adress "ether 00:1e:06:42:1b:1f". Plugged in everything, bootet armbian or your own ubuntu image and got perfect network gigabit speed without problems. Tried the same with the original odroid n2 still lying here for sending it back and poor performance. so the old odroid n2 has some bug with the network card and will now be returned. happy now to get starting building up my new odroid n2 to replace the raspi 3b.
  11. Just found one usb 3.0 ethernet adapter and connected it to the N2 and to the "old" network cable, voila working : [ 1550.073189] ax88179_178a 2-1.4:1.0 eth1: register 'ax88179_178a' at, ASIX AX88179 USB 3.0 Gigabit Ethernet, 74:da:38:4a:28:23 [ 1550.073308] usbcore: registered new interface driver ax88179_178a [ 1550.161967] IPv6: ADDRCONF(NETDEV_UP): eth1: link is not ready [ 1550.492764] IPv6: ADDRCONF(NETDEV_UP): eth1: link is not ready [ 1553.102308] ax88179_178a 2-1.4:1.0 eth1: ax88179 - Link status is: 1 [ 1553.110418] IPv6: ADDRCONF(NETDEV_CHANGE): eth1: link becomes ready Incoming traffic [ ID] Interval Transfer Bandwidth [ 4] 0.00-10.00 sec 1013 MBytes 850 Mbits/sec sender [ 4] 0.00-10.00 sec 1013 MBytes 850 Mbits/sec receiver Outgoing traffic [ ID] Interval Transfer Bandwidth Retr [ 4] 0.00-10.00 sec 845 MBytes 709 Mbits/sec 0 sender [ 4] 0.00-10.00 sec 844 MBytes 708 Mbits/sec receiver
  12. As I wrote in the odroid forum I did also some ping tests from the petiboot shell and with different paket sizes the N2 loses 1 - 2 pakets per 10 pakets to different targets. Maybe the N2 has a hardware problem.
  13. Hi yes actually I changed the setup but without any success. The N2 is still the problem with his own network access. For now I tested with: - armbian ubuntu latest build for N2 and switch to nightly build with all updates - Cat 5e cables 1 m / 10 m - Cat 6 cables 3 m / 5 m N2 connected to FritzBox directly or to LAN Switch HP PS1810-8G. Crosschecked iperf3 with two raspi's modell 3. Yes the had a problem on an unmanaged switch between the 100 mbit and 1 gbit modell after 10 sec. if I do iperf between them. so I connected them back to the fritzbox and put the unmanaged switch away. On my HP PS1810 I have windows client / server etc. connected and all with gigabit speed without any problem or so such lazy speed. Maybe the people at odroid have some more hint. I saw only ONE difference between Igor's N2 and mine on comparing the support output: eth0: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN group default qlen 1000 -> my N2 eth0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc fq_codel state DOWN group default qlen 1000 -> Igor's N2
  14. It would be nice to know which hardware revision you board is. My board has revision 0.4 with the plastic case from hardkernel. Ticket in odroid forum discussing this problem:
  15. Ok thankx for this important understanding for me. I thought already that there are small to no changes between the os images as the network kernel driver etc. was the same in all os versions. so I will switch to the armbian ubuntu image and will do some more testing. got two new different length network cables here from work and test again with them.