Strange problem with MacOS 9 and isc-dhcpd

[J. Seth Henry]

I realize this is probably not really a FreeBSD question, but I was hoping
someone had seen this before.

 

I am running isc-dhcpd 3.0.1.r14_6 on a FreeBSD 4.11-REL machine. This box
also serves as the primary gateway router and firewall (and general "network
services" machine).

 

All of my *nix and Windows machines get IP's just fine from the DHCP server,
but for some reason, my G3 Mac running Mac OS 9.2.2 won't get its reserved
address.

 

Although I use DHCP, I have assigned each machine (MAC address) a fixed IP &
DNS entry. The DHCP server is to simplify maintenance. So, for example, the
file server uses DHCP, but is always mapped to 192.168.1.2. The Mac,
however, is either refused, or refuses to take its preset address, and ends
up obtaining one in the "guest" pool.

 

I can upgrade to Mac OS X.2, but have been hesitant, as this is an older
machine with only built-in video. I also hate to sink any more money into
such an old system. I could just statically map the address, but that would
defeat the purpose of the DHCP server - which was to avoid hardcoding
network settings.

 

Is there a way to sweet talk either the DHCP server, or the Mac, into taking
the reserved address?

 

Thanks!

-Seth

___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

RE: freebsd-questions Digest, Vol 92, Issue 59

[J. Seth Henry]

> Hi have an IDE drive (bit old) that is starting to develop bad blocks.
> 
> Is there a tool to scan the disk and reassign/block (I don't care
> loosing some space on that disk) the bad bocks?
>
>
> Best regards,
>
> Olivier

Unfortunately, most ATA drives automatically map spares as they detect bad
blocks. If the drive is reporting bad blocks, then the drive has very likely
run out of spares.

I would seriously consider swapping the drive, and copying your data before
the corruption gets any worse.

Of course, depending on the age of the disk, it might not automatically
remap bad blocks - so I would suggest looking for a diagnostic tool on the
manufacturer's web site. These usually involve a bootable CD or floppy disk.

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]"

Having problems booting when attempting to mounting /dev from another filesystem on 4.11-REL

[J. Seth Henry]

Guys/Gals,

One of my embedded machines died a while back after several years of service
(enough to erase my memory.). I am trying to rebuild the flash file system
on the machine, and ran into a snag. I'm attempting to manually install
4.11-REL on this system, as it is a rather old device with little RAM
(32MB), and a troublesome ACPI system. (By manually, I mean I'm
creating/copying file systems from a "host" drive running 4.11 rather than
use the installer)

 

The flash memory is only 32MB, so I have to fairly particular about what I
put on it. Right now, I just have the kernel, /bin, /sbin, /etc, /boot, and
place holders for /usr. I symlink in /modules, /root, /home, /var, /tmp, etc
from /usr (which is an IBM micro drive). I mount /dev from another slice on
the flash memory.

 

The rule is, anything that doesn't need to be written, or is required for
boot, is placed on a read-only flash slice, /dev (which doesn't actually
harm the flash, but must be mounted read-write, is mounted from a separate
slice on the flash, and everything else is mounted on /usr.

 

The problem I'm seeing is that the kernel boots to "mounting root from
ad0s1a" and then it hangs. I suspect that is because I don't have the right
/dev entries on the primary slice's /dev.

 

The question is what are the minimal set of /dev devices required to boot
sufficiently to the point where it can attempt to mount the rest of the file
systems? I know this can be done, because the original install did it this
way (though it took quite a bit of hacking to get it to work right) I just
lost half the secret sauce formula. The other half was remembering to create
a 1MB slice, and using "newfs -b 4096 -i 128" on the /dev file system so
there are enough inodes.

 

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]"

Free NCD Explora 451's to a good home

[J. Seth Henry]

Guys/Gals,

I have an old NCD Explora 451 thin client I no longer have room for, as well 
as a copy of NCDware 5.1.140. (It's on a CD-R, but rest assured, it is a 
real, licensed copy from NCD).

I also have another 451, but I think it has a bad ethernet port - it doesn't 
pass a self-diagnostic. I'll toss it in for parts.

These terminals were originally intended to be used in a multimedia setup to 
control a remote media server. but I have since come into possession of a 
number of SFF PIII systems. These terminals are now just sitting around.

Both terminals have 12MB memory cards (with a copy of NCDware on them), so 
there is no need for a tftp/nfs server unless you need remote storage for 
configuration data.

So, for just the cost of shipping, you can get:

2x NCD Explora 451's (though one may have a damaged network port) - includes 
stands
2x 12MB memory cards - preloaded with a copy of NCDware 5.1.140
1x 18.5V 2.7A power supply
1x CD-ROM with a copy of NCDware 5.1.140

I'm going to be away for the holidays, so (unless I get responses before 
Wednesday) this would be available in early January.

Regards, and happy holidays to all!
-Seth
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Variety pack of problems installing 5.3-REL on a HP Pavilion XE746

[J. Seth Henry]

Guys,
I recently attempted to install FreeBSD 5.3-REL  on a HP Pavilion XE746. This 
system contains a TriGem Cognac+ mainboard, based on the Intel i810 chipset. 
For the curious, it is running the HP branded 3.0.7 BIOS firmware. ACPI is 
enabled be default, and can't be disabled - so that could be part of the 
problem. The system has been upgraded to a PIII-850 and 256MB of RAM. As 
usual, the system runs WinXP Pro like a champ.

dmesg output:
FreeBSD 5.3-RELEASE #0: Tue Dec 14 11:34:44 EST 2004
[EMAIL PROTECTED]:/usr/src/sys/i386/compile/testbed
Timecounter "i8254" frequency 1193182 Hz quality 0
CPU: Intel Pentium III (847.43-MHz 686-class CPU)
  Origin = "GenuineIntel"  Id = 0x68a  Stepping = 10
  
Features=0x383fbff
real memory  = 267321344 (254 MB)
avail memory = 251936768 (240 MB)
ACPI APIC Table: 
ioapic0  irqs 0-23 on motherboard
npx0: [FAST]
npx0:  on motherboard
npx0: INT 16 interface
acpi0:  on motherboard
acpi0: Power Button (fixed)
Timecounter "ACPI-fast" frequency 3579545 Hz quality 1000
acpi_timer0: <24-bit timer at 3.579545MHz> port 0x1008-0x100b on acpi0
cpu0:  on acpi0
pcib0:  port 0xcf8-0xcff on acpi0
pci0:  on pcib0
agp0:  mem 
0xf400-0xf407,0xf800-0xfbff irq 16 at device 1.0 on pci0
pcib1:  at device 30.0 on pci0
pci1:  on pcib1
ahc0:  port 0x3000-0x30ff mem 
0xf410-0xf4100fff irq 18 at device 11.0 on pci1
ahc0: [GIANT-LOCKED]
aic7860: Ultra Single Channel A, SCSI Id=7, 3/253 SCBs
pcib2:  at device 14.0 on pci1
pci2:  on pcib2
fxp0:  port 0x4000-0x401f mem 
0xf420-0xf42f,0xf440-0xf4400fff irq 16 at device 4.0 on pci2
miibus0:  on fxp0
inphy0:  on miibus0
inphy0:  10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto
fxp0: Ethernet address: 00:50:8b:66:49:fe
fxp1:  port 0x4020-0x403f mem 
0xf430-0xf43f,0xf4401000-0xf4401fff irq 17 at device 5.0 on pci2
miibus1:  on fxp1
inphy1:  on miibus1
inphy1:  10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto
fxp1: Ethernet address: 00:50:8b:66:49:ff
isab0:  at device 31.0 on pci0
isa0:  on isab0
atapci0:  port 
0x1800-0x180f,0x376,0x170-0x177,0x3f6,0x1f0-0x1f7 at device 31.1 on pci0
ata0: channel #0 on atapci0
ata1: channel #1 on atapci0
uhci0:  port 0x1820-0x183f irq 19 at 
device 31.2 on pci0
uhci0: [GIANT-LOCKED]
usb0:  on uhci0
usb0: USB revision 1.0
uhub0: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1
uhub0: 2 ports with 2 removable, self powered
ums0: Microsoft Microsoft IntelliMouse\M-. Explorer, rev 1.10/1.07, addr 2, 
iclass 3/1
ums0: 5 buttons and Z dir.
pci0:  at device 31.3 (no driver attached)
pci0:  at device 31.5 (no driver attached)
acpi_button0:  on acpi0
atkbdc0:  port 0x64,0x60 irq 1 on acpi0
atkbd0:  irq 1 on atkbdc0
kbd0 at atkbd0
atkbd0: [GIANT-LOCKED]
sio0: <16550A-compatible COM port> port 0x3f8-0x3ff irq 4 flags 0x10 on acpi0
sio0: type 16550A
sio1: <16550A-compatible COM port> port 0x2f8-0x2ff irq 3 on acpi0
sio1: type 16550A
fdc0:  port 0x3f7,0x3f2-0x3f5 irq 6 drq 2 on acpi0
fdc0: [FAST]
fd0: <1440-KB 3.5" drive> on fdc0 drive 0
ppc0:  port 0x778-0x77f,0x378-0x37f irq 7 drq 3 on 
acpi0
ppc0: Generic chipset (ECP/PS2/NIBBLE) in COMPATIBLE mode
ppc0: FIFO with 16/16/16 bytes threshold
ppbus0:  on ppc0
plip0:  on ppbus0
lpt0:  on ppbus0
lpt0: Interrupt-driven port
ppi0:  on ppbus0
orm0:  at iomem 0xd-0xd3fff,0xc-0xc9fff on isa0
pmtimer0 on isa0
sc0:  at flags 0x100 on isa0
sc0: VGA <16 virtual consoles, flags=0x300>
vga0:  at port 0x3c0-0x3df iomem 0xa-0xb on isa0
Timecounter "TSC" frequency 847428179 Hz quality 800
Timecounters tick every 1.000 msec
IP Filter: v3.4.35 initialized.  Default = block all, Logging = enabled
acpi_cpu: throttling enabled, 8 steps (100% to 12.5%), currently 100.0%
ad0: 2014MB  [4092/16/63] at ata0-master WDMA2
ata1-slave: FAILURE - ATA_IDENTIFY timed out
ata1-slave: FAILURE - ATA_IDENTIFY timed out
ata1-slave: FAILURE - ATA_IDENTIFY timed out
acd0: CDRW  at ata1-master PIO4
da0 at ahc0 bus 0 target 0 lun 0
da0:  Fixed Direct Access SCSI-2 device 
da0: 10.000MB/s transfers (10.000MHz, offset 15), Tagged Queueing Enabled
da0: 2049MB (4197405 512 byte sectors: 255H 63S/T 261C)
Mounting root from ufs:/dev/da0s1a

First off, I removed the original HDD to preserve the Windows installation. 
This install was done to an old 2GB drive that was laying around. The drive 
is known good - I previously installed 4.10 REL to the drive, and have since 
verified it was working again. Anyway, during the install I got numerous 
errors while trying to format the slices. I finally managed to find settings 
that allowed this stage of the install to proceed, only to get more errors 
about the volume being full. I used the following slice sizes:

128MB on ad0s1a for /
128MB on ad0s1b for 
64MB for ad0s1d for /var
1694 for ad0s1e for /usr

The install had a real issue with /usr, until I manually newfs'ed using -U -O2 
-b 4096. With the default settings, the installer would complain that it 
couldn't complete the operation. Once it failed, the installed

Odd performance with FreeBSD 4.10 and Compaq 317453-001 dual ethernet NIC

[J. Seth Henry]

Hello,
I recently decided to swap out the 3Com 3C905-TXM board in my router for a 
dual port Compaq NC3122 (317453-001) dual port NIC so I could avoid using the 
built-in NIC (the Intel ICH2 integrated fxp device) Ironically, I was told 
that this board would perform well for this application.

The board has a Intel/DEC 21152 PCI bridge, and two Intel S82558B ethernet 
controllers - all of which are found and initialized. The board shows up as 
fxp0 and fxp1 under pcib1. Both ports indicate a link to the switch, and show 
activity. 

The problem is that performance for both ports is, shall we say, extremely 
lacking. I will see normal performance for a few seconds, then the board will 
"disappear" for several seconds, then "reappear". In some cases, the board 
will quit responding so long that services will time out. When I ssh into the 
router through one of the ports on this board, I can see the remote end stop 
responding to my typing in mid-stream.

Other than the fact that remote hosts are having a devil of a time talking to 
the router when this board is used, there is nothing in the logs to indicate 
trouble, and the machine is stable.  The original NIC works fine - and I use 
it to log in and halt the box when I am testing.

Is this just a bad board, or is something else going on? If anything, I would 
suspect the bridge chip, as both ports exhibit this behavior.

Thanks!
- Seth Henry
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Using IPFW & DUMMYNET with an existing IPFILTER/IPNAT setup for QoS

[J. Seth Henry]

Hello,
I have an existing FreeBSD based router/internet gateway system that is using 
ipfilter & ipnat. It performs quite well, and my wife would be mightily 
irritated if I screwed it up. :)

However, we have VoIP through Vonage, and a standard Comcast cable modem 
connection to the Internet. Most of the time, everything works well, but when 
I upload large files to the office via FTP, the sound gets choppy - to the 
point where we end up having to use our cell phones.

So, I would like to set up IPFW & DUMMYNET to provide a basic QoS service.

All I really need to do is reserve sufficient bandwidth for, or give highest 
priority to, the ATA - followed by ssh. I believe it needs at least 128kbps 
in each direction for adequate sound quality. I merely want to give ssh 
traffic a higher priority (or reserve bandwidth for) over everything else, so 
that I can still get into my systems even when an ftp session is running.

First, a bit about my (fairly simple) network:

--< external IF: fxp0ROUTER internal IF: xl0 >---< SWITCH >

The switch has its own management port, 2 SmartUPS with management cards, a 
Cisco ATA, and 5 PC's.

To simplify management of IP addresses, I use isc-dhcp for both obtaining the 
router WAN address (dhclient), and for distributing fixed addresses to all of 
the network hosts (dhcpd) (except for the switch and UPS' - which don't 
support DHCP correctly) I don't yet manage local DNS services, so I simply 
distribute a fixed hosts file. 

The router is also a stratum 2 time server for the nework (all hosts that can 
synchronize their clocks to the router, not an external time server) via 
ntpd. 

Eventually, I plan to run a local DNS server - but I haven't gotten around to 
it yet. I would like to run my own to support my local naming scheme, without 
passing any information back up the tree, as well as caching DNS information 
should Comcast have a DNS problem. This, however, is a task for another day.

So, we have:


#
# Outside Interface
#

pass in quick on fxp0 proto tcp from any to any port = 21 flags S keep frags 
keep state
pass in quick on fxp0 proto tcp from any to any port = 22 flags S keep frags 
keep state
pass in quick on fxp0 proto tcp from any to any port = 23 flags S keep frags 
keep state
pass in quick on fxp0 proto udp from any to any port = 68 keep state
pass in quick on fxp0 proto tcp from any to any port = 110 flags S keep frags 
keep state

pass out quick on fxp0 proto tcp from any to any flags S keep frags keep state
pass out quick on fxp0 proto udp from any to any keep state keep frags
pass out quick on fxp0 proto icmp from any to any keep state

block out quick on fxp0 all
block in log quick on fxp0 all

#
# Inside Interface
#
pass in quick on xl0 all
pass out quick on xl0 all

#
# Loopback Interface
#
pass in quick on lo0 all
pass out quick on lo0 all


map fxp0 192.168.1.254/24 -> 0/32 proxy port ftp ftp/tcp
rdr fxp0 0.0.0.0/0 port 21 -> 192.168.1.2 port 21 tcp
rdr fxp0 0.0.0.0/0 port 22 -> 192.168.1.2 port 22 tcp
#below is a irc identd port forwarding example
#rdr fxp0 0.0.0.0/0 port 113 -> 192.168.1.5 port 113 tcp
map fxp0 192.168.1.254/24 -> 0/32 portmap tcp/udp auto
map fxp0 192.168.1.254/24 -> 0/32


# dhcpd.conf

# option definitions common to all supported networks...
option domain-name "gambrl01.md.comcast.net";
option domain-name-servers 68.48.0.6, 68.48.0.12;

default-lease-time 600;
max-lease-time 7200;

# If this DHCP server is the official DHCP server for the local
# network, the authoritative directive should be uncommented.
authoritative;

# ad-hoc DNS update scheme - set to "none" to disable dynamic DNS updates.
ddns-update-style ad-hoc;

# Use this to send dhcp log messages to a different log file (you also
# have to hack syslog.conf to complete the redirection).
log-facility local7;

# Local systems are defined here, and use DHCP as a convenience

host alexandria {
  hardware ethernet 00:30:48:21:8b:8a;
  fixed-address alexandria;
}

host switch {
  hardware ethernet 00:50:ba:ec:61:b3;
  fixed-address switch;
}

host net_ups {
  hardware ethernet 00:c0:b7:6a:00:dd;
  fixed-address net_ups;
}

host serv_ups {
  hardware ethernet 00:c0:b7:a3:a5:67;
  fixed-address serv_ups;
}

host vonage-ata {
  hardware ethernet 00:0d:29:0a:af:2e;
  fixed-address vonage-ata;
}

host office_pc {
  hardware ethernet 00:50:04:ae:90:16;
  fixed-address office_pc;
}

host den_pc {
  hardware ethernet 00:d0:b7:ab:cb:fd;
  fixed-address den_pc;
}

host bedroom_pc {
  hardware ethernet 00:e0:81:23:c2:fd;
  fixed-address bedroom_pc;
}

host spyglass {
  hardware ethernet 00:04:5a:95:47:

Re: freebsd-questions Digest, Vol 68, Issue 29

[J. Seth Henry]

Robert,
I have a FreeBSD based router running on an Intel PIII board (D815EFV) that 
uses a serial console. I redirect to com1/cuaa0 at 115 kbps. I also 
configured FreeBSD to use a serial console as the primary console, and I 
haven't had any problems with the router failing to boot, either with or 
without a terminal attached. Finally, I set up a getty session, so I can 
login via cuaa0. The only messages I miss are the fdisk/startup messages.

Sorry I can't help, but I would suspect a configuration issue.

-Seth Henry


On Tuesday, July 13, 2004 12:35, [EMAIL PROTECTED] wrote:
> Message: 30
> Date: Tue, 13 Jul 2004 12:05:14 -0400 (EDT)
> From: Robert Watson <[EMAIL PROTECTED]>
> Subject: BIOS console redirection *and* serial console with FreeBSD
> To: [EMAIL PROTECTED]
> Message-ID:
> <[EMAIL PROTECTED]>
> Content-Type: TEXT/PLAIN; charset=US-ASCII
>
>
> I have access to several boxes that support "BIOS console redirection", in
> which access to the BIOS and BIOS-based console I/O is redirected to a
> serial port.  This is pretty neat functionality, as it allows me to
> reconfigure RAID arrays, change a variety of system settings, boot
> preferences, etc, via the serial console.
>
> However, I run into a problem when I attempt to use BIOS redirection with
> FreeBSD's native serial console support.  If I just configure a login
> session on ttyd0, it pops up once the boot completes and appears perfectly
> workable.  However, if I turn on 'console="comconsole"' in loader.conf,
> the system will appear to hang or otherwise wedge rather than boot.
> Currently, the boxes where I've experienced this are all remote, so I
> can't report on what actually appears on the console -- however, the
> systems appear to never boot.
>
> My ideal world order would have a natural transition from BIOS console
> redirection to FreeBSD's serial console, letting me configure BIOS/RAID
> settings, configure loader pieces (swap kernels, set tunables, etc), then
> onto the kernel serial console pieces, and finally launching a login
> session on ttyd0.
>
> Does anyone have experience with making this actually happen, or similar
> experience with it not working?  I'm seeing it right now on a recent Xeon
> Intel-based motherboard ("Westville"), but also on an older Intel
> ServerWorkers PIII motherboard.  Is the FreeBSD loader serial code doing
> something un-kosher that the BIOS redirection implementation doesn't like?
> Can we make it behave better?  Or is the BIOS redirection implementation
> just broken when it comes to dealing with use of the serial port by the
> OS?
>
> Thanks,
>
> Robert N M Watson             FreeBSD Core Team, TrustedBSD Projects
> [EMAIL PROTECTED]      Principal Research Scientist, McAfee Research
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Odd performance issues - fxp vs xl?

[J. Seth Henry]

Guys,
I recently had a little run-in with lightning during a recent thunderstorm - 
which destroyed my FreeBSD based router (along with a good chunk of my home 
automation system...) 

The machine had a VIA EPIA mainboard with a 933MHz processor. I had two 3Com 
3C905C-TX boards installed for the router, and used the local vr interface 
for monitoring (although it was mostly unused). The machine had a 40GB ATA 
hard disk, and 128MB of RAM. It performed quite well as a router up until the 
storm. The machine ran a custom compiled version of FreeBSD 4.8, and I used 
ipfilter/ipnat for routing.

Now, I have a new machine with a Tyan S2425 mainboard, and a 850MHz Pentium 
III processor. The Tyan board has two Intel 10/100 Pro (fxp) interfaces 
onboard. The system has an 18GB Ultrawide SCSI drive and Adaptec 29160UW 
controller - and 256MB of RAM. (it was a workstation before being pressed 
into service as a  router). This machine had just been upgraded to FreeBSD 
4.10-REL - and I recently recompiled again to add some IPFILTER options.

The trouble is, the new machine routes much slower than the original. Even 
text based (ssh) traffic appears slower. X apps are always a bit slow, and I 
could always see the refreshes, but it takes forever now. 

I replicated as much of the configuration from the original machine as I could 
(same ipf.rules, ipnat.rules, sysctl.conf, etc). The new machine runs an 
identical software set (dhcpd, sshd, etc). As far as I know, nothing is 
consuming an inordinate amount of CPU time.

In theory, the new machine is better all around. More RAM, faster CPU, etc - 
so I am a little confused as to what the problem could be? It seems as though 
the network adapters could be the issue, but this is a broadband link 3Mb/s 
peak from comcast - to a 10/100 adapter???

I did enable the downloadable firmware for the internal network interface 
(link0), but turning it on or off doesn't seem to make a difference.

Any ideas?

Thanks,
-Seth
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Problem with AMD PCnet/Home internal phy

[J. Seth Henry]

Guys,
I asked about this during the reign of FreeBSD 4.7 - and no one had any ideas, 
so I thought I would toss this question back out now that three new versions 
have crept up - and none indicated any changes to the pcn driver.

I have a Compaq IA-1 internet appliance with an AMD 79C978 (PCnet/Home) 
ethernet adapter built-in. Both internal PHY's (the 1Mbit/s HPNA and 
10Mbits/s 10base-T) are attached to hardware.

