subscribe to our Youtube


14455 questions

17168 answers


0 members

We are migrating to our new platform at Moving forward, you can continue discussions on this new platform. This current platform will be temporarily maintained for reference purposes.
0 votes
258 views 1 comments
by anonymous

HI Firstly, i have used MANY firewalls in my time, and the RUTX09 and teltonika genrally have a really weird way of doing things in the firewall. please help..! :-)

This is my RUTx09 setup:

Pyhsical LAN port (LAN1) is called LAN in the interface page. The default setup.

In then have two vlans created (or virtual interfaces) added which show up as eth0.1 eth0.2 (ifconfig)

Then in the network interfaces page, I have created two interfaces, one called HOMELAN and the other called CAM which are (in the physical settings) associated with eth0.1 an etc0.2

I have the HOMELAN set to static, and the CAM is static to
Both have DHCP servers set with thier own address space.
In the CAM interfce settings, ive created a firewall zone called CAMZONE, and on the HOMELAN i have created a HOMELAN Zone.
All i want to be able to do is simply block one or two IP's in the CAM address space, eg and from getting out to the WAN port.
I just dont see where i can filter packet that is coming from the CAMZONE or the CAM interface and trying to go out to the WAN (internate)
This is such a simple rule to do.
In my other firewalls, i simple have a list of outgoing rules. By default there is no outgoing filtering. However, you can turn this off, so evertything is blocked, then you add specific rules one at a time to allow outgoing traffic.
What would be the process to do that in teltonika routers??
A simple step by step to create the interface, add it to a zone, then apply the firewalling would be really useful..please help!

2 Answers

0 votes
by anonymous

I have the same problem without VLAN's. I have tried to add traffic rules and iptables, but still the clients which should be dropped are allowed to access WAN. Here is my iptables. The first seven are the ones that should be blocked.

I think there is some major bug in the RUTX firewall. I have RUTX11.

root@Teltonika-RUTX11:~# iptables -t filter -L FORWARD --line-numbers -n -v
Chain FORWARD (policy DROP 0 packets, 0 bytes)
num   pkts bytes target     prot opt in     out     source               destination
1        0     0 DROP       all  --  *      wwan0 
2        0     0 DROP       all  --  *      wwan0 
3        0     0 DROP       all  --  *      wwan0 
4        0     0 DROP       all  --  *      wwan0 
5        0     0 DROP       all  --  *      wwan0
6        0     0 DROP       all  --  *      wwan0
7        0     0 DROP       all  --  *      wwan0
8     3403 1301K forwarding_rule  all  --  *      *              /* !fw3: Custom forwarding rule chain */
9     3357 1289K ACCEPT     all  --  *      *              ctstate RELATED,ESTABLISHED /* !fw3 */
10       0     0 DROP       all  --  *      *              ctstate INVALID /* !fw3 */
11      36 11207 zone_lan_forward  all  --  br-lan *              /* !fw3 */
12       0     0 zone_wan_forward  all  --  eth1   *              /* !fw3 */
13       0     0 zone_wan_forward  all  --  wwan0  *              /* !fw3 */
14       0     0 zone_wan_forward  all  --  qmimux0 *              /* !fw3 */
15      10   700 zone_openvpn_forward  all  --  tun_+  *              /* !fw3 */
16       0     0 reject     all  --  *      *              /* !fw3 */
0 votes
by anonymous
@routerhead you could try to add the iptables like this "iptables -I FORWARD 1 -s -o wwan0 -j DROP" under "Custom rules" The next client would then be  "iptables -I FORWARD 2 -s -o wwan0 -j DROP".
by anonymous
Thanks for info, but if i was going to start adding custom rules via ssh etc, then i may as well just run a linux box with IP tables, and not pay for a hardware device such as this.... The whole idea of paying for a device is that it should be 'EASY' to use and add rules etc. The changing of IPtables directly is easy, and i thank you for the suggestion, but this sort of thing should be reserved for really 'weird' edge case scenarios....not a simple IP block of a client within a VLAN...