Netgate Discussion Forum
    • Categories
    • Recent
    • Tags
    • Popular
    • Users
    • Search
    • Register
    • Login

    SG-1100 Upgrade Experience and Issues

    Scheduled Pinned Locked Moved 2.5 Development Snapshots (Retired)
    2 Posts 2 Posters 316 Views
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • S
      sd023fas
      last edited by sd023fas

      I upgraded to 2.5 last night with build 20201120-0650.

      Experience was good overall. It took over 2 hours to complete the process, but I believe that had more to do with my download speed and distance being located in Pakistan.

      A few issues I have seen:

      1. Package manager and the "update system" (https://xxxx/pkg_mgr_installed.php/*) seems broken. They hang and never load installing a package or retrieving build version/new updates under 2.5 DEVEL branch.

      2. Upon first boot, all my interfaces changed MAC address and defaulted to the mvneta0 MAC address. This broke MAC binding for my PPPoE WAN. I tried to use MAC spoofing under WAN interface to use old WAN MAC address, but this appeared to do nothing. I took pcaps using a hub between pfsense WAN interface and my ISP and confirmed the spoofed MAC address was not used.

      The default VLANs on SG1100 (4090, 4091, 4092) and 3 other VLAN's all have the same MAC address of mvneta0 00:51:82:11:22:00.

      I'm not too keen to reboot at this time because my ISP provides IP's from 3 different subnets, and the subnet I got an IP from appears to have less strict DPI and blocking/rate limiting. This may sound ridiculous, but it's what I've found after requesting a new IP dozens of time until I get an IP from "working" subnet that lets my OpenVPN connection work back home in TX.

      1 Reply Last reply Reply Quote 0
      • stephenw10S
        stephenw10 Netgate Administrator
        last edited by

        Hmm, sounds like you may have hit a known upgrade issue that will require some uboot envs to be reset. Unfortunately that means rebooting. Though there is no urgency since is will boot an run fine with the default values as you have found.

        You will probably need to set at a minimum the envs for ethaddr and serial. Both of which are written on the bottom of the device.

        To do so connect to the serial console and reboot the device.
        Interrupt the boot were you see Hit any key to stop autoboot to reach the 'Marvell>>' prompt (uboot).
        At that prompt enter the following commands:

        setenv ethaddr=f0:ad:4e:XX:XX:XX
        setenv serial NTGXXXXXXXXXX
        saveenv
        reset
        

        Replacing those values with those from your own device obviously.
        It should then boot back up to the expected MAC.

        Steve

        1 Reply Last reply Reply Quote 0
        • First post
          Last post
        Copyright 2025 Rubicon Communications LLC (Netgate). All rights reserved.