The problem is that the pcn driver doesn't seem to see them. It looks for an 
external PHY on the MII bus, and failing to find one, doesn't load the 
driver.

dmesg output:
pcn0:  port 0x1c00-0x1c1f mem 0x4120-0x4120001f 
irq 9 at device 5.0 on pci0
pcn0: Ethernet address: 00:01:fa:ff:ac:57
pcn0: MII without any PHY!
device_probe_and_attach: pcn0 attach returned 6

pciconf output (relevant section)
[EMAIL PROTECTED]:5:0: class=0x02 card=0x20001022 chip=0x20011022 rev=0x52 
hdr=0x00
vendor   = 'Advanced Micro Devices (AMD)'
device   = 'AM79C978 PCnet Single Chip Home Networking Controller 
1/10Mbps'
class= network
subclass = ethernet

Is there a way to get the pcn driver to use the internal PHY's? I'd like to 
use this interface, as it would obviate the need for an external USB ethernet 
adapter. 

Also, how does this driver work with regular PCI HPNA/ethernet cards based on 
this chip? The driver claims it supports these cards, but I'm not sure how if 
it can't use the onboard HPNA PHY?

Thanks,
-Seth Henry
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: freebsd-questions Digest, Vol 48, Issue 21

[J. Seth Henry]

Daniela,
The ugen device means that there wasn't a kernel driver to handle the device. 
I don't believe you can use the ugen device as a formatted device (like cuaa, 
tty, etc).

What is the exact model of your modem? Most of the Alcatel SpeedTouch models I 
looked at claimed to have a UTP network port on them. I'm on a cable modem 
myself, but could you switch out the modem for one that does have a network 
port?

Regards,
Seth Henry

On Friday, February 20, 2004 20:29, [EMAIL PROTECTED] 
wrote:
> From: Daniela <[EMAIL PROTECTED]>
> Subject: USB modem support?
> To: [EMAIL PROTECTED]
> Message-ID: <[EMAIL PROTECTED]>
> Content-Type: text/plain;  charset="us-ascii"
>
> I'm having problems with an USB ADSL modem (Alcatel Speed Touch). It is
> recognized at boot time, but when I try to connect, it tells me that the
> modem is busy.
> I symlinked /dev/cuaa3 to /dev/ugen1 (that's the device that showed up in
> the boot messages) and directed the kppp utility to use /dev/cuaa3. I
> entered all the information it asked me for, and then I got the error
> message: Modem is busy. My ISP told me to f*** off and get Windoze.
> Anything else is unsupported.
>
> Is it a hardware problem or a classical case of a dumb user?
> I'm not unexperienced with Ethernet connections, and I have a great
> knowledge of the TCP/IP standard, but I have never done anything with
> modems, so I can't even imagine how this stuff works.
>
> Regards,
> Daniela
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Kdevelop3 port HOWTO?

[J. Seth Henry]

Guys,
I would like to help out the kdevelop project by building and testing releases 
on my system. However, as it comes from the project, the source won't 
configure OR (if I managed to dink with the configure script enough to get it 
to complete) compile on my system. This includes the released 3.0.0 version, 
which works in the port tree, so clearly something was done in the ports tree 
to make it build on FreeBSD.

Can anyone tell me what? I'd like to test out a patch in the 3.0.1 version and 
verify that the bug was fixed. Alternately, does anyone know when 3.0.1 is 
going to be included in the ports tree for cvs?

BTW- I submitted a more detailed question to [EMAIL PROTECTED], but haven't 
gotten a reply.

Thanks,
Seth Henry
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: Firefox Process Not Exiting

[J. Seth Henry]

> Date: Mon, 16 Feb 2004 09:17:46 -0500
> From: "Daniel R. Curran" <[EMAIL PROTECTED]>
> Subject: Re: Firefox Process Not Exiting
> To: [EMAIL PROTECTED]
> Message-ID: <[EMAIL PROTECTED]>
> Content-Type: text/plain; charset=us-ascii; format=flowed
>
> Seeing as the problem would now seem to be in the linuxpluginwrapper or
> linux-flashplugin port is there a way to fix this problem? Is there any
> work being done on it? is it a known bug? What would the process be for
> one to get the ball rolling towards a fix?
>
> Thanks,
> Dan
>
> Matthew Seaman wrote:
> >On Mon, Feb 16, 2004 at 09:15:43PM +1100, Gautam Gopalakrishnan wrote:
> >  
> >
> >>On Mon, 16 Feb 2004 00:12:56 -0500
> >>"Daniel R. Curran" <[EMAIL PROTECTED]> wrote:
> >>
> >>    
> >>
> >>>I am wondering if anyone else has this issue and if there is a fix for
> >>>
> >>>it. When I run firefox and then exit the program the process remains
> >>>resident, and it starts eating up the CPU. Does anyone know of a fix
> >>>for this. I have been manually killing the process, but this seems
> >>>like a horrible way to work with the program.
> >>>      
> >>
> >>One more vote from me. Same behaviour with firebird too. So it's not
> >>newly introduced...
> >>    
> >
> >I've seen this happen with all of Mozilla, Firebird and now Firefox.
> >It's only certain web sites that trigger the effect, and it seems to
> >happen on sites which make use of a large amount of Flash stuff -- the
> >effect is even caused by Macromedia's test page at
> >http://www.macromedia.com/shockwave/welcome/ -- although quite often
> >what happens is that the flash infexted page will only load once (if
> >at all) and after that the whole browser freezes up and has to be
> >killed from the command line.
> >
> >I'd say it's more likely a bug in the linuxpluginwrapper or
> >linux-flashplugin ports.
> >
> >   Cheers,
> >
> >   Matthew
> >
> >  

Guys,
If it is the plug-in, then it affects more than just Linux/*BSD. I had this 
same problem occur on a Windows box the other day. My fiancee, a diehard 
AOL'er, sent me an e-card, and when I closed Mozilla after viewing it, the 
window closed, but I had a mozilla process sucking up all available cycles. I 
noticed this because the CPU fan went from its normal 55% on, to full up 
100%.

IOW - it may be something in Mozilla/FireFox itself. Unfortunately, Mozilla 
didn't technically crash, so I'm not sure how useful a bug report would be.

Regards,
Seth Henry
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Problems with kdevelop3

[J. Seth Henry]

Guys,
I recently built kdevelop3 from the ports tree, and it has been, to say the 
least, a bit unstable. Has anyone else had any problems with it?

Specifically, after opening a project, it will crash out very easily. Closing 
the project, adding files to the project -  even closing the application a 
project open will cause a crash handler to pop up. I thought it might be 
having a problem with old configuration files, so I removed all of the 
kdevelop specific configuration files from my home directory. 

I'm not sure whether this is a specific build problem on my system, perhaps a 
problem with the FreeBSD port, or a kdevelop issue. It seems a bit strange 
they would call this a "stable" build if it were happening to everyone. Also, 
since it isn't yet built into a package, perhaps it's just a port bug that 
hasn't been worked out yet?

As for the build environment, it's a FreeBSD 4.9-RELEASE system (I haven't 
cvsup'ed the base system). I am using the ports tree from Monday, around 
12:00 PM EST.

Also, how do you turn on debugging information when you compile via the ports 
tree? If I need to file a kde bug report, it would be nice to have a full 
backtrace.

Thanks,
Seth Henry
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Have two critical kmail 1.6 bugs been patched in the ports tree?

[J. Seth Henry]

Guys,
I was checking out the kde website, and noticed that there are (or were) two 
critical bugs in the 3.2.0 release of kmail. (http://dot.kde.org/1075969434/)

Have these been fixed in the ports tree, or do I need to attempt to apply a 
patch? (I would be affected by the pop3 filter bug.) I installed kmail after 
a cvsup upgrade Saturday at 12:30PM EST.

Thanks,
Seth Henry
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Autoconf 2.57 upgrade oddities - files all have '257 suffix.

[J. Seth Henry]

Guys,
I discovered this while attempting to upgrade to KDE 3.2.0 on my FreeBSD 
4.9-REL box last night. Unfortunately, kdevelop 3 won't build because of a 
problem with autoconf. When I first started the upgrade, I apparently had 
2.53_1 installed, so it complained that it needs 2.54 or later.

I tried manually updating autoconf alone, and portupgrade went through the 
motions, but when it finished, 2.53_1 was still there and 2.57_1 wasn't. I 
then tried manually deinstalling 2.53_1, and manually installing 2.57_1. This 
seemed to work, but now I don't have an autoconf anywhere! (the program isn't 
on the disk- I even tried find / -name autoconf)

Now, here's the interesting part. I dig around and find that the binary IS on 
the hard disk, but all of the autoconf binaries have a '257' suffix.  (ie 
autoconf257) I sym-link all of the binaries to their generic names, and 
things seem to be working?

So, at the moment, I have the following, and things seem to be working.

alexandria# ls -l /usr/local/bin | grep 257
lrwxr-xr-x  1 root  wheel   11 Feb  7 12:15 autoconf -> autoconf257
-r-xr-xr-x  1 root  wheel 7684 Feb  2 23:43 autoconf257
lrwxr-xr-x  1 root  wheel   13 Feb  7 12:16 autoheader -> autoheader257
-r-xr-xr-x  1 root  wheel 7959 Feb  2 23:43 autoheader257
lrwxr-xr-x  1 root  wheel   11 Feb  7 12:19 autom4te -> autom4te257
-r-xr-xr-x  1 root  wheel33557 Feb  2 23:43 autom4te257
lrwxr-xr-x  1 root  wheel   13 Feb  7 12:19 autoreconf -> autoreconf257
-r-xr-xr-x  1 root  wheel17612 Feb  2 23:43 autoreconf257
lrwxr-xr-x  1 root  wheel   11 Feb  7 12:19 autoscan -> autoscan257
-r-xr-xr-x  1 root  wheel16060 Feb  2 23:43 autoscan257
lrwxr-xr-x  1 root  wheel   13 Feb  7 12:19 autoupdate -> autoupdate257
-r-xr-xr-x  1 root  wheel32888 Feb  2 23:43 autoupdate257
lrwxr-xr-x  1 root  wheel   10 Feb  7 12:19 ifnames -> ifnames257
-r-xr-xr-x  1 root  wheel 3607 Feb  2 23:43 ifnames257

Is this a bug, or did I screw up something?

Thanks,
Seth Henry
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

IPFILTER/NAT problem

[J. Seth Henry]

Guys/gals,
I've got a curious networking problem with ipfilter/ipnat (or possibly ssh).

The firewall where I work allows only 4 ports to go through unmolested (i.e., 
no proxy servers/authentication). These are 21 (FTP), 22 (SSH), 23 (TELNET), 
and 110 (POP3). I have three hosts at the house I would like to be able to 
ssh into, and window X apps back. So, I thought I would use each of these 
ports to point to a host on the lan at home, plus FTP access to the file 
server host.

The local network is very simple. I have a FreeBSD router sitting between the 
CM and the local LAN. The two other hosts are connected to the router via  
switched ethenet - and all have LAN address in the 192.168.1.x range.

So, I allow these four ports to pass through my firewall, and use nat to 
redirect, ala: 

# External Interface
block out on xl0 all
block in log on xl0 all
 
pass in quick on xl0 proto tcp from any to any port = 21 flags S keep frags 
keep state
pass in quick on xl0 proto tcp from any to any port = 22 flags S keep frags 
keep state
pass in quick on xl0 proto tcp from any to any port = 23 flags S keep frags 
keep state
pass in quick on xl0 proto tcp from any to any port = 110 flags S keep frags 
keep state
pass in quick on xl0 proto udp from any to any port = 68 keep state
 
pass out quick on xl0 proto tcp from any to any flags S keep frags keep state
pass out quick on xl0 proto udp from any to any keep state keep frags
pass out quick on xl0 proto icmp from any to any keep state
 
# Internal Interface
pass in quick on vr0 all
pass out quick on vr0 all
 
pass in quick on xl1 all
pass out quick on xl1 all
 
# Loopback Interface
pass in quick on lo0 all
pass out quick on lo0 all

I checked the firewall log, and used tcpdump to verify that these ports were 
getting passed through. (well, they aren't being blocked at least)

And then redirect the ports to the appropriate hosts:


map xl0 192.168.1.254/24 -> 0/32 proxy port ftp ftp/tcp
rdr xl0 0.0.0.0/0 port 21 -> 192.168.1.1 port 21 tcp
rdr xl0 0.0.0.0/0 port 22 -> 192.168.1.1 port 22 tcp
rdr x10 0.0.0.0/0 port 23 -> 192.168.1.249 port 23 tcp
map xl0 192.168.1.254/24 -> 0/32 portmap tcp/udp auto
map xl0 192.168.1.254/24 -> 0/32

The router (which is also one of the hosts) is listening on port 110 at the 
moment, but it will work on any of the ports. Port 22 will work to either of 
the remote hosts. BUT if I try to to run sshd on an _internal_ host on port 
23, the connection doesn't go through. I know ssh is listening on the ports, 
because I can use ssh  -p 23 from the router or other host and get a 
login.  I can also toggle the local IP addresses for port 22 and 23 in the 
ipnat.rules file, and login on 22 to either host.

The router is a FreeBSD 4.8-REL system, and, although simply switching the IP 
addresses allows login to either host, the other hosts are a FreeBSD 4.9-REL 
file server, and a RedHat Linux 9 test box. Ipfilter is set to block all by 
default, so only the four ports mentioned are allowed in. My work machine is 
a Win2k box, and I'm using the F-secure client, version 5.2 build 33. (I've 
also tried putty 0.53b.

I have verified that the sshd daemons on all of the machines are responding on 
the both 22 and 23 by logging in from the other host (iow, I can ssh to 
192.168.1.249 at port 23 by typing 'ssh hades -p 23' from one of the other 
hosts, and it works.

The reason I suspect an ipnat problem is that i don't see any traffic on port 
23 on the local interface. (iow, typing tcpdump -i xl1 | grep telnet produces 
nothing)

I also don't see anything on the local network from any of the other hosts - 
so it doesn't appear that the router is passing packets on port 23 to the 
local interface. Programs on the remote network all report timeouts.

Did I miss something?

Thanks,
Seth Henry

___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Problems with ATEN UC232 & apcupsd

[J. Seth Henry]

Hey guys/gals,
I forgot to include the versions! I'm using FreeBSD 4.8-REL, and apcupsd 
version 3.8.6

Sorry, and thanks again!
Seth Henry

___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Problems with ATEN UC232 & apcupsd

[J. Seth Henry]

Hey guys/gals,
I realize this may not be a FreeBSD problem, but I thought I'd post it and see 
if anyone else has seen it. I want to connect an APC SmartUPS to a 
"legacy-free" FreeBSD system. I recently used another of these USB to serial 
converters with a home automation system, and it seems to work fairly well - 
but for some reason, the apcupsd software will not work with the converter. 

Here is the dmesg output for the device:
uplcom1: ATEN International Serial adapter, rev 1.10/0.01, addr 3

I don't get any errors in the dmesg output, but the apcupsd daemon errors out 
saying it can't communicate with the UPS.

I know the converter "seems" to work, as I can cat /dev/ucom1, and I get a 
stream of "SM" messages (from the UPS), and I can even log in interactively 
using tip (I have a management card in the UPS).

Any ideas what's going on?

Alternately, this UPS does have a USB port. Is there a way a to get FreeBSD to 
use it via that method?

Thanks,
Seth Henry

___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Need help finding bug using select()

[J. Seth Henry]

Guys,
I am, needless to say, still fairly new to programming under *nix - despite 
months of learning. So far, I have been able to work out a lot of things, but 
this issue with the select statement has me stumped.

I am attempting to listen to a serial port, and perform actions when data is 
received -or- simply wait a fixed amount of time. The waiting a fixed amount 
of time works great, but select doesn't return on serial events.

Would anyone be so kind as to tell me what I'm doing wrong? I know the data is 
being received - as I can read the port periodically (via the timeout) and I 
get what I am expecting. I would rather not wait until the timer expires, 
though.

Here is the code:

(from main.c)

#ifdef HAVE_CONFIG_H
#include 
#endif

#include 
#include 
#include 
#include 
#include 

/* local includes */
#include 
#include 
#include 

int
message_proc(daemon_obj *daemon_info);

int
main(int argc, char **argv)
{
   int  retval, i;

/* Setup the structures */

   daemon_obj   daemon_info;
   thermostat_obj   stat_info[MAX_STATS];
   fd_set   stat_set;
   struct timeval   tick_info;

   init_daemon_info(&daemon_info);
   init_stat_info(stat_info);
   retval = read_conf_file(&daemon_info, stat_info);

/* At least for now, the thermostat is the only device that
 can generate unanticipated data */

   if(open_ioport(&daemon_info, STAT) == SUCCESS) {
  FD_ZERO(&stat_set);
  FD_SET(daemon_info.ioport.stat_fd, &stat_set);
   } else { return IO_ERROR; }

/* They relay board doesn't generate unanticipated data
 so there is no point in selecting on it */

   if(open_ioport(&daemon_info, OVRD) != SUCCESS)
  return IO_ERROR;

   tick_info.tv_sec = daemon_info.params.tick_rate;
   tick_info.tv_usec = 0;

   retval = sync_stat_time(&daemon_info);
   printf("Thermostat time/date updated\n");

   do{
   retval = query_sensors(&daemon_info, stat_info, 0);
   if(retval != SUCCESS)
  return retval;


   retval = query_status(&daemon_info, stat_info, 0);
   for(i = 0; i < MAX_SENSORS; i++)
  if(stat_info[0].sensor_info[i].is_present == TRUE)
 printf("%d: %d%c ", i, stat_info[0].sensor_info[i].value, 
stat_info[0].sensor_info[i].suffix);

   printf("SYS_MODE: %d ",stat_info[0].status_info.sys_status);
   printf("SAMPLE: %e ", stat_info[0].samples);

   retval = select(FD_SETSIZE, &stat_set, NULL, NULL, &tick_info);
   if(retval != 0)
  message_proc(&daemon_info);

   printf("Returned: %d \n", retval);

   } while(1);
   return 0;
}

int
message_proc(daemon_obj *daemon_info)
{
   char tbuffer[MAX_RX_LEN];
   char *bufptr;
   int  nbytes, tries, int_fd;
   int  i;

   i = MAX_RX_LEN;
   while ((nbytes = read(int_fd, bufptr, tbuffer + sizeof(tbuffer) - bufptr - 
1)) > 0)
   {
  bufptr += nbytes;
  i--;
  if (bufptr[-1] == '\n' || bufptr[-1] == '\r')
 break;
  if (i == 0)
 return(OVR_FLOW);
   }
   *bufptr = '\0';
   bufptr = tbuffer;
   printf("%s\n",tbuffer);
   return (SUCCESS);

}

(from io_func.c)

#include/* Standard input/output definitions */
#include 
#include   /* UNIX standard function definitions */
#include/* File control definitions */
#include  /* POSIX terminal control definitions */
#include 

/* Local includes */
#include 

/*
   open_port opens a serial port for I/O

   daemon_info  -> points to the common daemon_info structure
   stat_or_ovrd -> determines which set of io information to use
   0 = statnet info, 1 = override relay info
*/

