Jump to content

sami

Members
  • Posts

    15
  • Joined

  • Last visited

Posts posted by sami

  1. hello guys,

     

    how to activate bridge mode between the 2 ethernet ports of R2S (WAN and LAN) which are referred to as eth0 and lan0 respectively, so as both of them have the same ip address.

     

    i tried this https://wiki.debian.org/BridgeNetworkConnections#Manual_bridge_setup but when i reach the command which adds interfaces to the bridge (# brctl addif br0 eth0 lan0)then the ssh connection is lost.

     

    i noticed something as well, in interfaces file i added eth0 and lan0 and gave each one a different ip. but then it seems as is now i have two IPs but for the same port (WAN), and no ip for lan port!!!

     

     

  2. I tried things from the beginning now it is not even updating!!!!

     

    root@nanopineo:~# apt update
    Err:1 http://httpredir.debian.org/debian buster InRelease
      Could not resolve 'httpredir.debian.org'
    Err:2 http://security.debian.org buster/updates InRelease
      Could not resolve 'security.debian.org'
    Err:3 http://apt.armbian.com buster InRelease
      Could not resolve 'apt.armbian.com'
    Err:4 http://httpredir.debian.org/debian buster-updates InRelease
      Could not resolve 'httpredir.debian.org'
    Err:5 http://httpredir.debian.org/debian buster-backports InRelease
      Could not resolve 'httpredir.debian.org'
    Reading package lists... Done
    Building dependency tree
    Reading state information... Done
    1 package can be upgraded. Run 'apt list --upgradable' to see it.
    W: Failed to fetch http://httpredir.debian.org/debian/dists/buster/InRelease  Could not resolve 'httpredir.debian.org'
    W: Failed to fetch http://httpredir.debian.org/debian/dists/buster-updates/InRelease  Could not resolve 'httpredir.debian.org'
    W: Failed to fetch http://httpredir.debian.org/debian/dists/buster-backports/InRelease  Could not resolve 'httpredir.debian.org'
    W: Failed to fetch http://security.debian.org/dists/buster/updates/InRelease  Could not resolve 'security.debian.org'
    W: Failed to fetch http://apt.armbian.com/dists/buster/InRelease  Could not resolve 'apt.armbian.com'
    W: Some index files failed to download. They have been ignored, or old ones used instead.


     

  3. I already had armbian buster installed on my nanopi neo core, i recently tried to update and upgrade but here is what m getting: 

     

    root@nanopineo:~# apt update
    Get:1 http://security.debian.org buster/updates InRelease [65.4 kB]
    Get:2 http://httpredir.debian.org/debian buster InRelease [122 kB]
    Get:3 http://httpredir.debian.org/debian buster-updates InRelease [51.9 kB]
    Hit:5 http://httpredir.debian.org/debian buster-backports InRelease
    E: Repository 'http://security.debian.org buster/updates InRelease' changed its 'Suite' value from 'stable' to 'oldstable'
    N: This must be accepted explicitly before updates for this repository can be applied. See apt-secure(8) manpage for details.
    Do you want to accept these changes and continue updating from this repository? [y/N]

     

    the armbian buster image is about 2 years old, 4.19

    so should i go for the newer images such as focal? or what should i do?

     

    anw when i press Y, then i upgrade. if i rebooted the image then the nanopi is dead. i can not access it anymore as if it is not even booting (i can tell from the BLUE LED which no more blinks)

     

  4. i still have another major problem ...

    the baudrate is unknown ... is there any tool that can ignoring setting a baudrate or that can dynamically assign the correct baudrate.

     

    i observed the signal on the oscilloscope and it seems that the baudrate is around 12800 which is not one of the standard baurates.

    and the baudrate is around 12800 might be because this serial data is converted from rs485 to rs232.

    it is confusing

  5. trying to read the serial data from the UART1 port then write it on the  UART2 port ....

    this is absolutely easy in the case of just reading the serial data.

     

    but now what m really trying to do is to read the serial binary bits which includes the serial data and the framing data ( parity bit/stop bit/start bit) and then write all of these binary bits to the other serial port.

     

    how could this be done? how could i read the serial  bits  without the framing bits being stripped? 

     

    thanks in advance

    best regards 

  6. This is the image i downloaded from freepbx https://www.freepbx.org/downloads/ 

    you could view all versions to check the iso images available.

     

    so this image contains freepbx with asterisk.

    i want to install this image on my nanopi neo core but i am afraid if it wont work.

     

    for more information about this operating system

    at my pc :

     

    command: cat /etc/os-release

    output:

    NAME="Sangoma Linux"
    VERSION="7 (Core)"
    ID="sangoma"
    ID_LIKE="centos rhel fedora"
    VERSION_ID="7"
    PRETTY_NAME="Sangoma Linux 7 (Core)"
    ANSI_COLOR="0;31"
    CPE_NAME="cpe:/o:sangoma:sng:7::server:utf8"
    HOME_URL="https://distro.sangoma.net/"
    BUG_REPORT_URL="https://issues.sangoma.net/"

    CENTOS_MANTISBT_PROJECT="Sangoma-7"
    CENTOS_MANTISBT_PROJECT_VERSION="7"
    REDHAT_SUPPORT_PRODUCT="sangoma"
    REDHAT_SUPPORT_PRODUCT_VERSION="7"
     

    command: hostnamectl

    output:
       Static hostname: freepbx.sangoma.local
             Icon name: computer-laptop
               Chassis: laptop
            Machine ID: b230bc99e3f54757988c502759a40135
               Boot ID: e7f281a29a2d47daa7c82fc79d4302a2
      Operating System: Sangoma Linux 7 (Core)
           CPE OS Name: cpe:/o:sangoma:sng:7::server:utf8
                Kernel: Linux 3.10.0-1127.19.1.el7.x86_64
          Architecture: x86-64

     

     

    so does this kind of linux images work on nanopi neo core or not ?

  7. THANKS !!! now I have this image on my pc but how could I write this image to the nanopi neo core without using sd card ?  tried connecting it directly through micro usb cable but it was not observed as a  usb device  it was only observed as a port ! so I could not just simply write it through win32 disk imager.

     

    is it something related to FEL MODE ? and how to check if board supports this mode?

×
×
  • Create New...

Important Information

Terms of Use - Privacy Policy - Guidelines