„NeuesPasswort“ ist nun das Container-Password. Das muss man dann beim importieren in die Mailprogramme eingeben.
Nun sollte man seine Zertifikate an einem sicheren Ort speichern.
FortiOS 6.4.x benutzt per default fortiguard-anycast.
fortiguard-anycast ist meiner Meinung nach noch nicht wirklich stabil und es führt zu Client-Disconnects, wenn die anycast Server aus irgendeinem Grund nicht erreichbar sind.
Kein Surfen und kein SSH.
—
Falls die Fortiguard Rating Server immer wieder ausfallen einfach auf die „alte“ Methode zurückswitchen
Heute kündigte Microsoft eine frühe Vorschau eines Sidetree-basierten DID-Netzwerks mit dem Namen ION (Identity Overlay Network) an, das auf der Bitcoin-Blockchain auf der Grundlage neuer offener Standards ausgeführt wird, die MS in Zusammenarbeit mit vielen ihrer Partner entwickelt hat.
Die Beschreibung zur Verwendung befindet sich im Quellcode.
#/usr/bin/perl -w
##############################################################################
# CGPro Honeypot 2 Fortigate Threat Feed
# Version 1.0
# Maintained by Juergen P. [core.at]
#
# This sample script writes Temporary Blacklisted IP's from a CommuniGate Pro SMTP/SIP Honeypot
# to a File for offloading BAD host blocking to a Fortigate Firewall with Forti OS 6x
# via the Fortigate Threat Feed Connector. You should adopt it to your needs.
# The Script should be run via cron (i suggest every 5 minutes) and write the o utput
# to a textfile into a specific CGPro users webspace(public) for downloading to the firewall
# via the following FortiOS CLI configuration commands:
######
# config system external-resource
# edit <name>
# set type {category | address | domain}
# set category <value>
# set comments [comments]
# set resource <resource-url>
# set refresh-rate <minutes>
# set last-update <datetime>
# next
# end
#####
#
# The Threat feed connector flushes the Table at each run, so IPs which are not blocked anymore, are removed.
# The size of the file can be a maximum of 10 MB, or 128,000 lines of text, whic hever is most restrictive.
#####
# Replace $CGServerAddress, $Login and $Password below with the correct Values in Section 2
# To run in interactive mode for testing, uncomment Section 1 and comment out S ection 2
# Replace $filename with the filename you defined in the Fortinet Fortigate con fig.
#
##############################################################################
use strict;
# Make sure the "CLI.pm" is in current directory
use CLI;
use LWP::UserAgent;
my $Data ="";
my $x =""; #counter
my $filename ="/var/CommuniGate/SharedDomains/my.domain/postmaster.macnt/account.w eb/honeypotlist.txt";
my $ua=new LWP::UserAgent;
my $request="";
my $response="";
my $content="";
my $url="";
####
#### Section 1
####
# print "Server address: "; # Print the server name prompt
# my $CGServerAddress = <STDIN>; # Read the domain name from standard inp ut
# chomp $CGServerAddress; # Remove \n if present
#
# print "Login (Enter for \"postmaster\"): ";
# my $Login = <STDIN>;
# chomp $Login;
# if ($Login eq '') { $Login = "postmaster"; }
#
# print "Password: ";
# my $Password = <STDIN>;
# chomp $Password;
#
#### End of Section 1
### Section 2
my $CGServerAddress = "1.2.3.4"; # CGPro Server IP
my $Login="postmaster"; # CGPro postmaster Account
my $Password="MyPassword"; # CGPro postmaster Password
#### End of Section 2
# Open TCP connection to given address port 106 (PWD, or CGPro CLI).
# Submit username and password. If login fail, the program will stop.
my $cli = new CGP::CLI( { PeerAddr => $CGServerAddress,
PeerPort => 106,
login => $Login,
password => $Password } )
|| die "Can't login to CGPro: ".$CGP::ERR_STRING."\n";
if($Data = $cli->GetTempBlacklistedIPs()) {
# my $a = split(/,/,$Data); # Number of Elements (uncomment, if needed)
my @b = split(/,/,$Data); # Array of IPs including time in seconds
open(my $OUTFILE, '>', "$filename") || die "could not open output file: $!" ;
select $OUTFILE;
foreach $x (@b) {
$x=~ s/\].*//; # remove everything after "]"
$x= substr $x,1; # remove first "["
print "$x\n"; # write IP to file
$ua->timeout(120);
$url='http://my.rbl.domain/drop.php?ipaddress='.$x.'&black orwhite=b¬es=blacklisted';
$request = new HTTP::Request('GET', $url);
$response = $ua->request($request);
$content = $response->content();
print $url;
print $content;
}
#print "$a\n"; # Print Number of elements
}
else
{
($cli->isSuccess) ? print "No Output created.\n"
: die "Error: ".$cli->getErrMessage.", quitting"; }
$cli->Logout; # Close the CLI session and disconnect
__END__
Threat Feed Connectors
This feature introduces the ability to dynamically import external block list text files from an HTTP server. The text files can contain IP addresses and domain names. These dynamic block lists are called ‚Threat Feeds‘. You can block access to the addresses in the text files by adding one or more threat feeds to:
FortiOS keeps threat feeds up to date by dynamically re-downloading them from the HTTP server according to the refresh rate.
Threat Feeds can be configured under Security Fabric > Fabric Connectorsby creating new Threat Feeds.
The New Fabric Connector edit page provides the following fields:
The domain resource is a text file which contains a domain name for each line and supports simple wildcard. For example:
The address resource is a text file which contains an IP/IP range for each line (note that only IPv4 is supported in DNS profiles, so IPv6 addresses will be ignored). For example:
config system external-resource edit set type {category | address | domain} set category set comments [comments] set resource set refresh-rate set last-update next end
In der Dokumentation sind nicht viele Informationen über die Felder auf dieser Settings-Page zu finden.
Hier nun eine etwas detailiiertere Beschreibung:
Local Area Code
Hier trägt man den aktuellen local Area Code für den Server/Domain-PSTN Standort ein.
für Österreich beispielsweise „43“ (das „+“ bitte weglassen).
43
Emergency Code
Das ist die Einstellung für die Notfallnummer. (Polizei, Feuerwehr, etc.)
Hier der Link zum Original: https://www.unixmen.com/linux-basics-create-network-bonding-on-centos-76-5/
What is Network bonding?
Network bonding is a
method of combining (joining) two or more network interfaces together
into a single interface. It will increase the network throughput,
bandwidth and will give redundancy. If one interface is down or
unplugged, the other one will keep the network traffic up and alive.
Network bonding can be used in situations wherever you need redundancy,
fault tolerance or load balancing networks.
Linux allows us to bond multiple network interfaces into single interface using a special kernel module named bonding. The Linux bonding driver provides a method for combining multiple network interfaces into a single logical “bonded”
interface. The behaviour of the bonded interfaces depends upon the
mode; generally speaking, modes provide either hot standby or load
balancing services. Additionally, link integrity monitoring, may be
performed.
Types of Network Bonding
According the to the official documentation, here is the types of network bonding modes.
mode=0 (balance-rr)
Round-robin policy:
It the default mode. It transmits packets in sequential order from the
first available slave through the last. This mode provides load
balancing and fault tolerance.
mode=1 (active-backup)
Active-backup policy:
In this mode, only one slave in the bond is active. The other one will
become active, only when the active slave fails. The bond’s MAC address
is externally visible on only one port (network adapter) to avoid
confusing the switch. This mode provides fault tolerance.
mode=2 (balance-xor)
XOR policy:
Transmit based on [(source MAC address XOR’d with destination MAC
address) modulo slave count]. This selects the same slave for each
destination MAC address. This mode provides load balancing and fault
tolerance.
mode=3 (broadcast)
Broadcast policy: transmits everything on all slave interfaces. This mode provides fault tolerance.
mode=4 (802.3ad)
IEEE 802.3ad Dynamic
link aggregation. Creates aggregation groups that share the same speed
and duplex settings. Utilizes all slaves in the active aggregator
according to the 802.3ad specification.
Prerequisites:
– Ethtool support in the base drivers for retrieving the speed and duplex of each slave.
– A switch that supports IEEE 802.3ad Dynamic link aggregation. Most
switches will require some type of configuration to enable 802.3ad mode.
mode=5 (balance-tlb)
Adaptive transmit load balancing:
channel bonding that does not require any special switch support. The
outgoing traffic is distributed according to the current load (computed
relative to the speed) on each slave. Incoming traffic is received by
the current slave. If the receiving slave fails, another slave takes
over the MAC address of the failed receiving slave.
Prerequisite:
– Ethtool support in the base drivers for retrieving the speed of each slave.
mode=6 (balance-alb)
Adaptive load balancing:
includes balance-tlb plus receive load balancing (rlb) for IPV4
traffic, and does not require any special switch support. The receive
load balancing is achieved by ARP negotiation. The bonding driver
intercepts the ARP Replies sent by the local system on their way out and
overwrites the source hardware address with the unique hardware address
of one of the slaves in the bond such that different peers use
different hardware addresses for the server.
In this handy tutorial let us see how to
setup network bonding on CentOS 7 and CentOS 6.5. Though it was tested
on CentOS, it should work on RHEL and Scientific Linux 6.x versions.
First, we will setup network bonding on CentOS 7.
1. Setting up Network Bonding on CentOS 7
Let us combine two NICs (enp0s8, and enp0s9) and make them into one NIC named bond0.
Configure Bond0 Interface
In CentOS 7, the bonding module is not loaded by default. Enter the following command as root user to enable it.
modprobe --first-time bonding
You can view the bonding module information using command:
modinfo bonding
Sample output:
filename: /lib/modules/3.10.0-123.el7.x86_64/kernel/drivers/net/bonding/bonding.ko alias: rtnl-link-bond author: Thomas Davis, tadavis@lbl.gov and many others description: Ethernet Channel Bonding Driver, v3.7.1 version: 3.7.1 license: GPL srcversion: E52AE00A79EA6FEFB5BF718 depends: intree: Y vermagic: 3.10.0-123.el7.x86_64 SMP mod_unload modversions signer: CentOS Linux kernel signing key sig_key: BC:83:D0:FE:70:C6:2F:AB:1C:58:B4:EB:AA:95:E3:93:61:28:FC:F4 sig_hashalgo: sha256 parm: max_bonds:Max number of bonded devices (int) parm: tx_queues:Max number of transmit queues (default = 16) (int) parm: num_grat_arp:Number of peer notifications to send on failover event (alias of num_unsol_na) (int) parm: num_unsol_na:Number of peer notifications to send on failover event (alias of num_grat_arp) (int) parm: miimon:Link check interval in milliseconds (int) parm: updelay:Delay before considering link up, in milliseconds (int) parm: downdelay:Delay before considering link down, in milliseconds (int) parm: use_carrier:Use netif_carrier_ok (vs MII ioctls) in miimon; 0 for off, 1 for on (default) (int) parm: mode:Mode of operation; 0 for balance-rr, 1 for active-backup, 2 for balance-xor, 3 for broadcast, 4 for 802.3ad, 5 for balance-tlb, 6 for balance-alb (charp) parm: primary:Primary network device to use (charp) parm: primary_reselect:Reselect primary slave once it comes up; 0 for always (default), 1 for only if speed of primary is better, 2 for only on active slave failure (charp) parm: lacp_rate:LACPDU tx rate to request from 802.3ad partner; 0 for slow, 1 for fast (charp) parm: ad_select:803.ad aggregation selection logic; 0 for stable (default), 1 for bandwidth, 2 for count (charp) parm: min_links:Minimum number of available links before turning on carrier (int) parm: xmit_hash_policy:balance-xor and 802.3ad hashing method; 0 for layer 2 (default), 1 for layer 3+4, 2 for layer 2+3 (charp) parm: arp_interval:arp interval in milliseconds (int) parm: arp_ip_target:arp targets in n.n.n.n form (array of charp) parm: arp_validate:validate src/dst of ARP probes; 0 for none (default), 1 for active, 2 for backup, 3 for all (charp) parm: fail_over_mac:For active-backup, do not set all slaves to the same MAC; 0 for none (default), 1 for active, 2 for follow (charp) parm: all_slaves_active:Keep all frames received on an interfaceby setting active flag for all slaves; 0 for never (default), 1 for always. (int) parm: resend_igmp:Number of IGMP membership reports to send on link failure (int) create a bond0 configuration file as shown below.
Note: Here, BONDING_OPTS describes the bonding mode. In our case, we will be configuring mode0(active-active). Save and close file. 192.168.1.50 is bond0 IP address.
Configure Network interfaces
Now, we should modify both(enp0s8 & enp0s9) configuration files as shown below. First, let us start from enp0s8.
Now, enter the following command to make Network Manager aware the changes.
nmcli con reload
Restart network service to take effect the changes.
systemctl restart network
Test Network Bonding
Now enter the following command to check whether the bonding interface bond0 is up and running:
cat /proc/net/bonding/bond0
As you see in the above output, the bond0 interface is up and running and it is configured as active-backup(mode1) mode. In this mode, only one slave in the bond is active. The other one will become active, only when the active slave fails.
To view the list of network interfaces and their IP address, enter the following command:
ip addr
That’s it.
Configure multiple IP addresses for bond0
I want to assign multiple IP addresses to bond0 interface. What should i do? Very simple, just create an alias for the bond0 interface and assign multiple IP addresses.
Let me make it more clear. Say for example we want to assign IP address 192.168.1.151 to bond0. To create an alias for bond0, copy the existing configuration file(ifcfg-bond0) to a new configuration file(ifcfg-bond0:1).
![[core]](https://core.at/wp-content/uploads/2020/06/core-responsive-small-200.png)
