| Age | Commit message (Collapse) | Author | Files | Lines |
|---|
|
This ensures that all of the rules are processed and unexpected packets
are not allowed or blocked by the kernel at any time.
Change-Id: Ia7bb1d7f604f8ed1bd9759a23e370d20cb0c690d
Signed-off-by: William A. Kennington III <wak@google.com>
|
|
The nft rules were not deleted in cases where the public addresses are
removed from the gbmc-br interface. This would create broken rules.
Change-Id: I22a88f1fb15ccbea49e586061ea8e93bbbfb1bc1
Signed-off-by: William A. Kennington III <wak@google.com>
|
|
We were missing this address but we want neighbor discovery from outside
the BMC to work against this range.
Change-Id: I6ef139486f382df21596c460626bfe2f692c7236
Signed-off-by: William A. Kennington III <wak@google.com>
|
|
We use functions from the network-sh library and need to include it.
Change-Id: I7f78b7dd37c4e5d38342c4625c26c4b583133bf5
Signed-off-by: William A. Kennington III <wak@google.com>
|
|
This scans the gbmcbr interface for public addresses, and adds the
relevant addresses to the NCSI interface of the BMC. This is required
for neighbor discovery to work from prod over the NCSI link, when the
addresses do not already exist (BMC DHCP will not have them).
Change-Id: I27ff0cd3c4750b752b35399b8a0288db5ac9fe28
Signed-off-by: William A. Kennington III <wak@google.com>
|
