2.4.4.a.20180716.1125 & frr 0.2_2 issues

[NogBadTheBad]

Not exactly sure where to post this, been having a play with 2.4.4.a.20180716.1125 and OSPF.

Noticed that the OSPF cleartext password isn't in the OSPF packets and also its being truncated in the config untill you enable MD5.

Also the interface used the OPT# rather than the renamed VTI# interface name.

I'd attach packet captures but it looks like you can't.

Can we have a FFR section in pfSense Packages ?

[jimp]

@nogbadthebad said in 2.4.4.a.20180716.1125 & frr 0.2_2 issues:

Noticed that the OSPF cleartext password isn't in the OSPF packets and also its being truncated in the config untill you enable MD5.

The OSPF "password" is limited to 8 chars: http://docs.frrouting.org/en/latest/ospfd.html#clicmd-ipospfauthentication-keyAUTH_KEY -- The backend imposes this limit. I'm not sure why it wouldn't be showing in the packets, but the config looks right, so if it's missing it may be an FRR bug.

Also the interface used the OPT# rather than the renamed VTI# interface name.

That's a side effect of how the pkg edit interface works in the base system, the package can't influence that.

Can we have a FFR section in pfSense Packages ?

It hasn't had quite enough traffic to warrant its own, but I might make a 'routing packages' category.

[NogBadTheBad]

@jimp said in 2.4.4.a.20180716.1125 & frr 0.2_2 issues:

That's a side effect of how the pkg edit interfac

Many thanks Jim, think I'll pop in a redmine re the length of the password string, to either check the length before saving or mention in the text there is a length limit.