int
open_ioport(daemon_obj *daemon_info, int stat_or_ovrd)
{
   char *device, *buffer_to, *buffer_from;
   int int_fd, int_baudrate;
   struct termios options;

   if(stat_or_ovrd == STAT) {
  device = daemon_info->ioport.stat_ioport;
  int_baudrate = daemon_info->ioport.stat_baudrate;
   } else if(stat_or_ovrd == OVRD) {
  if( daemon_info->ioport.port_linked == FALSE) {
 device = daemon_info->ioport.ovrd_ioport;
 int_baudrate = daemon_info->ioport.ovrd_baudrate;
  } else if( daemon_info->ioport.port_linked == TRUE) {
 buffer_from = daemon_info->ioport.stat_ioport;
 buffer_to = daemon_info->ioport.ovrd_ioport;
 strcpy(buffer_to, buffer_from);
 buffer_to[sizeof(buffer_to) - 1] = NULL;
 daemon_info->ioport.ovrd_baudrate = 
daemon_info->ioport.stat_baudrate;
 daemon_info->ioport.ovrd_fd = daemon_info->ioport.stat_fd;
 return SUCCESS;
  }
   } else { return FAILURE; }

   int_fd = open(device, O_RDWR | O_NOCTTY | O_NDELAY);
   if(stat_or_ovrd == STAT){
  daemon_info->ioport.stat_fd = int_fd;
   } else {
  daemon_info->ioport.ovrd_fd = int_fd;
   }

   if (int_fd == FAILURE) {
  if(stat_or_ovrd == 0){
 printf("Unable to open thermostat port at %s\n", device);
  } else {
 printf("Unable to open override relay at %s\n", device);
  }
  return(IO_ERROR);
   } else {
  fcntl(int_fd, F_SETFL, 0);
   }

   tcgetattr(int_fd, &options);

   if(

Re: freebsd-questions Digest, Vol 43, Issue 4

[J. Seth Henry]

Guys,
You can get a two slot chassis for a mini-ITX or flex-ATX board. The Travla 
C137 can take a 2-slot riser, though you are limited to using a 2.5" HDD. I 
used one of these chassis' for my primary router, with two 3Com 3C905TX NIC's 
installed. Although present and working, I don't use the onboard NIC; though 
the problems I had may have been with the cable modem, not the NIC.

Caseoutlet sells them, but you can get more info on them from Travla. (http://
www.travla.com/Products/C137/c137.html)

Keep in mind, the onboard NIC is there, so all you really need is one 
additional PCI NIC.

Regards,
Seth Henry

On Tuesday 13 January 2004 01:37, [EMAIL PROTECTED] wrote:
> Date: Tue, 13 Jan 2004 01:25:22 +
> From: Chris Howells <[EMAIL PROTECTED]>
> Subject: Re: Mini atx for firewall
> To: [EMAIL PROTECTED]
> Message-ID: <[EMAIL PROTECTED]>
> Content-Type: Text/Plain;  charset="iso-8859-1"
>
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> On Wednesday 19 November 2003 14:24, Francisco Reyes wrote:
> > My primary concern is the network card. Since these small machines only
> > have one PCI slot I will add one card for the internal network and then
> > would need the onboard card to connect to the outside world.
>
> I just got a 4 port Adaptec NIC very very cheaply from ebay (about £20 GBP,
> which included international shipping). Works great with de(4).
>
> I had the same problem with lack of PCI slots,  my server/router is
> mini-ATX based and so only has three PCI slots, so it's working great now
> with PCI IDE ,SCSI and 4 port net.

___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Free X terminals for a good home!

[J. Seth Henry]

Guys/Gals,
   In another attempt to reduce my inventory of gadgets, I've decided to to a 
bit more purging. This time, it's X terminals. Yes - I do have the server 
side software for all of them, so they won't end up as doorstops.

2x IBM Netstation 1000 terminals. Nice, fast - but limited to 256 colors. They 
also require an NFS server to mount the OS, as they don't have the PCMCIA 
slot for local storage. I have given up on attempting to run NetBSD on them, 
as I am no kernel hacker. They have an unbelievable amount of RAM (64 in one, 
32 in the other), but only about 12 is required for the X server.

2x NCD Explora 451 terminals. Also nice, though not as fast as the 
Netstations. These, unfortunately, have the faulty PCI bridge chip - limiting 
them to 256 colors. Trust me on that one, I learned the hard way... At 256 
colors, though, they are quite stable. These DO have 12MB PCMCIA flash cards, 
so they don't require an NFS server.

2x NCD Explora 701 terminals. Nice, fast - and they run in 16-bit color. One 
of them is a bit finicky about booting up, but I suspect the SIMM socket just 
needs a bit of cleaning. The other works fine. Not sure why, but the X server 
has some "issues" with certain X apps. Specifically xmms and mozilla. The 
"good" one has a 12Mb PCMCIA memory card.

The NCD terminals have a copy of NCDware 5.1.140 on their flash memory cards - 
and their NFS servers are enabled (so you can mount them remotely, and muck 
with the configuration). I have the Netstation server software, which I can 
put on a CD-R, or I can make it available on an FTP server.

These terminals are great for headless servers running in closets, or for 
application servers. In fact, my primary server doesn't even have a video 
card or keyboard. It literally has only a power cord, network cable, and SCSI 
cable. I use two NCD Explora 451's (with the good PCI bridge) as displays.

As a side note, they DO support NAS audio (it's called MWM audio on the 
Explora's, but it is compatable with NAS). However, the output is EXTREMELY 
noisy. You can hear the mouse move by listening to the static...

Lastly, these are full of old EDO SIMM's. Most are 16Mb modules, but some are 
32Mb modules. However, the RAM goes with the terminals. :)

They are available for the cost of shipping them to you. (Free if you happen 
to live near Ft. Meade or Baltimore MD)

Regards,
Seth Henry

___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Accessing DOCSIS diagnostics from within/behind FreeBSD router

[J. Seth Henry]

Guys,
I'm not sure if this is even a FreeBSD question, but googling hasn't turned up 
much on it, so I thought I'd toss this one out there.

I have a Motorola SB5100 cable modem directly attached to a FreeBSD router 
(running ipfilters/ipnat). The external network is a comcast segment, and is 
assigned a dynamic IP. The internal network is routed on 192.168.1.x, where 
the router is 192.168.1.254.

The trick is, the cable modem is on the "external" side, but apparently 
listening on 192.168.1.100 for HTTP requests (for its diagnostics report).

Is there anyway to access this diagnostic page without temporarily plugging 
the CM into a Windows box?

Thanks,
Seth Henry

___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: Mini atx for firewall

[J. Seth Henry]

The C137 (in my case, black with a 90W PSU). It wil accomodate a flex ATX 
board, as well as the smaller Mini ITX board. If you order the dual riser 
card, they will throw in an extra extender with it (since they assume you 
will be running an ITX board in it)

Case Outlet doesn't appear to carry them, but you can get an AGP riser from 
the company that builds them, should you want to use a flex ATX board. My 
next pvr system will likely be built in one of these.

One important caveat - you can't stuff both a normal 3.5" HDD and a 2nd PCI 
card.  Fortunately, the bracket can accomodate a laptop (2.5") hard disk as 
well as a normal 3.5" drive, so I went that route instead.

Regards,
Seth Henry

On Thursday 20 November 2003 13:25, [EMAIL PROTECTED] wrote:
> On Thu, 20 Nov 2003, J. Seth Henry wrote:
> > Guys,
> > Case Outlet*, and perhaps others by now, have the Travla Flex ATX / mini
> > ITX case that will accomodate two PCI cards. I have an 933MHz EPIA board
> > with two 3c905TX-C NICs, and have seen a substantial improvement in
> > performance over my old Netgear router.
>
> Which model did you get?
> Don't see any model as "Flex". The models they have are C### (ie C137,
> etc). The only one I see listed with 2 PCI is the 137. Is that the one you
> got?

___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: Mini atx for firewall

[J. Seth Henry]

Guys,
Case Outlet*, and perhaps others by now, have the Travla Flex ATX / mini ITX 
case that will accomodate two PCI cards. I have an 933MHz EPIA board with two 
3c905TX-C NICs, and have seen a substantial improvement in performance over 
my old Netgear router. 

Trust me, the onboard NIC's are crap. If you are building a firewall/router - 
get real NIC's. On the other hand, most cable modems are band limited by the 
cable company to about 1.5 to 2Mbps, so a USB ethernet device might not be a 
serious limitation - but I would definitely suggest a good NIC for the LAN 
side. I've had problems with the rl device on my ITX board "locking up"

Regards,
Seth Henry

*I've done business with them before, and they seem to have fair prices, and 
decent configurations - but other than that, I don't have any relations with 
them.

On Wednesday 19 November 2003 15:00, [EMAIL PROTECTED] 
wrote:
> On Wed, Nov 19, 2003 at 04:11:46PM +0100, Nico Meijer wrote:
> > Hi Francisco,
> >
> > >Anyone used a mini ATX machine with FreeBSD?
> >
> > It's mini ITX and yes, just did one yesterday. Small, quiet and
> > beautiful. ;-)
> >
> > It was a ME6000 (fanless 600Mhz machine):
> > http://www.freebsd.org/cgi/getmsg.cgi?fetch=794445+0+/usr/local/www/db/te
> >xt/2003/freebsd-questions/20030928.freebsd-questions
> >
> > >My primary concern is the network card. Since these small machines only
> > >have one PCI slot I will add one card for the internal network and then
> > >would need the onboard card to connect to the outside world.
> >
> > I tried a 3com 3c905 with this box and it wouldn't boot. Putting in a
> > RTL8139 worked flawlessly. Since the box won't be doing any 'real' work,
> > that's okay with me for now.
> >
> > HTH... Nico
>
> I'm using a USB Ethernet adapter for the 'outside' interface on my ME6000,
> since I needed the PCI slot for the wireless card.  Seems to work just
> fine - it's only talking to a cable modem so the fact that the USB
> connection only runs at 11Mbps is not a problem.  Just another option to
> consider.

___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Problems with Kdevelop under 4.9-REL

[J. Seth Henry]

Guys,
I know this doesn't *seem* like a FreeBSD question, but the problems started 
after an upgrade from 4.8 to 4.9. I understand a lot of libraries got minor 
version upgrades as well.

Has anyone had any problems using the Kdevelop editor? I find that it 
occasionally hangs while typing. There doesn't appear to be any pattern to 
it, but I have noticed that if I type the same thing when I restart the app, 
it will crash again, and at the same character. I haven't found any other 
issues with the app, so I have started using kate instead.

Does anyone else use Kdevelop under FreeBSD, and have you noticed this problem 
since the upgrade?

Thanks,
Seth Henry

___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: freebsd-questions Digest, Vol 33, Issue 6

[J. Seth Henry]

Actually, I have noted this same issue, and both points are correct.

I have a Compaq IA-1 internet terminal which I converted into an X terminal. 
The hardware (was) unmodified, and ran WinCE with no active cooling at all. 
The little machine was perfectly stable, and in fact was designed to never 
completely power down - but instead enter a sleep state when the power button 
was pressed.

I then ran Midori Linux on the system (my first attempt at an X terminal), but 
the X server and mouse driver had some serious issues. Nevertheless, the 
hardware didn't lock up or crash.

I then loaded FreeBSD 4.8-REL on the box, and it started locking up right and 
left. Eventually, I added a cooling fan/ heatsink to the AMD K6-2 CPU, and 
the lockups were greatly reduced. (they still occur, but only under duress). 
Keep in mind, all I changed was the OS - the bus clock and multiplier didn't 
change. Eventually, I installed a K6-III+ mobile processor, and now I very 
rarely get lockups - but it does run noticeably warmer.

This isn't just on AMD hardware, either. I have a dual PIII server that 
suffers the same problem. It runs at least 4-5 degC cooler under RedHat Linux 
(doing the same chores) than it does under 4.8-REL. However, it is a much 
better built system than the IA-1, and doesn't crash, although the cooling is 
so loud that I've been tempted to put Linux back on it just to get rid of 
some of the fans.

The fact is, FreeBSD, for some reason, causes hardware to run hotter. Perhaps 
it is a difference in the idle routine, perhaps it is more "active" about 
checking hardware - I'm no kernel expert. However, this *IS* an issue. For 
those who don't believe the OS can drive the power requirements of a system, 
think again. I installed a SmartUPS on my network, and monitored the load on 
the power supply. Yep - it increased running FreeBSD versus Windows2k.

However, I feel that FreeBSD is, overall, a superior operating system. There 
is no way I would go back to the hell that is linux - much less Win2k. As 
such, I just do a little more homework when buying hardware.

Regards,
Seth Henry

On Tuesday 04 November 2003 13:42, [EMAIL PROTECTED] 
wrote:
> Date: Tue, 4 Nov 2003 09:45:51 -0500
> From: Paul Mather <[EMAIL PROTECTED]>
> Subject: Re: Overheating attributed to Freebsd --sysctl variables
> notavailable--
> To: [EMAIL PROTECTED]
> Message-ID: <[EMAIL PROTECTED]>
> Content-Type: text/plain; charset=iso-8859-1
>
> On Mon, 3 Nov 2003 21:07:45 -0700 (MST), Technical Director
> <[EMAIL PROTECTED]> wrote:
>
> => Forgive me for saying:
> =>
> => If this system is borked with FreeBSD due to the cpu's not cycling
> => 'down', then use a different operating system. FreeBSD is not
> responsible => for your trouble if you can solve the problem by moving on.
> Doing so and => solving the problem is more important than holding the OS
> and the => contributors to it accountable to something so seemingly far
> fetched. =>
> => One way to test overall integrity of your hardware is to boot to bios
> and => leave it. Does it bake out on you? Then there is definitely
> something => wrong with your hardware, perhaps a fan is spinning less rpms
> than when => new.
> =>
> => In my humble opinion this is probably not associated with the OS, but,
> => that doesn't solve 'your' problem. So besides seeing it for myself I
> can't => see an absolute need to use FreeBSD, in your words the problem,
> and not => use some other [$]NIX.
> =>
> => One last thing, if your CPU's are baking out and crashing, are you not
> => nervous that under load this will happen no matter what the OS? Tweaking
> => system variables will not help you if your server is working ultra-hard,
> => at some point you will reach a mark that your system should still be
> able => to do which currently it can't.
> =>
> => I doubt hardware manufactuers put out equipment that can't run at 100%
> at => least.
>
> FWIW, I doubt the accuracy of that last paragraph, and don't think
> this is "so seemingly far fetched" at all. :-)
>
> I have a related problem.  In my case, it's a borrowed laptop on which
> I installed FreeBSD 5.1-CURRENT (quite a while ago, but last
> {build,install}{kernel,world} was circa July 2003).  Also installed on
> the system is Windows 2000 Professional.  The related problem I have
> is that I can fairly easily get the laptop to power off due to
> thermally-initiated shutdown using FreeBSD (complete with "current
> temperature has exceeded system limits" type messages on the console
> beforehand), but can't seem to do so via Win2K. :-(
>
> Now I know that in a sense this is apples and oranges, because I don't
> do precisely the same things under both operating systems.  But, it
> seems that high-CPU/system activity under FreeBSD will ultimately lead
> to a thermal shutdown, but not on Win2K (no so far as I've been able
> to manage, anyway).  This is inconvenient, to say the least.  For
> example, a FreeBSD buildworld or buildkernel will not co

RE: Via EPIA 800Mhz

[J. Seth Henry]

>Hi!
>
>  Does anyone know if the Via EPIA 800MHz is supported in any version of
>freebsd. I tried it with 4.6.2 and it reboots as soon as kernel loads.
>Or do I need to enable any specific options in the kernel config.
>
>It has the following CPU-
>VIA C3 800 E-Series processor, 800 MHz
>
>I would appreciate any kind of help.
>
>Thanks
>
>***
> Pranav A. Desai

Yes, it does. My ipfilter/NAT machine is running 4.8-REL on a 933MHz EPIA 
board, and I have an X terminal running 4.8-REL on a 800MHz EPIA board.

I use the following kernel configuration (for the X terminal):

# Kernel configuration for gearbox (4/25/2003) working copy

machine i386
cpu I686_CPU
ident   gearbox
maxusers0

options INET#InterNETworking
#optionsINET6   #IPv6 Communications Protocols
options FFS #Berkeley Fast Filesystem
options FFS_ROOT#FFS usable as root device [keep this!]
options SOFTUPDATES #Enable FFS soft updates support
options MFS #Memory Filesystem
options MD_ROOT #MD is a potential root device
options MSDOSFS #MSDOS Filesystem
options CD9660  #ISO 9660 Filesystem
options CD9660_ROOT #CD-ROM usable as root, CD9660 required
options PROCFS  #Process filesystem
options COMPAT_43   #Compatible with BSD 4.3 [KEEP THIS!]
options SCSI_DELAY=1000 #Delay (in ms) before probing SCSI
options UCONSOLE#Allow users to grab the console
options USERCONFIG  #boot -c editor
options VISUAL_USERCONFIG   #visual boot -c editor
options KTRACE  #ktrace(1) support
options SYSVSHM #SYSV-style shared memory
options SYSVMSG #SYSV-style message queues
options SYSVSEM #SYSV-style semaphores
options P1003_1B#Posix P1003_1B real-time extensions
options _KPOSIX_PRIORITY_SCHEDULING
options ICMP_BANDLIM#Rate limit bad replies
options KBD_INSTALL_CDEV# install a CDEV entry in /dev
options QUOTA
options SUIDDIR
options NO_F00F_HACK
options DDB_UNATTENDED

device  isa
device  eisa
device  pci

# Floppy drives
#device fdc0at isa? port IO_FD1 irq 6 drq 2
#device fd0 at fdc0 drive 0
#device fd1 at fdc0 drive 1

# ATA and ATAPI devices
device  ata
device  atadisk # ATA disk drives
device  atapicd # ATAPI CDROM drives
#device atapifd # ATAPI floppy drives
#device atapist # ATAPI tape drives
options ATA_STATIC_ID   #Static device numbering

# SCSI Controllers
#device ahc # AHA2940 and onboard AIC7xxx devices
#device sym # NCR/Symbios Logic device

# SCSI peripherals
device  scbus   # SCSI bus (required)
device  da  # Direct Access (disks)
#device sa  # Sequential Access (tape etc)
device  cd  # CD
device  pass# Passthrough device (direct SCSI access)

# atkbdc0 controls both the keyboard and the PS/2 mouse
device  atkbdc0 at isa? port IO_KBD
device  atkbd0  at atkbdc? irq 1 flags 0x1
device  psm0at atkbdc? irq 12
device  vga0at isa?

# splash screen/screen saver
pseudo-device   splash

# syscons is the default console driver, resembling an SCO console
device  sc0 at isa? flags 0x100

# Floating point support - do not disable.
device  npx0at nexus? port IO_NPX irq 13

# Power management support (see LINT for more options)
#device apm0at nexus? disable flags 0x20 # Advanced Power Management

# Serial (COM) ports
device  sio0at isa? port IO_COM1 irq 4
device  sio1at isa? port IO_COM2 flags 0x10 irq 3

# Parallel port
device  ppc0at isa? irq 7
device  ppbus   # Parallel port bus (required)
device  lpt # Printer
device  plip# TCP/IP over parallel
device  ppi # Parallel port interface device
#device vpo # Requires scbus and da


# PCI Ethernet NICs.
device  miibus
device  vr  # Intel EtherExpress PRO/100B (82557, 82558)

# Pseudo devices - the number indicates how many units to allocate.
pseudo-device   loop# Network loopback
pseudo-device   ether   # Ethernet support
pseudo-device   sl  1   # Kernel SLIP
#pseudo-device  ppp 1   # Kernel PPP
#p

4.8-REL firewall/gateway not playing nicely with Comcast COM21 modem

[J. Seth Henry]

Hey gang,
I have been trying to build an Internet gateway using a 933MHz EPIA
mainboard, and a couple of 3Com 3C905C-TX NIC cards. The gateway works
great, under low load - but has a problem with dropping connectivity
under load.

At first, I thought it might be the VIA LAN port, a vr device. However,
I put two 3Com cards in the box, and it still has problems. Both boards
are known good - they run just fine, at full loads, in other systems.

I have noticed it has a real issue when I window applications through
ssh, or use the cisco ATA (for Vonage VOIP). Sometimes it will work just
fine for hours, then just die. The router host itself is fine - it just
stops routing. I can login at the console, run ifconfig, etc. It just
won't send or receive packets.

Sometimes this causes the cable modem to hang, but other times the cable
modem appears fine. I can't tell, of course, but it is happily blinking
away as normal. I typically reboot both the router and the modem when
this occurs, so I don't know for sure if it was still "alive".

Oddly enough, sometimes this issue "self-corrects". Today, I lost
connectivity for an hour, then it came back up on its own.

Given the odd nature of the problem, I'm not sure what info I should
include - but I'll take a stab at it.

-dmesg:



Copyright (c) 1992-2003 The FreeBSD Project.
Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994
The Regents of the University of California. All rights
reserved.
FreeBSD 4.8-RELEASE #0: Mon Oct 20 19:32:12 EDT 2003
[EMAIL PROTECTED]:/usr/src/sys/compile/router
Timecounter "i8254"  frequency 1193182 Hz
Timecounter "TSC"  frequency 933371982 Hz
CPU: VIA C3 Samuel 2 (933.37-MHz 686-class CPU)
  Origin = "CentaurHauls"  Id = 0x67a  Stepping = 10
  Features=0x803035
real memory  = 264175616 (257984K bytes)
avail memory = 253591552 (247648K bytes)
Preloaded elf kernel "kernel" at 0xc0369000.
md0: Malloc disk
Using $PIR table, 5 entries at 0xc00fdc80
npx0:  on motherboard
npx0: INT 16 interface
pcib0:  on motherboard
pci0:  on pcib0
pcib1:  at device 1.0 on
pci0
pci1:  on pcib1
pci1:  at 0.0 irq 10
isab0:  at device 17.0 on
pci0
isa0:  on isab0
atapci0:  port 0xc000-0xc00f at device 17.1
on pci0
ata0: at 0x1f0 irq 14 on atapci0
ata1: at 0x170 irq 15 on atapci0
uhci0:  port 0xc400-0xc41f irq 9 at device
17.2 on pci0
usb0:  on uhci0
usb0: USB revision 1.0
uhub0: VIA UHCI root hub, class 9/0, rev 1.00/1.00, addr 1
uhub0: 2 ports with 2 removable, self powered
uplcom0: ATEN International Serial adapter, rev 1.10/0.01, addr 2
uhci1:  port 0xc800-0xc81f irq 9 at device
17.3 on pci0
usb1:  on uhci1
usb1: USB revision 1.0
uhub1: VIA UHCI root hub, class 9/0, rev 1.00/1.00, addr 1
uhub1: 2 ports with 2 removable, self powered
chip1:  at device 17.4 on
pci0
pcm0:  port 0xd400-0xd403,0xd000-0xd003,0xcc00-0xccff irq
3 at device 17.5 on pci0
pcm0:  (id=0x56494161)
pci0:  (vendor=0x1106, dev=0x3065) at 18.0 irq 10
xl0: <3Com 3c905C-TX Fast Etherlink XL> port 0xdc00-0xdc7f mem
0xe400-0xe47f irq 10 at device 19.0 on pci0
xl0: Ethernet address: 00:04:75:95:08:13
miibus0:  on xl0
xlphy0: <3c905C 10/100 internal PHY> on miibus0
xlphy0:  10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto
xl1: <3Com 3c905C-TX Fast Etherlink XL> port 0xe000-0xe07f mem
0xe4002000-0xe400207f irq 11 at device 20.0 on pci0
xl1: Ethernet address: 00:04:75:95:07:fa
miibus1:  on xl1
xlphy1: <3c905C 10/100 internal PHY> on miibus1
xlphy1:  10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto
orm0:  at iomem
0xc-0xcbfff,0xcc000-0xc,0xd-0xd97ff on isa0
atkbdc0:  at port 0x60,0x64 on isa0
atkbd0:  flags 0x1 irq 1 on atkbdc0
kbd0 at atkbd0
psm0:  irq 12 on atkbdc0
psm0: model MouseMan+, device ID 0
vga0:  at port 0x3c0-0x3df iomem 0xa-0xb on
isa0
sc0:  at flags 0x100 on isa0
sc0: VGA <16 virtual consoles, flags=0x300>
sio0 at port 0x3f8-0x3ff irq 4 on isa0
sio0: type 16550A
ppc0:  at port 0x378-0x37f irq 7 on isa0
ppc0: Generic chipset (EPP/NIBBLE) in COMPATIBLE mode
plip0:  on ppbus0
lpt0:  on ppbus0
lpt0: Interrupt-driven port
ppi0:  on ppbus0
joy0 at port 0x201 on isa0
IP Filter: v3.4.31 initialized.  Default = block all, Logging = enabled
ad0: 38154MB  [77520/16/63] at ata0-master UDMA100
acd0: CDROM  at ata1-master PIO4
Mounting root from ufs:/dev/ad0s1a

