Displaying 4 results from an estimated 4 matches for "befe".
Did you mean:
bee
2011 Aug 29
2
[Bug 742] New: ip6tables "-m iprange" ipv6 range detection
...Component: ip6_tables (kernel)
AssignedTo: netfilter-buglog at lists.netfilter.org
ReportedBy: mailxiening at gmail.com
Estimated Hours: 0.0
I am using ip6tables to allow/disallow connection from clients with specific IP
address.
My client's IPv6 address is "fe80::e91b:befe:97dc:9df5".
The "-m iprange --src-range" detects the client is in or out of the specified
range as follows.
I create the rules and set log prefix.
ip6tables -I INPUT -m iprange --src-range 1000::0-ffff::0 -j LOG --log-level 7
--log-prefix "1000"
ip6tables -I INPUT -m ipran...
2009 Apr 30
2
Defaults of CentOS Install not working with SELinux
...e with these issues but finding a
solution has not been self evident. Hoping someone here can help.
For Dovecot I get the following:
SELinux is preventing dovecot (dovecot_t) "create" to <Unknown>
(dovecot_t). For complete SELinux messages. run sealert -l
e1b070ab-586a-4c5a-befe-b6a46b9ab992
For procmail I get the following:
SELinux is preventing procmail (procmail_t) "execute" to ./spamc
(spamc_exec_t). For complete SELinux messages. run sealert -l
0a554689-4948-4edf-9964-dddbfe6a2492
SELinux is preventing sh (procmail_t) "read" to ./spamc
(sp...
2007 Jun 11
3
groups with spaces in their name
I''m trying to set puppet up to manage users and groups on an OpenBSD
Samba server, but puppet doesn''t want to handle group names with spaces.
I know this horribly ugly, but compatibility with windows clients seems
to demand groups like "Domain Users" and "Domain Computers", and puppet
chokes on them even though the underlying OS handles them at least well
2017 Mar 29
5
NT_STATUS_NO_LOGON_SERVERS after removing a DC and WERR_BADFILE when trying to remove broken DC
Situation: Trying to upgrade Samba from 4.1 to 4.5 without disruption
too much by adding new DCs and demoting old ones.
After bringing online the first 4.5 DC, I ran `demote
--remove-other-dead-server=` on that DC to remove one of the old 4.1 DCs
(held no FSMO roles). That seemed to run fine (the DC had been offline
for a few weeks at that point and I didn't want to restore it just for