Re: openldap23 sasl server
The port you are looking for is net/openldap23-server. If you do a make config on this port and enable SASL support the resulting package will be openldap23-sasl-server. Regards, Denis Lemire On 1/6/06, Randy Schultz [EMAIL PROTECTED] wrote: Hi there, I had a 5.4 system running the openldap23 sasl server that I did a bin upgrade to 6.0-stable. Once that was done I cvsup'd everything to bring it up to date. When I did a portupgrade -a I noticed, due to portupgrade dying, that openldap23-sasl-server does not exist in the ports tree. Yet using sysinstall, which is what I did initially to install, it's there for installing. Can somebody point me to the answer as to why it's available using sysinstall but not when using the ports tree? The 2.3 sasl client is there but not the 2.3 sasl server. -- Randy([EMAIL PROTECTED]) 715-726-2832 email bodhisattva * There is no fire like passion, there is no shark like hatred, there is no snare like folly, there is no torrent like greed. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Creating IPSec VPN between FreeBSD and Linksys WRV54G
I have setup many IPSec FreeBSD VPN's using racoon and gif interfaces. On the FreeBSD side I've got: gif0: flags=8051UP,POINTOPOINT,RUNNING,MULTICAST mtu 1280 tunnel inet [LOCAL_WAN_IP] -- [REMOTE_WAN_IP] inet 172.31.1.1 -- 192.168.1.1 netmask 0x I have the usual setkey policies in /etc/ipsec.conf (loaded with setkey -f). The router and the BSD box are establishing IKE no problem according to racoon logs, however I can't actually get any traffic across. Clearly there is something about the Linksys implementation that I'm not familiar with. Anybody have any luck with this particular setup? ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
clamav-0.86.2_1 from ports - freshclam core dumps
When run using the startup script in /usr/local/etc/rc.d/clamav-freshclam.sh, freshclam built from ports segfaults and core dumps with the following message: Starting clamav_freshclam. freshclam in free(): error: modified (chunk-) pointer Abort trap (core dumped) Oddly enough if I run: gdb freshclam Then enter run. It executes and finishes normally. Anybody having any simular issues with the clamav port on FreeBSD 5.4 STABLE? Ports tree has been updated via cvsup to the latest just prior to posting this message. Issue has existed for serveral updates of the port thus far. Config file is default from the port: ## ## Example config file for freshclam ## Please read the freshclam.conf(5) manual before editing this file. ## This file may be optionally merged with clamd.conf. ## # Comment or remove the line below. #Example # Path to the database directory. # WARNING: It must match clamd.conf's directive! # Default: hardcoded (depends on installation options) DatabaseDirectory /var/db/clamav # Path to the log file (make sure it has proper permissions) # Default: disabled UpdateLogFile /var/log/clamav/freshclam.log # Enable verbose logging. # Default: disabled #LogVerbose # Use system logger (can work together with UpdateLogFile). # Default: disabled #LogSyslog # Specify the type of syslog messages - please refer to 'man syslog' # for facility names. # Default: LOG_LOCAL6 #LogFacility LOG_MAIL # This option allows you to save the process identifier of the daemon # Default: disabled PidFile /var/run/clamav/freshclam.pid # By default when started freshclam drops privileges and switches to the # clamav user. This directive allows you to change the database owner. # Default: clamav (may depend on installation options) DatabaseOwner clamav # Initialize supplementary group access (freshclam must be started by root). # Default: disabled AllowSupplementaryGroups # Use DNS to verify virus database version. Freshclam uses DNS TXT records # to verify database and software versions. With this directive you can change # the database verification domain. # Default: enabled, pointing to current.cvd.clamav.net #DNSDatabaseInfo current.cvd.clamav.net # Uncomment the following line and replace XY with your country # code. See http://www.iana.org/cctld/cctld-whois.htm for the full list. # Default: There is no default, which results in an error when running freshclam #DatabaseMirror db.XY.clamav.net # database.clamav.net is a round-robin record which points to our most # reliable mirrors. It's used as a fall back in case db.XY.clamav.net is # not working. DO NOT TOUCH the following line unless you know what you # are doing. DatabaseMirror database.clamav.net # How many attempts to make before giving up. # Default: 3 (per mirror) #MaxAttempts 5 # Number of database checks per day. # Default: 12 (every two hours) #Checks 24 # Proxy settings # Default: disabled #HTTPProxyServer myproxy.com #HTTPProxyPort 1234 #HTTPProxyUsername myusername #HTTPProxyPassword mypass # Use aaa.bbb.ccc.ddd as client address for downloading databases. Useful for # multi-homed systems. # Default: Use OS'es default outgoing IP address. #LocalIPAddress aaa.bbb.ccc.ddd # Send the RELOAD command to clamd. # Default: disabled NotifyClamd # By default it uses the hardcoded configuration file but you can force an # another one. #NotifyClamd /config/file/path # Run command after successful database update. # Default: disabled #OnUpdateExecute command # Run command when database update process fails. # Default: disabled #OnErrorExecute command # Don't fork into background. # Default: disabled #Foreground # Enable debug messages in libclamav. # Default: disabled #Debug Any ideas would be greatly appreciated. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Heimdal Kerberos with LDAP support
I would like to setup Heimdal Kerberos and use OpenLDAP to store its database. Too my knowledge the kerberos installation in the base of FreeBSD 5.4 does not support LDAP. I could install from ports but then I end up with two kerberos installations which is sure to give me a headache somewhere down the line. How can I replace the Kerberos installation in the base with the one from ports with LDAP support? Apologies if this is a common question, but I can't seem to find an answer. Regards, Denis Lemire ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: NAT/DIVERT Issues in 5.2.1 Release
I've downgraded back to 4.10 and my problems have disapeared. I'm not sure what has changed in the 5 series to cause these issues. A few observations I've made though: netstat -rn gives you a bunch of kvm_read error messages. Also the output of netstat -rn is completely corrupt (the netif, use, and expire columns show numerical garbage. Also I've noticed that any firewall rule (in IPFW) which uses an interface in the rule takes no affect whatsoever, other rules work fine (hence why my divert rule which matched the external interface didn't take any affect (confirmed via the counters in ipfw show). Not sure whats broken, I'll try again when the 5.x tree goes STABLE and see if my results vary. Until then the 4.x series should meet my needs. Thanks for the advice, especially the link to rewritten firewall section of the handbook. I will look that over when I have more time to spare. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
NAT/DIVERT Issues in 5.2.1 Release
I've just completed a frustrating day of attempting to get nat working on 5.2.1 RELEASE. I've very familiar with using FreeBSD as a nat enabled Internet gateway, I have set this up on many machines with prior versions. I've compiled my kernel with the ip divert and firewall options needed. I have enabled the firewall and natd in my rc.conf, and have (for now) set firewall type to open and gateway_enable=yes. The setup simply won't work, the appropriate rules are in the firewall, and the natd daemon is running. The main thing I find that doesn't make sense is running ipfw -a l lists the divert rule but its values are zeroed out such that it has been used. Is there an issue with nat on 5.2.1-RELEASE? I've even tried compiling a kernel from cvsup (5.2.1-RELEASE-p9 I believe). Any suggestions on where I might have messed this up would be excellent. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