-- i/f configuration:
ifconfig_xl0="DHCP"
ifconfig_xl1="inet 192.168.1.254  netmask 255.255.255.0"

-- sysctl settings:
net.inet.ip.forwarding=1
net.inet.ip.check_interface=1
net.inet.tcp.blackhole=2
net.inet.udp.blackhole=1
net.inet.tcp.recvspace=65535
net.inet.tcp.sendspace=65535

-- firewall settings:
# External Interface
block out on xl0 all
block in log on xl0 all

pass in quick on xl0 proto tcp from any to any port = 21 flags S keep
frags keep state
pass in quick on xl0 proto tcp from any to any port = 22 flags S keep
frags keep state
pass in quick on xl0 proto tcp from any to any port = 23 flags S keep
frags keep state
pass in quick on xl0 proto udp from any to any port = 68 

isc-dhcp & dyndns

[J. Seth Henry]

Hello,
I (finally) have my FBSD 4.8-REL internet gateway running, and have
replaced my old Netgear router with the new machine. Everything works
except for dynamic DNS updates. In fact, my Cisco ATA actually works
BETTER through the new router :)

I have found several dynDNS updater programs, but they all seem to get
the new IP info from a hardware router's web interface (which I no
longer have). Given that the router is now a *nix box, it would seem
reasonable that this could be simplified. However, I noted on the
dynDNS.org website that they discourage users from simply running
scripts from the dhcp exit script.

How is everyone else updating their dynamic DNS entries from a FreeBSD
based gateway router?

BTW - I'm using isc-dhcp3-3.0.1.r11_1 from the ports tree.

Thanks,
Seth Henry

___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

ipfilter/ipnat weirdness

[J. Seth Henry]

Hello all,
I could use a bit of help with a networking problem. I am trying to
replace a dying Netgear RT314 with a FreeBSD 4.8-REL system configured
as an Internet gateway.

My network is as such:

\
   |
   /--/
  |

|
+---
|
+---
|
+---
|
+---
|
+---
|
+---
|
\---

I would like the Cisco ATA to only be able to route packets to Vonage,
but I that isn't that big of a deal. More important is that I would like
only Vonage to be able to talk to the ATA uninitiated. I haven't even
attempted this yet, as I can't get a connection now.

I need to forward all incoming FTP and SSH sessions to the server on
192.168.1.1. I have attempted this in the ipnat.rules file - however, it
doesn't appear to work.

I know this might sound strange, but I need to map inbound port 23 to an
ssh daemon on the router itself, while using the normal ssh port, 22, on
the internal interface. I imagine this is as simple as simply running
two copies of sshd with different arguments - but I haven't gotten it
working yet.

Everything else can live with just the normal NAT'ed connections.

I managed to get MOST services working with this ipf.rules file, but
ntpd, and the vonage ATA, both report "no route to host" The Vonage ATA
is unable to use tftp or SIP - I don't know if audio is working or not -
but I doubt it.

Does anyone see the problem with this ruleset?

# Interface: all
block in log all
block out log all

# Interface: lo0
pass in quick on lo0 all
pass out quick on lo0 all

# Interface: xl0
pass in quick on xl0 all
pass out quick on xl0 all

# Interface: vr0
# Internal initiated connections
# [passive ftp client to outside world step 1]
pass out quick on vr0 proto tcp from any to any port = 21 flags S keep
state keep frags
pass out quick on vr0 proto tcp from any to any port > 1023 flags S keep
state keep frags

# [ssh to outside world step 1]
pass out quick on vr0 proto tcp from any to any port = 22 flags S keep
state keep frags

# [smtp to outside world]
pass out quick on vr0 proto tcp from any to any port = 25 flags S keep
state keep frags

# [whois to outside world]
pass out quick on vr0 proto tcp from any to any port = 43 flags S keep
state keep frags

# [domain to outside world]
pass out quick on vr0 proto tcp from any to any port = 53 flags S keep
state keep frags
pass out quick on vr0 proto udp from any to any port = 53 keep state
keep frags

# [Vonage tftp]
pass out quick on vr0 proto tcp from any to any port = 69 flags S keep
state keep frags
pass out quick on vr0 proto udp from any to any port = 69 keep state
keep frags

# [http to outside world]
pass out quick on vr0 proto tcp from any to any port = 80 flags S keep
state keep frags

# [ntpd to outside world]
pass out quick on vr0 proto tcp from any to any port = 123 flags S keep
state keep frags
pass out quick on vr0 proto udp from any to any port = 123 flags S keep
state keep frags

# [pop3 to outside world]
pass out quick on vr0 proto tcp from any to any port = 110 flags S keep
state keep frags

# [https to outside world]
pass out quick on vr0 proto tcp from any to any port = 443 flags S keep
state keep frags

# [traceroute to outside world 1st stage ]
pass out quick on vr0 proto udp from any to any port 33434 >< 33525 keep
state keep frags

# [Vonage VOIP]
pass out quick on vr0 proto udp from any to any port 5060 >< 5061 keep
state keep frags
pass out quick on vr0 proto udp from any to any port 1 >< 2 keep
state keep frags

# [ping to outside world]
pass out quick on vr0 proto icmp from any to any keep state keep frags

# External initiated connections
# Secure Shell access (ssh)
pass in quick on vr0 proto tcp from any to any port = 22 keep state keep
frags

# [dhclient]
pass in quick on vr0 proto udp from any to any port = 68 keep state keep
frags

# [Vonage VOIP - SIP]
pass in quick on vr0 proto udp from any to any port = 5060 >< 5061 keep
state keep frags

# [traceroute to internal host 2nd stage: receiving error code of
icmp-type 3
# (destination unreachable) and icmp-type 11 (time exceeded)]
pass in quick on vr0 proto icmp from any to any icmp-type 3 keep state
keep frags
pass in quick on vr0 proto icmp from any to any icmp-type 11 keep state
keep frags


Also, here is my ipnat.rules.

map vr0 0.0.0.0/0 -> 0.0.0.0/32 proxy port ftp ftp/tcp
map vr0 192.168.1.0/24 -> 192.168.1.1 proxy port ftp ftp/tcp
map vr0 192.168.1.0/24 -> 192.168.1.1 proxy port ssh ssh/tcp
map vr0 192.168.1.0/24 -> 0.0.0.0/32 proxy port 500 ipsec/udp
map vr0 192.168.1.0/24 -> 0.0.0.0/32 proxy port 7070 raudio/tcp
map vr0 192.168.1.0/24 -> 0.0.0.0/32 portmap tcp/udp 4:6
map vr0 192.168.1.0/24 -> 0.0.0.0/32

Again, most stuff works (web, ftp, dns, pop3, smtp, etc). In fact, I
sent this mail through this gateway.

Any help would be greatly appreciated (especially the Vonage stuff - as
I miss the cheap LD!)

Thanks,
Seth Henry

___

Problem with comserv

[J. Seth Henry]

Hello,
I'm trying to use the comserv daemon in the ports tree to share a SIIG
Cyber 4S multiport serial board. The ports work locally, and it appears
that comserv is, in fact, working. However, I can't write to the ports
once I open them on the remote end.

I don't think it is a permissions problem. I changed the ownership of
/dev/cuaa? to root:wheel, and assigned permissions 664. Other programs
running as root can access the ports properly.

gearbox# ls -l | grep cuaa
crw-rw-r--   1 root  wheel  28, 128 Oct  3 19:43 cuaa0
crw-rw-r--   1 root  wheel  28, 129 Oct  3 16:40 cuaa1
crw-rw-r--   1 root  wheel  28, 130 Oct  3 16:13 cuaa2
crw-rw-r--   1 root  wheel  28, 131 Oct  3 16:13 cuaa3
crw-rw-r--   1 root  wheel  28, 132 Oct  3 16:13 cuaa4

Lastly, when connecting to the comserv control port, typing status
produces this:

comservd> status
COMSERV revision timestamp 2002/06/20 01:52:48 GMT
logdir = /var/log
devdir = /usr/local/comserv
Srl  TCP   Local Endpoint  Remote Endpoint
Id  HostPort Port  Device  Conn Fd  Rd Wr Data Conn Fd  Rd Wr
Data
--- ---  - ---  --- -- --   --- -- --

comserv0 0 comserv  yes   5  X   0   no
rcom2   gearbox2  2200 statnet  yes   4  X   0  yes   9  X  
0
rcom3   gearbox3  2300 rcuaa2   yes   6  X   0  yes  10  X  
0
rcom4   gearbox4  2400 rcuaa3   yes   7  X   0  yes  11  X  
0
rcom5   gearbox5  2500 rcuaa4   yes   8  X   0  yes  12  X  
0

(sorry for the wrap)

I configured the server as such:

# default directory for device log files
logdir /var/log

# default directory from which to make symlinks to /dev pty's
devdir /usr/local/comserv

# a control port that we can use to issue commands to the daemon
ctl comserv comserv

# don't block the remote side of a connection if there is no one
# listening locally
set default options=noblock

# Serve up our own local serial ports com1 and com2 at ports 2100 and
# 2200 respectively
#
#   DevId  Device  Com#  TCP/IP Port  LogFile Spec
#   -  --    ---  
#serve  com1   /dev/cuaa0 1 2100  nolog
serve  com2   /dev/cuaa1 2 2200  log
serve  com3   /dev/cuaa2 3 2300  log
serve  com4   /dev/cuaa3 4 2400  log
serve  com5   /dev/cuaa4 5 2500  log

#DevId  Device   TermSrv   TermsrvTermSrv  LogFile
#   Symlink  Hostname   Port #  TCP/IP Port # Spec
#-  ---    ---  -  ---
add   mir0  statnet   gearbox1   2200  nolog
add   mir1   lcuaa2   gearbox2   2300  nolog
add   mir2   lcuaa3   gearbox3   2400  nolog
add   mir3   lcuaa4   gearbox4   2500  nolog

Note that the local serial ports are also mirrored by comservd on the
local host. These don't work properly either.

I configured the client as such:

# default directory for device log files
logdir /var/log

# default directory from which to make symlinks to /dev pty's
devdir /usr/local/comserv

# a control port that we can use to issue commands to the daemon
ctl comserv comserv

# don't block the remote side of a connection if there is no one
# listening locally
set default options=noblock

# Serve up our own local serial ports com1 and com2 at ports 2100 and
# 2200 respectively
#
#   DevId  Device  Com#  TCP/IP Port  LogFile Spec
#   -  --    ---  
#serve  com1   /dev/cuaa0 1 2100  nolog
#serve  com2   /dev/cuaa1 2 2200  nolog


#DevId  Device   TermSrv   TermsrvTermSrv  LogFile
#   Symlink  Hostname   Port #  TCP/IP Port # Spec
#-  ---    ---  -  ---
add  rcom2  statnet   gearbox2   2200  nolog
add  rcom3   rcuaa2   gearbox3   2300  nolog
add  rcom4   rcuaa3   gearbox4   2400  nolog
add  rcom5   rcuaa4   gearbox5   2500  nolog


It would appear that comserv is the one preventing the write access, but
poking through the man pages revealed nothing about this. The log files
which should be created on the server are empty.

Any help is greatly appreciated,
Seth Henry

___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: FreeBSD as router - performance vs hardware routers

[J. Seth Henry]

Wow, I think you guys have convinced me. I have had very good luck with
FreeBSD on an 933MHz EPIA board. It has performed well, and remained
stable for several months now. Nary a single lockup, even under load
(though it doesn't like floating point math much - [EMAIL PROTECTED] crashes
immediately)

Only the network controller has problems occasionally, sometimes causing
initial connections to hang for a few seconds. I understand it's a quirk
in the VIA ethernet controller - but I've found a dual slot PCI riser
board, so I can load two normal cards into the router.

One quick question, though - how much RAM should I install in this
beast? I have a 65Mb DIMM laying around, but I could probably pull some
128's from my Windows box if need be.

Thanks,
Seth Henry


On Thu, 2003-08-14 at 11:16, Mykroft Holmes IV wrote:
> J. Seth Henry wrote:
> 
> > Hello,
> > I have recently been having problems with my Netgear RT314 broadband
> > gateway router. Having decided to replace it, I started searching for a
> > new router - only to discover that every sub $300 router I found had a
> > history of problems. Lockups, random reboots, or worse, they would just
> > turn into black holes (like my RT314).
> > 
> > First, and I know this is off-topic, is anyone here happy with their
> > router enough to recommend it? I'd prefer to go with a hardware router,
> > but I prize reliability and stability apparently higher than the current
> > crop of manufacturers. Even the Cisco SOHO9x/83x series has a bad track
> > record, and they are $250/$500 respectively! I'd like to keep it under
> > $300, as I can build a mini-ITX box with everything I need for a router
> > for about that.
> > 
> > Barring finding a decent, reliable router, I thought about building a
> > mini-ITX system (with the 800Mhz C3) with a second NIC, and a CF card
> > for storage - and using FreeBSD as a router. I'm fairly certain that I
> > can get most of what I need to work going, DHCP client on the WAN link,
> > DHCP server and NAT/PAT on the LAN side. Apparently, firewall support is
> > built-in as well.
> > 
> > What I'm not sure about is performance. Has anyone built a cable modem
> > gateway router using FreeBSD and "low-end" hardware like this? If so,
> > what were your results?
> > 
> > Also, can a FreeBSD router support things like the Vonage VOIP box (the
> > Cisco ATA186)?
> > 
> > Thanks,
> > Seth Henry
> > 
> 
> 
> Well, a FreeBSD router is going to significantly outperform any of those 
> cheapo routers. Which are mostly running either a custom Linux or 
> something similar on a 386 or 486 equivalent. Of course, the issues with 
> them tend to be either buggy proprietary code or flaky hardware. Even a 
> P100 running FreeBSD will easily outperform them, and will be very 
> stable if the hardware's decent.
> 
> I've used Linux, Mac OS X (Darwin) and FreeBSD as a router, routing 
> PPPoE 1MB DSL, Dial and my current PPPoA 3MB DSL, on systems ranging 
> from a P90 with 16MB of RAM to the current PowerMac G3/333. The hardware 
> you're looking at is massive overkill, a used P2 or Pentium system is 
> more than enough to route cable or DSL.
> 
> And yes, it will support just about anything you have living behind it. 
> Probably better than the POS hardware routers you were looking at.
> 
> Hardware routers don't really get to be decent until you;'re looking at 
> a real Cisco (1000 series or better) running real IOS.
> 
> As a Note, the top end routers out there, Junipers, run JunOS, which is 
> a FreeBSD variant. A Juniper M160 can route OC192's at wire speed 
> (That's 10Gb/s folks).
> 
> Adam
> 
> 

___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

FreeBSD as router - performance vs hardware routers

[J. Seth Henry]

Hello,
I have recently been having problems with my Netgear RT314 broadband
gateway router. Having decided to replace it, I started searching for a
new router - only to discover that every sub $300 router I found had a
history of problems. Lockups, random reboots, or worse, they would just
turn into black holes (like my RT314).

First, and I know this is off-topic, is anyone here happy with their
router enough to recommend it? I'd prefer to go with a hardware router,
but I prize reliability and stability apparently higher than the current
crop of manufacturers. Even the Cisco SOHO9x/83x series has a bad track
record, and they are $250/$500 respectively! I'd like to keep it under
$300, as I can build a mini-ITX box with everything I need for a router
for about that.

Barring finding a decent, reliable router, I thought about building a
mini-ITX system (with the 800Mhz C3) with a second NIC, and a CF card
for storage - and using FreeBSD as a router. I'm fairly certain that I
can get most of what I need to work going, DHCP client on the WAN link,
DHCP server and NAT/PAT on the LAN side. Apparently, firewall support is
built-in as well.

What I'm not sure about is performance. Has anyone built a cable modem
gateway router using FreeBSD and "low-end" hardware like this? If so,
what were your results?

Also, can a FreeBSD router support things like the Vonage VOIP box (the
Cisco ATA186)?

Thanks,
Seth Henry

___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

FreeBSD programming question

[J. Seth Henry]

Not sure if this is the right list or not, but I could really use some
pointers.

How can I code trap serial port interrupts in my C program?

For example, I want to read values from a serial device every
user-specified number of seconds, calculate some stuff and then sit for
a while. Should the serial device decide it wants to send some data
unsolicited, I would like to enter an interrupt service routine, handle
the communication, and then return to the previous loop.

I can get the loop going by using sleep(n), but I don't know how to
write the ISR in C, and (additionally) make it such that it will run on
any *nix like platform. 

Any pointers, HOWTO's, or examples would be greatly appreciated!

Thanks,
Seth

___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: FreeBSD programming question

[J. Seth Henry]

That looks exactly like what I want. I need to resume programming on
either serial activity and at periodic intervals. Eventually, I plan to
toss networking into the mix, and this program will function as a
daemon, but I'm relatively new to programming for *nix (though not new
to programming in general), so I'm going to steer clear of that until I
get the basic IO working.

I've already written, and for the most part debugged, my configuration
file parser, and this was the next step. :)

When I finish, I want to be able to check the status, and control, the
HVAC system from any terminal on the network. 

Thanks again  for the help,
Seth Henry

