Can you really modify vlan0ports in NVRAM?

Discussion in 'Tomato Firmware' started by Horia Giurgiu, Oct 28, 2011.

  1. Horia Giurgiu

    Horia Giurgiu Networkin' Nut Member

    When I started to play with VLANs I found something very odd: every attempt to modify vlan0ports was unsuccessful. Here is the smallest test sequence:

    nvram set vlan0ports='3 2 1 5*'
    nvram commit

    and next time you check

    nvram set vlan0ports

    you will get always

    3 2 1 0 5*

    I know that I can use init script. But why can I change everything in nvram except this?

    I use a Linksys WRT54GL v1.1
    I test this odd behavior in TeaMan (last 3), ToastMan (last), TomatoUSB (last std) and finallly with Tomato 1.28 and 1.25 releases. All tested firmwares displayed the same result.
    You can change vlan1ports or other vlan ports but vlan0ports value is the same after every reboot.
  2. mstombs

    mstombs Network Guru Member

  3. Horia Giurgiu

    Horia Giurgiu Networkin' Nut Member

    Thanks. Finally I found the explanation: Some routers (with BCM5352E chipset (?)), when manual_boot_nv is set to the default value of 0, the vlan0ports and vlan1ports nvram variables get reset at boot time.

    The solution is so set also manual_boot_nv to 1 before commit so next time at boot the vlan0ports and vlan1ports will not be reseted to the default values.

    nvram set vlan0ports="3 2 1 5*"
    nvram set manual_boot_nv=1
    nvram commit
  1. This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
    By continuing to use this site, you are consenting to our use of cookies.
    Dismiss Notice