I run Advanced Tomato 136 which is based on Shibby on a Netgear R7000.
For some reason my router will not port forward to anything running on the router itself, such as Transmission, the built in NGINX web server, etc. But port 9091 seems to be open, which is Transmission's port for the gui. I can access it locally but not remotely. I have DDNS set up so I use the name not my WAN IP, which changes from time to time.
I just tried 132 without nvram clear and it didn't work.
I will try it with nvram clear but there is a lot more to it. I need to kick everyone off the network and recreate all my settings. I have a fair amount of that - different MAC, different IP than the default, guest network, DHCP reservations, firewall script, port forwarding, etc.
In my experience when you do nvram clear followed by applying a settings file, usually whatever issue you have returns. So you have to do clear and rebuild everything from scratch. Wish me luck.
w/o nvram clear will not work for sure. Question is when you upgraded from v132 to v136 did you clear nvram? - it is obligatory and will definitely not work if you will not do that. Because from v133 MultiWAN was added there was a lot of changes, different parameters etc and without nvram clear will not work. You cannot even load your confirg from v132 to new v136 after nvram clear and you cannot back to old version the same way.
Orange 300/50 Mb/s + ONT Terminal HPE MS gen8 Proxmox 7.0-11 VMs: Router OPNsense 23.X-amd64 and OMV HPE MicroServer gen8: Xeon E3-1265Lv2, 16GB (2x KTH-PL316E/8G), HP 331T, 4x4TB WD RED Asus RT-AC68U AccessPoint
port forward to anything running on the router itself
port forward you should use if you want forward connections to any of device INSIDE your local network. If server is launched directly on router, then you have to OPEN port(s), not forward them.
Build-in services will open required ports automatically. Make sure that:
1) you erase nvram after install newer version of tomato
2) you have DISABLED DMZ service
3) you don`t configure those port on port forwarding page
That`s it.
Proxmox VE:i5-13400T, 64GB RAM, 2x 512GB NVMe, 3x 2TB SSD, Intel X710-DA2 SFP+ VM Router:OpenWRT 22.03.4 VM NAS:Synology SA6400 VM VPS:Debian, WWW, Home Assistant Switch:Netgear MS510TXPP Switch:Ubiquiti USW-Flex-mini - szt. 2 Wi-Fi:Ubiquiti U6-Lite - szt. 2
Thanks to Shibby and the others that have chimed in.
I did notice in my iptables that 9091 was opened when I use the gui (advanced tomato) to turn on Transmission. On another forum it was suggested I add a rule to open 9091. I did try that but in the end I was really applying the same rule the built in service did automatically. So there are now two duplicate rules for the same port.
I will put it back to 136 with erase nvram when I have a chance. I'm bummed I have to rebuild all the settings from scratch but it is what it is.
Thanks to Shibby and the others that have chimed in.
I did notice in my iptables that 9091 was opened when I use the gui (advanced tomato) to turn on Transmission. On another forum it was suggested I add a rule to open 9091. I did try that but in the end I was really applying the same rule the built in service did automatically. So there are now two duplicate rules for the same port.
I will put it back to 136 with erase nvram when I have a chance. I'm bummed I have to rebuild all the settings from scratch but it is what it is.
I'll post results afterwards.
136 with clear nvram did not work. I will try 132 next. I also read on another forum there actually is a way to save most of your settings and use them after re-flashing and clearing nvram. The only thing is I failed to use a quotation mark in the right place, so I rebuilt most of the settings manually before discovering this... nvram set "...." rather than nvram set ....
Thanks to Shibby and the others that have chimed in.
I did notice in my iptables that 9091 was opened when I use the gui (advanced tomato) to turn on Transmission. On another forum it was suggested I add a rule to open 9091. I did try that but in the end I was really applying the same rule the built in service did automatically. So there are now two duplicate rules for the same port.
I will put it back to 136 with erase nvram when I have a chance. I'm bummed I have to rebuild all the settings from scratch but it is what it is.
Thanks to Shibby and the others that have chimed in.
I did notice in my iptables that 9091 was opened when I use the gui (advanced tomato) to turn on Transmission. On another forum it was suggested I add a rule to open 9091. I did try that but in the end I was really applying the same rule the built in service did automatically. So there are now two duplicate rules for the same port.
I will put it back to 136 with erase nvram when I have a chance. I'm bummed I have to rebuild all the settings from scratch but it is what it is.
Thanks to Shibby and the others that have chimed in.
I did notice in my iptables that 9091 was opened when I use the gui (advanced tomato) to turn on Transmission. On another forum it was suggested I add a rule to open 9091. I did try that but in the end I was really applying the same rule the built in service did automatically. So there are now two duplicate rules for the same port.
I will put it back to 136 with erase nvram when I have a chance. I'm bummed I have to rebuild all the settings from scratch but it is what it is.
I'll post results afterwards.
136 with clear nvram did not work. I will try 132 next. I also read on another forum there actually is a way to save most of your settings and use them after re-flashing and clearing nvram. The only thing is I failed to use a quotation mark in the right place, so I rebuilt most of the settings manually before discovering this... nvram set "...." rather than nvram set ....
Thanks to Shibby and the others that have chimed in.
I did notice in my iptables that 9091 was opened when I use the gui (advanced tomato) to turn on Transmission. On another forum it was suggested I add a rule to open 9091. I did try that but in the end I was really applying the same rule the built in service did automatically. So there are now two duplicate rules for the same port.
I will put it back to 136 with erase nvram when I have a chance. I'm bummed I have to rebuild all the settings from scratch but it is what it is.
I'll post results afterwards.
Połączony z 14 czerwiec 2016 18:06:28:
Thanks to Shibby and the others that have chimed in.
I did notice in my iptables that 9091 was opened when I use the gui (advanced tomato) to turn on Transmission. On another forum it was suggested I add a rule to open 9091. I did try that but in the end I was really applying the same rule the built in service did automatically. So there are now two duplicate rules for the same port.
I will put it back to 136 with erase nvram when I have a chance. I'm bummed I have to rebuild all the settings from scratch but it is what it is.
I'll post results afterwards.
Edytowany przez shredhead1080 dnia 14-06-2016 18:06
· Łącznie użytkowników: 24,115 · Najnowszy użytkownik: Ja
Czat
Musisz się zalogować, aby opublikować wiadomość.
Maniek91PL
06-11-2024 22:37
dzięki !
maxikaaz
29-10-2024 14:27
@Maniek91PL - Administration=> Admin Access, i tam masz "Allow Wireless Access" do zaznaczenia
Maniek91PL
26-10-2024 22:07
siemka! ktoś przypomni co się ustawiało jeśli nie mogę wejść od strony wifi do tomato? od lan działa
overflow2
04-10-2024 17:34
Kupowałem Asusy n10u albo n12d1 ale nie widzę ich, chyba już nie produkują, Chodzi o coś nowego i taniego. Transfery niewielkie.
maxikaaz
04-10-2024 09:38
@overflow2 patrząc po dostępności funkcji w nowych kompilacjach, to chyba nawet WRT54G/GL jeszcze ma OpenVPN, albo jakiś odpowiednik... zależy, na jakie transfery liczysz.
overflow2
30-09-2024 20:53
Jaki aktualnie najtańszy router do tomato do openvpn?
maxikaaz
27-07-2024 15:07
@servee - na początek router do rozebrania i obejrzenia, ciężko wróżyć tak tylko po objawach
maxikaaz
27-07-2024 14:55
@servee - cały kontroler nie pada tak sobie z powodu "zbiegu okoliczności", więc prawdopodobnie gdzieś przepięcie.
servee
25-07-2024 13:33
@maxikaaz: działało, aż pewnego pięknego dnia przestało działać. W tym dniu była też burza, ale to raczej zbieg okoliczności.
maxikaaz
25-07-2024 11:38
@servee - o ile problem jest w obrębie samych wyjść (dławiki, warystory), to naprawialne, ale jeśli w samym SoC - to nienaprawialne ze względu na koszta. A co było przyczyną?
' target='_blank'>Link