On Wed, 2003-08-06 at 13:43, Michael Conlen wrote:
> select() should work for you, similar to trigering an interrupt. Instead 
> of triggering an ISR select() will sleep until there's an event on the 
> file descriptors. So you open() the device for the serial port and 
> select() on it. When you return from select() the return value will tell 
> you why you returned and you handle the situation similar to programing 
> for the 8250 (read from the port to see which event).
> 
> In any case, you can select() on the file descriptors for the standard 
> input and the serial port, though remember that STDIN uses buffered IO 
> and open() will return an unbuffered file descriptor, which is what 
> select() uses, so you need to find the unbuffered file descriptor for 
> the stadard IO, which is either 0, 1 or 2, but I forget which on FreeBSD 
> (I've been doing network daemons to much lately).
> 
> In any case, you create an FD_SET
> 
> fd_set mySet;
> FD_ZERO(&mySet);
> FD_SET(fd, &mySet);
> 
> where fd is the file descriptor returned from open, or the file 
> descriptor for the standard input.
> 
> Use the set as a read set with select along iwth a timeout. struct 
> timeval is
> 
> struct timeval {
> longtv_sec; /* seconds */
> longtv_usec;/* and microseconds */
> };
> 
> if the pointer to the struct timeval is NULL then it waits forever. (or 
> until a signal causes an exit).
> 
> (Note, usleep() is often implemented using select on no file descriptors 
> and a timeval).
> 
> int rc;
> struct timeval myTimeout;
> rc = select(2, &mySet, NULL, NULL, &myTimeout);
> 
> This call will return when either timeval is up or there's data to read 
> on your file descriptors. Be sure to check errno if select returns -1. 
> When select returns the fd_set will be set to the descriptors that are 
> actionable. Use FD_ISSET(fd, &mySet) to see if that file descriptor is 
> waiting to be actioned on (read, write, or other) until you've found all 
> the ones that are ready (the number returned by select()) and do your thing.
> 
> There's a really great book called "Advanced Programing in the UNIX 
> environment" and it will show you all the system calls you ever needed 
> to know to work with UNIX, though it's light on the concurrency issues, 
> but it doesn't sound like your writing multithreaded memory shared 
> programs so it's no worry.
> 
> I haven't really looked at the sio driver, but I doubt it, it still 
> works with the 8250, which only had one IO address (tell it what you 
> want to do, read the result, tell it what you want to do, send it info, 
> tell it what you want to know, read the info it has... ...programing was 
> much more fun back then).
> 
> 
> 
> 
> J. Seth Henry wrote:
> 
> >It appears that my experience on microcontrollers is throwing me off.
> >I'm used to having a touch more control at the hardware level.
> >
> >It sounds like I would be best served by setting up a loop that sleeps
> >for a certain number of milliseconds, and then looks for new data in the
> >serial port buffers. Knowing the amount of time per loop, I could handle
> >the periodic data polling as well. My largest concern was in creating a
> >CPU hog. I don't want to slow the system down by constantly accessing
> >the serial port.
> >
> >It occurred to me that I may be able to deal with this another way. I
> >can poll the thermostat for MOST things, only the user interface
> >requires fairly speedy interactions. I can simply listen for the "ENTER"
> >button, and then increase the polling rate until the UI exits.
> >
> >As it were, I'm poking around in the ports to see how other programs
> >have dealt with this.
> >
> >Just out of curiousity, since I can check the driver source, does the
> >sio driver add any additional buffering, or does it simply read the
> >16byte FIFO on the serial port? Most of the messages I am expecting

Re: FreeBSD programming question

[J. Seth Henry]

It appears that my experience on microcontrollers is throwing me off.
I'm used to having a touch more control at the hardware level.

It sounds like I would be best served by setting up a loop that sleeps
for a certain number of milliseconds, and then looks for new data in the
serial port buffers. Knowing the amount of time per loop, I could handle
the periodic data polling as well. My largest concern was in creating a
CPU hog. I don't want to slow the system down by constantly accessing
the serial port.

It occurred to me that I may be able to deal with this another way. I
can poll the thermostat for MOST things, only the user interface
requires fairly speedy interactions. I can simply listen for the "ENTER"
button, and then increase the polling rate until the UI exits.

As it were, I'm poking around in the ports to see how other programs
have dealt with this.

Just out of curiousity, since I can check the driver source, does the
sio driver add any additional buffering, or does it simply read the
16byte FIFO on the serial port? Most of the messages I am expecting
should fit in that FIFO anyway.

Thanks,
Seth Henry

On Wed, 2003-08-06 at 09:58, Malcolm Kay wrote:
> On Wed, 6 Aug 2003 07:00, J. Seth Henry wrote:
> > Not sure if this is the right list or not, but I could really use some
> > pointers.
> >
> > How can I code trap serial port interrupts in my C program?
> >
> 
> For any modern hosted system interrupt trapping and servicing is in the 
> province of the system -- it should not be a userland activity.
> 
> > For example, I want to read values from a serial device every
> > user-specified number of seconds, calculate some stuff and then sit for
> > a while. Should the serial device decide it wants to send some data
> > unsolicited, I would like to enter an interrupt service routine, handle
> > the communication, and then return to the previous loop.
> 
> There are a number of techniques which may or may not suit your needs;
> it is not too clear just what you are trying to do.
> 
> Generally the system will provide some buffering of input so it is not usually
> important that your code processes each character immediately on arrival.
> 
> In many cases using placing the select(2) system call in a loop will meet the 
> needs.
> 
> In more difficult cases you may need to look at threading pthread(3) or 
> forking fork(2) or vfork(2)
> 
> >
> > I can get the loop going by using sleep(n), but I don't know how to
> > write the ISR in C, and (additionally) make it such that it will run on
> > any *nix like platform.
> 
> You might be able to do something at system level by adding your driver to the 
> kernel possibly as a kernel module. This is not generally the way to go if 
> userland alternatives work and it certainly will be very operating system and 
> platform specific possibly even requiring significant editing from one OS 
> version to the next.
> 
> >
> > Any pointers, HOWTO's, or examples would be greatly appreciated!
> >
> > Thanks,
> > Seth
> >
> 
> Malcolm Kay
> 

___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: Help PLEASE! on proper kernel config file to use serial portswith puc driver

[J. Seth Henry]

Stan,
Could you describe your hardware in a bit more detail. I can't imagine
why your system would hard lock, unless there is something seriously
wrong. Also, I'm curious why puc is detecting your card as sio4 and sio5
(COM5 and COM6 respectively) Most mainboards only have sio0/COM1 and
sio1/COM2. What is using sio2 and sio3?

BTW - I would start from a generic kernel configuration if you don't
remember what you did. Then, make the necessary changes to the copy of
GENERIC, and go from there. Then, rebuild the kernel - it probably isn't
necessary, but it will at least return your kernel to something closer
to the baseline.

Regards,
Seth Henry

On Thu, 2003-07-31 at 13:18, stan wrote:
> On Thu, Jul 31, 2003 at 10:34:14AM -0400, J. Seth Henry wrote:
> > All you need in your kernel config is 'device puc'. You already appear
> > to have this in your config, as your system detected the adapter.
> > 
> 
> Him
> 
> I've made some "progress" on this ;-(
> 
> I have created teh devices in /dev. I now have just the puc line in the
> kernel config, and the ports are getting detected like this:
> 
> puc0:  port 0xfce0-0xfcff irq 11 at device 6.0 on pci0
> sio4: type 16550A
> sio5: type 16550A
> 
> That;s the good nes. The bad news is that when I do "cu -l cuaa4", the
> computer locks up! No response to any keyboard input, no response to a ping
> etc. I have to power cycle it to get it back :-(
> 
> Sugestions?

___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

RE: Help PLEASE! on proper kernel config file to use serial portswith puc driver

[J. Seth Henry]

All you need in your kernel config is 'device puc'. You already appear
to have this in your config, as your system detected the adapter.

You will have to "sh MAKEDEV cuaa" (where 0 < n < NUM_PORTS) to get
the device nodes in your /dev directory.

Alternately, since they have sequential minor numbers, you can make them
yourself.

'mknod cuaa0 c 28,128 root:wheel'
'mknod cuaa1 c 28,129 root:wheel'
'mknod cuaa2 c 28,130 root:wheel'
'mknod cuaa3 c 28,131 root:wheel'
'mknod cuaa4 c 28,131 root:wheel'
'mknod cuaa5 c 28,131 root:wheel'

You can also do this for the tty nodes as well.

I prefer making the nodes myself, but the MAKEDEV script will do the
same thing.

Good luck,
Seth Henry


>OK, I've spent all night complaining kernels with no luck. I've read
>the man page for puc, I've read the man page for sio, I've looked at
>the code for puc, I've searched d Googlee, and STILL I can't get sio
>devices assigned to my PCI serial port card.
>
> It's detected as:
>
>puc0:  port 0xfce0-0xfcff irq 11 at device
>6.0 on pci0
>sio4: type 16550A
>sio5: type 16550A
>
>
>But I feel certain I don't have the correct syntax in my kernel conf
>file for the sio ports I want to assign to this.

___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: Remap mouse buttons for remote X serverss

[J. Seth Henry]

LLeweLLyn,
Thanks for the idea, but unfortunately, the X server is running on the
Explora, and it doesn't have the equivalent of an XF86Config. It is
beginning to look like I may just be out of luck, unless I can get KDE
or gnome to handle the mouse mangling for me, as they (and the apps),
are the only thing running on the BSD box.

Thanks,
Seth Henry

On Sun, 2003-07-20 at 23:29, LLeweLLyn Reese wrote:
> "J. Seth Henry" <[EMAIL PROTECTED]> writes:
> 
> > Hi gang,
> > I've recently started using NCD Explora's to connect to my FreeBSD
> > server. They are quiet, reasonably fast, and small. Unfortunately,
> > NCDware has some odd quirks.
> > 
> > The first is that it only supports a two-button mouse. What's odd is
> > that when I run xev, it reports button1 and button3? (I have a wheel
> > mouse attached - but the wheel button doesn't show up).
> > 
> > I'd like to chord the mouse buttons, but I'm not sure how to do that,
> > given that I'm no longer running X locally. IOW - I'd like to be able to
> > use cut and paste in xterms again.
> 
> You should be able to chord by putting this in your XF86Config:
> 
> Option "Emulate3Buttons"
> 
> Also, you may find:
> 
> http://www.xfree86.org/~dawes/4.3.0/mouse5.html#21
> 
> useful in general.
> 
> 
> > 
> > The other is that the page-up key doesn't work correctly. However, I
> > think that may be "fixable" with xmodmap.
> [snip]
> 
> You could try different XkbModels.
> 

___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Remap mouse buttons for remote X serverss

[J. Seth Henry]

Hi gang,
I've recently started using NCD Explora's to connect to my FreeBSD
server. They are quiet, reasonably fast, and small. Unfortunately,
NCDware has some odd quirks.

The first is that it only supports a two-button mouse. What's odd is
that when I run xev, it reports button1 and button3? (I have a wheel
mouse attached - but the wheel button doesn't show up).

I'd like to chord the mouse buttons, but I'm not sure how to do that,
given that I'm no longer running X locally. IOW - I'd like to be able to
use cut and paste in xterms again.

The other is that the page-up key doesn't work correctly. However, I
think that may be "fixable" with xmodmap.

Thanks,
Seth Henry

___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

offtopic: NCD Exploras and FreeBSD

[J. Seth Henry]

I know this is a bit offtopic, but I'm hoping someone can help out.

I have a couple of NCD Explora 451 X terminals I picked up on the cheap.
They came with NCDware 5.1.140. Presently, I'm connecting to a FreeBSD
server running 4.8-REL with KDE 3.1.

The problem is that I've been getting random kernel panics on the
terminals. I don't have the exact message, but it goes something like
this:

assertion failure "rRingPtr -> ..." in file lance_ordered_input.c line
99

I'm probably toast, but I thought I'd give it a shot and see if anyone
else has run into this.

Thanks,
Seth Henry

___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

NAS 1.6 hangs on certain streams

[J. Seth Henry]

Guys/gals,
I have been experiencing an odd problem with my NAS setup. I finally got
things to work, sort of.

I have a small FreeBSD 4-8-REL system running nasd (NAS 1.6). I want to
connect to it via a separate machine on the network.

Now, I CAN play simple .WAV files via auplay, and this works. I can also
use auinfo to get the particulars of the server:

alexandria# auinfo -audio gearbox:0
Audio Server:   tcp/gearbox:8000
Version Number: 2.2
Vendor: Network Audio System Release 1.6 - VoxWare
Vendor Release: 1
Min Sample Rate:5000
Max Sample Rate:44100
Max Tracks: 32
Number of Formats:  7
Formats:ULAW8  LinearUnsigned8  LinearSigned8
LinearSigned16MSB  LinearUnsigned16MSB
LinearSigned16LSB  LinearUnsigned16LSB
Number of Elem Types:   12
Element Types:  ImportClient  ImportDevice  ImportBucket
ImportWaveForm  Bundle  MultiplyConstant 
AddConstant
Sum  ExportClient  ExportDevice  ExportBucket
ExportMonitor
Number of Wave Forms:   2
Wave Forms: Square  Sine
Number of Actions:  3
Actions:ChangeState  SendNotify  Noop
Number of Devices:  3
Device 0:
Changable:  Gain  LineMode
ID: 0x23
Kind:   PhysicalInput
Use:Import
Format: LinearUnsigned8
Num Tracks: 2
Access: Import  List
Description:"Stereo Channel Input"
Min Rate:   5000
Max Rate:   44100
Location:   Left  Right  External
Gain Percent:   50
Num Children:   0
Device 1:
Changable:  Gain
ID: 0x22
Kind:   PhysicalOutput
Use:Export
Format: LinearSigned16LSB
Num Tracks: 2
Access: Export  List
Description:"Stereo Channel Output"
Min Rate:   5000
Max Rate:   44100
Location:   Center  Internal
Gain Percent:   50
Num Children:   1
Children:   0x21
Device 2:
Changable:  Gain
ID: 0x21
Kind:   PhysicalOutput
Use:Export
Format: LinearSigned16LSB
Num Tracks: 1
Access: Export  List
Description:"Mono Channel Output"
Min Rate:   5000
Max Rate:   44100
Location:   Center  Internal
Gain Percent:   50
Num Children:   0
Number of Buckets:  0

However, if I attempt to use mpg123 or xmms with the NAS plugin, the
server hangs. After it hangs, I can no longer use auplay or auinfo.
There is nothing in the log files to indicate what happened, it simply
no longer does anything. When using xmms or mpg123, I don't hear
anything - there isn't even a few bad samples, just silence.

Now, I have verified that both mpg123 and xmms-nas can send audio data
to my IBM Netstations. It's bad, but audible (probably due to the lack
of CPU in the netstations).

It doesn't appear to be related to sample size - as I have played 16-bit
waves through auplay. 

Any ideas?

Thanks,
Seth Henry

___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Need help with NAS server setup

[J. Seth Henry]

Hello,
I recently split up my FreeBSD server into two machines. One is a small
ITX based system than [is intended to] handle audio and home automation.
I installed nasd 1.6 on this machine, and it appears to be loaded (I can
telnet to port 8000 and it connects), but I can't actually use it. So
far, I've tried connecting with XMMS and mp3blaster, using the address
gearbox:0, however, when I actually try to play a file, I get the error,
"Failed to open sound device." (in mp3blaster).

I used the default nasd.conf, which (for playback) should be fine. Audio
is working, as I can play files using a local player. Also, I checked
fstat, and nothing is holding the device open. (which is kind of
surprising, given that I would have thought nasd would have held it
open)

Am I missing something?

Thanks,
Seth Henry

___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: X TrueType font spacing

[J. Seth Henry]

It isn't just an X problem, it's also a KDE problem. I ran into this recently, 
after installing some IBM netstations on my network. When I attempted to use 
anything other than the fixed fonts in Konsole, I would get this strange 
spacing and video corruption. On my system console, they work fine. I believe 
it may have something to do with the extensions that KDE uses. When I load K 
apps on an X terminal, I get several warnings about GLX not being supported.

It is interesting that you ran into this problem ostensibly windowing ON a 
freeBSD host, though. I didn't have any problems when I loaded KDE on console 
- only when using remote X terminals that didn't support all of the 
extensions KDE uses. My console runs Xfree86 4.3.0, and I'm running KDE 3.1

BTW - it occurs for all truetype fonts - not just the Microsoft TTF files. 
Believe me, I've tried several. The BIGGER problem (at least for Konsole) is 
that there doesn't appear to be any support for ANSI line characters, such 
that sysinstall and other ncurses apps look terrible. I usually bring up a 
traditional Xterm if I need to use a curses app.

Regards,
Seth Henry
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

RE: Dynamic DNS (DDNS)

[J. Seth Henry]

Jay,
I'm on Comcast in MD, and my DHCP lease is a bit longer - on the order of 3 
months. Not sure if that is because I am a holdover of @Home or what. Just a 
note of caution, though. Comcast doesn't technically allow any kind of 
server. They will tolerate SMALL servers that don't generate a lot of 
bandwidth "under the radar" though. I have a *very* private FTP server, sshd 
and telnet (to my UPS). The rest is firewalled off. As unfair as it may seem, 
getting busted for running an FTP/HTTP server is worse than for running Kazaa 
or some other P2P crap. (despite the fact the latter tend to use more 
bandwidth)

I get around the dhcp problem by having my system send me an email every 
morning - and looking at the headers. It's also a great way to get morning 
status from my systems.

I thought about going to the DDNS route, until I heard stories of Comcast 
dropping customers who did this. There is also the fact that Comcast, unlike 
Millenium, doesn't actually block any ports (yet). (I think 25 may be an 
exception). I fear if very many people start trying to run servers and attach 
them to DNS records, Comcast may start blocking inbound ports as well.

Yes, this warning is self-serving. If Comcast starts blocking ports, the only 
choice left is DSL - and I HATE verizon with a passion. They have screwed me 
over so many times, I lost count; and I dread the day I have to sign up for 
DSL because Comcast actually starts enforcing the "no server" rule strictly.

Regards,
Seth Henry

Hello. I am on Comcast CABLE and the DHCP lease is
only 4 days to expire, all the time. So my IP changes
every four days. I was wondering in FreeBSD
(FreeBSD4.8) how I can set up Dynamic DNS. I checked
the online docs and I could not find anything on DDNS,
is it some rc.x file or a file in /etc for me to edit?
I would be more than happy if you got back with me
A.S.A.P. Thanks.

- Jay Buhrt
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

nutball video question

[J. Seth Henry]

Ok, I'm not sure if this will work (or if it does, how well), but I'm
curious to see what happens.

I have one of the older Happauge WinTV boards (that is supported by
FreeBSD). Unfortunately, the only machine with an open PCI slot is my
headless server. I have a number of IBM netstations attached to this
server via a 100Mbps switched ethernet LAN. Currently, I am using KDE as
my desktop environment. I have no idea what the X server is, but I do know
KDE apps grumple a lot about the X server lacking features.

Is it possible to stream video to these X terminals, even if it's not
"movie quality"? I'm thinking something along the lines of a security
camera setup, where it is OK if the video is the size of a business card,
and isn't updated terribly fast. That being said, could the same stream
be sent to two or more terminals simultaneously?

The likely problems here are that the video transmission would be done in
X, which could result in bandwidth issues, and the little problem of my
monitor locking the video device.

Alternately, and perhaps even better, is there a way to capture still
images from this board, for use as a "webcam"?

FYR, this is strictly for experimentation purposes. :)

Thanks,
Seth Henry
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: freebsd-questions Digest, Vol 12, Issue 2

[J. Seth Henry]

Actually, this should work, but it will require some twiddling with the
disks partition table in disklabel. I used to have an old drive array with
a bunch of HP labelled Seagate ST32550WD drives. For some unearthly
reason, some of the drives were formatted to have only 2 billion bytes
(2000MB), not 2GB (2047MB). I was able to get the array going by manually
altering the partition tables on the larger drives to match the smallest
drives. The rest of the space was left unformatted, and the array worked
just fine.

I later figured out how to load new firmware in the drives, and low-level
formatted them all to match - but for about a month I had the array going
with the mix-and-match.

In this case, you will only have to muck with the partition table on the
one disk, since it is bigger than the rest. First, create at least two
partitions on the disk, filling the entire space. Then, use disklabel to
get the paramaters for one of the 120's. Write all this down, and then use
diskabel to make the FIRST partition on your 170 match. You will need to
do some math to calculate the paramters for the second partition, but it
isn't too hard. As a bonus, you can even use this second partition while
the first partition is part of an array. Unfortunately, I don't believe
you can boot from this partition, but you could mount it as /usr or
something.

If you really don't mind losing the 50Gb, you can just make the disklabel
info EXACTLY the same - but 50Gb is quite a bit of space to toss.

Keep in mind, this was a while back - probably 4 years, but I definitely
remember doing this. All the drives were SCSI, but that shouldn't matter
in this case.

Seth Henry


On Mon, Jun 09, 2003 at 05:10:37PM +0200 or thereabouts, Josh seemed to
write:
> I have three 120GB disks and one 170GB disk. The first three is forming
> a raid-5 volume using Vinum and the last one is just fooling around
> without any purpose.
>
> Can I add this 170GB to the raid5 volume in any way at all? I do realise
> that I will loose 50Gb, but that's better than not using it at all.

Sorry, no.
On the other hand, if the first three were a concat plex, you *could* do
it,
and you wouldn't even lose 50gb!
Your best bet is either:
a) mount the 170gb on /usr2 or something
b) backup the data on the raid5, restore to a concat

HTH,
-- Josh


___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: Reliable USB NIC?

[J. Seth Henry]

I have had very good luck with the Linksys USB100TX adapters. I have four
of them supporting small X terminals, and they have turned out to be more
reliable than the terminals (they crash for reasons unrelated to their
network connections). They also have decent performance for a USB 1.x
device.

If your system has support for USB 2.0, Linksys does make a USB 2.0
version of the adapter, but I don't have any experience with them.

Regards,
Seth Henry

>I know it sounds like an oxymoron, but I'm looking for a reliable USB NIC
>that's supported by FreeBSD 4.8 or -STABLE.  It's going to be attached to
>my cable modem (currently 512kbps down, 128kbps up, transferring a few
>hundred MB daily) so speed is not really relevant.  What I do need is
>something that will stay up for months -- essentially the time between
>kernel upgrades -- without needing any attention from me.  Sadly it has
>to be USB, since the machine it's going in only has room for 1 PCI card,
>and that's occupied by the wireless adapter.
>
>Hmm, I guess 'not too expensive' and 'available in the UK' should be on
>that list too :-)
>
>Does such a beast exist?
>
>Cheers,
>
>Scott

___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Kdevelop C/C++ reference problem SOLVED

[J. Seth Henry]

I was somewhat distraught to find that after all my trouble, the "package"
was little more than a bunch of HTML files. ARGH! Unfortunately, for me, I
discovered this after mucking with the configure script.

Anyway, I discovered that the --enable-mt option in the configure script
was only allowed on a linux system. Apparently, there is a case
structure, and if it sees anything other than "some linux" it craps
out. Since FreeBSD obviously supports multithreading of Qt, I "fixed"
this by commenting out the case statements, leaving only the GCC check.
Not the "correct" solution, but it works.

It also installs to the wrong place. I manually moved the files from
/usr/local/kde/share/doc/HTML/en/kdevelop/reference to
/usr/local/share/doc/HTML/en/kdevelop/reference. And, since the installer
didn't remove it, I removed the existing index.html and symlinked c.html
to index.html.

Lastly, there is an error in c.html. The Master Index link should
reference master_index.html, not mindxbdy.html. So far, this is the only
place I have encounted the incorrect link.

Not entirely certain if it was worth it, but I now have the Kdevelop
C/C++ reference installed on my dev system. :)

Regards, and thanks for the pointers,
Seth Henry
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: Problem compiling the C/C++ reference for Kdevelop

[J. Seth Henry]

Argh - it appears that I have no libqt.so on my system. Interesting - I
installed from the package system. Having poked through the configure
script, I finally figured out what it was barfing on, and manually
searched to see if it was present, but perhaps in some odd location.
(find / | grep libqt resulted in libqt-mt.so, but no libqt.so)

Next question. Why don't I have a libqt.so?

In the meantime, I'm compiling from source using ports tree. If there is
source for libqt, then I'll know something is up.

Oh, and I accept the dumba** award for failing to notice the
--with-extra-libraries/includes option for the configure script. It now
finds the jpeg libraries.

Thanks,
Seth Henry

On Wed, 4 Jun 2003, Joshua Oreman wrote:

