System Freeze w/ IPNAT
We have a box doing routing and NAT using IPNAT that freezes up after a couple days. We have swapped out the Box with a different model and continue to see the same problem. Symptoms are that the machine no longer passes traffic and the console is unresponsive to any keyboard input (not even ctrl-alt-del).What we are doing is just Nat'ing a portion of the network traffic (we want to pass certain areas of the network address space un-modified).We are pretty certain that our problem has something to do with ipnat becasue we are using other BSD boxes as routers without issue. We have seen a couple: bge1: watchdog timeout -- resetting bge1: link state changed to DOWN bge1: link state changed to UP in the log file that were not present on the first machine because it had a different set of network cards... I mention it only for completeness. Any help that someone can provide would be appreciated. Additional pertinent info is provided below. Thanks Ted Relevant Kernel Options: optionsIPFILTER #ipfilter support optionsIPFILTER_LOG #ipfilter logging optionsIPFILTER_LOOKUP#ipfilter pools Relevant rc.conf settings: # # ROUTING # router_enable=YES router_flags=-s gateway_enable=YES # # Network firewall / NAT (IPF) # gateway_enable=YES ipfilter_enable=YES ipfilter_flags=-T ipf_nattable_max=50 -E ipnat_enable=YES ipnat_program=/sbin/ipnat ipnat_rules=/etc/ipnat.rules ipmon_enable=YES ipmon_flags=-Ds -N /dev/ipnat -f /dev/ipl -S /dev/ipstate Example rule from /etc/ipnat.rules (we have a number of these based on areas of our network)... Each subnet is associated with a different ip on the outgoing side of the NAT. # map bge0 192.168.100.0/23 - 192.168.4.64/32 proxy port ftp ftp/tcp map bge0 192.168.100.0/23 - 192.168.4.64/32 icmpidmap icmp 6:65535 map bge0 192.168.100.0/23 - 192.168.4.64/32 portmap tcp/udp 42000:65535 # Background info: FreeBSD 6.2 pl-8 Using Dell Poweredge 860 1 Gig RAM Dual - Broadcom BCM5750 B1, ASIC rev. 0x4101 Latest Firmware First Interface (bge0): with 11 IP's (1 for host with 10 aliases for NAT) operating at media: Ethernet autoselect (1000baseTX full-duplex) Second interface (bge1): with one IP operating at media: Ethernet autoselect (1000baseTX full-duplex) ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: PAE causing system crashes
You weren't by chance also using NFS? I was, all my other 5.x systems did not use NFS and are stable. I saw this same behavior and wound up going back to 4.11 to keep the system stable. Ted On Tuesday 17 January 2006 03:17 pm, Michael Barnett wrote: To ammend this slightly.. When running the PAE kernel, they will stay online indefinitely under little to no load. It is only when i want them to actually work will they freak out and reboot. -m On Jan 17, 2006, at 1:47 PM, Michael Barnett wrote: I have 3 dell machines with 2x xeon procs, 8G of ram, and a half terabyte raid 5. I attempted to run the AMD64 distribution on these boxes which was fine for everything except mysql, (which is all these boxes are going to do) so I reinstalled 5.4 i386. uname -a looks like (hostname obscured): FreeBSD myhost.mydomain.com 5.4-RELEASE-p9 FreeBSD 5.4-RELEASE-p9 #2: Mon Jan 16 23:27:12 PST 2006 [EMAIL PROTECTED]:/usr/ obj/usr/src/sys/SMP-PAE i386 My problem is, if i don't enable PAE in the kernel, i can only address half the ram in the boxes, but... the machines are stable. If i do enable PAE, i can address all the memory, but they randomly reboot without dumping any errors or logging. To enable PAE, i am building and booting off the following kernel config: snip include PAE ident SMP-PAE options SMP options KVA_PAGES=512 /snip I added the KVA_PAGES options hoping to stabilize the machine (doesn't seem to have made any difference.) The only other tuning i am doing at the moment is in loader.conf: snip kern.maxdsiz=2147483648# Set the max data size /snip When i boot without PAE I use the generic SMP kernel, and the machine is stable. I know that there are a number of other kernel tunables i could be tweaking, but I am not really sure where to start as the machine dies silently. I was hoping that someone who has run a stable PAE kernel with 8G of ram + could point me in the right direction. Thanks, -Michael ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions- [EMAIL PROTECTED] ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] -- | Ted WisniewskiE-Mail: [EMAIL PROTECTED]| | Manager, Systems GroupWEB:http://oz.plymouth.edu/~ted/ | | Information Technology Services| | Plymouth State University Phone: (603) 535-2661 | | Plymouth NH, 03264Fax:(603) 535-2263 | ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Problem w/ vacation prg using NFS under 6.0p2
I am using 6.0-RELEASE-p2 (SMP PAE kernel) and have noticed that the vacation program does not work properly when the .vacation.db is on an NFS partition. The following shows up in the mailllog: Jan 18 07:56:59 mail sendmail[70185]: k0ICuv3r070159: to=| /usr/bin/vacation testuser, [EMAIL PROTECTED] (1388/100), delay=00:00:02, xdelay=00:00:00, mailer=prog, pri=60954, dsn=5.6.0, stat=Data format error The same setup has been working on a 4.11 system forever. I have tried compiling vacation from the sendmail source (even tried the version from the 4.11 system). I tried it under 5.4 (non PAE kernel), same behavior. This is definitely a problem that appears to be in 5.4 and 6.0. Any Ideas? -- | Ted WisniewskiE-Mail: [EMAIL PROTECTED]| | Manager, Systems GroupWEB:http://oz.plymouth.edu/~ted/ | | Information Technology Services| | Plymouth State University Phone: (603) 535-2661 | | Plymouth NH, 03264Fax:(603) 535-2263 | ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Netgraph - 2 physical interfaces mirrored to 3rd
I pieced some info together from various sources... See the following script
(running on 5.4-p2, comments are in the script). I seem to have run into a
roadblock though... I am hoping someone else has seen this and solved it.
Ted
#!/bin/csh
#+-+
# (sk0) ---| |--- (sk1)
#| |
#+-+
# ^
# |
# (xl0)
#
# In this case, sk0 and sk1 are two sides of a firewall and
# xl0 represents a physical interface that the traffic is to
# be mirrored to. The intent is to create a place where a
# sniffer / network monitoring tool can be connected.
#
# The problem...
#
# As soon as ngctl connect sk0: xl0:lower lower many0 is run,
# No traffic passes on sk0. Am I missing something obvious?
#
#
kldload ng_ether
kldload ng_one2many
kldload netgraph
ifconfig sk0 up
ifconfig sk1 up
ifconfig xl0 inet 10.10.10.10 netmask 255.255.255.0 media 100baseTX mediaopt
ful
l-duplex up
ngctl list
ngctl mkpeer xl0: one2many lower one
#
# The following line causes no traffic to pass on sk0.
#
ngctl connect sk0: xl0:lower lower many0
#
ngctl connect sk1: xl0:lower lower many1
ngctl msg sk0: setpromisc 1
ngctl msg sk1: setpromisc 1
ngctl msg xl0:lower setconfig { xmitAlg=1 failAlg=1 enabledLinks=[ 1 1 ] }
--
| Ted WisniewskiE-Mail: [EMAIL PROTECTED]|
| Manager, Systems GroupWEB:http://oz.plymouth.edu/~ted/ |
| Information Technology Services|
| Plymouth State University Phone: (603) 535-2661 |
| Plymouth NH, 03264Fax:(603) 535-2263 |
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]
Creating a mirror port
I have a FreeBSD box with three Nic's; what I would like to do is mimic the functionality of a mirror-port commonly found on switches. On a routing firewall I would like traffic from say sk0 destined to sk1 and vice versa to be mirrored on xl0 for purposes of network management. I am pretty sure this can be done, but what is the easiest/best way do implement? How would this be done for a bridging firewall? Any advice is appreciated. Thankd, Ted -- | Ted WisniewskiE-Mail: [EMAIL PROTECTED]| | Manager, Systems GroupWEB:http://oz.plymouth.edu/~ted/ | | Information Technology Services| | Plymouth State University Phone: (603) 535-2661 | | Plymouth NH, 03264Fax:(603) 535-2263 | ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: 5.2-RELEASE - Show stopper problem
I have some followup details that I have discovered that make make a difference in nailing this down. I tried to duplicate the hung process on disk I/O problem on an older (hence slower machine) and was unable to duplicate it. This got me to thinking about the problems I have experienced; It appears that the faster the machine the more likely the problem is to occur. So, with my new dual-3.06 Ghz server I could reproduce the Disk (getblk) state at will. ON the slower 2.0 Ghz I had to work at it a bit but I could reproduce it. ON the 400Mhz (Dell PE 4300) unable to re-create (well at least I have not been able to yet). If someone has things to try, I will give it a whirl. Ted (* (* In the last episode (Jan 11), Ted Wisniewski said: (* (* Thanks for your response... As you can see in this output from the (* (* ps command you suggested, the processes are dfinitely waiting on the (* (* disk. BTW.. The syste in question was a fresh install from yesterday (* (* with no users other than myself (I did the cvsup to get it to (* (* 5.2-RELEASE). It did hang when I did that with a similar result. (* (* One of the install -s etc.. processes went into the same state. (* (* (* (* Are you seeing any errors in dmesg or /var/log/messages? I haven't (* (* seen any other reports of I/O hanging, so it might still be something (* (* to do with your hardware or kernel config. (* (* No messages at all in /var/log/messages. I am using the generic (* kernel in one instance and a custom one in another. For the machine I sent (* the ps info it is a Dell power edge 2650 running a generic kernel. The (* disk is configuration is a big raid 5 memory is 2G. Since I can duplicate (* (seemingly at will) on a number of different systems, I doubt it is specific (* to one machines hardware (3 dell servers of differeing models, 1 dell PC, (* and 3 noname brand PC's). (* (* (* On my test system the machine will run for days with this happening, (* (* however, I have another system that is actually doing a lot of (* (* I/O eventually it crashes (well locks up completely)... If (* (* there is any particular info you might need, I am willing to do what (* (* I can. (* (* (* (* If you can drop into ddb when it's locked up, I think there are some (* (* commands you can run to print the kernel locks held by all the (* (* processes, but I'm not sure what they are or how to interpret the (* (* results. (* (* When it locks up... It is literally frozen... Only a power off (* will cure. I have occasionally seen a page not present panic.. Most (* of the time the processes just start to pile up accessing the same place(s) (* on disk. None being able to be killed, and always when I reboot the system (* after this there is a message about not being able to write buffers... giving up... (* (* (* (* Ted (* (* -- (* | Ted WisniewskiE-Mail: [EMAIL PROTECTED]| (* | Manager, Systems Group WEB: http://oz.plymouth.edu/~ted/ | (* | Information Technology Services| (* | Plymouth State UniversityPhone: (603) 535-2661 | (* | Plymouth NH, 03264 Fax: (603) 535-2263 | (* ___ (* [EMAIL PROTECTED] mailing list (* http://lists.freebsd.org/mailman/listinfo/freebsd-questions (* To unsubscribe, send any mail to [EMAIL PROTECTED] (* -- | Ted Wisniewski E-Mail: [EMAIL PROTECTED]| | Manager, Systems Group WEB: http://oz.plymouth.edu/~ted/ | | Information Technology Services| | Plymouth State UniversityPhone: (603) 535-2661 | | Plymouth NH, 03264 Fax: (603) 535-2263 | ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: 5.2-RELEASE - Show stopper problem
Dan, Thanks for your response... As you can see in this output from the ps command you suggested, the processes are dfinitely waiting on the disk. BTW.. The syste in question was a fresh install from yesterday with no users other than myself (I did the cvsup to get it to 5.2-RELEASE). It did hang when I did that with a similar result. One of the install -s etc.. processes went into the same state. Output from PS: 692 wait?? Is 0:00.00 /bin/sh -c periodic daily 1694 wait?? I 0:00.00 /bin/sh - /usr/sbin/periodic daily 1701 wait?? I 0:00.02 /bin/sh - /usr/sbin/periodic daily 1702 wait?? I 0:00.00 /bin/sh - /usr/sbin/periodic daily 1703 piperd ?? I 0:00.00 mail -s testhost.plymouth.edu daily run output 1779 wait?? I 0:00.00 /bin/sh /etc/periodic/daily/450.status-securit 1780 wait?? I 0:00.00 /bin/sh - /usr/sbin/periodic security 1786 wait?? I 0:00.00 /bin/sh - /usr/sbin/periodic security 1787 wait?? I 0:00.00 /bin/sh - /usr/sbin/periodic security 1788 piperd ?? I 0:00.00 mail -s testhost.plymouth.edu security run out 1789 wait?? I 0:00.00 /bin/sh - /etc/periodic/security/100.chksetuid 1795 wait?? I 0:00.00 /bin/sh - /etc/periodic/security/100.chksetuid 1796 piperd ?? I 0:00.00 xargs -0 -n 20 ls -liTd 1797 piperd ?? I 0:00.00 sed s/^ *// 1798 piperd ?? I 0:00.00 sort -k 11 1799 wait?? I 0:00.00 /bin/sh - /etc/periodic/security/100.chksetuid 1802 piperd ?? I 0:00.00 cat 1805 ufs ?? D 0:02.10 find /usr -xdev -type f ( -perm -u+x -or -perm 2779 sbwait ?? Is 0:00.02 sshd: sysop [priv] (sshd) 2782 select ?? S 0:00.01 sshd: [EMAIL PROTECTED] (sshd) 737 getblk p0- D 0:02.14 find /usr -xdev -type f ( -perm -u+x -or -perm 2783 pause p0 Ss 0:00.01 -csh (csh) 2786 - p0 R+ 0:00.00 ps -axO wchan These have been running for about 9 hours now, on a base system with nothing extra installed. Originally, I thought it had something to do with the raid controllers on the various machines I tried, however, I was able to duplicate the condition on an ATA based system (I had to work a lot harder at getting the condition to occur on it). It is almost like the I/O is too fast and something happens.. On my test system the machine will run for days with this happening, however, I have another system that is actually doing a lot of I/O eventually it crashes (well locks up completely)... If there is any particular info you might need, I am willing to do what I can. Ted (* In the last episode (Jan 10), Ted Wisniewski said: (* In 5.2-RC and 5.2-RELEASE there appears to be some issue with (* filesystem or I/O subsystem under 5.2-X. Now, You can install and do (* the normal kind of things, however, when you create a lot of I/O on (* the disk there seems to be a problem actually reading/writing it (* to/from disk. For example, If I do a make buildworld... It (* appears to go along ok. However, I have had a number of (repeatable) (* situations where the make installworld will go so far then will not (* be able to complete. In this case, there is an attempt to write data (* to disk that cannot complete; the process goes into a disk wait state (* (it cannot be killed, and will stay in this state ... forever). (* (* For example the standard daily security script: (* (*727 p0 T 0:00.00 sh 100.chksetuid (*737 p0 T 0:02.14 find /usr -xdev -type f ( -perm -u+x -or -perm -g+x -or -perm -o+x ) ( -perm -u+s -or -perm -g+s (* (* The 'T' state usually means that someone sent the process a STOP (* signal. Try running kill -CONT 727 737 to start them back up. (* (* Processes waiting on disk I/O will be in the 'D' state, and you can run (* ps axO wchan to print the specific part of the kernel it's waiting (* in. (* (* -- (* Dan Nelson (* [EMAIL PROTECTED] (* -- | Ted Wisniewski E-Mail: [EMAIL PROTECTED]| | Manager, Systems Group WEB: http://oz.plymouth.edu/~ted/ | | Information Technology Services| | Plymouth State UniversityPhone: (603) 535-2661 | | Plymouth NH, 03264 Fax: (603) 535-2263 | ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: 5.2-RELEASE - Show stopper problem
(* In the last episode (Jan 11), Ted Wisniewski said: (* Thanks for your response... As you can see in this output from the (* ps command you suggested, the processes are dfinitely waiting on the (* disk. BTW.. The syste in question was a fresh install from yesterday (* with no users other than myself (I did the cvsup to get it to (* 5.2-RELEASE). It did hang when I did that with a similar result. (* One of the install -s etc.. processes went into the same state. (* (* Are you seeing any errors in dmesg or /var/log/messages? I haven't (* seen any other reports of I/O hanging, so it might still be something (* to do with your hardware or kernel config. No messages at all in /var/log/messages. I am using the generic kernel in one instance and a custom one in another. For the machine I sent the ps info it is a Dell power edge 2650 running a generic kernel. The disk is configuration is a big raid 5 memory is 2G. Since I can duplicate (seemingly at will) on a number of different systems, I doubt it is specific to one machines hardware (3 dell servers of differeing models, 1 dell PC, and 3 noname brand PC's). (* On my test system the machine will run for days with this happening, (* however, I have another system that is actually doing a lot of (* I/O eventually it crashes (well locks up completely)... If (* there is any particular info you might need, I am willing to do what (* I can. (* (* If you can drop into ddb when it's locked up, I think there are some (* commands you can run to print the kernel locks held by all the (* processes, but I'm not sure what they are or how to interpret the (* results. When it locks up... It is literally frozen... Only a power off will cure. I have occasionally seen a page not present panic.. Most of the time the processes just start to pile up accessing the same place(s) on disk. None being able to be killed, and always when I reboot the system after this there is a message about not being able to write buffers... giving up... Ted -- | Ted Wisniewski E-Mail: [EMAIL PROTECTED]| | Manager, Systems Group WEB: http://oz.plymouth.edu/~ted/ | | Information Technology Services| | Plymouth State UniversityPhone: (603) 535-2661 | | Plymouth NH, 03264 Fax: (603) 535-2263 | ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
5.2-RELEASE - Show stopper problem
Here is a description of the problem... In 5.2-RC and 5.2-RELEASE there appears to be some issue with filesystem or I/O subsystem under 5.2-X. Now, You can install and do the normal kind of things, however, when you create a lot of I/O on the disk there seems to be a problem actually reading/writing it to/from disk. For example, If I do a make buildworld... It appears to go along ok. However, I have had a number of (repeatable) situations where the make installworld will go so far then will not be able to complete. In this case, there is an attempt to write data to disk that cannot complete; the process goes into a disk wait state (it cannot be killed, and will stay in this state ... forever). For example the standard daily security script: 727 p0 T 0:00.00 sh 100.chksetuid 737 p0 T 0:02.14 find /usr -xdev -type f ( -perm -u+x -or -perm -g+x -or -perm -o+x ) ( -perm -u+s -or -perm -g+s I have experienced the same problem on a number of hardware types (Servers like New Dell Power edge 6550's and variety of PC's). For some reason, it appears that data cannot be read or written to/from the disk. Possibly due to some lock never being released. So, the only way to get rid of the process is to reboot... During the reboot, the system complains about not being able to flush buffers and gives up and on boot, all the filesystems are dirty and must be FSCK'ed. Originally, I thought it had something to do with the server model, but it does occur on a number of Desktop model (a variety of vendors) machines as well. I did send in a PR or two a couple of weeks ago)... but since I see RELEASE tag... Anyway, If someone could shed any light on why... I have not been able to repeat this behavior on 4.9. Ted ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
XF86 Multiple Head video cards
Hi, Can anyone recommend a Multi-head video card (the more heads the better, I am thinking 4 heads if possible) that will work with XF86 and FreeBSD 4.8 or 5.1. The sooner the better. I may be able to get some Free FreeBSD press out of the results.. Thanks, Ted -- | Ted Wisniewski E-Mail: [EMAIL PROTECTED]| | Manager, Systems Group WEB: http://oz.plymouth.edu/~ted/ | | Information Technology Services| | Plymouth State College Phone: (603) 535-2661 | | Plymouth NH, 03264 Fax: (603) 535-2263 | ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
MMAP 2GB Limit
Hello, Currently mmap(2) is limited to 2GB as described in the man pages; does anyone know if that limitation will be lifted in the near future either in the 4.X branch or in the 5.X branch? We have a package called ldm which uses mmap on large files and we are concerned about this limit for the future. If someone knows and can get back to me it would be a big help. Thanks, Ted -- | Ted Wisniewski E-Mail: [EMAIL PROTECTED]| | Manager, Systems Group WEB: http://oz.plymouth.edu/~ted/ | | Information Technology Services| | Plymouth State College Phone: (603) 535-2661 | | Plymouth NH, 03264 Fax: (603) 535-2263 | To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
Timeout - Broadcom BCM5701 Gigabit Ethernet
Hello, I am hoping that someone can point me to a solution for a problem I am having with a Broadcom BCM5701 Gigabit Ethernet card/driver. I am using FreeBSD 4.6.2 on a Dell PowerEdge 2650 that has 2 of these NIC's builtin. I have tried this on both NIC's and continue to get: Sep 18 08:56:05 myhost /kernel: bge0: watchdog timeout -- resetting Sep 18 08:58:00 myhost /kernel: bge0: watchdog timeout -- resetting During the moments before the reset, all traffic stops flowing from the host (the switch is still sending data). I have also changed cables and ports on the switch. I have tried it with autoneg (both switch and host) and hardwired to 100-full (both switch and host). The problem seems to be intermittent (not repeatable on any kind of predictable pattern). Traffic does begin to flow after the timeout -- resetting. The lags between problem and reset can be up to 2 full minutes. Version of if_bge.c: $FreeBSD: src/sys/dev/bge/if_bge.c,v 1.3.2.14 2002/07/27 17:00:41 jdp Exp $ Version of if_bgereg.h: $FreeBSD: src/sys/dev/bge/if_bgereg.h,v 1.1.2.5 2002/07/27 17:00:41 jdp Exp $ This file (if_bgereg.h) has been modified in the following way: #define ETHER_ALIGN 0 I saw this change in the mailing list as a solution to get the card working. (Otherwise it did not want to pass traffic for more than a few moments). So, what might cause bge_watchdog(ifp) to be called? Ted -- | Ted Wisniewski INET: [EMAIL PROTECTED]| | Information Technology Services [EMAIL PROTECTED] | | Plymouth State College | | Plymouth NH, 03264 HTTP: http://oz.plymouth.edu/~ted/ | To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
FreeBSD LDAP Auth
Hi, I am having difficulty Authenticating IMAP/POP3 services vs. and LDAP server under FreeBSD. My Environment: 4.6-RELEASE-p1 Openldap 2.0.25 UW imap-2001a pam_ldap-150 (from padl.com) I have successfully gotten ftp/ssh/telnet to authenticate vs. the LDAP using the pam_ldap module.. However, the IMAP/POP3 servers will not not matter what I do to the ldap.conf file. Has anyone gotten POP/IMAP serves to authenticate vs. an LDAP on a similar set up? If so, what (if anything) did you do to get it to work? Is there anything special that I have to put in pam.conf? Any help / advice would be greatly appreciated. Ted -- | Ted Wisniewski INET: [EMAIL PROTECTED]| | Information Technology Services [EMAIL PROTECTED] | | Plymouth State College | | Plymouth NH, 03264 HTTP: http://oz.plymouth.edu/~ted/ | To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
