This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revisionNext revisionBoth sides next revision | ||
faq [2023/05/07 20:48] – [How Do I Choose a Build? (build naming scheme)]-clarity-build number meaning hogwild | faq [2023/05/24 21:02] – [Netgear R-series] hogwild | ||
---|---|---|---|
Line 7: | Line 7: | ||
\\ | \\ | ||
- | * You are in the right place. | + | * You' |
- | * Verify whether your device is supported by your router via the [[hardware_compatibility|Hardware compatibility]] page. Pay attention to the HW revision column and the notes. | + | * Go the [[hardware_compatibility|Hardware compatibility]] page and verify check whether your device is supported by FreshTomato. Read the HW revision column and the notes column. |
- | * Overall, the installation process is relatively safe. Depending on your hardware, there are a recovery procedures to try if things don't go as planned. However, please know that you are fully responsible for any risks involved in upgrading your device to FreshTomato. | + | * Overall, the installation process is relatively safe. Depending on your hardware, there are recovery procedures to try if things don't go as planned. However, please know that you are fully responsible for any risks involved in upgrading your device to FreshTomato. |
* You need to have an Ethernet connection between your client device and a LAN port on the router. | * You need to have an Ethernet connection between your client device and a LAN port on the router. | ||
* You must read and follow the [[firmware_basics_procedures|Installing FreshTomato]] section. This will guide you through all the steps needed. | * You must read and follow the [[firmware_basics_procedures|Installing FreshTomato]] section. This will guide you through all the steps needed. | ||
+ | * There is a lot of information on this wiki. Not all of it is where you might expect to find it. Take a good look around. | ||
Line 18: | Line 19: | ||
//Q: Does FreshTomato support only old devices or newer ones too?// | //Q: Does FreshTomato support only old devices or newer ones too?// | ||
- | \\ A: FreshTomato supports a variety of devices. See the [[hardware_compatibility|Hardware compatibility]] page for more details. Keep a close eye on CPU speed, Ethernet port speed and WiFi speed (with 802.11ac currently supporting the fastest WiFi speed). | + | \\ A: FreshTomato supports a variety of devices. See the [[hardware_compatibility|Hardware compatibility]] page for more details. Keep a close eye on CPU speed, Ethernet port speed and WiFi speed. |
- | Until recently, it would not have been possible to create new releases that support 802.11ax or newer WiFi standards. However, since Broadcom has released some details about their wireless drivers, FreshTomato developers are currently //in the planning stages// of writing firmware for at least one model with 802.11ax. Traditionally, | + | Until recently, it would not have been possible to create new releases that support 802.11ax or newer WiFi standards. However, since Broadcom has released some details about their wireless drivers, FreshTomato developers are currently //in the planning stages// of writing firmware for at least one model that supports the 802.11ax |
Line 51: | Line 52: | ||
| FreshTomato | The Tomato mod name. This is always FreshTomato, | | FreshTomato | The Tomato mod name. This is always FreshTomato, | ||
| Hardware model | Specifies the router or access point model number. | | | Hardware model | Specifies the router or access point model number. | | ||
- | | ARM | Specifies the build is intended for devices with ARM CPU architecture. | | + | | ARM/MIPS | Specifies the build is intended for devices with ARM or MIPS CPU architecture. | |
| Wireless Driver (optional) | NG - Indicates whether the New Generation Broadcom binary wireless driver is in the build. \\ Broadcom never released the driver source code, so developers rely on binary drivers. \\ Builds for newer hardware required the newer wireless driver and a newer software development\\ kit (SDK). | | Wireless Driver (optional) | NG - Indicates whether the New Generation Broadcom binary wireless driver is in the build. \\ Broadcom never released the driver source code, so developers rely on binary drivers. \\ Builds for newer hardware required the newer wireless driver and a newer software development\\ kit (SDK). | ||
| Release name | e.g. 2021.3 | | Release name | e.g. 2021.3 | ||
| Build Type | e.g. (Mini / AIO / VPN) - indicates the features included in the build. See [[: | | Build Type | e.g. (Mini / AIO / VPN) - indicates the features included in the build. See [[: | ||
| NVRAM size | (32K / 64K / 128K) - Optional. For models with multiple hardware revisions \\ where each revision may include more or less NVRAM. | | | NVRAM size | (32K / 64K / 128K) - Optional. For models with multiple hardware revisions \\ where each revision may include more or less NVRAM. | | ||
- | | NOSMP | (Optional) | + | | NOSMP | (Optional) |
| Custom | | Custom | ||
| | Reserved for future use | | | | Reserved for future use | | ||
Line 83: | Line 84: | ||
The other subfolders such as K26RT-AC and K26RT-N contain dedicated builds, meant for specific router models. Unless you're experienced, | The other subfolders such as K26RT-AC and K26RT-N contain dedicated builds, meant for specific router models. Unless you're experienced, | ||
+ | |||
+ | If you have a Netgear R-series router with Netgear firmware installed, you must first flash with one of the " | ||
\\ | \\ | ||
Line 103: | Line 106: | ||
===== Device Name Defaults ===== | ===== Device Name Defaults ===== | ||
- | //Q: What are the common device names used to represent router interfaces/ | + | //Q: What are some common device names used to represent router interfaces/ |
- | \\ | + | |
+ | |||
+ | * ethX: is a physical interface. It can be used to represent Ethernet of WiFi interfaces. | ||
+ | * wlX: identifies a physical wireless interface. It is often associated with an eth reference. | ||
+ | * brX: is a logical interface. It bridges together two physical interfaces. | ||
+ | * vlanX: identifies a VLAN (a logical separation). | ||
+ | * tunXX: is an OpenVPN interface. (for example, tun13 = client3, tun21 = server1) | ||
+ | * tinc: is a logical tunnel interface used by tinc VPN technology. | ||
+ | * wg0: is an interface used by Wireguard. | ||
+ | |||
+ | Some structures, like additional SSIDs (Virtual Wireless) will create sub-interfaces. For this reason, it's common to see interfaces with periods in them. For example, wl0.2 would represent the second alias of the first WiFi radio. | ||
- | * vlan0: Wired (Ethernet) LAN ports | ||
- | * eth1: Wireless LAN | ||
- | * br0: Internal LAN bridge (configurable) for wired LAN and Wireless LAN | ||
- | * eth0: internal interface between CPU and the 6-port switch | ||
===== Log Location Default ===== | ===== Log Location Default ===== | ||
Line 138: | Line 147: | ||
Read more at: [[https:// | Read more at: [[https:// | ||
- | ===== GUI is Slow or not Responding ===== | + | ===== The Web Interface (GUI) is Slow or not Responding ===== |
//Q: The GUI is slow. Is this normal?// | //Q: The GUI is slow. Is this normal?// | ||
Line 163: | Line 172: | ||
\\ | \\ | ||
- | If you have the Original Netgear firmware installed, use these files to install FreshTomato | + | If you have the Original Netgear firmware installed, |
+ | |||
+ | After you' | ||
Line 230: | Line 241: | ||
Assuming there is no pin enabled, FreshTomato sets the // | Assuming there is no pin enabled, FreshTomato sets the // | ||
- | nvram set modem_pin= "" | + | '' |
+ | nvram set modem_pin= "" | ||
- | nvram commit | + | nvram commit'' |
If the card does have a PIN set, the variable must be set in nvram: | If the card does have a PIN set, the variable must be set in nvram: | ||
- | nvram set modem_pin= " | + | '' |