> On Wed, Jun 04, 2003 at 12:57:24PM -0400 or thereabouts, J. Seth Henry seemed to 
> write:
> > I recently started playing around with Kdevelop 2.x on my server, and
> > found it much improved over the older releases. Getting into it, I decided
> > to download and compile the C/C++ reference documentation, and ran into a
> > snag. I'm not sure if it is because the configure script is having
> > problems running on a FreeBSD box or what, but here is what I get:
> >
> > alexandria# ./configure
> > checking build system type... i386-unknown-freebsd4.8
> > checking host system type... i386-unknown-freebsd4.8
> > checking target system type... i386-unknown-freebsd4.8
> > checking for a BSD compatible install... /usr/bin/install -c
> > checking for -p flag to install... yes
> > checking whether build environment is sane... yes
> > checking for mawk... no
> > checking for gawk... no
> > checking for nawk... nawk
> > checking whether make sets ${MAKE}... yes
> > checking for style of include used by make... GNU
> > checking for gcc... gcc
> > checking for C compiler default output... a.out
> > checking whether the C compiler works... yes
> > checking whether we are cross compiling... no
> > checking for executable suffix...
> > checking for object suffix... o
> > checking whether we are using the GNU C compiler... yes
> > checking whether gcc accepts -g... yes
> > checking dependency style of gcc... gcc
> > checking for g++... g++
> > checking whether we are using the GNU C++ compiler... yes
> > checking whether g++ accepts -g... yes
> > checking dependency style of g++... gcc
> > checking whether g++ supports -fno-exceptions... yes
> > checking whether g++ supports -fno-check-new... yes
> > checking whether g++ supports -fexceptions... yes
> > checking how to run the C++ preprocessor... g++ -E
> > checking whether g++ supports -frepo... yes
> > checking for ld used by GCC... /usr/libexec/elf/ld
> > checking if the linker (/usr/libexec/elf/ld) is GNU ld... yes
> > checking for /usr/libexec/elf/ld option to reload object files... -r
> > checking for BSD-compatible nm... /usr/bin/nm -B
> > checking whether ln -s works... yes
> > checking how to recognise dependant libraries... pass_all
> > checking for ranlib... ranlib
> > checking for strip... strip
> > checking whether -lc should be explicitly linked in... (skipping, using
> > no) no
> > checking for objdir... .libs
> > checking for gcc option to produce PIC... -fPIC -DPIC
> > checking if gcc PIC flag -fPIC -DPIC works... yes
> > checking if gcc static flag -static works... yes
> > finding the maximum length of command line arguments... 36865
> > checking if gcc supports -c -o file.o... yes
> > checking if gcc supports -fno-rtti -fno-exceptions ... yes
> > checking whether the linker (/usr/libexec/elf/ld) supports shared
> > libraries... yes
> > checking how to hardcode library paths into programs... immediate
> > checking whether stripping libraries is possible... yes
> > checking dynamic linker characteristics... freebsd4.8 ld.so
> > checking command to parse /usr/bin/nm -B output... ok
> > checking if libtool supports shared libraries... yes
> > checking whether to build shared libraries... yes
> > checking whether to build static libraries... no
> > checking for dlopen in -ldl... no
> > checking for dlopen... yes
> > checking for dlfcn.h... yes
> > checking whether a program can dlopen itself... yes
> > checking whether a statically linked program can dlopen itself... no
> > creating libtool
> > updating cache /dev/null
> > checking host system type... i386-unknown-freebsd4.8
> > checking build system type... i386-unknown-freebsd4.8
> > ltcf-cxx: with_gcc=yes ; with_gnu_ld=yes
> > checking for objdir... .libs
> > checking for g++ option to produce PIC... -fPIC -DPIC
> &

Spring cleaning giveaway - UPDATE

[J. Seth Henry]

I managed to get rid of some of my surplus gear, but not all.

I had a fellow claim the serial terminal, and some of the K6 CPU's, but
never got back to me with an address. If you still want these items, let
me know.

I had someone else looking for a K6 CPU, but my emails have been bouncing.

Right now, I still have:

1) CIT224 serial terminal VT52/100/200 - runs up to 9600 baud reliably,
19200 with occasional problems.

~15 lbs

2) 4x K6-2 266 CPU's. Presently in a tray, but I can divide them up.

3) 1x K6-3+ 450 CPU with heatsink/fan (not sure if it works)

4) Voodoo2 board. I believe this is the 12Mb version of the card. I have
the passthrough cable, and I believe the SLI cable as well.

5) 4x 1Mb 30-pin SIMM's

6) 1x Compaq RAM for 386LTE, or similar vintage laptop.

Last call - after this, it goes to the dump, or the local thrift shops.

Regards,
Seth Henry
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Problem compiling the C/C++ reference for Kdevelop

[J. Seth Henry]

I recently started playing around with Kdevelop 2.x on my server, and
found it much improved over the older releases. Getting into it, I decided
to download and compile the C/C++ reference documentation, and ran into a
snag. I'm not sure if it is because the configure script is having
problems running on a FreeBSD box or what, but here is what I get:

alexandria# ./configure
checking build system type... i386-unknown-freebsd4.8
checking host system type... i386-unknown-freebsd4.8
checking target system type... i386-unknown-freebsd4.8
checking for a BSD compatible install... /usr/bin/install -c
checking for -p flag to install... yes
checking whether build environment is sane... yes
checking for mawk... no
checking for gawk... no
checking for nawk... nawk
checking whether make sets ${MAKE}... yes
checking for style of include used by make... GNU
checking for gcc... gcc
checking for C compiler default output... a.out
checking whether the C compiler works... yes
checking whether we are cross compiling... no
checking for executable suffix...
checking for object suffix... o
checking whether we are using the GNU C compiler... yes
checking whether gcc accepts -g... yes
checking dependency style of gcc... gcc
checking for g++... g++
checking whether we are using the GNU C++ compiler... yes
checking whether g++ accepts -g... yes
checking dependency style of g++... gcc
checking whether g++ supports -fno-exceptions... yes
checking whether g++ supports -fno-check-new... yes
checking whether g++ supports -fexceptions... yes
checking how to run the C++ preprocessor... g++ -E
checking whether g++ supports -frepo... yes
checking for ld used by GCC... /usr/libexec/elf/ld
checking if the linker (/usr/libexec/elf/ld) is GNU ld... yes
checking for /usr/libexec/elf/ld option to reload object files... -r
checking for BSD-compatible nm... /usr/bin/nm -B
checking whether ln -s works... yes
checking how to recognise dependant libraries... pass_all
checking for ranlib... ranlib
checking for strip... strip
checking whether -lc should be explicitly linked in... (skipping, using
no) no
checking for objdir... .libs
checking for gcc option to produce PIC... -fPIC -DPIC
checking if gcc PIC flag -fPIC -DPIC works... yes
checking if gcc static flag -static works... yes
finding the maximum length of command line arguments... 36865
checking if gcc supports -c -o file.o... yes
checking if gcc supports -fno-rtti -fno-exceptions ... yes
checking whether the linker (/usr/libexec/elf/ld) supports shared
libraries... yes
checking how to hardcode library paths into programs... immediate
checking whether stripping libraries is possible... yes
checking dynamic linker characteristics... freebsd4.8 ld.so
checking command to parse /usr/bin/nm -B output... ok
checking if libtool supports shared libraries... yes
checking whether to build shared libraries... yes
checking whether to build static libraries... no
checking for dlopen in -ldl... no
checking for dlopen... yes
checking for dlfcn.h... yes
checking whether a program can dlopen itself... yes
checking whether a statically linked program can dlopen itself... no
creating libtool
updating cache /dev/null
checking host system type... i386-unknown-freebsd4.8
checking build system type... i386-unknown-freebsd4.8
ltcf-cxx: with_gcc=yes ; with_gnu_ld=yes
checking for objdir... .libs
checking for g++ option to produce PIC... -fPIC -DPIC
checking if g++ PIC flag -fPIC -DPIC works... yes
checking if g++ static flag -static works... yes
finding the maximum length of command line arguments... 36865
checking if g++ supports -c -o file.o... yes
checking if g++ supports -fno-rtti -fno-exceptions ... yes
checking whether the linker (/usr/libexec/elf/ld) supports shared
libraries... yes
checking how to hardcode library paths into programs... immediate
checking whether stripping libraries is possible... yes
checking dynamic linker characteristics... freebsd4.8 ld.so
checking command to parse /usr/bin/nm -B output... ok
checking if libtool supports shared libraries... yes
checking whether to build shared libraries... yes
checking whether to build static libraries... no
checking for dlopen in -ldl... no
checking for dlopen... yes
checking for dlfcn.h... yes
checking whether a program can dlopen itself... no
appending configuration tag "CXX" to libtool
checking for msgfmt... /usr/local/bin/msgfmt
checking for gmsgfmt... /usr/local/bin/msgfmt
checking for xgettext... /usr/local/bin/xgettext
checking how to run the C preprocessor... gcc -E
checking for ANSI C header files... yes
checking for sys/types.h... yes
checking for sys/stat.h... yes
checking for stdlib.h... yes
checking for string.h... yes
checking for memory.h... yes
checking for strings.h... yes
checking for inttypes.h... yes
checking for stdint.h... no
checking for unistd.h... yes
checking for main in -lutil... yes
checking for main in -lcompat... yes
checking for crypt in -lcrypt... yes
checking for socklen_t... socklen_t
checking for dnet_ntoa in -ldnet... no
ch

Spring cleaning update

[J. Seth Henry]

Wow - most of the stuff in the list was claimed in a half hour. Anyway,
the following items are remaining:

1) tray of 4 AMD K6-2 266 CPU's
2) AMD K6-3+ mobile processor with heatsink/fan. Not sure if it works
3) Compaq RAM module for 386LTE
4) 4x 1Mb 30-pin SIMMs

I've decided to roll the Paralan converter in with the Symbios card, since
most of the people asking about it weren't aware a HVD controller couldn't
drive a SE/LVD device.

Regards,
Seth
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Spring cleaning - hardware give-away (CONT)

[J. Seth Henry]

Ok, I've about finished going through the closets and boxes, and I have
the following:

9) Tray of 4 K6-2 266MHz processors.

10) K6-3+ (mobile) processor. Not sure if it works, though. The system it
was in was dead. I know the mainboard was dead, but I'm not sure if the
CPU bought it with the board. Hell, even if it doesn't work, the box is so
light it shouldn't cost much to ship. I will ship this with a Heatsink&Fan
combo (I know the fan works ;)

11) set of 4 SIMM's (old school, 30-pin). Great for soundblasters with the
DRAM sockets on them. Not sure what size, probably 1MB each.

12) 4Mb Compaq RAM card for a 386 laptop. Compaq part# 121127-007, spares#
129947-001. Sad story about this module. I had an old 386 laptop I
originally used to write and debug ASM for the M68HC11 in college with. It
had this memory card, giving it a total of 6Mb of RAM (whopping plenty for
what I used it for). Then, thinking I might find an upgrade, I took the
card out - and promptly lost it. Later, I sold the laptop because it
didn't have enough ram to boot Linux or FreeBSD. Then, I graduated, and
found the card in a bunch of papers in the back of my desk. (sigh>

Probably too damn old to be of interest, but it was in a 386LTE. Not sure
what other models might use it.

Again, first come, first served - and remember, all you have to come up
with is shipping. I'd just like to see this gear end up in the hands of
someone who could use it.

Later,
Seth Henry
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: Spring cleaning - hardware give-away

[J. Seth Henry]

I live near Baltimore, Maryland (US) ZIP is 21113

Regards,
Seth Henry

On Sun, 1 Jun 2003, MaryAnne Olsen wrote:

> What is your zip code?
> - Original Message -
> From: "J. Seth Henry" <[EMAIL PROTECTED]>
> To: <[EMAIL PROTECTED]>; <[EMAIL PROTECTED]>
> Sent: Sunday, June 01, 2003 4:37 PM
> Subject: Spring cleaning - hardware give-away
>
>
> > I have a bit of functional, but older equipment I hate to throw away, but
> > no longer have the space to keep. If anyone is interested, it's yours for
> > the price of (actual) shipping. Some of this stuff might be able to go on
> > eBay (and may, if no one claims any of it), but I'd rather see if any of
> > my fellow FreeBSD users/fans are interested first.
> >
> > 1) Old vinum disk array. Contains 11 Seagate ST32550WD (HVD differential)
> > SCSI hard disks, a 20MB/s HVD/LVD converter, HVD terminator, and beefy
> > power supply. There is a cut out for a 8" fan, but the fan has long since
> > gone out. However, the mounting hardware for the fan and filter remain.
> >
> > I used this in college to store MP3's, and as far as I know, they are
> > still on the array.
> >
> > Weighs approximately 35 pounds - I can probably be talked into breaking
> > this up if you don't want all of the disks, or are only interested in the
> > SCSI converter, etc.
> >
> > 2) 15 meter (yes, meters) HVD SCSI cable. It's long, folks. Originally I
> > picked this up on eBay so I could keep the above array in a different room
> > (for noise reasons).
> >
> > Somewhere around 5-6 pounds
> >
> > 3) CIT 224 serial terminal. Supports VT52/100/200 terminal modes, and can
> > operate (reliably) up to 9600 baud. 19200 is supported, but has problems.
> > I currently use it as a "head" for my headless server, but am looking to
> > replace it with an X terminal that draws just as much juice, and has a
> > GUI :) The keyboard is a tad yellow, but otherwise fine. It's previous
> > life was spent monitoring a router, so there may be some faint burn-in.
> >
> > Probably 10-15 pounds with keyboard.
> >
> > 4) Symbios UW HVD SCSI controller. I'm trying to ditch all my HVD SCSI
> > gear, and this is the last controller on hand. Great if you want the above
> > array, but don't have an HVD controller. It is supported by FreeBSD (works
> > great too)
> >
> > 5) Voodoo 2 3D graphics accelerator - with passthrough cable. Still holds
> > up for older games. I may even have the SLI cable somewhere, though I only
> > have the one card.
> >
> > 6) Digi Digiboard PC/4e with DB9 (male) breakout cable. This is the older
> > ISA version of the card. In excellent condition (was bought new), but
> > replaced with PCI card after a server upgrade. This board is well
> > supported by FreeBSD - it formed the communications portion of a home
> > automation controller for some time. No manuals or disks, though - long
> > since lost in moves.
> >
> > 7) Analog Devices SHARC ez-kit lite development kit. Comes with
> > development board, power supply, and CD-ROM with software. I thought I was
> > going to get into programming DSP's, and bought the kit - but later
> > decided home automation was my thing. Works great, has stereo input and
> > output. Great for home-made equalizers or effects boxes, though it is a
> > tad underpowered.
> >
> > 2-3 pounds (mostly the power supply)
> >
> > 8) Motorola MC68ICS05P microcontroller development kit. Comes with lots of
> > interesting stuff, including the dev board. This part is well supported by
> > free tools, including from Motorola. Perfect for a senior design project -
> > unfortunately, I've already got a MSEE, and I don't plan on using this
> > kit anymore.
> >
> > 9) Paralan NARROW HVD-SE SCSI converter. Mounted in a 5.25" chassis, it
> > allows you to attach normal narrow SCSI devices to a HVD SCSI controller
> > (or vice versa). It is presently configured to terminate, but this can be
> > changed with jumpers.
> >
> > More stuff may be dredged up as I finish Spring cleaning, but that's it
> > for now.
> >
> > First come, first served - and remember, all you have to come up with is
> > shipping. I'd just like to see this gear end up in the hands of someone
> > who could use it.
> >
> > Later,
> > Seth Henry
> > ___
> > [EMAIL PROTECTED] mailing list
> > http://lists.freebsd.org/mailman/listinfo/freebsd-questions
> > To unsubscribe, send any mail to
> "[EMAIL PROTECTED]"
>
>
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Spring cleaning - hardware give-away

[J. Seth Henry]

I have a bit of functional, but older equipment I hate to throw away, but
no longer have the space to keep. If anyone is interested, it's yours for
the price of (actual) shipping. Some of this stuff might be able to go on
eBay (and may, if no one claims any of it), but I'd rather see if any of
my fellow FreeBSD users/fans are interested first.

1) Old vinum disk array. Contains 11 Seagate ST32550WD (HVD differential)
SCSI hard disks, a 20MB/s HVD/LVD converter, HVD terminator, and beefy
power supply. There is a cut out for a 8" fan, but the fan has long since
gone out. However, the mounting hardware for the fan and filter remain.

I used this in college to store MP3's, and as far as I know, they are
still on the array.

Weighs approximately 35 pounds - I can probably be talked into breaking
this up if you don't want all of the disks, or are only interested in the
SCSI converter, etc.

2) 15 meter (yes, meters) HVD SCSI cable. It's long, folks. Originally I
picked this up on eBay so I could keep the above array in a different room
(for noise reasons).

Somewhere around 5-6 pounds

3) CIT 224 serial terminal. Supports VT52/100/200 terminal modes, and can
operate (reliably) up to 9600 baud. 19200 is supported, but has problems.
I currently use it as a "head" for my headless server, but am looking to
replace it with an X terminal that draws just as much juice, and has a
GUI :) The keyboard is a tad yellow, but otherwise fine. It's previous
life was spent monitoring a router, so there may be some faint burn-in.

Probably 10-15 pounds with keyboard.

4) Symbios UW HVD SCSI controller. I'm trying to ditch all my HVD SCSI
gear, and this is the last controller on hand. Great if you want the above
array, but don't have an HVD controller. It is supported by FreeBSD (works
great too)

5) Voodoo 2 3D graphics accelerator - with passthrough cable. Still holds
up for older games. I may even have the SLI cable somewhere, though I only
have the one card.

6) Digi Digiboard PC/4e with DB9 (male) breakout cable. This is the older
ISA version of the card. In excellent condition (was bought new), but
replaced with PCI card after a server upgrade. This board is well
supported by FreeBSD - it formed the communications portion of a home
automation controller for some time. No manuals or disks, though - long
since lost in moves.

7) Analog Devices SHARC ez-kit lite development kit. Comes with
development board, power supply, and CD-ROM with software. I thought I was
going to get into programming DSP's, and bought the kit - but later
decided home automation was my thing. Works great, has stereo input and
output. Great for home-made equalizers or effects boxes, though it is a
tad underpowered.

2-3 pounds (mostly the power supply)

8) Motorola MC68ICS05P microcontroller development kit. Comes with lots of
interesting stuff, including the dev board. This part is well supported by
free tools, including from Motorola. Perfect for a senior design project -
unfortunately, I've already got a MSEE, and I don't plan on using this
kit anymore.

9) Paralan NARROW HVD-SE SCSI converter. Mounted in a 5.25" chassis, it
allows you to attach normal narrow SCSI devices to a HVD SCSI controller
(or vice versa). It is presently configured to terminate, but this can be
changed with jumpers.

More stuff may be dredged up as I finish Spring cleaning, but that's it
for now.

First come, first served - and remember, all you have to come up with is
shipping. I'd just like to see this gear end up in the hands of someone
who could use it.

Later,
Seth Henry
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

RE: The clock is too fast in FreeBSD!

[J. Seth Henry]

Eric,
First, you didn't mention how fast the clock was under FreeBSD. If you
are talking about minutes/seconds, then you can use ntpd to keep the
clock in line. If you have permanent network access, then you can
actually keep your clock to within a few milliseconds of the NIST/Navy
"official" time.

For a server, you really should be running a time synchronization service
anyway, negating any clock "problems" in the local OS. Although most
useful for multiple servers, even a stand-alone server can benefit from
being in agreement with a "standard" clock. As a result, Windows2k/XP,
Linux, and FreeBSD all support time synchronization out of the box. My
local network has two tier 2 time server (which attach to a navy time
server), both of which can be used by rdate on terminals to get the
correct time.

I have used this setup for years, and the clocks are always
the most accurate in the house - such that I use them to set the VCR
clock, my own wristwatch, and any other miscellanous non-network attached,
clock.

However, even with all of that, I haven't noticed a serious problem on any
of my FreeBSD systems wrt the clock. An uncorrected clock in FreeBSD seems
to lose/gain about 0.5 second per day on standard commodity hardware.

Second, FreeBSD 5.0/5.1-BETA are not production ready. I am still using
the 4.x-REL series, as they are much more stable. In fact, I will probably
wait until 5.2-REL before upgrading my primary app server (it's a dual
proc, and can benefit from the new multi-processor support). There may
very well be bugs in these newer versions that could be causing your clock
problem. I would suggest you try 4.8-REL if you are evaluating FreeBSD
for a server environment.

If you feel you may have found a problem with FreeBSD 5.1 BETA, please
post in the freebsd-hardware list. If the clock is screwed up in the
latest versions, I'm sure they would love to know about it now, rather
than later.


>Hi!
>The clock in FreeBSD is too fast!
>I tried GENERIC kernel, the BSD clock is still too fast.
>the problem is on 5.0 Release, 5.1 BETA1, and 5.1 BETA2.
>I have not yet tried 4.x.
>I'm using PII 366Mhz Acer notebook w/ 192mb RAM ALi Chipset
>but there is no problem on Win98 and Linux(Redhat 8)

>I guess, in a Windows system, the timing function read time
>from CMOS(Hardware Clock), where as FreeBSD just add itself
>which is too dangerous for a server.
>
>Hope the problem will be solved in future.
>good luck.
>
>
>Eric.
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: SSH failing randomly in 4.7-REL (SOLVED)

[J. Seth Henry]

It turned out to be a problem with dhclient. It wanted to write to
/etc/resolv.conf which was on a read-only file system at the time.
Eventually, it crashed out - perhaps trashing the interface configuration
on its way down.

I moved resolv.conf to /usr/local/etc and symlinked it in /etc - and the
problem appears to be resolved. I haven't seen any other strange network
related problems since.

Thanks,
Seth Henry

BTW - the Linksys USB100TX uses the aue driver.

Thanks,
Seth Henry

On Fri, 4 Apr 2003, Toomas Aas wrote:

> Hi!
>
> > All of these machines have identical hardware. They use Linksys USB100TX
> > USB network interfaces, and are on a 100Mb ethernet segment. The machines
> > themselves are AMD K6-2+ systems, with 32Mb of RAM. The boot volume is a
> > 16Mb sandisk, and they mount everything but /etc, /dev, and /boot from a
> > microdrive.
>
> I don't have any experience at all with USB Ethernet devices or DHCP so I
> apologize in advance if my comments are totally irrelevant.
>
> What driver are these Linksys devices using? Is it dc? I've seen a lot
> of messages in the list about some problem with Linksys NICs using dc
> driver, where the MAC address is incorrectly set as 08:00:08:00:08:00.
> If there are multiple devices with identical MAC addresses on the same wire,
> then there can certainly be strange networking issues.
>
> Another thing that can cause the "host is not on local network" message
> might be an incorrectly set netmask.
>
> ifconfig output from some of these machines would be interesting.
> --
> Toomas Aas | [EMAIL PROTECTED] | http://www.raad.tartu.ee/~toomas/
> * User Error: Replace user.
>
>

___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: dhclient acts odd with read-only '/' (SOLVED)

[J. Seth Henry]

That did it - I copied resolv.conf to /usr/local/etc and created a
symlink. dhclient runs properly, and now I can remote reboot without
making a visit.

