Bug in Firmwares
Bug in Firmwares
Hi there.
I'm using the Routertech version "RouterTech AR7WRD (TNETW1350A) Custom Firmware ( v2.80 )".
the bug I found is:
When I try to add a lan client I get this message:
ERROR: IP Addr Should be in 192.168.128.0 network (this is the router network)
The firmware doesn't take in account the IP Gamas that are configured in the static routing and doesn't let me map ports to that networks.
Any Idea?
PS: I've seen this problem in original router firmwares too (D-link, Edimax, and others), one firmware that doesn't have this problem is the Speedtouch ones.
Best Regards.
I'm using the Routertech version "RouterTech AR7WRD (TNETW1350A) Custom Firmware ( v2.80 )".
the bug I found is:
When I try to add a lan client I get this message:
ERROR: IP Addr Should be in 192.168.128.0 network (this is the router network)
The firmware doesn't take in account the IP Gamas that are configured in the static routing and doesn't let me map ports to that networks.
Any Idea?
PS: I've seen this problem in original router firmwares too (D-link, Edimax, and others), one firmware that doesn't have this problem is the Speedtouch ones.
Best Regards.
Re: Bug in Firmwares
speedtouch routers seem to have both 192. and 10. lan ip addresses as default, I think your switch has to be fully supported to be able to create multiple lan networks in RouterTech firmware.
Re: Bug in Firmwares
Let me explain better:
I have 3 independent networks
- One (192.168.128.x) between the router and a Linux Server (only 2 ips and only one cable connecting the router and the linux network card)
- One (192.168.16.x) for my business (one network card at the linux server connected to a switch and an AP);
- One (192.168.192.x) for my home (one network card at the linux server connected to a switch for my home computers);
The Linux server has this IP in their respective network cards:
192.168.128.100
192.168.16.254
192.168.192.254
The router had this IP:
192.168.128.254
The Router has this routing table:
Destination IP Mask Gateway Metric
192.168.16.0 255.255.255.0 192.168.128.100 10
192.168.192.0 255.255.255.0 192.168.128.100 10
The problem is that I connot map ports to the internal networks.
Best Regards.
I have 3 independent networks
- One (192.168.128.x) between the router and a Linux Server (only 2 ips and only one cable connecting the router and the linux network card)
- One (192.168.16.x) for my business (one network card at the linux server connected to a switch and an AP);
- One (192.168.192.x) for my home (one network card at the linux server connected to a switch for my home computers);
The Linux server has this IP in their respective network cards:
192.168.128.100
192.168.16.254
192.168.192.254
The router had this IP:
192.168.128.254
The Router has this routing table:
Destination IP Mask Gateway Metric
192.168.16.0 255.255.255.0 192.168.128.100 10
192.168.192.0 255.255.255.0 192.168.128.100 10
The problem is that I connot map ports to the internal networks.
Best Regards.
- notinthisworld
- Experienced
- Posts: 159
- Joined: Wed Feb 27, 2008 11:28 am
Re: Bug in Firmwares
CidiRome wrote:Hi there.
I'm using the Routertech version "RouterTech AR7WRD (TNETW1350A) Custom Firmware ( v2.80 )".
not sure if it can help though, maybe try upgrading to a newer version of the firmware?
Re: Bug in Firmwares
Hi there.
You are right, upgraded to version 2.92 and it didn't help, the bug persists.
Best Regards.
You are right, upgraded to version 2.92 and it didn't help, the bug persists.
Best Regards.
- biro
- RouterTech Team
- Posts: 1274
- Joined: Wed Jan 25, 2006 10:03 pm
- Location: Letchworth Garden City, ENGLAND
- Contact:
Re: Bug in Firmwares
Is the linux box acting as a router ie IPCop / smoothwall etc. ?
If so then the AR7WRD should forward the required ports to linux box "WAN" IP 192.168.128.100 and then the linux box should forward the ports to the correct LAN IP's.
I am assuming that the linux box is the only thing connected to the AR7WRD.
If so then the AR7WRD should forward the required ports to linux box "WAN" IP 192.168.128.100 and then the linux box should forward the ports to the correct LAN IP's.
I am assuming that the linux box is the only thing connected to the AR7WRD.
Re: Bug in Firmwares
Hi there.
Exaclty, my linux is the reouter between the 3 net works and the router is connected only to it.
I have already thought about mapping/redirecting the ports in the linux too but why have to do it too times (router + Linux) if the Router should be able to do it all?
My purpose in this forum reporting this bug is not to correct my problem, but to help improve the Routertech Firmware that I think is spactacular. For my usage I use a Speedtouch Router that is cappable of doing this, and I was only testing a router with this formware to see if it would fully replace the Speedtouchs I use....
Best Regards.
Exaclty, my linux is the reouter between the 3 net works and the router is connected only to it.
I have already thought about mapping/redirecting the ports in the linux too but why have to do it too times (router + Linux) if the Router should be able to do it all?
My purpose in this forum reporting this bug is not to correct my problem, but to help improve the Routertech Firmware that I think is spactacular. For my usage I use a Speedtouch Router that is cappable of doing this, and I was only testing a router with this formware to see if it would fully replace the Speedtouchs I use....
Best Regards.
Re: Bug in Firmwares
Unfortunately this seems to be a feature we don't have direct access to change.
Port forwards can only be set through the web gui to static dhcp lan clients - which is sensible.
Static dhcp lan clients can only be created in valid local lans.
The Linux OS would support iptables rules diverting anything to anything, and the packets would get through if the route table told it where to route.
Port forwards need an entry in the nat PREROUTING and FORWARD filter chains, this could be done with custom commands but need to be careful about when and what order, as the core logic will also do its own thing.
Port forwards can only be set through the web gui to static dhcp lan clients - which is sensible.
Static dhcp lan clients can only be created in valid local lans.
The Linux OS would support iptables rules diverting anything to anything, and the packets would get through if the route table told it where to route.
Port forwards need an entry in the nat PREROUTING and FORWARD filter chains, this could be done with custom commands but need to be careful about when and what order, as the core logic will also do its own thing.