pfsense 2.1-releas error network conflicts with address configured on interface

[mauricioniñoavella]

Help with this error when I try to do a static route on the LAN, the Following Were input errors detected

This Conflicts with network address configured on interface.

LAN IP address: 192.168.200.1/24

System> Gateways> Static Routes> Edit route

Destination network    192.168.200.0/24
Gateway                        192.168.200.1

error: This network Conflicts with address configured on interface.

atached image error

Thanks for collaboration

Mauricio Niño Avella

[cmb]

That's not a valid static route, hence it's rejected. You don't want that static route. Describe what you're trying to accomplish and someone might be able to assist.

[mauricioniñoavella]

cmb Hi,

why not a valid static route?

If I am trying to route 192.168.200.0/24 Network
Gateway 192.168.200.1

The LAN IP address is 192.168.200.1, and the path I'm creating on the LAN interface.

This Conflicts with network address configured on interface.

The picture attached is an example sent to another network and another IP LAN interface

If I am trying to route 192.168.1.0/24 Network
Gateway 192.168.1.1

This Conflicts with network address configured on interface.

This is happening when I try to route the network that owns the IP address of the LAN interface.

Regards

Mauricio Niño Avella

[Brutal]

The very fact that your LAN interface is 192.168.200.1 with a CIDR of /24 means the router already knows that interface is for the full /24 of that subnet.  In effect, your trying to add a duplicate in the form of a static.

[mauricioniñoavella]

Hi,  cmb , Brutal

You say that the router (Pfsense), you know that your gateway to the same CIDR IP is the LAN interface.

as a result there is no need to do this route?

What I wonder is that in Pfsense 2.0.1-RELEASE (amd64) to do this type of routing.

I am sending attached image where Pfsense 2.0.1-RELEASE (amd64) version if you can do this type of routes.

Regards.

Mauricio Niño Avella

[jimp]

It was an error/misconfiguration to allow it before. The input validation is correct now. You do not need nor do you want that route manually added.

By having an IP in the subnet the OS gets a route to the subnet automatically for that link. A static route can/will break that.