I changed to /32 and that worked :)
This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.
Show posts MenuQuote from: Greelan on May 01, 2021, 01:14:58 PMQuote from: slusk on May 01, 2021, 12:56:29 PMEnable hybrid mode, then in the rule make the translation/target "interface address", the rest should be self-explanatoryQuote from: Greelan on May 01, 2021, 01:33:39 AM
Outbound NAT rule on the IoT interface?
This seems to be the way, I will just need to figure out how :D
Quote from: marjohn56 on May 01, 2021, 10:15:36 AM
You can do it the way I do it between my primary VLAN and my IOT VLAN. Primary can talk to any device on my IOT, IOT devices have no access to anything on the primary VLAN.
On your Primary VLAN you add a rule, this one should be there already, but if not.
Action: Pass
Proto: IPv4/6
Source: Any
Dest: Any
and on the IOT VLAN
Action: Block
Proto: IPv4/6
Source: Any
Dest: VLAN_Net
There are some others to block/allow specifics, but that's the basics.
Quote from: Greelan on May 01, 2021, 01:33:39 AM
Outbound NAT rule on the IoT interface?
{
"service":{
"nat":{
"rule":{
"5010":{
"description":"IoT",
"destination":{
"address":"192.168.20.0/24"
},
"log":"disable",
"outbound-interface":"eth0.20",
"protocol":"all",
"source":{
"address":"192.168.1.0/24"
},
"type":"masquerade"
}
}
}
}