Now if I could just figure the /dev thing out...

Thanks again for the help!
Seth Henry

On Fri, 4 Apr 2003, Dan Pelleg wrote:

> "J. Seth Henry" <[EMAIL PROTECTED]> writes:
>
> > Ok, I think I just qualified for an idiot award. After a little more
> > poking around, I discovered that it was the read-only filesystem that was
> > causing the problem. I rebuilt the microdrive image, and included a
> > special /dev this time - which I mount over the original /dev.  Now, I
> > don't seem to be having any problems with sshd.
> >
> > Unfortunately, I appear to have made my dhclient problem worse. Now, it
> > hangs, producing volumes of log data like this:
> >
> > Apr  3 17:52:45  dhclient: New IP Address (aue0): 192.168.1.5
> > Apr  3 17:52:45  dhclient: New Subnet Mask (aue0): 255.255.255.0
> > Apr  3 17:52:45  dhclient: New Broadcast Address (aue0): 192.168.1.255
> > Apr  3 17:52:45  dhclient: New Routers: 192.168.1.254
> > Apr  3 17:52:45  dhclient: New Network Number: 192.168.1.0
> > Apr  3 17:52:45  dhclient: New Broadcast Address: 192.168.1.255
> > Apr  3 17:52:45  dhclient: New IP Address (aue0): 192.168.1.5
> > Apr  3 17:52:45  dhclient: New Subnet Mask (aue0): 255.255.255.0
> > Apr  3 17:52:45  dhclient: New Broadcast Address (aue0): 192.168.1.255
> > Apr  3 17:52:45  dhclient: New Routers: 192.168.1.254
> >
> > I have to hit CTRL-C to get a login...
> >
> > I tried running dhclient under truss, but it gives me a segmentation fault
> > before getting very far. It doesn't seem to be attempting to write to
> > files on a read-only filesystem though. I can post the output of truss if
> > anyone is interested.
> >
>
> I don't remember the history of this thread, but my first thought
> would be that it's probably trying to update /etc/resolv.conf and/or
> /var/db/dhclient.leases
>
> I don't think a failure to update resolv.conf would result in
> this behaviour. But for dhclient.leases, it might.
>
> Advance warning: if you're using ntp, you will have a similar
> issue for ntp.drift.
>
> --
>
>   Dan Pelleg
>

___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: dhclient acts odd with read-only '/' & other questions about/dev

[J. Seth Henry]

Dan,
That's an interesting idea on the resolv.conf, but /var/db is on a
writable file-system. I'll try creating a symlink to a copy of resolv.conf
in /usr/local/etc and see if that clears things up.

Thanks,
Seth Henry

On Fri, 4 Apr 2003, Dan Pelleg wrote:

> "J. Seth Henry" <[EMAIL PROTECTED]> writes:
>
> > Ok, I think I just qualified for an idiot award. After a little more
> > poking around, I discovered that it was the read-only filesystem that was
> > causing the problem. I rebuilt the microdrive image, and included a
> > special /dev this time - which I mount over the original /dev.  Now, I
> > don't seem to be having any problems with sshd.
> >
> > Unfortunately, I appear to have made my dhclient problem worse. Now, it
> > hangs, producing volumes of log data like this:
> >
> > Apr  3 17:52:45  dhclient: New IP Address (aue0): 192.168.1.5
> > Apr  3 17:52:45  dhclient: New Subnet Mask (aue0): 255.255.255.0
> > Apr  3 17:52:45  dhclient: New Broadcast Address (aue0): 192.168.1.255
> > Apr  3 17:52:45  dhclient: New Routers: 192.168.1.254
> > Apr  3 17:52:45  dhclient: New Network Number: 192.168.1.0
> > Apr  3 17:52:45  dhclient: New Broadcast Address: 192.168.1.255
> > Apr  3 17:52:45  dhclient: New IP Address (aue0): 192.168.1.5
> > Apr  3 17:52:45  dhclient: New Subnet Mask (aue0): 255.255.255.0
> > Apr  3 17:52:45  dhclient: New Broadcast Address (aue0): 192.168.1.255
> > Apr  3 17:52:45  dhclient: New Routers: 192.168.1.254
> >
> > I have to hit CTRL-C to get a login...
> >
> > I tried running dhclient under truss, but it gives me a segmentation fault
> > before getting very far. It doesn't seem to be attempting to write to
> > files on a read-only filesystem though. I can post the output of truss if
> > anyone is interested.
> >
>
> I don't remember the history of this thread, but my first thought
> would be that it's probably trying to update /etc/resolv.conf and/or
> /var/db/dhclient.leases
>
> I don't think a failure to update resolv.conf would result in
> this behaviour. But for dhclient.leases, it might.
>
> Advance warning: if you're using ntp, you will have a similar
> issue for ntp.drift.
>
> --
>
>   Dan Pelleg
>

___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

dhclient acts odd with read-only '/' & other questions about /dev

[J. Seth Henry]

Ok, I think I just qualified for an idiot award. After a little more
poking around, I discovered that it was the read-only filesystem that was
causing the problem. I rebuilt the microdrive image, and included a
special /dev this time - which I mount over the original /dev.  Now, I
don't seem to be having any problems with sshd.

Unfortunately, I appear to have made my dhclient problem worse. Now, it
hangs, producing volumes of log data like this:

Apr  3 17:52:45  dhclient: New IP Address (aue0): 192.168.1.5
Apr  3 17:52:45  dhclient: New Subnet Mask (aue0): 255.255.255.0
Apr  3 17:52:45  dhclient: New Broadcast Address (aue0): 192.168.1.255
Apr  3 17:52:45  dhclient: New Routers: 192.168.1.254
Apr  3 17:52:45  dhclient: New Network Number: 192.168.1.0
Apr  3 17:52:45  dhclient: New Broadcast Address: 192.168.1.255
Apr  3 17:52:45  dhclient: New IP Address (aue0): 192.168.1.5
Apr  3 17:52:45  dhclient: New Subnet Mask (aue0): 255.255.255.0
Apr  3 17:52:45  dhclient: New Broadcast Address (aue0): 192.168.1.255
Apr  3 17:52:45  dhclient: New Routers: 192.168.1.254

I have to hit CTRL-C to get a login...

I tried running dhclient under truss, but it gives me a segmentation fault
before getting very far. It doesn't seem to be attempting to write to
files on a read-only filesystem though. I can post the output of truss if
anyone is interested.

Also, on a slightly related note, I noted that mount_devfs wasn't on my
system. Is this not present in 4.7, or did I miss something? It seems
like that would be a better way to handle this situation, particularly since
the microdrive is a slow, and twitchy, device. I think a rash of nasty
crashes I had the last time I got this far was due to /dev being on the
microdrive. I've already had one strange crash since mounting /dev from
the microdrive - which given the history of this project - would indicate
that the system doesn't like having the kernel interface mounted from
there.

This is a  shame, as the system was very stable with /dev on the flash
disk. That said, is there a way to create a memory disk just for /dev, and
if so, how are the device nodes built? I can't netboot, because of the
USB NIC, but I do have the onboard flash disk. As for the memory disk, do
the same newfs parameters apply? I had to specify 'newfs -b 8192 -i 16' to
get all the inodes I needed for /dev.

I'm willing to give 5.0 a shot, but I spent a pretty good bit of time
paring down 4.7 to fit in such a small space. I'm not sure if 5.0, with
all its new features, would be as easy to squeeze. (4.7 just barely fits
on a 16Mb flash and a 340Mb microdrive) I'm even down to tweaking the
newfs paramaters to get stuff to fit.

Again, thanks for the help!
Seth Henry


___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

SSH failing randomly in 4.7-REL

[J. Seth Henry]

I appreciate the help so far in trying to get these X terminals going.
Unfortunately, I have discovered another oddity, this time with sshd and
dhclient. I'm not sure if they are related or not.

The first is with sshd. Randomly, and for no apparent reason, sshd will
refuse to allow logins. Instead, it dumps me out with:

whitetower# ssh dhcp3
Password:
Connection to dhcp3 closed by remote host.
Connection to dhcp3 closed.

Interestingly, I can usually clear this up with a reboot. For example,
dhcp3 would allow logins up until recently and other machines wouldn't.
Now, it is refusing logins - and other machines are. They were all
rebooted at about the same time,

All of these machines are binary identical - including their RSA/DSA key
pairs. This was supposed to make it easier, considering they all obtain
IP addresses via DHCP.

The other is with dhclient. When sshd starts refusing to respond, dhclient
is invariably ballooned out to 13-14Mb of RAM usage - and is quite dead. I
tested this by invalidating all DHCP leases at the server, and the
machines didn't renew leases. Normally, dhclient has an image size of
about 932kB.

I think I might be able to partly explain this behavior based on other
strangeness in the logs. I get a bunch of messages from something called
arpresolver stating that 192.168.1.1 isn't on the local network.
(192.168.1.1 is the XDM host, which each terminal is programmed to
query). I also get messages from arpresolver about 192.168.1.254 (the
router) not being on the local network. The kicker is that ifconfig
reports that the local ip address is 192.168.1.x (where x is from 2 to 33)

running arp -a produces a list of hosts with "incomplete" MAC addresses. I
can manually ping hosts, and from then on arp will show the correct MAC
address. I can also ping the hosts (even when they are "dead"), and they
respond. I don't see ANY messages from aue0 regarding the interface going
down, and I know the adapters are good (they have been running under linux
24/7 for months). Traffic is fairly light right now, because the app
server is still under construction. Right now, they have nothing but the
static xdm login screen on their displays.

Lastly, even when the arp table is rebuilt by pinging hosts, sshd won't
allow incoming connections. It doesn't sever existing connections, though.
I have existing connections to each machine which are still working - but
no new connections.

I don't even know where to start with providing background info - but here
is some:

All of these machines have identical hardware. They use Linksys USB100TX
USB network interfaces, and are on a 100Mb ethernet segment. The machines
themselves are AMD K6-2+ systems, with 32Mb of RAM. The boot volume is a
16Mb sandisk, and they mount everything but /etc, /dev, and /boot from a
microdrive.

BTW - I have (for the moment) started mounting the sandisk read-write, but
the problem still occurs. It doesn't seem to make a difference whether /
is mounted read-only or not.

Many thanks,
Seth Henry

___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: /dev on a read-only filesystem?

[J. Seth Henry]

I'll have to give this a try. Right now, I am just remounting / read-only
after boot as part of my /usr/local/etc/rc.d scripts. I'd prefer to
eliminate all writes, though.  I suppose this means I'm going to
have to repartition the microdrive again. /usr keeps getting smaller and
smaller.

Thanks for the help,
Seth Henry

On Mon, 31 Mar 2003, Lowell Gilbert wrote:

> "J. Seth Henry" <[EMAIL PROTECTED]> writes:
>
> > The trick is, if I make / read-only, I run into problems with /dev. During
> > boot, I get numerous error messages - and things don't seem to work quite
> > right. Is there a way to mount / read-only, while maintaining a working
> > /dev? Can /dev be mounted from another filesystem - or, preferably (since
> > the OS is already running) be linked to, say, /usr/dev?
>
> I think you still need the devices on the root filesystem, even if you
> later mount something else over the directory.  That's because there's
> a chicken and egg problem -- they need to be there for the other
> filesystems to be mounted in the first place.  So the symlink approach
> won't work, but mounting it on top of /dev from elsewhere would work.
>
> I believe the typical approach on diskless machines is to put it into
> an mfs, but you'd have to doublecheck the documentation on it.
>
> You could also use devfs, of course, but I'm not sure, offhand, how
> well that worked before 5.x.
>
>

___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

4.7-REL and the AM79C978C PCNet-Home HNPA/10Base-T adapter

[J. Seth Henry]

I think this came up a while back, and no one had any clues, but this
device doesn't seem to be fully supported in 4.7-REL. The adapter itself
is, but I always get an error message about there being no supported PHY's
- which is interesting, because there are actually two MII phy's in the
ASIC.

Here is the kernel info:
pcn0:  port 0x1c00-0x1c1f mem
0x4120-0x4120001f irq 9 at device 5.0 on pci0
pcn0: Ethernet address: 00:01:fa:ff:ac:57
pcn0: MII without any PHY!
device_probe_and_attach: pcn0 attach returned 6

I have configured my kernel thusly:
# PCI Ethernet NICs that use the common MII bus controller code.
# NOTE: Be sure to keep the 'device miibus' line in order to use these
NICs!
device  miibus0 # MII bus support
device  miibus
device  xl  # 3Com 3c905c support
device  pcn # AMD PCnet32/PCI support

# Pseudo devices - the number indicates how many units to allocate.
pseudo-device   loop# Network loopback
pseudo-device   ether   # Ethernet support
pseudo-device   tun # Packet tunnel.
pseudo-device   pty # Pseudo-ttys (telnet etc)
pseudo-device   md  # Memory "disks"
#pseudo-device  gif # IPv6 and IPv4 tunneling
#pseudo-device  faith   1   # IPv6-to-IPv4 relaying (translation)

# The `bpf' pseudo-device enables the Berkeley Packet Filter.
# Be aware of the administrative consequences of enabling this!
pseudo-device   bpf #Berkeley packet filter

# USB support
device  uhci# UHCI PCI->USB interface
device  ohci# OHCI PCI->USB interface
device  usb # USB Bus (required)
device  ugen# Generic
device  uhid# "Human Interface Devices"
device  ukbd# Keyboard
device  ulpt# Printer
device  umass   # Disks/Mass storage
device  ums # Mouse
# USB Ethernet, requires mii
device  aue # ADMtek USB ethernet
device  cue # CATC USB ethernet
device  kue # Kawasaki LSI USB ethernet

(note - I only included the network and USB sections for brevity)

the xl driver was included for development builds - as my development PC
has a 3Com nic in it (just makes things easier)

Does anyone know if this is on the bug-board, or fixed in the next
release? I ask only because I can't replace it - it is built into the
Compaq IA-1's with ethernet. Presently, I am working around the issue with
a USB NIC, but performance is far from optimal.

Thanks,
Seth Henry

___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

/dev on a read-only filesystem?

[J. Seth Henry]

I have managed, through hook and crook, to get a full 4.7-REL install on a
Compaq IA-1 internet appliance. I put a kernel, /bin, /etc, /boot, /dev,
/proc, and a partial /sbin on the internal flash memory. During boot, I
mount a complete /sbin, /usr and  on a microdrive. Since I want to
reduce the number of writes to the flash, I linked /tmp, /var, and /root
to directories in /usr. So far, so good - the bulk of the write/update
activity is now pointed to the microdrive which has no physical write
limits.

The trick is, if I make / read-only, I run into problems with /dev. During
boot, I get numerous error messages - and things don't seem to work quite
right. Is there a way to mount / read-only, while maintaining a working
/dev? Can /dev be mounted from another filesystem - or, preferably (since
the OS is already running) be linked to, say, /usr/dev?

If not, how much write activity to the actual, physical volume takes place
in /dev. Also, does anything happen on the physical disk with /proc. I
don't think it does squat to the physical disk, since a "procfs"
filesystem is mounted there, but I want to make sure I don't damage the
flash with periodic writes. I would feel best if the internal flash were
completely read-only. BTW - if it wasn't clear, the system boots from
flash, and them mounts the microdrive.

Also, and perhaps unrelated, if I attempt to run getty from the flash, I
get an error message about getty spawning too fast - and I can't ever
login on the console. This doesn't happen when I launch getty from the
microdrive. Odd, but unimportant - as the microdrive is necessary for the
system to "run"

Thanks,
Seth Henry

___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Thanks for the help!

[J. Seth Henry]

I appreciate all the helpful comments regarding programming under FreeBSD.
I think I have enough to take another stab at it. I also discovered that
the developer's handbook has a lot of useful info - though it seems the
chapter on signals is missing?

Thanks again,
Seth Henry


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-questions" in the body of the message

Looking for POSIX programming resources

[J. Seth Henry]

I realize this isn't exactly on topic, but I figure a bunch of you
guys/gals have probably done stuff like this, and might know where to
point me.

I am trying to write an automation program in FreeBSD that listens for
commands on a serial port, and responds by issuing commands in response. I
also need to accept commands and data from local users or shell scripts.

Right now, I poll the serial ports periodically, and this seems to work
OK. I would prefer to put the program to sleep until either a fixed amount of
time has passed ( a timer interrupt ), or data arrives at one of the
serial ports ( a device interrupt ). Unfortunately, I don't know how to do
to this under FreeBSD. (All my C programming so far has been "filters"
and such). Could someone point me to a resource on how to do this?

Also, this program should run as a daemon, but I don't know how to make it
disconnect from the tty (currently, I just run it using &).

How can I call programs, and read their output, from within my program?

How can I read the system clock? A lot of events need to occur based on
real-time (I presently use cron and shell scripts, but I would like to be
able to calculate future times programmatically, and set my own "alarms")

Lastly, how can I get data and commands into and out of my program? I
figure a file interface would be the simplest, and simply check the file
periodically to see if it has changed. Is there an easier way, or is this
an accepted method? I would eventually like to write a web page and use my
existing web server and CGI scripts to control/monitor the daemon - but
I'm not sure I'm ready to write my own web server code into this app.

In summary, can anyone help me write code that:
1) puts my daemon to sleep, awaking only when either a timer has expired,
data has arrived one of the controlled serial ports, or the user has
invoked some interface from a script or command line utility.

2) Daemonizes my program (dissasociating itself from the terminal)

3) Accepts commands and/or data from scripts or command line utilities.

4) Call other programs, and pass them parameters.

5) Read the system clock.

Like I said, presently I have a program which manages to work around the
above issues, but it requires a lot more CPU than I believe is necessary
(and I'd like to learn how to do it). My code so far has been written in
ANSI C. IOW - I know how to program "in general", I'm just a little fuzzy
on how I talk to the operating system beyond stdin and stdout.

If this discussion belongs elsewhere, please, point me in the right
place! I'm also open to books, if anyone has any recommendations. Is
there a "Programming POSIX for dummies" out there?

Many thanks,
Seth Henry


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-questions" in the body of the message

Re: APC UPS

[J. Seth Henry]

Mark,
I have an APC 750XL smart UPS powering my server and home automation
setup. I have taken to using the PowerChute software provided by APC under
linux emulation, which works quite well so long as you modify the shell
scripts for use on a BSD system.

I haven't tried running the apcupsd daemon, though, so YMMV.

Good luck,
Seth Henry


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-questions" in the body of the message

X terminal saga continues

[J. Seth Henry]

Thanks much for the help so far, but this X terminal project is
reminiscent of the dutch boy and dike. Everytime I get one thing working,
something else goes screwy.

I now have X starting automatically by initd, and it connects to an xdm
application server. This works correctly, and I can log in as any user on
the server from the terminal. (Note, the console doesn't have a monitor,
but it should also be displaying an xdm login)

Presently, I have a local .xsession in every user's home directory, which
starts icewm. This is OK, as I can add it to /etc/skel, but it would be
nice if there were an override file, which automatically started the wm.

Also, I've noticed that some applications, such as Mozilla, aren't
recieving keyboard shortcuts anymore. When I log into the terminal
console, manually start X, and connect to the server, Mozilla runs fine -
responds to CTRL+ALT+L, ALT+RIGHT/LEFT etc. When I log in graphically,
Mozilla doesn't "see" any of these commands. I have used xev, running
from the application server, to verify that the X server is sending the
keystrokes. I also checked PINE, and it responds to the keystrokes.

So, it would appear to be a problem with Mozilla, but I can't figure out
why it works when I start the application via an xterm?

Did I misconfigure xdm?

Notes:
I am using Xfree86 4.2.x libraries on the server (the default for FBSD
4.7-REL), the terminals are running Xfree 3.3.6 for memory reasons. The X
server on the terminals were modified slightly to remap "special" keys to
normal keys, but are otherwise unmodified. The server has worked before,
so I don't suspect it is the problem, and xev on either the server or the
client reports that the keystrokes are, indeed, being generated correctly.

All the systems involved are running 4.7-REL with custom kernels.

problem only occurs when the wm is launched via xdm - launching via xterm
after manual login doesn't appear to result in the problem

I am using the Linux Mozilla binary

No errors are being reported in either the terminal or app server's
syslog, or xdm-errors log.

Any help would be greatly appreciated, as ironically, Mozilla was the
primary purpose for these terminals. :)

Thanks,
Seth Henry


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-questions" in the body of the message

Launch X at boot

[J. Seth Henry]

I know this is probably an obvious question, but so far my attempts at
writing a script to do this have failed.

I would like to launch X windows at boot, and have it query an xdm server.
I attempted to put a script with:

#/bin/sh
/usr/X11R6/bin/X -query whitetower

in my /usr/local/etc/rc.d directory. When I boot, though, I get nothing -
not even error messages. I did check that the file permissions were set
(700) - and it works if I run it from the command line (after logging in)

Am I missing something?

Thanks,
Seth Henry


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-questions" in the body of the message

vinum write crashed machine

[J. Seth Henry]

I strongly suspect you have a hardware problem. Either in the controller,
or one of the disks. It is possible that something is crapping out in
vinum, or in the kernel, but I've dumped massive amounts of data to a
vinum raid5 volume before, and it didn't even burp - much less crash. I've
also had bad EIDE disks cause the system to panic, and they weren't even
in a RAID configuration; just normal data drives.

As it is, Greg Lehey is "the man" when it comes to vinum, (something about
writing it or other) so I'll ask the obligatory questions

+What hardware is this (SCSI/EIDE/other?)
+Can you post a copy of any console messages or panic info?

Regards,
Seth Henry



To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-questions" in the body of the message

Building Linux binaries under FreeBSD/Linux layer

[J. Seth Henry]

I know this is probably going to be an odd question, but is there a way to
create true "linux" shell within FreeBSD, capable of running linux gcc and
creating a linux binary?

I want to play with Midori Linux, which involves compiling a lot of Linux
source, for Linux. Dual booting is out of the question (my FreeBSD box
runs the home automation system). I suspect it *could* be done with a
carefully configured shell, and a bunch of Linux RPM's installed to
support gcc and the assorted libraries.

