S32G3 Linux PFE libfci_cli: L2 Bridge in FW_ONLY(static) Mode

cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 

S32G3 Linux PFE libfci_cli: L2 Bridge in FW_ONLY(static) Mode

Jump to solution
1,902 Views
minJ
Contributor I

I have a question regarding the S32G3 Linux PFE L2 bridge configuration in FW_ONLY(static) mode.

The broadcast MAC address (ff:ff:ff:ff:ff:ff) is automatically registered in the MAC table, so broadcast packets such as ARP requests are delivered normally.
However, if I do not register the destination PC’s unicast MAC address using bd-stent-add, unicast packets (such as ping) to that PC are not delivered.

My questions are:

  • In FW_ONLY(static) mode, is it mandatory to pre-register the MAC addresses of all devices (such as PCs) that will communicate, since dynamic MAC learning is completely disabled? In other words, do I need to know all unicast MAC addresses in advance for communication to work?
  • If so, in a real network environment where it is not possible to know the MAC addresses of all peers beforehand, is there any recommended way to handle this situation? (For example, is there any method for automatic registration or workaround when using fw_only mode?)
0 Kudos
Reply
1 Solution
1,869 Views
chenyin_h
NXP Employee
NXP Employee

Hello, @minJ 

Thanks for your post.

The FW_ONLY mode means learning disabled, forwarding enabled, the
traffic is forwarded only if its both source and destination MAC addresses are known to the bridge, so if they are not registered, the unicast packets would not be delivered as expected.

 

BR

Chenyin

View solution in original post

0 Kudos
Reply
2 Replies
1,870 Views
chenyin_h
NXP Employee
NXP Employee

Hello, @minJ 

Thanks for your post.

The FW_ONLY mode means learning disabled, forwarding enabled, the
traffic is forwarded only if its both source and destination MAC addresses are known to the bridge, so if they are not registered, the unicast packets would not be delivered as expected.

 

BR

Chenyin

0 Kudos
Reply
1,637 Views
minJ
Contributor I
Thank you for your response.
Have a nice day!
0 Kudos
Reply
%3CLINGO-SUB%20id%3D%22lingo-sub-2322312%22%20slang%3D%22en-US%22%20mode%3D%22CREATE%22%3ES32G3%20Linux%20PFE%20libfci_cli%3A%20L2%20Bridge%20in%20FW_ONLY(static)%20Mode%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2322312%22%20slang%3D%22en-US%22%20mode%3D%22CREATE%22%3E%3CP%3EI%20have%20a%20question%20regarding%20the%20S32G3%20Linux%20PFE%20L2%20bridge%20configuration%20in%20FW_ONLY(static)%20mode.%3C%2FP%3E%3CP%3EThe%20broadcast%20MAC%20address%20(ff%3Aff%3Aff%3Aff%3Aff%3Aff)%20is%20automatically%20registered%20in%20the%20MAC%20table%2C%20so%20broadcast%20packets%20such%20as%20ARP%20requests%20are%20delivered%20normally.%3CBR%20%2F%3EHowever%2C%20if%20I%20do%20not%20register%20the%20destination%20PC%E2%80%99s%20unicast%20MAC%20address%20using%20bd-stent-add%2C%20unicast%20packets%20(such%20as%20ping)%20to%20that%20PC%20are%20not%20delivered.%3C%2FP%3E%3CP%3EMy%20questions%20are%3A%3C%2FP%3E%3CUL%3E%3CLI%3EIn%20FW_ONLY(static)%20mode%2C%20is%20it%20mandatory%20to%20pre-register%20the%20MAC%20addresses%20of%20all%20devices%20(such%20as%20PCs)%20that%20will%20communicate%2C%20since%20dynamic%20MAC%20learning%20is%20completely%20disabled%3F%20In%20other%20words%2C%20do%20I%20need%20to%20know%20all%20unicast%20MAC%20addresses%20in%20advance%20for%20communication%20to%20work%3F%3C%2FLI%3E%3CLI%3EIf%20so%2C%20in%20a%20real%20network%20environment%20where%20it%20is%20not%20possible%20to%20know%20the%20MAC%20addresses%20of%20all%20peers%20beforehand%2C%20is%20there%20any%20recommended%20way%20to%20handle%20this%20situation%3F%20(For%20example%2C%20is%20there%20any%20method%20for%20automatic%20registration%20or%20workaround%20when%20using%20fw_only%20mode%3F)%3C%2FLI%3E%3C%2FUL%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2323574%22%20slang%3D%22en-US%22%20mode%3D%22CREATE%22%20translate%3D%22no%22%3ERe%3A%20S32G3%20Linux%20PFE%20libfci_cli%3A%20L2%20Bridge%20in%20FW_ONLY(static)%20Mode%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2323574%22%20slang%3D%22en-US%22%20mode%3D%22CREATE%22%3E%3CP%3EHello%2C%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Fcommunity.nxp.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F260071%22%20target%3D%22_blank%22%3E%40minJ%3C%2FA%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EThanks%20for%20your%20post.%3C%2FP%3E%0A%3CP%3EThe%20FW_ONLY%20mode%20means%20l%3CSPAN%20class%3D%22fontstyle0%22%3Eearning%20disabled%2C%20forwarding%20enabled%2C%20the%3C%2FSPAN%3E%3CBR%20%2F%3Etraffic%20is%20forwarded%20only%20if%20its%20both%20source%20and%20destination%20MAC%20addresses%20are%20known%20to%20the%20bridge%2C%20so%20if%20they%20are%20not%20registered%2C%20the%20unicast%20packets%20would%20not%20be%20delivered%20as%20expected.%3C%2FP%3E%0A%3CBR%20%2F%3E%0A%3CP%3EBR%3C%2FP%3E%0A%3CP%3EChenyin%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2332620%22%20slang%3D%22en-US%22%20mode%3D%22CREATE%22%20translate%3D%22no%22%3ERe%3A%20S32G3%20Linux%20PFE%20libfci_cli%3A%20L2%20Bridge%20in%20FW_ONLY(static)%20Mode%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2332620%22%20slang%3D%22en-US%22%20mode%3D%22CREATE%22%3EThank%20you%20for%20your%20response.%3CBR%20%2F%3EHave%20a%20nice%20day!%3C%2FLINGO-BODY%3E