I have one of these routers I attempted to upload firmware from the gui and now I cannot access it and no wifi networks show up.
I can access the serial console and attempted to run a TFTP server from my pc in order to re-flash but it just times out when I try to load the firmware from the server.
I have the IP of the server set to 0.0.0.0:69 when I try to set it to 10.10.10.3 (per the wiki) The server on my pc won’t start and gives an error. I know it’s probably a network setting that won’t let me set the correct ip address, just not sure where to go from here. Any help is appreciated.

  • PriorityMotif@lemmy.worldOP
    link
    fedilink
    English
    arrow-up
    3
    ·
    edit-2
    1 day ago

    I was correct that it is a networking error
    cannot bind to local IPv4 socket: Cannot assign requested address

    current ifconfig says:

    enp7s0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500 inet 169.254.210.0 netmask 255.255.0.0 broadcast 169.254.255.255 inet6 fe80::9a40:bbff:fe28:459b prefixlen 64 scopeid 0x20<link> ether 98:40:bb:28:45:9b txqueuelen 1000 (Ethernet) RX packets 15 bytes 900 (900.0 B) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 1466 bytes 492951 (492.9 KB) TX errors 0 dropped 78 overruns 0 carrier 0 collisions 0

    • tal@lemmy.today
      link
      fedilink
      English
      arrow-up
      3
      ·
      edit-2
      1 day ago

      cannot bind to local IPv4 socket: Cannot assign requested address

      inet 169.254.210.0

      Yeah. That’ll be that you’re needing an interface with that address assigned.

      ifconfig

      Going from memory, I believe that if you’ve got ifconfig available and this is a Linux system and you need to keep the address on the current interface to keep the system connected to the Internet or something, you can use something like ifconfig enp7s0:0 10.10.10.3 to use an interface alias, use both addresses (169.254.210.0 and 10.10.10.3) at the same time. Might also need ifconfig enp7s0:0 up after that. That being said, (a) I don’t think that I’ve set up an interface alias in probably a decade, and it’s possible that’s something has changed, (b) that’s a bit of additional complexity, and if you aren’t super familiar with Linux networking, you might not want to add more complexity if you don’t mind dropping just setting the address on the interface to something else.

      Probably an iproute2-based approach to do this too (the ip command rather than the ifconfig command) but I haven’t bothered to pick up iproute2 equivalents for a bunch of stuff.

      EDIT: Sounds like you can assign the address and bring the interface alias up as one step (or could a decade ago, when this comment was written):

      https://askubuntu.com/questions/585468/how-do-i-add-an-additional-ip-address-to-an-interface-in-ubuntu-14

      To setup eth0:0 alias type the following command as the root user:

      # ifconfig eth0:0 192.168.1.6 up
      

      So probably give ifconfig enp7s0:0 10.10.10.3 up a try, then see if the TFTP server package can bind to the 10.10.10.3 address.

      • non_burglar@lemmy.world
        link
        fedilink
        English
        arrow-up
        2
        ·
        13 hours ago

        An apipa address is a sign that networking is not working as intended. This should be resolved first before assigning a class C private addr manually.