Is this possible, and if so, has pulled a stunt like this?

If not, how well does VMware run under FreeBSD, and can you ssh into the
virtual machine once it's up?

Thanks,
Seth Henry



To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-questions" in the body of the message

ServerWorks environmental monitoring?

[J. Seth Henry]

I recently built a small server with a SuperMicro 370DL3 mainboard, only
do discover that neither healthd nor lmmon support the environmental
monitoring interface on the ServerWorks chipset.

Does anyone know of a tool that will work with this chipset?

Thanks,
Seth Henry


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-questions" in the body of the message

FreeBSD and AMD power management

[J. Seth Henry]

I have noticed that my Compaq IA-1's (AMD K6-2/266 & VIA chipset) run
substantially hotter under FreeBSD than under Linux. I didn't realize just
how much until the machines began spontaneously rebooting under load.

Right now, I have a minimal 4.7R install (with X) running from a
microdrive - but I don't have problems until I start running X for long
periods of time. I am migrating from Midori linux with kernel rev 2.4.18,
and it can go for weeks (even months) running xmms locally. Just
windowing xmms from another machine will cause spontanous reboots under
FreeBSD.

It doesn't appear to be a kernel panic - this machine has a thermal
protection circuit which will hold the system in reset if it gets too
warm, and so far, nothing has shown up in the logs (beyond the usual
startup message regarding / being unmounted improperly). This leads me to
believe that FreeBSD isn't issuing halts when it is idle, or the CPU is
simply "idle" less. I have noticed that FreeBSD accesses the microdrive a
*lot* (though Linux may be as well, but I can't hear it because it's
running from flash)

Is this a "normal" limitation in FreeBSD, or did I miss something in the
kernel config?

Thanks,
Seth Henry
jshamletcomcast(dot)net


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-questions" in the body of the message

Re: questions-digest V5 #1820

[J. Seth Henry]

I have a command line utility that handles the lights for now, but I'm
still working on shoehorning the business end into the blanksaver. I
didn't have a development system over the holidays, but I plan to make
another go of it this weekend. I can email you the C source for the
current program, though - it's not terribly complicated.

Right now, I have scripts that turn the green (power) light on during the
boot sequence, and I *almost* have an X server that handles the
extra keyboard/LED's. It translates the "function" buttons as F1-F10, F13
- remaps the volume/mute buttons as 147,148,149. The arrow keys are
simply mapped as, well arrow keys. I thought about having them produce
"ALT+RIGHT/LEFT", but I find I use them on the command line as well.
Lastly, the "PRINTER" button is now an "ESCAPE" key. I really wish I could
get xmodmap to recognize higher scancodes... Lastly, the power button
currently calls an empty function that will toggle the screen backlight on
and off. I'm still working out how this should work with the blanker, but
I get the feeling it won't be a big deal.

I hard-coded most of this in a modified Xfree86 3.3.6 SVGA server. 3.3.6
uses *FAR* less RAM than 4.x does, but it doesn't natively handle
keycodes above 150. I have tried mucking with the 3.x version of xmodmap,
but I can't make it see scancodes over 150 - even when the X server
clearly generates them (I can see them using xev). Otherwise, I would
simply have the server generate high value scancodes, and use Xmodmap to
remap. Can't have it all, I suppose. I find I have ~4Mb of free RAM after
everything is up on this testbed system. (I was swapping heavily with
4.1.2)

BTW - I have a good XF86Config for 3.3.6. 800x600@16bit color. It's
trimmed down to just the basics, but it works quite well.

If I could just get xdm to work! ARGHH - no one on the list seems to know
how to set up xdm at all, much less for remote logins. At least xfs is
working, so I still get pretty fonts in applications. Once I get xdm
licked, I'll be a long ways towards my dedicated x terminals.

Anyway, once I get all the code finished, I'll be more than happy to
share. The entire OS fits on a 340MB microdrive with nearly 50Mb to
spare.

Seth Henry

>>>
Date: Fri, 3 Jan 2003 12:53:45 -0500
From: "Joshua Coombs" <[EMAIL PROTECTED]>
Subject: Re: 5.0RC2 on an iPaq IA1

Mine's a white unit, no onboard ethernet.  The only bus powered device I'm
running right now is the aue ethernet, which I can easily dump for
testing.
The HD is self powered.  I'd love a microdrive, but figured I had this
60GB
IDE drive floating loose, and the enclosure/adapter was only $35... might
as
well try right? : )  Previously I've been netbooting but getting ticked
with
random locks under load, under both Net and FreeBSD.  No warning, no
errors
just stops dead in it's tracks.  Figured getting 'local' storage might
stabilize things.

Have you gotten the backlight control code ported over to FreeBSD for
these
rigs?  I'd love to have a screensaver module that just shut the LCD down.

Joshua Coombs

- - Original Message -
From: "J. Seth Henry" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Cc: <[EMAIL PROTECTED]>
Sent: Friday, January 03, 2003 10:25 AM
Subject: RE: 5.0RC2 on an iPaq IA1


> Don't rule out hardware problems. I have been working with 4.7R on an
> IA-1. The power supplies in there aren't the greatest, and I've had
> problems with wireless keyboards loading the units down to where they
had
> problems booting.
>
> I would suggest you get a self-powered USB hub, and make all your
> connections through it (or try one of those keychain NAND drives). I
> managed to get everything, including the wireless keyboard transciever,
to
> work just fine that way.
>
> That said, I've had the most success with booting my IA-1 from a
> microdrive. I did have to boost the CF Vcc to 5V by lifting and
jumpering
> the middle two pins to an unused serial connector (CN10), but that done,
> the system is remarkably stable.
>
> BTW - is your IA-1 a white or blue unit? I'm still trying to figure out
> how to get FBSD to recognize the external MII PHY on the clipper
ethernet
> port.
>
> Good luck,
> Seth Henry
>
> >>>
> iPaq# usbdevs -v
> Controller /dev/usb0:
> addr 1: full speed, self powered, config 1, UHCI root hub(0x),
> VIA(0x), rev 1.00
>  port 1 powered
>  port 2 addr 2: full speed, self powered, config 2, USB 2.0 Storage
> Adaptor(0xb001), DMI(0x0c0b), rev 11.10
> Controller /dev/usb1:
> addr 1: full speed, self powered, config 1, UHCI root hub(0x),
> VIA(0x), rev 1.00
>  port 1 powered
>  port 2 addr 2: full speed, power 156 mA, config 1, LINKSYS USB
&g

RE: 5.0RC2 on an iPaq IA1

[J. Seth Henry]

Don't rule out hardware problems. I have been working with 4.7R on an
IA-1. The power supplies in there aren't the greatest, and I've had
problems with wireless keyboards loading the units down to where they had
problems booting.

I would suggest you get a self-powered USB hub, and make all your
connections through it (or try one of those keychain NAND drives). I
managed to get everything, including the wireless keyboard transciever, to
work just fine that way.

That said, I've had the most success with booting my IA-1 from a
microdrive. I did have to boost the CF Vcc to 5V by lifting and jumpering
the middle two pins to an unused serial connector (CN10), but that done,
the system is remarkably stable.

BTW - is your IA-1 a white or blue unit? I'm still trying to figure out
how to get FBSD to recognize the external MII PHY on the clipper ethernet
port.

Good luck,
Seth Henry

>>>
iPaq# usbdevs -v
Controller /dev/usb0:
addr 1: full speed, self powered, config 1, UHCI root hub(0x),
VIA(0x), rev 1.00
 port 1 powered
 port 2 addr 2: full speed, self powered, config 2, USB 2.0 Storage
Adaptor(0xb001), DMI(0x0c0b), rev 11.10
Controller /dev/usb1:
addr 1: full speed, self powered, config 1, UHCI root hub(0x),
VIA(0x), rev 1.00
 port 1 powered
 port 2 addr 2: full speed, power 156 mA, config 1, LINKSYS USB
Adapter(0x400b), LINKSYS Inc.(0x066b), rev 1.01

Suggestions on how to debug or reduce the errors?  The drive has good
media
(hooked direct to IDE it tests clean using Quantum's diag util) and the
system will boot fine with a warm reboot of the comp itself, so I'm
guessing
the problem is driver related and not a fault with the HW.

Joshua Coombs
[EMAIL PROTECTED]



To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-questions" in the body of the message

Problem with AMD AM79C978 (PCNet32/Home - HomeHPNA) and external PHY

[J. Seth Henry]

I have a system with an onboard ethernet controller, the above mentioned
PCNet32/Home device. Instead of using the two onboard PHY's, there is an
external 10/100 PHY. Both are detected by the kernel, but in the wrong
order. As such, the pcn device fails because it can't find any MII PHY's,
and a few devices later, finds ukphy0

Here is the dmesg output:

[EMAIL PROTECTED]:/export3/src/sys/compile/xterminal
Timecounter "i8254"  frequency 1193182 Hz
CPU: AMD-K6(tm) 3D processor (267.28-MHz 586-class CPU)
  Origin = "AuthenticAMD"  Id = 0x58c  Stepping = 12
  Features=0x8021bf
  AMD Features=0x8800
real memory  = 31457280 (30720K bytes)
avail memory = 27189248 (26552K bytes)
Preloaded elf kernel "kernel" at 0xc0383000.
K6-family MTRR support enabled (2 registers)
md0: Malloc disk
Using $PIR table, 7 entries at 0xc00fa040
npx0:  on motherboard
npx0: INT 16 interface
pcib0:  on motherboard
pci0:  on pcib0
pcib1:  at device 1.0 on pci0
pci1:  on pcib1
pci1:  at 0.0 irq 10
pci0:  (vendor=0x11c1, dev=0x0441) at 4.0 irq 7
pcn0:  port 0x1c00-0x1c1f mem
0x4120-0x4120001f irq 9 at device 5.0 on pci0
pcn0: Ethernet address: 00:01:fa:ff:ac:57
pcn0: MII without any PHY!
device_probe_and_attach: pcn0 attach returned 6
isab0:  at device 7.0 on pci0
isa0:  on isab0
atapci0:  port 0x1c60-0x1c6f at device 7.1 on
pci0
ata0: at 0x1f0 irq 14 on atapci0
ata1: at 0x170 irq 15 on atapci0
uhci0:  port 0x1c20-0x1c3f irq 11 at device 7.2
on pci0
usb0:  on uhci0
usb0: USB revision 1.0
uhub0: VIA UHCI root hub, class 9/0, rev 1.00/1.00, addr 1
uhub0: 2 ports with 2 removable, self powered
uhci1:  port 0x1c40-0x1c5f irq 11 at device 7.3
on pci0
usb1:  on uhci1
usb1: USB revision 1.0
uhub1: VIA UHCI root hub, class 9/0, rev 1.00/1.00, addr 1
uhub1: 2 ports with 2 removable, self powered
aue0: LINKSYS Inc. LINKSYS USB Adapter, rev 1.10/1.01, addr 2
aue0: Ethernet address: 00:04:5a:95:47:aa
miibus0:  on aue0
ukphy0:  on miibus0
ukphy0:  10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto
pci0:  (vendor=0x1106, dev=0x3057) at 7.4
pcm0:  port 0x1c7c-0x1c7f,0x1c78-0x1c7b,0x1400-0x14ff irq
10 at device 7.5 on pci0
chip1:  port 0x1800-0x18ff irq 10 at device 7.6 on
pci0
orm0:  at iomem
0xc-0xc,0xe9000-0xebfff,0xec000-0xe on isa0
atkbdc0:  at port 0x60,0x64 on isa0
atkbd0:  flags 0x1 irq 1 on atkbdc0
kbd0 at atkbd0
psm0:  irq 12 on atkbdc0
psm0: model Generic PS/2 mouse, device ID 0
vga0:  at port 0x3c0-0x3df iomem 0xa-0xb on isa0
sc0:  at flags 0x100 on isa0
sc0: VGA <16 virtual consoles, flags=0x300>
sio0 at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0
sio0: type 16550A
sio1 at port 0x2f8-0x2ff irq 3 on isa0
sio1: type 16550A
ad0: 30MB  [490/4/32] at ata0-master PIO1
ad2: 342MB  [695/16/63] at ata1-master PIO1
Mounting root from ufs:/dev/ad2s1a

And here is my kernel config:

machine i386
cpu I586_CPU
cpu I686_CPU
ident   xterminal
maxusers32
#makeoptionsDEBUG=-g#Build kernel with gdb(1) debug
symbols

options MATH_EMULATE#Support for x87 emulation
options INET#InterNETworking
options FFS #Berkeley Fast Filesystem
options FFS_ROOT#FFS usable as root device [keep
this!]
options SOFTUPDATES #Enable FFS soft updates support
options UFS_DIRHASH #Improve performance on big
directories
options MFS #Memory Filesystem
options MD_ROOT #MD is a potential root device
options NFS #Network Filesystem
options NFS_ROOT#NFS usable as root device, NFS
required
options MSDOSFS #MSDOS Filesystem
options PROCFS  #Process filesystem
options COMPAT_43   #Compatible with BSD 4.3 [KEEP
THIS!]
options SCSI_DELAY=5000 #Delay (in ms) before probing SCSI
options UCONSOLE#Allow users to grab the console
options USERCONFIG  #boot -c editor
options VISUAL_USERCONFIG   #visual boot -c editor
options KTRACE  #ktrace(1) support
options SYSVSHM #SYSV-style shared memory
options SYSVMSG #SYSV-style message queues
options SYSVSEM #SYSV-style semaphores
options P1003_1B#Posix P1003_1B real-time
extensions
options _KPOSIX_PRIORITY_SCHEDULING
options ICMP_BANDLIM#Rate limit bad replies
options KBD_INSTALL_CDEV# install a CDEV entry in /dev

device  isa
#device eisa
device  pci

# Floppy drive
device  fd0

# ATA and ATAPI devices
device  ata0at isa? port IO_WD1 irq 14
device  ata1at isa? port IO_WD2 irq 15
device  ata
device  atadisk # ATA disk drives
#device a

[no subject]

[J. Seth Henry]

I asked almost the exact same question a month ago, and more recently a
few days ago. Apparently no one has been able to get xdm to work across
a network in FreeBSD, or they felt it was some rite of passage and didn't
want to spoil the surprise. Having tried for a month to get it to work
correctly, I suspect the former.

I have a very similar setup, except I plan to use minimalist FreeBSD
systems to connect to the server. The terminals I am attempting to setup
are pure X terminals, and I plan to have them display a logon prompt to
the server directly. My server does have a keyboard and CRT, but they are
stowed away in a wiring closet.

Here is what I do know. You can configure the XDMCP server (xdm) fairly
easily on the server. It involves adding a script to /usr/local/etc/rc.d
or modifying rc.conf to start it. You will need to modify Xaccess in
/usr/X11R6/lib/X11/lib/xdm (I believe), and remove a comment to allow your
X servers to connect.

On the server (or client depending on your POV), you run xdm --broadcast
-and it should pick up the first server it finds.

Unfortunately, I haven't had any luck getting xdm to work either at the
console or from the terminals as yet. I sometimes manage to get a login
prompt, but the login always fails. If you figure out, I'd like to know
how you did it - and I'll likewise remember you if I manage to work it
out.

Good luck,
Seth Henry

Date: Mon, 23 Dec 2002 13:09:26 -0800 (PST)
From: Shvetima Gulati <[EMAIL PROTECTED]>
Subject: simple xdm setup

Hi all,
  I want to set up my X configuration as follows:

1) I want all clients (people) to log in to machine 'Server'using the GUI
login.This brings them to their desktop. Typically these people are on
windows machines running X servers such as eXceed or X-Win32. Some might
be tunneling through ssh (port forwarding)so they would need to connect to
local displays?
2) There is no physical keyboard or mouse attached to 'Server'
3) for administration purposes the command line is adequate, so there is
no need for a GUI console.

Essentially I want the PCs to function like dumb terminals running X
displays. This is a fairly common scenario right ? How do I set up xdm for
this?

I searched the web but clear info was very sparse for FreeBSD (I am on
4.6.2).

All pointers/help appreciated.
Thanks,
Shv.



To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-questions" in the body of the message

blank saver question

[J. Seth Henry]

Hello,
I am working on adapting FreeBSD to a Compaq IA-1. The display on this
system is not DPMS compliant, so shutting off the backlight requires
writing to a PCI register.

I currently have a small C program which I can use to manipulate this
register from the command line, and I would like to either integrate, or
call, this code from the blanksaver module. Unfortunately, I don't know
enough about how it works to change it.

Could someone give me some tips on how to do this? Is it as simple as
simply adding the code to the blank_saver() function, and adding the
appropriate header and include files? I'm a bit nervous mucking in
modules, as I understand they can cause "problems" that are hard to
recover from.

If it is, this would be a good place to initialize all of the front panel
LED's as well :)

Thanks,
Seth Henry


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-questions" in the body of the message

xdm setup for dummies?

[J. Seth Henry]

Hello,
I have been struggling with setting up an X host and X terminals for a few
weeks now. I figure it's time to stop and ask for directions :)

I have a FBSD 4.7R server which I intend to host X sessions from. It has
the libraries for Xfree86 4.2.0 and runs icewm. (X does work, but isn't
normally running given it's headless most of the time) The terminals are
also running 4.7R, but use Xfree86 3.3.6 due to limited RAM. I
have manually started icewm and redirected it to the terminals
successfully - which works great until the terminals are powered down.
Currently, I start xinit at boot, which sorta works but I still have to
ssh into the server and redirect the DISPLAY. It's also kind of ugly :)

I would like to simply boot the X terminals, and have them immediately
start xdm and display a login to the server. I don't want anyone to be
able to log into the terminal locally, and there is only one server - so
I don't need a chooser.

So far, I have modified the Xsessions to exec icewm. I have added all of
the hosts to the Xaccess file (though I understand this shouldn't be
necessary in a XDMCP broadcast environment), and written a startup script
to launch xdm.

Another snag is that the terminals use DHCP. I would almost prefer that
the X terminals "look for" the server, rather than the server broadcast.
The server has a static IP, so I wouldn't mind hard coding this into their
configurations.

Ironically, the xdm broadcast does appear to be working somewhat - I have
a linux system in the Xaccess list which shows a login prompt... On top of
the current WM! (I just minimize it)

Any help would be greatly appreciated,
Seth Henry


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-questions" in the body of the message

RE: compact flash use

[J. Seth Henry]

Randall,
I took a look at the adapter, and it appears to support multiple formats.
This could be the source of your problem. I use a much simpler CF -> IDE
adapter for programming FreeBSD images to CF devices for use in embedded
systems. My adapter has an IDE header, CF slot and LED - that's it. CF
devices can operate in true ATA mode. Perhaps your adapter is operating it
in some other mode?

Anyway, I have a copy of FreeBSD 4.7R booting from a CF card. I even NFS
mounted the kernel source, and installed a new kernel last night. IOW - it
should work. If it doesn't, I would tend to suspect your adapter. Unless
you really need the other formats, I would go for an adapter that operates
the CF device as a true ATA device. I got mine from Mesa.

One thing to note, CF is not terribly fast. On my systems, it shows up as
PIO1. It is also possible that the controller is getting hosed because
your system is sending data too fast.

Good luck,
Seth Henry


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-questions" in the body of the message

Re: Intel EtherExpress Pro 100 w/ WOL

[J. Seth Henry]

The Wake on Lan functionality operates below the operating system level.
It's actually a signal to the mainboard that simulates the power button
(though it can only turn a system "ON" as far as I know). This feature
should work fine for any system whose BIOS supports it, though I can't
imagine turning a *BSD system off? ;)

The onboard management stuff is a mixed bag. Some of that is just renamed
functionality (it has a boot NVRAM that can be programmed through the
card, etc). Other things, like the ProSet software is windows only. Even
so, it's still a good card. The controller chip on that card is widely
used on motherboards that have integrated ethernet, so it enjoys
widespread support by practically every PC operating system.

Regards,
Seth Henry


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-questions" in the body of the message

Re: Interest in diskless booting?

[J. Seth Henry]

I have a working install of FBSD 4.7R running on a 340MB microdrive. It's
not terribly fast, but it seems stable. My only problem is that the
Netgear USB NIC craps out randomly after a few days, and FreeBSD doesn't
really support the Linksys USB100TX, even though it claims to.

I'd be interested to see your configuration, though. Once I find a fully
supported USB NIC, I think I'm going to try and mount /usr and /usr/home
from another system.

Seth Henry
jshamletcomcastnet


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-questions" in the body of the message

APC 350AV

[J. Seth Henry]

Mark,
I saw your post on freebsd-questions, and I should point out that you can
get the RJ45 -> DB9 adapter for free from APC. It took about two months
for some reason, but you might be able to speed that along if you give
them a call. You should have gotten a card with the unit, which entitles
you to a free cable (I did).

Unfortunately, I haven't used the cable yet - so I don't know how it works
with existing software. I went ahead and took the plunge and got a
SmartUPS 750XL, replacing separate UPS' for my server and network gear.
The 350 was moved to support a windows box, which uses USB.

The 350AV isn't a true "dumb" UPS, as it can send status information via
USB (battery capacity) - so it's possible that the serial adapter will
provide something between basic signalling and a true smart interface.
I'll have to check this out sometime - might be interesting.

Good luck,
Seth Henry


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-questions" in the body of the message

AprilAire 8870 and FreeBSD?

[J. Seth Henry]

I am about to install an AprilAire 8870 communicating thermostat to add
HVAC control to my home automation setup. Has anyone written anything for
this thermostat (or the statnet protocol) for FreeBSD?

Alternately, if I indeed have to write my own interface program, where
can I find example code that handles the serial port in C? (I haven't
gotten around to learning C++) I plan to poll the thermostat after
sending commands, so I don't need to worry about interrupts (I don't
think), and I have the full protocol from the manufacturer.

At this point, I would like to roughly duplicate "bottlerocket", and use
Perl scripts to handle the logic.

Any help would be greatly appreciated!

Thanks,
Seth Henry


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-questions" in the body of the message