Hello All,

I'm working in a RB2011UAS-RM (the later version of the hardware that has POE out on ETH10) on a pretty straightforward config for an edge router that uses some VLAN's with several networks, some bridged some NAT'd.

In any event, when I try to add 10.10.22.0/22 to:

IP-Firewall-Filter Rules
IP-Firewall-NAT
IP-Firewall-Address List
or Queues
(possibly more areas?)

I get an "Error in Address - ip address expected".

I can put 10.0.0.0/22, and other IP's with a subnet that large or larger in those areas just fine but I can't put 10.10.22.0/22, or 10.10.22.0/21, 192.168.1.0/22, /21, /20, ect. I also tried variations of that IP such as 10.10.21.0/22 and others to no avail.

I can add 10.10.22.0/22 to IP - Address' just fine and it populates a route that works for the whole /22, but otherwise I have to put 2 /23 rules in everywhere to effectively cover the entire range with filter rules, NAT rules, ect.

This address exists on ETH10 as a VLAN but I can duplicate this on other 2011's and an x86 config. that is not running VLAN's. I'm running RouterOS 6.27 (on all tested devices)

Can anyone else replicate this issue, is it perhaps a known issue, can anyone think of why it may not be working?

Best Regards,

Chris

If you add a network - 10.10.20.0/22 is correct. 10.10.22.0/22 is just one ip in the 10.10.20.0/22 net .

10.10.20.0 is net - and addresses from 10.10.20.1 to 10.10.23.255 is addresses in this subnet. 10.10.23.255 is the broadcast.

PS! you can use 10.10.22.0 as an ip - just like 10.10.20.1 in the 10.10.20.0/22 net. Im sure you misstakly thinks of the .0 as the "net" - but its not after +/24 mask (23,22,21 eg)

samsung nailed it.

I've walked into many networks where things were broken into ranges that weren't subnet boundaries.

/22 = 4 "class C" ranges, so if you assign a network of /22, then the 3rd octet has to be an even multiple of 4.

"Use the subnet calculator, Luke!"

-- Nathan

hehe

Hello All,

So I feel like the dunce of the class now. I've been through subnetting in college and the army and been doing it for entirely too long to make a stupid mistake like that, so you would think that I would have thought of that but it didn't occur to me. I just wanted a /22 size subnet where I wanted it and not where it was supposed to go.

Thanks for setting me straight without putting me down, just another thing to love about Mikrotik's, the community.

Best Regards,

Chris

don't worry mate, I'm sure everyone done mistakes which could be considered "lame" by the community at the time.
sometimes, even those who are deep in telecommunications and maybe gurus "can't see the wood for the trees".

S

Yeah - you know how there are those guys who just seem to know instinctively some strange thing is the problem, and thinking "how do they know that?" This is how they know that - they got burned before.
You'll probably recognize this type of thing instantly for the rest of your career now.

This is how they know that - they got burned before.

So true.

-- Nathan