[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[NOAAPORT #MJB-944803]: rhel8 noaaport gaps
- Subject: [NOAAPORT #MJB-944803]: rhel8 noaaport gaps
- Date: Tue, 01 Nov 2022 09:33:01 -0600
If the rp_filter == 2 works for you, cool beans. "0" means no filtering, "1"
means strict filtering (default), and "2" means "loose" filtering. The 4.x
kernel interprets these differently than 3.x, such that to get absolutely no
filtering, you have to articulate both the "all", and each NIC for which you do
not want filtering. If "loose" is working, then good to go on that angle.
On VM machines, my experience has shown that the noaaport instance NIC has to
be given a bridging configuration . . . i.e., it has to be a "straight through"
pass of the traffic for the device that is connected to the Novra. I assume
that was already the case with the RH7 VM, but maybe the loading of the RH8
scrubbed that?
Stonie
Ticket Details
===================
Ticket ID: MJB-944803
Department: Support NOAAPORT
Priority: Normal
Status: Open
===================
NOTE: All email exchanges with Unidata User Support are recorded in the Unidata
inquiry tracking system and then made publicly available through the web. If
you do not want to have your interactions made available in this way, you must
let us know in each email you send to us.