What is the best use for this stuff?
Ok, I have a lot of older computer equipment - and I've been feeling the need to clean up again. On that thought, I've also been thinking about the best way to divvy up what I have based on the task. I'm hoping a few folks here might have an opinion on the best way to put this stuff to use: What I have: My current router is based around an old ECS P6IWP-Fe board with an 850MHz PIII and 1x128MB of RAM. Due to the chassis, it has a 2.5 HDD. This board *sucks* as a router, primarily because of the onboard ethernet. I'm not entirely sure WHY I chose this board for the router in retrospect, and this board is a likely candidate for eBay. The case is a heavily modified Travla C137 - the original HDD/PSU tray was removed, and the powersupply rotated (and screwed down directly), a 2.5HDD installed, and mounting posts were added to support a true FlexATX board. The back was modified to allow for two PCI boards in separate risers. Thankfully, any true FlexATX board will fit. My file server is a dual proc SuperMicro/ServerWorks LE board with 2x 1.0GHz PIII's and 1GB (4x256MB) of ECC RAM. It was originally intended to be an application server for a network of X terminals (which is why it was so beefy), but has since become little more than a file server. It is a nice system, though - and has built-in U160 SCSI. It presently serves 72GB (2x36GB) over SMB and NFS, and is the primary FTP server. It is sitting in a gigantic SuperMicro chassis (full height ATX) and sounds like a jet engine idling. The case, and probably mainboard, are overkill for the current usage. My FreeBSD/devel workstation is an Intel D815EFV mainboard with a 1.2GHz PIII, (2x256MB) 512MB of RAM, and an Adaptec 29160 controller with an 18GB U160 drive. It is a dual head system, using both the onboard video and a 3Dfx Voodoo4 adapter. It's housed in a fairly non-descript Enlight micro-atx chassis. (fits nicely, not much personality) I have a couple of WindowsXP stations, one of which is very custom - built around a Tyan S2425 board with a 1.2GHz PIII, 512MB (2x256MB) of RAM, a 40GB 2.5 HDD, and a sound card mounted in a PCI riser - all stuffed in an old IBM NetVista case. I like this machine very much - as it took a lot of work to get everything to fit (involved a dremel tool, a file, and a drill). It also has a very custom wiring harness. This machine will probably stay as is - it's just right. Amazingly, it runs cool and quiet - even at night. (it's currently sitting by the bed - and is probably the second most used PC in the house) The other is a D815EFV board stuffed into an old HP Pavilion XE746 chassis with a 850MHz PIII, 1x256 MB of RAM, and a 30GB HDD. It is also dual head, and uses the onboard video and an ATI Rage Pro video card. This machine is currently unused - my wife got tired of a PC in every room... :) Lastly, my sole Pentium IV system, has a Abit BL7-R(raid) mainboard with a 1.5GHz P4, 1x256MB of RAM, a Creative SB Audigy and a couple of TV tuner cards. It's (eventually) going to become a PVR, with a couple of 120GB HDD's in it. To round things out, I also have an old Intel dot.station with a 667MHz Celeron and two loose mainboards - another Tyan S2425 (minus a video connector), the original mainboard from the HP (Trigem Cognac+) in a bag - along with a Celeron 300A. I also have 2 Creative/Ensoniq sound cards, 3 3Com 3c905C NIC's, a couple of dual port NICS (Compaq) that don't seem to work terribly well in FreeBSD 4.x, and a variety of other odds and ends. An ISA digiboard Xe/8, that I would love to use instead of that crappy 4-port SIIG board, with breakout cable. Too old to really be of use, but I'll mention them - I have an Adaptec 2940AU (narrow) SCSI controller, and three 2GB narrow SCSI drives (old Seagate drives) I use when I want to test out new versions of FreeBSD without trashing my current configuration. It's beginning to get to the point where 6GB is cutting it, though. All of the RAM is PC133 - most of it is Crucial CAS2, but there are a couple of Buffalo sticks that are CAS3, and have questional SPD EEPROMs. The wife is not pleased, as this menagerie consumes a great deal of space. So, it's time to consolidate - but I'm at a loss as to what the best combinations of parts are. So, with all these parts, I need to outfit: 1 router/HA controller (or terminal server) 1 file server ( workstation?) 1 FreeBSD workstation for development. 1 Windows workstation (for the wife) 1 digital video recorder. I can't combine the router and the file server easily - the router is in a small closet, and the ambient temp is ~83degF with the current router, which is one of the most power-thrifty machines I own. The last time I attempted to put the server in the closet, the temperature was getting to nearly 95degF ambient, and the thermal alarm kept going off. (not good) The router really needs to run the HA software - as the wiring closet is fairly small, and all the house
RE: sshd listening on more than one port.
Hello, I am wanting to know if it is possible to enabled the sshd to listen on more than one port, without having to spawn another instance of the server itself. If it is possible does anyone have any idea how I could accomplish this. Thanks in advance. Mick Walker Yes, simply add additional Port lines to your sshd_config file and kill -HUP your sshd server. For example, my ssh server listens on 22 23 because of the way I handle incoming NAT connections, so I have: Port 22 Port 23 in my config file. Regards, Seth Henry ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
X apps timeout on IPv6 after cvsup to Xfree86-4-clients-4.4.0.5
Guys/Gals;
I recently cvsup'ed my 4.11 machine to the latest XFree86 source - and ran into
a snag.
I don't typically sit at console, so I didn't have a full X install (I do now -
as part of debugging this problem...) Instead, I use Xwin32/Putty's automatic
ssh tunnelling feature, and launch apps from my Windows desktop with icons
(really slick).
After the upgrade, though; apps take over 30 seconds to launch. This doesn't
happen locally - I tested this by completing the X installation, and launching
xterms from the console, and I didn't see any delay.
So, I ran xterm under truss from a SSH session, and discovered that it was
timing out on a connect with an IPv6 address. It later tried to connect using
an IPv4 address, and everything went fine. This makes sense - I don't have IPv6
configured on this system (though it is in the kernel).
Truss output:
output snipped
socket(0x1c,0x1,0x0) = 3 (0x3)
setsockopt(0x3,0x6,0x1,0xbfbff67c,0x4) = 0 (0x0)
open(/etc/host.conf,0x0,0666) = 4 (0x4)
fstat(4,0xbfbfef50) = 0 (0x0)
break(0x8097000) = 0 (0x0)
read(0x4,0x8093000,0x4000) = 205 (0xcd)
read(0x4,0x8093000,0x4000) = 0 (0x0)
close(4) = 0 (0x0)
open(/etc/hosts,0x0,0666) = 4 (0x4)
fstat(4,0xbfbfd2d0) = 0 (0x0)
read(0x4,0x8093000,0x4000) = 1085 (0x43d)
read(0x4,0x8093000,0x4000) = 0 (0x0)
close(4) = 0 (0x0)
setsockopt(0x3,0x,0x8,0xbfbff5ac,0x4)= 0 (0x0)
connect(0x3,{ AF_INET6 [::1]:6010 },28) ERR#60 'Operation timed out'
close(3) = 0 (0x0)
nanosleep(0xbfbff768,0xbfbff760) = 0 (0x0)
socket(0x1c,0x1,0x0) = 3 (0x3)
setsockopt(0x3,0x6,0x1,0xbfbff67c,0x4) = 0 (0x0)
close(3) = 0 (0x0)
socket(0x2,0x1,0x0) = 3 (0x3)
setsockopt(0x3,0x6,0x1,0xbfbff4fc,0x4) = 0 (0x0)
setsockopt(0x3,0x,0x8,0xbfbff5ac,0x4)= 0 (0x0)
connect(0x3,{ AF_INET 127.0.0.1:6010 },16) = 0 (0x0)
getsockname(0x3,{ AF_INET 127.0.0.1:4512 },0xbfbff4bc) = 0 (0x0)
getpeername(0x3,{ AF_INET 127.0.0.1:6010 },0xbfbff4bc) = 0 (0x0)
__sysctl(0xbfbff5c8,0x2,0xbfbff634,0xbfbff5c4,0x0,0x0) = 0 (0x0)
What is odd is that this DIDN'T happen before the update. I am going to try
disabling ipv6 support in the kernel, with the hopes that this will fix the
problem.
Has anyone else seen this?
Thanks,
Seth Henry
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]
Internal Cable modem support (or, recommendations for a good external CM)
Hey gang, I think the problems I have been having lately are due to the Com21 DoxPort cable modem. The brand spanking new FreeBSD based router is acting just like the old NetGear router (which may be good news - the router may actually be OK!). The symptoms are fairly repeatable. Under duress, the interface will appear to go down. On the NetGear, I could recover by rebooting (via command - the router itself, and the LAN ports, would work fine). On the FreeBSD router, I can ifconfig xl0 down; ifconfig xl0 up - and regain connectivity. I would suspect the card, but the same symptoms on two routers? That sounds suspiciously like a problem with the CM. Also, having poked around on google, the concensus is that Com21 modems are a load of poop - and I have one of the earliest models (I was an @home customer before the big bang) That said, I'm looking to replace the Com21 modem with a new one. I'd like to go with an Internal unit, but I'm not sure (1) whether they are any good or not, and (2) if they are supported by FreeBSD 4.8-REL (or 4.9, which I hope is coming soon) Otherwise, can anyone recommend a good DOCSIS 1.1 cable modem (with an RJ45 port)? I'm on Comcast in Maryland, but I believe any DOCSIS modem should do the job. Thanks, Seth Henry ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
