28 Marca 2024 15:28:16
Nawigacja
· Strona Główna
· Forum

· Tomato by Shibby
· FreshTomato


Wątki na forum
Najnowsze dyskusje
· [MOD] Tomato64 (x86-64)
· [Howto] Xpenology na...
· [MOD] FreshTomato-AR...
· Optware na CIFS
· RT-AX56U - Status kl...
· Asus TUF-AX3000_V2 p...
· [MOD] FreshTomato-MI...
· Multiroom N z wykorz...
· [S] Asus RT-AC68U E1
· [S] ASUS RT-AC68U
· Rozłączanie klient...
· serwer VPN za wan'em
· Przejscie z dyndns f...
· WDR3600 i problem z WAN
· Jaki USB hub do syno...
· [S] Karta sieciowa Q...
· Asus rt-n18u port fo...
· Netflix dzielenie ko...
· Nextcloud konfigurac...
· Netgear WNR3500L
Najpopularniejsze obecnie wątki
· [MOD] FreshTomato... [869]
· [MOD] Tomato64 (x... [27]
· [Howto] Xpenology... [13]
Ankieta
Jaki procesor posiada twój router?

Broadcom MIPSEL
Broadcom MIPSEL
36% [151 głosów]

Broadcom ARM
Broadcom ARM
52% [216 głosów]

Atheros
Atheros
5% [22 głosów]

Marvell
Marvell
1% [4 głosów]

Ralink
Ralink
1% [3 głosów]

Intel/AMD/VIA
Intel/AMD/VIA
1% [5 głosów]

Żaden z powyższych
Żaden z powyższych
4% [15 głosów]

Ogółem głosów: 416
Musisz zalogować się, aby móc zagłosować.
Rozpoczęto: 02/02/2015 09:38
Twoje IP
18.234.55.154
Zobacz wątek
OpenLinksys » :: OPROGRAMOWANIE :: » Tomato - firmware
 Drukuj wątek
port forwarding issues
shredhead1080
sorry this is all in English....

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.



root@my-router:/tmp/home/root# iptables --list -vn    [I've removed everything except for what pertains to this issue]
Chain INPUT (policy DROP 24 packets, 1265 bytes)
 pkts bytes target     prot opt in     out     source               destination
   [bcolor=#ffff00] 0     0 ACCEPT     tcp  --  *      *       0.0.0.0/0            0.0.0.0/0            tcp dpt:9091[/bcolor]


I've run into this before using Tomato on a previous router and I cannot remember how I fixed it.

Any ideas?
 
Adooni
Try to install v132 tomato by Shibby. One user have got similar issue with v136 and back to v132 with nvram clear and it is working.
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
 
shredhead1080
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.
 
Adooni
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
 
shibby

Cytat

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: i7-7700T, 48GB RAM, 3x2TB SSD, 1x1TB SSD, 512GB NVMe, Intel X710-DA2 SFP+
VM Router: OpenWRT 22.03.4
VM NAS: Synology DS920+
VM VPS: Debian, WWW, Home Assistant
Switch: Netgear MS510TXPP
Switch: Ubiquiti USW-Flex-mini - szt. 2
Wi-Fi: Ubiquiti U6-Lite - szt. 2
 
shredhead1080
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 17:38:15:

Cytat

shredhead1080 napisał(a):

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 ....

Połączony z 14 czerwiec 2016 17:39:16:

Cytat

shredhead1080 napisał(a):

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 17:41:05:
[quote]shredhead1080 napisał(a):

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 17:46:49:
[quote]shredhead1080 napisał(a):

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 ....

Połączony z 14 czerwiec 2016 17:50:02:
[quote]shredhead1080 napisał(a):

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
 
Przejdź do forum
Zaloguj
Wprowadź adres e-mail lub nazwę użytkownika

Hasło



Nie masz jeszcze konta? Zarejestruj się.

Zapomniałeś/aś hasła?
Aktualnie online
· Gości online: 9

· Użytkowników online: 0

· Łącznie użytkowników: 24,117
· Najnowszy użytkownik: Ja
Czat
Musisz się zalogować, aby opublikować wiadomość.

Adooni
24-03-2024 13:16
Guest network is currently designed to allow the first set of each band (2.4G, 5G, 5G-1) available to the AiMesh node

tamtosiamto
24-03-2024 03:03
ale w 1 jest opcja do wyboru - dla calej sieci albo rutera only i wlasnie o tym mowie, ze nie dziala

Adooni
23-03-2024 16:31
w dokumencie asusa jest ze wlasnie dla 1 ma dzialac na nodach tez

tamtosiamto
23-03-2024 15:39
tak, ale nie zmienia to faktu, ze w pierwszej nie dziala wylaczanie aimesh dla goscinnej( a powinno), czyli jest jakis bug. Mam start soft, bo to dsl-ac68 ktory nie jest juz updateowany

Adooni
22-03-2024 18:07
nie, 1 wsza bedzie wszedzie trzeba 2ga zrobic dla kazdego pasma te nie sa przenoszone

tamtosiamto
19-03-2024 19:57
czyli jak mam jedna siec goscinna to powinno dzialac separowanie gosci od noda -a nie dziala Smile

tamtosiamto
19-03-2024 19:50
@Adooni 'Only one set is available for 1 band' i tak mam-1 set dla 2.4ghz i 1 dla 5ghz-czy czegos nie rozumiemW drugiej sieci goscinnej nie ma opcji wyboru Ruter only/ All nodes

Adooni
19-03-2024 19:14
no to przeczytaj to 2 pod - 1 stet z kazdego pasma jest dopuszczony na nody. zrob 2 siec jako goscinna na danym pasmie i wtedy sprawdz

tamtosiamto
19-03-2024 14:17
@Adooni 'Guest network on AiMesh - Router only'

Adooni
18-03-2024 19:20
Asus napisał coś takiego Note: Guest network is currently designed to allow the first set of each band (2.4G, 5G, 5G-1) available to the AiMesh node. Only one set is available for each band.

70,421,009 unikalnych wizyt