Re: dhcpd on 4.4 is problematic
I read the upgrade guide, followed it, and have a 4.4-router in front of me.
Alas, it does not at all dish out an IP-address to an OpenSolaris client
(nv98). It used to do so before, without any fail at all, ever.
Immediately after the upgrade to 4.4, it fails 100%.
It does dish out IP-addresses to Knoppix 5.3.1 on the very same
interface of the very same machine when booted to Knoppix.
I have as well restarted the dhcpd with the interface on which I want
the address to be given out ('dhcpd xl0'), to no avail.
'ifconfig nge0 dhcp' on OpenSolaris also times out all the time. I only
need to 'ifonfig nge0 ..' and 'route add ..', on the OpenSolaris,
though, to connect to the router. Therefore it is not a hardware problem.
It looks much more like a compatibility problem between OpenBSD 4.4 and
(Open?)Solaris, which didn't exist before and which must not happen.
Any detail can be furnished on request,
Oh, we are supposed to ask? Please, get real. If you want to give us
all the information you can file a bug report. By now you should know
we won't bend over backwards to ask for information. You want this
fixed as much as we do.
Re: dhcpd on 4.4 is problematic
Theo de Raadt wrote:
Oh, we are supposed to ask? Please, get real. If you want to give us
all the information you can file a bug report. By now you should know
we won't bend over backwards to ask for information. You want this
fixed as much as we do.
Sorry, Theo,
the message to gnats is on the way. I hope it goes through all our
filters ...
Here are some relevant info, in case:
OpenBSD 4.4 (GENERIC) #1021: Tue Aug 12 17:16:55 MDT 2008
[EMAIL PROTECTED]:/usr/src/sys/arch/i386/compile/GENERIC
cpu0: Intel Pentium/MMX (GenuineIntel 586-class) 233 MHz
cpu0: FPU,V86,DE,PSE,TSC,MSR,MCE,CX8,MMX
cpu0: F00F bug workaround installed
real mem = 66678784 (63MB)
avail mem = 55009280 (52MB)
mainbus0 at root
bios0 at mainbus0: AT/286+ BIOS, date 07/07/97, BIOS32 rev. 0 @ 0xfd920
pcibios0 at bios0: rev 2.1 @ 0xf/0x1
pcibios0: PCI BIOS has 6 Interrupt Routing table entries
pcibios0: PCI Interrupt Router at 000:07:0 (Intel 82371SB ISA rev 0x00)
pcibios0: PCI bus #0 is the last bus
bios0: ROM list: 0xc/0x8000 0xea000/0x2000
cpu0 at mainbus0
pci0 at mainbus0 bus 0: configuration mode 1 (bios)
pchb0 at pci0 dev 0 function 0 Intel 82437VX rev 0x02
pcib0 at pci0 dev 7 function 0 Intel 82371SB ISA rev 0x01
pciide0 at pci0 dev 7 function 1 Intel 82371SB IDE rev 0x00: DMA, channel 0
wired to compatibility, channel 1 wired to compatibility
wd0 at pciide0 channel 0 drive 0: WDC AC12500R
wd0: 16-sector PIO, LBA, 2441MB, 4999680 sectors
wd0(pciide0:0:0): using PIO mode 4, DMA mode 2
pciide0: channel 1 ignored (disabled)
vga1 at pci0 dev 8 function 0 S3 Trio32/64 rev 0x54
wsdisplay0 at vga1 mux 1: console (80x25, vt100 emulation)
wsdisplay0: screen 1-5 added (80x25, vt100 emulation)
drm at vga1 unsupported
rl0 at pci0 dev 17 function 0 Realtek 8139 rev 0x10: irq 9, address
00:40:95:00:21:a8
rlphy0 at rl0 phy 0: RTL internal PHY
xl0 at pci0 dev 19 function 0 3Com 3c905 100Base-TX rev 0x00: irq 9, address
00:60:97:73:55:1a
nsphy0 at xl0 phy 24: DP83840 10/100 PHY, rev. 1
isa0 at pcib0
isadma0 at isa0
com0 at isa0 port 0x3f8/8 irq 4: ns16550a, 16 byte fifo
com1 at isa0 port 0x2f8/8 irq 3: ns16550a, 16 byte fifo
pckbc0 at isa0 port 0x60/5
pckbd0 at pckbc0 (kbd slot)
pckbc0: using irq 1 for kbd slot
wskbd0 at pckbd0: console keyboard, using wsdisplay0
ne1 at isa0 port 0x300/32 irq 10, NE2000, address 00:50:ba:c0:41:17
pcppi0 at isa0 port 0x61
midi0 at pcppi0: PC speaker
spkr0 at pcppi0
lpt0 at isa0 port 0x378/4 irq 7
npx0 at isa0 port 0xf0/16: reported by CPUID; using exception 16
fdc0 at isa0 port 0x3f0/6 irq 6 drq 2
fd0 at fdc0 drive 0: 1.44MB 80 cyl, 2 head, 18 sec
biomask f965 netmask ff65 ttymask
softraid0 at root
root on wd0a swap on wd0b dump on wd0b
/etc/dhcpd.conf:
shared-network LOCAL-NET {
option domain-name my.domain.com;
option domain-name-servers 192.168.116.200;
option netbios-name-servers 172.16.3.247;
subnet 192.168.116.0 netmask 255.255.255.0 {
range 192.168.116.101 192.168.116.199;
default-lease-time 86400;
max-lease-time 259200;
option broadcast-address 192.168.116.255;
option routers 192.168.116.200;
}
}
ps aux | grep dhcp:
_dhcp 2000 0.0 1.5 452 972 ?? Is 3:13PM0:00.05 dhcpd xl0
ifconfig:
lo0: flags=8049UP,LOOPBACK,RUNNING,MULTICAST mtu 33204
groups: lo
inet 127.0.0.1 netmask 0xff00
inet6 ::1 prefixlen 128
inet6 fe80::1%lo0 prefixlen 64 scopeid 0x5
rl0: flags=8843UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST mtu 1500
lladdr 00:40:95:00:21:a8
groups: egress
media: Ethernet autoselect (100baseTX full-duplex)
status: active
inet 172.20.16.207 netmask 0xff00 broadcast 172.20.16.255
inet6 fe80::240:95ff:fe00:21a8%rl0 prefixlen 64 scopeid 0x1
xl0: flags=8843UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST mtu 1500
lladdr 00:60:97:73:55:1a
media: Ethernet autoselect (100baseTX full-duplex)
status: active
inet 192.168.116.200 netmask 0xff00 broadcast 192.168.116.255
inet6 fe80::260:97ff:fe73:551a%xl0 prefixlen 64 scopeid 0x2
ne1: flags=8822BROADCAST,NOTRAILERS,SIMPLEX,MULTICAST mtu 1500
lladdr 00:50:ba:c0:41:17
media: Ethernet manual
enc0: flags=0 mtu 1536
pflog0: flags=141UP,RUNNING,PROMISC mtu 33204
groups: pflog
Uwe
Re: how to install the xfce4 desktop ?
http://www.openbsd.org/cgi-bin/cvsweb/ports/x11/xfce4/xfce4-session/files/README.OpenBSD?rev=1.2 It says how to install all xfce4 things. ++ It's exactly the file I've used to install XFCE. Good info. -- Thanks, Jordi Espasa Clofent
Re: dhcpd on 4.4 is problematic
On Tue, Nov 04, 2008 at 04:55:23PM +0800, Uwe Dippel wrote: Theo de Raadt wrote: Oh, we are supposed to ask? Please, get real. If you want to give us all the information you can file a bug report. By now you should know we won't bend over backwards to ask for information. You want this fixed as much as we do. Sorry, Theo, the message to gnats is on the way. I hope it goes through all our filters ... Here are some relevant info, in case: Missing info would be output from dhcpd in the /var/log/daemon. Please grep there on dhcpd and send this. Also add the mac address of the failing machine. This will give us atleast info about the request and offers to this box. regards Robert snip -- Microsoft: Where do you want to go today? Linux: Where do you want to go tomorrow? FreeBSD: Are you guys coming or what? OpenBSD: Hey guys you left some holes out there!
Re: dhcpd on 4.4 is problematic
Robert Blacquiere wrote: Missing info would be output from dhcpd in the /var/log/daemon. Please grep there on dhcpd and send this. Also add the mac address of the failing machine. This will give us atleast info about the request and offers to this box. Sure. It is a tad long, but maybe, maybe, it adds information. In between you can see the successful transaction with the Knoppix 5.3.1 to which I booted the machine for debugging purposes, to exclude hardware. I remember I saw the 167 in the Knoppix terminal. Nov 4 14:00:23 firewall dhcpd[28296]: DHCPDISCOVER from 00:20:ed:ee:ed:14 via xl0 Nov 4 14:00:23 firewall dhcpd[28296]: DHCPOFFER on 192.168.116.162 to 00:20:ed:ee:ed:14 via xl0 Nov 4 14:01:28 firewall dhcpd[28296]: DHCPDISCOVER from 00:20:ed:ee:ed:14 via xl0 Nov 4 14:01:28 firewall dhcpd[28296]: DHCPOFFER on 192.168.116.162 to 00:20:ed:ee:ed:14 via xl0 Nov 4 14:02:33 firewall dhcpd[28296]: DHCPDISCOVER from 00:20:ed:ee:ed:14 via xl0 Nov 4 14:02:33 firewall dhcpd[28296]: DHCPOFFER on 192.168.116.162 to 00:20:ed:ee:ed:14 via xl0 Nov 4 14:03:36 firewall dhcpd[28296]: DHCPDISCOVER from 00:20:ed:ee:ed:14 via xl0 Nov 4 14:03:36 firewall dhcpd[28296]: DHCPOFFER on 192.168.116.162 to 00:20:ed:ee:ed:14 via xl0 Nov 4 14:04:41 firewall dhcpd[28296]: DHCPDISCOVER from 00:20:ed:ee:ed:14 via xl0 Nov 4 14:04:41 firewall dhcpd[28296]: DHCPOFFER on 192.168.116.162 to 00:20:ed:ee:ed:14 via xl0 Nov 4 14:05:45 firewall dhcpd[28296]: DHCPDISCOVER from 00:20:ed:ee:ed:14 via xl0 Nov 4 14:05:45 firewall dhcpd[28296]: DHCPOFFER on 192.168.116.162 to 00:20:ed:ee:ed:14 via xl0 Nov 4 14:06:50 firewall dhcpd[28296]: DHCPDISCOVER from 00:20:ed:ee:ed:14 via xl0 Nov 4 14:06:50 firewall dhcpd[28296]: DHCPOFFER on 192.168.116.162 to 00:20:ed:ee:ed:14 via xl0 Nov 4 14:07:53 firewall dhcpd[28296]: DHCPDISCOVER from 00:20:ed:ee:ed:14 via xl0 Nov 4 14:07:53 firewall dhcpd[28296]: DHCPOFFER on 192.168.116.162 to 00:20:ed:ee:ed:14 via xl0 Nov 4 14:08:57 firewall dhcpd[28296]: DHCPDISCOVER from 00:20:ed:ee:ed:14 via xl0 Nov 4 14:08:57 firewall dhcpd[28296]: DHCPOFFER on 192.168.116.162 to 00:20:ed:ee:ed:14 via xl0 Nov 4 14:10:00 firewall dhcpd[28296]: DHCPDISCOVER from 00:20:ed:ee:ed:14 via xl0 Nov 4 14:10:00 firewall dhcpd[28296]: DHCPOFFER on 192.168.116.162 to 00:20:ed:ee:ed:14 via xl0 Nov 4 14:11:05 firewall dhcpd[28296]: DHCPDISCOVER from 00:20:ed:ee:ed:14 via xl0 Nov 4 14:11:05 firewall dhcpd[28296]: DHCPOFFER on 192.168.116.162 to 00:20:ed:ee:ed:14 via xl0 Nov 4 14:12:09 firewall dhcpd[28296]: DHCPDISCOVER from 00:20:ed:ee:ed:14 via xl0 Nov 4 14:12:09 firewall dhcpd[28296]: DHCPOFFER on 192.168.116.162 to 00:20:ed:ee:ed:14 via xl0 Nov 4 14:13:13 firewall dhcpd[28296]: DHCPDISCOVER from 00:20:ed:ee:ed:14 via xl0 Nov 4 14:13:13 firewall dhcpd[28296]: DHCPOFFER on 192.168.116.162 to 00:20:ed:ee:ed:14 via xl0 Nov 4 14:14:17 firewall dhcpd[28296]: DHCPDISCOVER from 00:20:ed:ee:ed:14 via xl0 Nov 4 14:14:17 firewall dhcpd[28296]: DHCPOFFER on 192.168.116.162 to 00:20:ed:ee:ed:14 via xl0 Nov 4 14:15:21 firewall dhcpd[28296]: DHCPDISCOVER from 00:20:ed:ee:ed:14 via xl0 Nov 4 14:15:21 firewall dhcpd[28296]: DHCPOFFER on 192.168.116.162 to 00:20:ed:ee:ed:14 via xl0 Nov 4 14:16:25 firewall dhcpd[28296]: DHCPDISCOVER from 00:20:ed:ee:ed:14 via xl0 Nov 4 14:16:25 firewall dhcpd[28296]: DHCPOFFER on 192.168.116.162 to 00:20:ed:ee:ed:14 via xl0 Nov 4 14:17:30 firewall dhcpd[28296]: DHCPDISCOVER from 00:20:ed:ee:ed:14 via xl0 Nov 4 14:17:30 firewall dhcpd[28296]: DHCPOFFER on 192.168.116.162 to 00:20:ed:ee:ed:14 via xl0 Nov 4 14:18:34 firewall dhcpd[28296]: DHCPDISCOVER from 00:20:ed:ee:ed:14 via xl0 Nov 4 14:18:34 firewall dhcpd[28296]: DHCPOFFER on 192.168.116.162 to 00:20:ed:ee:ed:14 via xl0 Nov 4 14:19:38 firewall dhcpd[28296]: DHCPDISCOVER from 00:20:ed:ee:ed:14 via xl0 Nov 4 14:19:38 firewall dhcpd[28296]: DHCPOFFER on 192.168.116.162 to 00:20:ed:ee:ed:14 via xl0 Nov 4 14:20:41 firewall dhcpd[28296]: DHCPDISCOVER from 00:20:ed:ee:ed:14 via xl0 Nov 4 14:20:41 firewall dhcpd[28296]: DHCPOFFER on 192.168.116.162 to 00:20:ed:ee:ed:14 via xl0 Nov 4 14:21:46 firewall dhcpd[28296]: DHCPDISCOVER from 00:20:ed:ee:ed:14 via xl0 Nov 4 14:21:46 firewall dhcpd[28296]: DHCPOFFER on 192.168.116.162 to 00:20:ed:ee:ed:14 via xl0 Nov 4 14:22:49 firewall dhcpd[28296]: DHCPDISCOVER from 00:20:ed:ee:ed:14 via xl0 Nov 4 14:22:49 firewall dhcpd[28296]: DHCPOFFER on 192.168.116.162 to 00:20:ed:ee:ed:14 via xl0 Nov 4 14:23:52 firewall dhcpd[28296]: DHCPDISCOVER from 00:20:ed:ee:ed:14 via xl0 Nov 4 14:23:52 firewall dhcpd[28296]: DHCPOFFER on 192.168.116.162 to 00:20:ed:ee:ed:14 via xl0 Nov 4 14:24:56 firewall dhcpd[28296]: DHCPDISCOVER from 00:20:ed:ee:ed:14 via xl0 Nov 4 14:24:56 firewall dhcpd[28296]: DHCPOFFER on 192.168.116.162 to 00:20:ed:ee:ed:14 via xl0 Nov 4 14:25:59 firewall dhcpd[28296]: DHCPDISCOVER from 00:20:ed:ee:ed:14 via xl0 Nov 4 14:25:59 firewall
Re: dhcpd on 4.4 is problematic
On 2008-11-04, Uwe Dippel [EMAIL PROTECTED] wrote: Robert Blacquiere wrote: Missing info would be output from dhcpd in the /var/log/daemon. Please grep there on dhcpd and send this. Also add the mac address of the failing machine. This will give us atleast info about the request and offers to this box. Sure. It is a tad long, but maybe, maybe, it adds information. In between you can see the successful transaction with the Knoppix 5.3.1 to which I booted the machine for debugging purposes, to exclude hardware. I remember I saw the 167 in the Knoppix terminal. please include tcpdump -eniinterface -Xvvs port 67 or port 68 from an opensolaris attempt.
trunk(4), VLANs and MTU problems
Hi list
I've just deployed two redundant OpenBSD 4.4's as main gateways for a
network, and all in all its working great, as expected with OpenBSD :)
Each box (HP DL320) have one Intel Quad GigE adapter each (82571EB),
connected to a HP 2810-48 GigE switch.
em0 and em1 are trunk0, and running the external link on top (Thus
normal 1500 MTU)
em2 and em3 are trunk1, and here I run a couple of VLAN's, and thus
the MTU is 1496.
The problems I'm having is this:
When some mailservers (out of my control) tries to send email to our
server (located on one of the VLANs), they connect all fine and
performs SMTP handshake etc, but then when the get around to sending
DATA followed by the actual mail, they start to using 1500b frames
with the DF bit set.
All fine in a normal env.. But for me, this of course fails, since my
net can only handle 1496 bytes. As expected my box sends ICMP
unreachable - need to frag (mtu 1496) to the remote server.
This works fine and is respected in most cases, the package is
retransmitted in smaller frames, but some sending servers seems to
ignore my ICMP (firewalled away at their end? shouldnt be a problem
here since other servers gets it and retransmits), and just keeps on
sending 1500b packets.. And my box continues to drop em and returning
ICMP unreach..
So, I started looking in to enabling jumbo frames on my local net (or
at least make sure i can transmit 1500b on the VLANs), but it seems
I've hit a stop at trunk, since from what I can tell I cannot get
1500b MTU there:
if_trunk.c:
...
case SIOCSIFMTU:
if (ifr-ifr_mtu ETHERMTU) {
error = EINVAL;
break;
}
ifp-if_mtu = ifr-ifr_mtu;
break;
ETHERMTU is #defined as 1500
So... Dead end there? Is there any way to get 1500b MTU on a trunk
somehow? Would it be possible to just hack if_trunk.c, and making sure
the underlying interface are running at at least 1502 bytes? That
would be enough for me.. That was what I first tried, changing the MTU
of em2/3 to 1502 in order to allow space for the VLAN tag, hoping that
the trunk interface would see this and change, but no.
I guess someone here probably had this problem sometime, how have you
solved it?
I could of course try to get in touch with the admins of these servers
but that is probably not the easiest task (the list of servers I got
problems with includes big global unnamed companies).
Thanks for any help, and many many thanks for the great OpenBSD 4.4
release! :)
Johan
Source address algorithm
Hi misc, How does the OpenBSD source address selection algorithm works? Is there a way to override the source address? I have two interfaces on my box: tun0 and vr0. tun0 uses A::2/64 as its IPv6 address. vr0 uses B::2/48 as its IPv6 address. The default route ::/0 is on the tun0 interface. Hence, when sending IPv6 packets, the source address is the one from tun0 (A::2/64). Is there a way to override the source address for _all_ traffic (i.e. not having to bind services to an specific IP) to be B::2/48 instead? Thanks! -- http://www.felipe-alfaro.org/blog/disclaimer/
Re: pkg_add error
Gregory Edigarov wrote: What gives? Is this a problem on my side? Try another mirror. ftp.openbsd.org is probably hammered. -- chs
OpenBSD 4.4 - fdisk issue
Hi I just try to install OpenBSD 4.4 on a serveur (HP DL120 G5) to test the functionality of the raid (seens it works again .). I configure the first disk without any issue, and then try following commands: disklabel wd0 disklabel.wd1 fdisk -i wd1 disklabel -R -r wd1 disklabel.wd1 newfs /dev/wd1a Error: newfs: /dev/wd1a: block device Same message when I try a mount. Not a problem I continue and made a new installation on wd1 (with the CD) Then I build my raid0 configuration (by compiling the kernel) and try to create the new disk: fdisk -i raid0 disklabel -E -raid0 newfs /dev/raid0a = same error by newfs and mount What do I wrong ? Regards
Re: OpenBSD 4.4 installation error: write failed; file system full
Ross Cameron wrote: On Tue, Nov 4, 2008 at 12:32 PM, Chris [EMAIL PROTECTED] wrote: I've download and burned the 4.4 ISO from a local mirror and trying to upgrade from 4.3 to 4.4 on i386. After the installer does the fsck -fp, I get the following error: uid 0 on /: file system full /: write failed; file system full cp: /tmp/hosts: No space left on device I've also tried the 4.3 base CD and I get the same error. This has never happened before. Is there something I'm doing wrong? Yes! Here's my df -h output: /dev/rd0a 1.7M 1.7M 38.5k 98% / Here's you're problem,... you're trying to install a whole OS onto a 1,7MB partition. I doubt he's trying to install stuff to the ramdisk...
newbie network segment routing query
Hello misc@, I don't know if this is really a packet filtering, or DMZ kind of query. What I've looked at so far (eg: http://www.openbsd.org/faq/pf/queueing.html) doesn't really describe what I'm trying to do. I hope someone can help. I have a range (a /28) of real IP addresses. The openbsd box (4.0, soon to be upgraded to 4.4) functions as a firewall/router. It forwards packets to the speedtouch router that manages the connection. All the speedtouch router does is to accept traffic for this range, it does not do NAT. presently the openbsd box nats everything. The openbsd box sits behind the router. It has 4 NICs in it: fxp0 to the speedtouch fxp1 for a network that I want to be unfiltered, in other words, real IPs (wired) fxp2 the top usable real IP - this I want to nat behind, it is for wireless fxp3 is unused. Is this a DMZ for fxp1? I don't need this traffic to be processed by the openbsd box, I just want it to go down the right interface. From what I've read, a DMZ involves some queuing/processing. Not sure if my nomenclature is right for what I'm describing. Is there a howto for what I'm trying to do? Do I have to split the /28? many thanks -- John
Re: OpenBSD 4.4 - fdisk issue
On Tue, Nov 04, 2008 at 04:31:57PM +0100, [EMAIL PROTECTED] wrote: I just try to install OpenBSD 4.4 on a serveur (HP DL120 G5) to test the functionality of the raid (seens it works again .). I configure the first disk without any issue, and then try following commands: disklabel wd0 disklabel.wd1 fdisk -i wd1 disklabel -R -r wd1 disklabel.wd1 newfs /dev/wd1a Error: newfs: /dev/wd1a: block device Second section of the newfs(8) manpage. -- Olivier Cherrier mailto:[EMAIL PROTECTED]
Re: OpenBSD 4.4 - fdisk issue
On Tue, Nov 04, 2008 at 04:31:57PM +0100, [EMAIL PROTECTED] wrote: I just try to install OpenBSD 4.4 on a serveur (HP DL120 G5) to test the functionality of the raid (seens it works again .). I configure the first disk without any issue, and then try following commands: disklabel wd0 disklabel.wd1 fdisk -i wd1 disklabel -R -r wd1 disklabel.wd1 newfs /dev/wd1a Error: newfs: /dev/wd1a: block device Second section of the newfs(8) manpage. Great ... This worked in 4.3 without any thing else; I didn't find anything in this section. http://www.openbsd.org/cgi-bin/man.cgi?query=newfsapropos=0sektion=0manpa th=OpenBSD+4.4arch=i386format=html What should I search for ?
Re: dhcpd on 4.4 is problematic
Robert Blacquiere wrote: Missing info would be output from dhcpd in the /var/log/daemon. Please grep there on dhcpd and send this. Also add the mac address of the failing machine. This will give us atleast info about the request and offers to this box. Sure. It is a tad long, but maybe, maybe, it adds information. In between you can see the successful transaction with the Knoppix 5.3.1 to which I booted the machine for debugging purposes, to exclude hardware. I remember I saw the 167 in the Knoppix terminal. Nov 4 14:00:23 firewall dhcpd[28296]: DHCPDISCOVER from 00:20:ed:ee:ed:14 via xl0 Nov 4 14:00:23 firewall dhcpd[28296]: DHCPOFFER on 192.168.116.162 to 00:20:ed:ee:ed:14 via xl0 Nov 4 14:01:28 firewall dhcpd[28296]: DHCPDISCOVER from 00:20:ed:ee:ed:14 via xl0 Nov 4 14:01:28 firewall dhcpd[28296]: DHCPOFFER on 192.168.116.162 to 00:20:ed:ee:ed:14 via xl0 Nov 4 14:02:33 firewall dhcpd[28296]: DHCPDISCOVER from 00:20:ed:ee:ed:14 via xl0 Nov 4 14:02:33 firewall dhcpd[28296]: DHCPOFFER on 192.168.116.162 to 00:20:ed:ee:ed:14 via xl0 Nov 4 14:03:36 firewall dhcpd[28296]: DHCPDISCOVER from 00:20:ed:ee:ed:14 via xl0 Nov 4 14:03:36 firewall dhcpd[28296]: DHCPOFFER on 192.168.116.162 to 00:20:ed:ee:ed:14 via xl0 Nov 4 14:04:41 firewall dhcpd[28296]: DHCPDISCOVER from 00:20:ed:ee:ed:14 via xl0 Nov 4 14:04:41 firewall dhcpd[28296]: DHCPOFFER on 192.168.116.162 to 00:20:ed:ee:ed:14 via xl0 Nov 4 14:05:45 firewall dhcpd[28296]: DHCPDISCOVER from 00:20:ed:ee:ed:14 via xl0 Nov 4 14:05:45 firewall dhcpd[28296]: DHCPOFFER on 192.168.116.162 to 00:20:ed:ee:ed:14 via xl0 Nov 4 14:06:50 firewall dhcpd[28296]: DHCPDISCOVER from 00:20:ed:ee:ed:14 via xl0 Nov 4 14:06:50 firewall dhcpd[28296]: DHCPOFFER on 192.168.116.162 to 00:20:ed:ee:ed:14 via xl0 Nov 4 14:07:53 firewall dhcpd[28296]: DHCPDISCOVER from 00:20:ed:ee:ed:14 via xl0 Nov 4 14:07:53 firewall dhcpd[28296]: DHCPOFFER on 192.168.116.162 to 00:20:ed:ee:ed:14 via xl0 Nov 4 14:08:57 firewall dhcpd[28296]: DHCPDISCOVER from 00:20:ed:ee:ed:14 via xl0 Nov 4 14:08:57 firewall dhcpd[28296]: DHCPOFFER on 192.168.116.162 to 00:20:ed:ee:ed:14 via xl0 Nov 4 14:10:00 firewall dhcpd[28296]: DHCPDISCOVER from 00:20:ed:ee:ed:14 via xl0 Nov 4 14:10:00 firewall dhcpd[28296]: DHCPOFFER on 192.168.116.162 to 00:20:ed:ee:ed:14 via xl0 Nov 4 14:11:05 firewall dhcpd[28296]: DHCPDISCOVER from 00:20:ed:ee:ed:14 via xl0 Nov 4 14:11:05 firewall dhcpd[28296]: DHCPOFFER on 192.168.116.162 to 00:20:ed:ee:ed:14 via xl0 Nov 4 14:12:09 firewall dhcpd[28296]: DHCPDISCOVER from 00:20:ed:ee:ed:14 via xl0 Nov 4 14:12:09 firewall dhcpd[28296]: DHCPOFFER on 192.168.116.162 to 00:20:ed:ee:ed:14 via xl0 Nov 4 14:13:13 firewall dhcpd[28296]: DHCPDISCOVER from 00:20:ed:ee:ed:14 via xl0 Nov 4 14:13:13 firewall dhcpd[28296]: DHCPOFFER on 192.168.116.162 to 00:20:ed:ee:ed:14 via xl0 Nov 4 14:14:17 firewall dhcpd[28296]: DHCPDISCOVER from 00:20:ed:ee:ed:14 via xl0 Nov 4 14:14:17 firewall dhcpd[28296]: DHCPOFFER on 192.168.116.162 to 00:20:ed:ee:ed:14 via xl0 Nov 4 14:15:21 firewall dhcpd[28296]: DHCPDISCOVER from 00:20:ed:ee:ed:14 via xl0 Nov 4 14:15:21 firewall dhcpd[28296]: DHCPOFFER on 192.168.116.162 to 00:20:ed:ee:ed:14 via xl0 Nov 4 14:16:25 firewall dhcpd[28296]: DHCPDISCOVER from 00:20:ed:ee:ed:14 via xl0 Nov 4 14:16:25 firewall dhcpd[28296]: DHCPOFFER on 192.168.116.162 to 00:20:ed:ee:ed:14 via xl0 Nov 4 14:17:30 firewall dhcpd[28296]: DHCPDISCOVER from 00:20:ed:ee:ed:14 via xl0 Nov 4 14:17:30 firewall dhcpd[28296]: DHCPOFFER on 192.168.116.162 to 00:20:ed:ee:ed:14 via xl0 Nov 4 14:18:34 firewall dhcpd[28296]: DHCPDISCOVER from 00:20:ed:ee:ed:14 via xl0 Nov 4 14:18:34 firewall dhcpd[28296]: DHCPOFFER on 192.168.116.162 to 00:20:ed:ee:ed:14 via xl0 Nov 4 14:19:38 firewall dhcpd[28296]: DHCPDISCOVER from 00:20:ed:ee:ed:14 via xl0 Nov 4 14:19:38 firewall dhcpd[28296]: DHCPOFFER on 192.168.116.162 to 00:20:ed:ee:ed:14 via xl0 Nov 4 14:20:41 firewall dhcpd[28296]: DHCPDISCOVER from 00:20:ed:ee:ed:14 via xl0 Nov 4 14:20:41 firewall dhcpd[28296]: DHCPOFFER on 192.168.116.162 to 00:20:ed:ee:ed:14 via xl0 Nov 4 14:21:46 firewall dhcpd[28296]: DHCPDISCOVER from 00:20:ed:ee:ed:14 via xl0 Nov 4 14:21:46 firewall dhcpd[28296]: DHCPOFFER on 192.168.116.162 to 00:20:ed:ee:ed:14 via xl0 Nov 4 14:22:49 firewall dhcpd[28296]: DHCPDISCOVER from 00:20:ed:ee:ed:14 via xl0 Nov 4 14:22:49 firewall dhcpd[28296]: DHCPOFFER on 192.168.116.162 to 00:20:ed:ee:ed:14 via xl0 Nov 4 14:23:52 firewall dhcpd[28296]: DHCPDISCOVER from 00:20:ed:ee:ed:14 via xl0 Nov 4 14:23:52 firewall dhcpd[28296]: DHCPOFFER on 192.168.116.162 to 00:20:ed:ee:ed:14 via xl0 Nov 4 14:24:56 firewall dhcpd[28296]: DHCPDISCOVER from 00:20:ed:ee:ed:14 via xl0 Nov 4 14:24:56 firewall dhcpd[28296]: DHCPOFFER on 192.168.116.162 to 00:20:ed:ee:ed:14 via xl0 Nov 4 14:25:59 firewall dhcpd[28296]: DHCPDISCOVER from 00:20:ed:ee:ed:14 via xl0 Nov 4 14:25:59
Re: USB CD-ROM support
Tom-100 wrote: When (if ever) will support for installing OpenBSD with a USB CD-ROM be added? I use it all the time. Have for quite some time. In fact, I just installed 4.4 using a very old Iomega 2x USB cd writer. No problems at all... just slow b/c of the age of the drive. -- View this message in context: http://www.nabble.com/USB-CD-ROM-support-tp20302017p20326370.html Sent from the openbsd user - misc mailing list archive at Nabble.com.
in 4.4 kernel - in6.c defines same function twice ()
Anybody seen this before ? I just got my src via cvsup and recompiled my kernel. /usr/src/sys/netinet6/in6.c:1977: error: redefinition of `in6ifa_ifplocaladdr' /usr/src/sys/netinet6/in6.c:1952: error: `in6ifa_ifplocaladdr' previously defined here *** Error code 1
redhat_base not found in packages
Hello list, I can't find redhat_base in the 4.4 packages . Has it been discontinued? Regards, Marcos Laufer
Herhaling: Amsterdam OpenBSD 4.4 release party op donderdag 6 november
Donderdag 6 november Cafe de Deugniet Oude Brugsteeg 12, 1012 JP Amsterdam http://maps.google.nl/maps?f=qhl=enq=Oudebrugsteeg+12,+Amsterdam+1012+Amsterdam,+North+Holland,+The+Netherlandssll=52.469397,5.509644sspn=3.741684,6.097412ie=UTF8cd=1geocode=0,52.375293,4.897561t=hz=17iwloc=addr 18:00 verzamelen voor De Deugniet voor eten in de buurt, vanaf 20:00 in De Deugniet, in de hoek linksachter. +++chefren p.s. The above language is called Dutch, doesn't matter if you don't fully understand, if you like OpenBSD a little or a lot: you are invited too!
Re: OpenBSD 4.4 - fdisk issue
On Tue, Nov 04, 2008 at 05:39:46PM +0100, Christophe Rioux wrote: On Tue, Nov 04, 2008 at 04:31:57PM +0100, [EMAIL PROTECTED] wrote: I just try to install OpenBSD 4.4 on a serveur (HP DL120 G5) to test the functionality of the raid (seens it works again .). I configure the first disk without any issue, and then try following commands: disklabel wd0 disklabel.wd1 fdisk -i wd1 disklabel -R -r wd1 disklabel.wd1 newfs /dev/wd1a Error: newfs: /dev/wd1a: block device Second section of the newfs(8) manpage. Great ... This worked in 4.3 without any thing else; Likely not just as typed above. What should I search for ? The second paragraph under DESCRIPTION in http://www.openbsd.org/cgi-bin/man.cgi?query=newfs seems pretty clear, and pretty clearly relevant. cheers, -wb
Re: OpenBSD 4.4 - fdisk issue
On Tue, Nov 04, 2008 at 12:59:29PM -0500, William Boshuck wrote: On Tue, Nov 04, 2008 at 05:39:46PM +0100, Christophe Rioux wrote: On Tue, Nov 04, 2008 at 04:31:57PM +0100, [EMAIL PROTECTED] wrote: I just try to install OpenBSD 4.4 on a serveur (HP DL120 G5) to test the functionality of the raid (seens it works again .). I configure the first disk without any issue, and then try following commands: disklabel wd0 disklabel.wd1 fdisk -i wd1 disklabel -R -r wd1 disklabel.wd1 newfs /dev/wd1a Error: newfs: /dev/wd1a: block device Second section of the newfs(8) manpage. Great ... This worked in 4.3 without any thing else; Likely not just as typed above. Sorry, this does seem ok in 4.3. (An example in the FAQ uses a relative path, and that's what I've always done.) cheers, -wb
Re: redhat_base not found in packages
Marcos Laufer escreveu: Hello list, I can't find redhat_base in the 4.4 packages . Has it been discontinued? Regards, Marcos Laufer It was replaced with the fedora_base package, with updated libs and other things. This happened on 4.3, AFAICR. This page: http://www.openbsd.org/4.4_packages/ Is the starting point to find packages. I always recall to it when i need to find something. Or, if you have it, you can use the ports and make a search on it. My regards, -- Giancarlo Razzolini http://lock.razzolini.adm.br Linux User 172199 Red Hat Certified Engineer no:804006389722501 Verify:https://www.redhat.com/certification/rhce/current/ Moleque Sem Conteudo Numero #002 OpenBSD Stable Ubuntu 8.04 Hardy Heron 4386 2A6F FFD4 4D5F 5842 6EA0 7ABE BBAB 9C0E 6B85
Re: Duplicate incoming packets to multiple destinations using pf
Hi Giancarlo/misc, Thanks for the answer, I guess dup-to isn4t the right tool then... Has anyone tried to achieve what I am trying to do though? I am obviously open to other ideas. The main objective though, is to preserve the source address, while replacing the destination address to multiple hosts Cheers, Simon. On Nov 4, 2008, at 5:32 PM, Giancarlo Razzolini wrote: Simen Stavdal escreveu: Hello, I have the following scenario. A router (let's call it router A) is sending snmp traps to an nms (Network Monitoring System). Between the router A and the nms (let's call it nms-a) is a Dell PowerEdge 860 running OpenBSD 4.1 i386 (bsd.mp) and pf. On the same segment as nms-a, is nms-b, nms-c etc. I am trying to make pf copy the incoming trap, while keeping the source ip address (of router A), and changing the destination ip for nms- a,b,c etc, but I am not even sure if this is the right way about it. This is a variant of the rule that I have tried : pass in on $int_if dup-to ($nms_if $nms-b ) proto udp from 10.10.10.1 to $nms-a port 162 (all macros are defined, and expanded correctly in the ruleset when issuing pfctl -s all ) The way I have understood the syntax, is that traps destined for nms-a, will be duplicated to nms-b. However, when I tcpdump the nms_if, I can only see traps for nms-a (and none for b). I mentioned that the rule was a variant, because I have tried several other options, but to no avail. Has anyone done this before? Am I barking up the wrong tree? Here is some more (hopefully) useful information : tcpdump output (x.x.x.2 is the ip of nms-a, and Y.Y.Y.Y is the agent address (the source ip of the trap)) 12:21:04.798192 10.10.10.1.2074 X.X.X.2.snmp-trap: Trap(36) E:cisco.9.41.2 [Y.Y.Y.Y] enterpriseSpecific[specific-trap(1)!=0] 16671316 .iso.org=[|snmp] The expanded rule from pfctl -s all | grep dup-to pass in on bge1 dup-to (vlan4 Z.Z.Z.1) inet proto udp from 10.10.10.1 to X.X.X.2 port = snmp-trap keep state (Z.Z.z.1 is nms-b) Any input is very welcomed, Cheers, Simon Stavdal. - Fe din egen, gratis e-postadresse pe Start.no As the man page states, it literally duplicate the packet. It means that an exact copy of it will be sent to the specified machine. Also, you are not seeing them when you use tcpdump, because they are all the same. If nms-b isn't prepared to receive an packet which wasn't destined for it, it will discard the packet silently. You must check on nms-b if it is receiving the packets. My regards, -- Giancarlo Razzolini http://lock.razzolini.adm.br Linux User 172199 Red Hat Certified Engineer no:804006389722501 Verify:https://www.redhat.com/certification/rhce/current/ Moleque Sem Conteudo Numero #002 OpenBSD Stable Ubuntu 8.04 Hardy Heron 4386 2A6F FFD4 4D5F 5842 6EA0 7ABE BBAB 9C0E 6B85
Re: Duplicate incoming packets to multiple destinations using pf
Simen Stavdal escreveu: Hi Giancarlo/misc, Thanks for the answer, I guess dup-to isn4t the right tool then... Has anyone tried to achieve what I am trying to do though? I am obviously open to other ideas. The main objective though, is to preserve the source address, while replacing the destination address to multiple hosts Cheers, Simon. On Nov 4, 2008, at 5:32 PM, Giancarlo Razzolini wrote: Simen Stavdal escreveu: Hello, I have the following scenario. A router (let's call it router A) is sending snmp traps to an nms (Network Monitoring System). Between the router A and the nms (let's call it nms-a) is a Dell PowerEdge 860 running OpenBSD 4.1 i386 (bsd.mp) and pf. On the same segment as nms-a, is nms-b, nms-c etc. I am trying to make pf copy the incoming trap, while keeping the source ip address (of router A), and changing the destination ip for nms-a,b,c etc, but I am not even sure if this is the right way about it. This is a variant of the rule that I have tried : pass in on $int_if dup-to ($nms_if $nms-b ) proto udp from 10.10.10.1 to $nms-a port 162 (all macros are defined, and expanded correctly in the ruleset when issuing pfctl -s all ) The way I have understood the syntax, is that traps destined for nms-a, will be duplicated to nms-b. However, when I tcpdump the nms_if, I can only see traps for nms-a (and none for b). I mentioned that the rule was a variant, because I have tried several other options, but to no avail. Has anyone done this before? Am I barking up the wrong tree? Here is some more (hopefully) useful information : tcpdump output (x.x.x.2 is the ip of nms-a, and Y.Y.Y.Y is the agent address (the source ip of the trap)) 12:21:04.798192 10.10.10.1.2074 X.X.X.2.snmp-trap: Trap(36) E:cisco.9.41.2 [Y.Y.Y.Y] enterpriseSpecific[specific-trap(1)!=0] 16671316 .iso.org=[|snmp] The expanded rule from pfctl -s all | grep dup-to pass in on bge1 dup-to (vlan4 Z.Z.Z.1) inet proto udp from 10.10.10.1 to X.X.X.2 port = snmp-trap keep state (Z.Z.z.1 is nms-b) Any input is very welcomed, Cheers, Simon Stavdal. - Fe din egen, gratis e-postadresse pe Start.no As the man page states, it literally duplicate the packet. It means that an exact copy of it will be sent to the specified machine. Also, you are not seeing them when you use tcpdump, because they are all the same. If nms-b isn't prepared to receive an packet which wasn't destined for it, it will discard the packet silently. You must check on nms-b if it is receiving the packets. My regards, -- Giancarlo Razzolini http://lock.razzolini.adm.br Linux User 172199 Red Hat Certified Engineer no:804006389722501 Verify:https://www.redhat.com/certification/rhce/current/ Moleque Sem Conteudo Numero #002 OpenBSD Stable Ubuntu 8.04 Hardy Heron 4386 2A6F FFD4 4D5F 5842 6EA0 7ABE BBAB 9C0E 6B85 I've never tried, but i think that you can use the dup-to rule you're using associated with a nat rule that filter the outgoing packets created by the dup-to rule, to change it's destination addresses. I recommend that you use tag's to make your life simple and also help on debugging. My regards, -- Giancarlo Razzolini http://lock.razzolini.adm.br Linux User 172199 Red Hat Certified Engineer no:804006389722501 Verify:https://www.redhat.com/certification/rhce/current/ Moleque Sem Conteudo Numero #002 OpenBSD Stable Ubuntu 8.04 Hardy Heron 4386 2A6F FFD4 4D5F 5842 6EA0 7ABE BBAB 9C0E 6B85
Re: Duplicate incoming packets to multiple destinations using pf
On Tue, Nov 04 2008 at 02:19, Simen Stavdal wrote: Hi Giancarlo/misc, Hello, Thanks for the answer, I guess dup-to isn4t the right tool then... Has anyone tried to achieve what I am trying to do though? I am obviously open to other ideas. Maybe I'll give you a wrong path but, did you looked at proxying the trap with net-snmp ? Direct the original trap to your firewall (carped ?) and then when the trap arrives on it, ask net-snmp to send serveral traps to the supervision servers. Claer The main objective though, is to preserve the source address, while replacing the destination address to multiple hosts Cheers, Simon. On Nov 4, 2008, at 5:32 PM, Giancarlo Razzolini wrote: Simen Stavdal escreveu: Hello, I have the following scenario. A router (let's call it router A) is sending snmp traps to an nms (Network Monitoring System). Between the router A and the nms (let's call it nms-a) is a Dell PowerEdge 860 running OpenBSD 4.1 i386 (bsd.mp) and pf. On the same segment as nms-a, is nms-b, nms-c etc. I am trying to make pf copy the incoming trap, while keeping the source ip address (of router A), and changing the destination ip for nms- a,b,c etc, but I am not even sure if this is the right way about it. This is a variant of the rule that I have tried : pass in on $int_if dup-to ($nms_if $nms-b ) proto udp from 10.10.10.1 to $nms-a port 162 (all macros are defined, and expanded correctly in the ruleset when issuing pfctl -s all ) The way I have understood the syntax, is that traps destined for nms-a, will be duplicated to nms-b. However, when I tcpdump the nms_if, I can only see traps for nms-a (and none for b). I mentioned that the rule was a variant, because I have tried several other options, but to no avail. Has anyone done this before? Am I barking up the wrong tree? Here is some more (hopefully) useful information : tcpdump output (x.x.x.2 is the ip of nms-a, and Y.Y.Y.Y is the agent address (the source ip of the trap)) 12:21:04.798192 10.10.10.1.2074 X.X.X.2.snmp-trap: Trap(36) E:cisco.9.41.2 [Y.Y.Y.Y] enterpriseSpecific[specific-trap(1)!=0] 16671316 .iso.org=[|snmp] The expanded rule from pfctl -s all | grep dup-to pass in on bge1 dup-to (vlan4 Z.Z.Z.1) inet proto udp from 10.10.10.1 to X.X.X.2 port = snmp-trap keep state (Z.Z.z.1 is nms-b) Any input is very welcomed, Cheers, Simon Stavdal. - Fe din egen, gratis e-postadresse pe Start.no As the man page states, it literally duplicate the packet. It means that an exact copy of it will be sent to the specified machine. Also, you are not seeing them when you use tcpdump, because they are all the same. If nms-b isn't prepared to receive an packet which wasn't destined for it, it will discard the packet silently. You must check on nms-b if it is receiving the packets. My regards,
Re: pkg_add error
On 2008-11-04, Gregory Edigarov [EMAIL PROTECTED] wrote: While running pkg_add -u -F updatedenpends: updatedepends, not updatedenpends - Cut - Verifying dependencies still match for kdelibs-3.5.8p3, kdebase-3.5.8p1 Can't update forward dependency of kdelibs-3.5.8p3 on OpenEXR-1.2.2p3: ilmbase-1.0.1p2 doesn't match (use -F updatedepends to force it) Can't update OpenEXR-1.2.2p3 into ilmbase-1.0.1p2 Error from ftp://ftp.openbsd.org//pub/OpenBSD/4.4/packages/i386/ilmbase-1.0.1p2.tgz: ftp: -: short write 421 Service not available, remote server has closed connection. /usr/sbin/pkg_add: ilmbase-1.0.1p2:Fatal error --- Cut - What gives? Is this a problem on my side?
Re: QEMU crashes
Todd T. Fries wrote: Just out of curiosity, humor me, run qemu as root with the following added options: -net nic,vlan=0 -net tap,vlan=0 I've observed that at some point user mode networking has started segv'ed on amd64 when running any qemu guest, and am sorry to report I have not yet tracked down the source of the issue.. Please let me know if you have other experiences. Thanks, This was interesting; I learned some new things. First I tried su -; then qemu ... - but this results in sdl errors. The above -net options cause /etc/qemu-ifup to be invoked; it took me a few minutes to figure out how to make that work properly. When I try export ETHER=em0 ; sudo -E qemu ...; I am now able to send my files out of the guest - THANKS. One problem - when I shutdown the guest, I get: /etc/qemu-ifdown: could not launch network script I run the script manually no problem. BTW: Since I first started using Win98 under qemu about a year ago; I noticed that Win98 guest does not keep accurate time? It looks like only every other second is counted; so that after 2 hours, Win98 clock advanced only one hour. Does this also happen on other guests? Frank
dhcpd on 4.4 is problematic
I read the upgrade guide, followed it, and have a 4.4-router in front of me.
Alas, it does not at all dish out an IP-address to an OpenSolaris client
(nv98). It used to do so before, without any fail at all, ever.
Immediately after the upgrade to 4.4, it fails 100%.
It does dish out IP-addresses to Knoppix 5.3.1 on the very same
interface of the very same machine when booted to Knoppix.
I have as well restarted the dhcpd with the interface on which I want
the address to be given out ('dhcpd xl0'), to no avail.
'ifconfig nge0 dhcp' on OpenSolaris also times out all the time. I only
need to 'ifonfig nge0 ..' and 'route add ..', on the OpenSolaris,
though, to connect to the router. Therefore it is not a hardware problem.
It looks much more like a compatibility problem between OpenBSD 4.4 and
(Open?)Solaris, which didn't exist before and which must not happen.
Any detail can be furnished on request,
Uwe
Re: OpenBGPd: Neighbor rejects prefix - bgpd don't announce it any more, to no one?!
Am 02.11.2008 um 23:06 schrieb Claudio Jeker: If you can reproduce the situation please include all the RIB information for the prefix: As the router are in a productive environment I can't reproduce this situation without any outage. But I'll set up a test environment and come back to you, if this is done. Regards, Falk
Re: OpenBSD 4.4 installation error: write failed; file system full
On Tue, Nov 4, 2008 at 12:32 PM, Chris [EMAIL PROTECTED] wrote: I've download and burned the 4.4 ISO from a local mirror and trying to upgrade from 4.3 to 4.4 on i386. After the installer does the fsck -fp, I get the following error: uid 0 on /: file system full /: write failed; file system full cp: /tmp/hosts: No space left on device I've also tried the 4.3 base CD and I get the same error. This has never happened before. Is there something I'm doing wrong? Yes! Here's my df -h output: /dev/rd0a 1.7M 1.7M 38.5k 98% / Here's you're problem,... you're trying to install a whole OS onto a 1,7MB partition.
Duplicate incoming packets to multiple destinations using pf
Hello, I have the following scenario. A router (let's call it router A) is sending snmp traps to an nms (Network Monitoring System). Between the router A and the nms (let's call it nms-a) is a Dell PowerEdge 860 running OpenBSD 4.1 i386 (bsd.mp) and pf. On the same segment as nms-a, is nms-b, nms-c etc. I am trying to make pf copy the incoming trap, while keeping the source ip address (of router A), and changing the destination ip for nms-a,b,c etc, but I am not even sure if this is the right way about it. This is a variant of the rule that I have tried : pass in on $int_if dup-to ($nms_if $nms-b ) proto udp from 10.10.10.1 to $nms-a port 162 (all macros are defined, and expanded correctly in the ruleset when issuing pfctl -s all ) The way I have understood the syntax, is that traps destined for nms-a, will be duplicated to nms-b. However, when I tcpdump the nms_if, I can only see traps for nms-a (and none for b). I mentioned that the rule was a variant, because I have tried several other options, but to no avail. Has anyone done this before? Am I barking up the wrong tree? Here is some more (hopefully) useful information : tcpdump output (x.x.x.2 is the ip of nms-a, and Y.Y.Y.Y is the agent address (the source ip of the trap)) 12:21:04.798192 10.10.10.1.2074 X.X.X.2.snmp-trap: Trap(36) E:cisco.9.41.2 [Y.Y.Y.Y] enterpriseSpecific[specific-trap(1)!=0] 16671316 .iso.org=[|snmp] The expanded rule from pfctl -s all | grep dup-to pass in on bge1 dup-to (vlan4 Z.Z.Z.1) inet proto udp from 10.10.10.1 to X.X.X.2 port = snmp-trap keep state (Z.Z.z.1 is nms-b) Any input is very welcomed, Cheers, Simon Stavdal. - Fe din egen, gratis e-postadresse pe Start.no
Re: OpenBSD 4.4 - fdisk issue
On Tue, Nov 04, 2008 at 05:39:46PM +0100, Christophe Rioux wrote: On Tue, Nov 04, 2008 at 04:31:57PM +0100, [EMAIL PROTECTED] wrote: I just try to install OpenBSD 4.4 on a serveur (HP DL120 G5) to test the functionality of the raid (seens it works again .). I configure the first disk without any issue, and then try following commands: disklabel wd0 disklabel.wd1 fdisk -i wd1 disklabel -R -r wd1 disklabel.wd1 newfs /dev/wd1a Error: newfs: /dev/wd1a: block device Second section of the newfs(8) manpage. Great ... This worked in 4.3 without any thing else; I didn't find anything in this section. http://www.openbsd.org/cgi-bin/man.cgi?query=newfsapropos=0sektion=0manpa th=OpenBSD+4.4arch=i386format=html What should I search for ? Use the raw device (/dev/rwd1a). Running newfs on a block device (/dev/wd1a) can lead to subtle and hard to diagnose problems. That's why it has been disabled in 4.4. -Otto
Re: Duplicate incoming packets to multiple destinations using pf
Claer wrote: : Thanks for the answer, I guess dup-to isn4t the right tool then... : Has anyone tried to achieve what I am trying to do though? : I am obviously open to other ideas. : Maybe I'll give you a wrong path but, did you looked at proxying the : trap with net-snmp ? : Direct the original trap to your firewall (carped ?) and then when the : trap arrives on it, ask net-snmp to send serveral traps to the : supervision servers. I can't help but feel that the OP is trying to use the wrong tool for the job. There are two really good options when dealing with what he's trying to do: 1) Configure multiple SNMP trap destinations in the client. Any halfway decent SNMP stack supports trapping to more than one destination. But in the cases this doesn't work... 2) Investigate a trap exploder. Heck, you could even run it right on the firewall itself, as Claer has suggested. (In fact, this is *exactly* what Claer suggested, only I've called it a fancy name: trap exploder.)
pkg_add error
While running pkg_add -u -F updatedenpends: - Cut - Verifying dependencies still match for kdelibs-3.5.8p3, kdebase-3.5.8p1 Can't update forward dependency of kdelibs-3.5.8p3 on OpenEXR-1.2.2p3: ilmbase-1.0.1p2 doesn't match (use -F updatedepends to force it) Can't update OpenEXR-1.2.2p3 into ilmbase-1.0.1p2 Error from ftp://ftp.openbsd.org//pub/OpenBSD/4.4/packages/i386/ilmbase-1.0.1p2.tgz: ftp: -: short write 421 Service not available, remote server has closed connection. /usr/sbin/pkg_add: ilmbase-1.0.1p2:Fatal error --- Cut - What gives? Is this a problem on my side? -- With best regards, Gregory Edigarov
OpenBSD 4.4 installation error: write failed; file system full
I've download and burned the 4.4 ISO from a local mirror and trying to upgrade from 4.3 to 4.4 on i386. After the installer does the fsck -fp, I get the following error: uid 0 on /: file system full /: write failed; file system full cp: /tmp/hosts: No space left on device I've also tried the 4.3 base CD and I get the same error. This has never happened before. Is there something I'm doing wrong? Here's my df -h output: /dev/rd0a 1.7M 1.7M 38.5k 98% / /dev/sd0a 68.9g 30.8g 34.7g 47% /mnt Thanks for any help.
uvm_fault again...
Hello again, After a long time since my initial post, I managed to test the machine which stopped three times in a week because of this uvm_fault. At first I thought it was the RAM. The RAM checked out fine after a full day of Memtest. Then some board/processor issue (the machine is a firewall running off a PC made in 2000): ran burnK6 for a couple of days: nothing. At last I was suggested it must be the disk: ran 30 passes of badblocks in r/w mode. Guess what? No defects. fsck turns out clean, too. Finally I was suggested to try -current and see if the issue would go away. This is a firewall, if I put it offline I won't get much stress testing (basically , it would just sit there idle). So I'm back at square one. Straight OBSD 4.3 kernel, off the CD set. Powered by a generous dual conversion UPS, so power spikes are out of the question. At this point, two questions: 1) Any ideas on what the cause might be? 2) In case it shows up again, what would be the best course of action? Keep in mind that the machine basically freezes, so I had to copy the whole trace (but is it really of any use?) by hand... Many thanks in advance! --Vic
Apache and probably other problems - OpenBSD 4.4
Hi, I've just set up two 4.4 boxes, i386 and amd64 on same king of hardware. I've started bundled apache and compiled ab from apache 2.2.10 The problem is that ab stops after about 100 requests with error: ab started on local machine: apr_socket_connect(): Connection refused (61) ab started on different machine: apr_connect(): apr_socket_connect(): Operation already in progress (37) ab started with parameters: -c 100 -n 1000 After this experience, I've reinstalled the boxes with OpenBSD 4.3, and the problem is gone... Am I missing something ? is the problem ab related ? ab started with -c 1 does not produce any errors. ab -c 100 -n 1000 to other OpenBSD 4.3 machines works also fine... Also checked with enabled and disabled pf, and with statefull filtering, and even with a help of relayd. I've also compiled squid, and checked it with ab, and the problem remains. Any help appreciated. Regards M.K.
Re: dhcpd on 4.4 is problematic
On Tue, Nov 4, 2008 at 2:53 AM, Uwe Dippel [EMAIL PROTECTED] wrote: Nov 4 14:00:23 firewall dhcpd[28296]: DHCPDISCOVER from 00:20:ed:ee:ed:14 via xl0 Nov 4 14:00:23 firewall dhcpd[28296]: DHCPOFFER on 192.168.116.162 to 00:20:ed:ee:ed:14 via xl0 Nov 4 14:01:28 firewall dhcpd[28296]: DHCPDISCOVER from 00:20:ed:ee:ed:14 via xl0 ...snip... Nov 4 15:35:55 firewall dhcpd[2000]: DHCPOFFER on 192.168.116.168 to 00:20:ed:59:2b:a2 via xl0 This same thing happened to me last night between me and my ISP. I deleted /var/db/dhclient.leases.if and rebooted which worked.
Re: Promise SATA 300 TX4 strangeness
I have one of these cards working in my file server system. Something I noticed is that while I had four drives hooked up to it, I ran into system freezes as well. The system console had some time out errors however. It is working well with just two 500 GB drives hooked up to it. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Joseph A Borg Sent: Tuesday, November 04, 2008 8:16 AM To: Duncan Patton a Campbell Cc: misc@openbsd.org Subject: Re: Promise SATA 300 TX4 strangeness I'm having the same problem. At first i thought it was a failed pci card, then the old bios. Now with a replacement card and updated bios, I tried to copy a hefty multi-Gb gzip file from an other disk to drive on the sata card and the machine is still hanging, hard: I have to switch it off. I just placed an order for 4.4. If this is resolved there I'll wait for it, but in the meantime any pointers would be appreciated. dmesg OpenBSD 4.3 (netatalk) #0: Sun May 18 21:32:08 CEST 2008 [EMAIL PROTECTED]:/usr/src/sys/arch/i386/compile/netatalk cpu0: Intel(R) Celeron(R) CPU 2.53GHz (GenuineIntel 686-class) 2.54 GHz cpu0: FPU ,V86 ,DE ,PSE ,TSC ,MSR ,PAE ,MCE ,CX8 ,APIC ,SEP ,MTRR ,PGE ,MCA ,CMOV ,PAT ,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,SBF,SSE3,MWAIT,DS- CPL,TM2,CNXT-ID,CX16,xTPR real mem = 2146267136 (2046MB) avail mem = 2067304448 (1971MB) mainbus0 at root bios0 at mainbus0: AT/286+ BIOS, date 05/28/07, BIOS32 rev. 0 @ 0xf0010, SMBIOS rev. 2.4 @ 0xfcd70 (22 entries) bios0: vendor American Megatrends Inc. version P3.20 date 05/28/2007 apm0 at bios0: Power Management spec V1.2 apm0: battery life expectancy 0% apm0: AC off, battery charge unknown, estimated 0:00 hours acpi at bios0 function 0x0 not configured pcibios0 at bios0: rev 2.1 @ 0xf/0x1 pcibios0: PCI IRQ Routing Table rev 1.0 @ 0xf4a80/192 (10 entries) pcibios0: PCI Interrupt Router at 000:31:0 (Intel 82801EB/ER LPC rev 0x00) pcibios0: PCI bus #2 is the last bus bios0: ROM list: 0xc/0xf800 0xcf800/0x5000 cpu0 at mainbus0 pci0 at mainbus0 bus 0: configuration mode 1 (no bios) pchb0 at pci0 dev 0 function 0 Intel 82865G Host rev 0x02 agp0 at pchb0: aperture at 0xf800, size 0x400 ppb0 at pci0 dev 1 function 0 Intel 82865G AGP rev 0x02 pci1 at ppb0 bus 1 vga1 at pci1 dev 0 function 0 NVIDIA GeForce FX 5200 rev 0xa1 wsdisplay0 at vga1 mux 1: console (80x25, vt100 emulation) wsdisplay0: screen 1-5 added (80x25, vt100 emulation) uhci0 at pci0 dev 29 function 0 Intel 82801EB/ER USB rev 0x02: irq 10 uhci1 at pci0 dev 29 function 1 Intel 82801EB/ER USB rev 0x02: irq 3 uhci2 at pci0 dev 29 function 2 Intel 82801EB/ER USB rev 0x02: irq 5 uhci3 at pci0 dev 29 function 3 Intel 82801EB/ER USB rev 0x02: irq 10 ehci0 at pci0 dev 29 function 7 Intel 82801EB/ER USB2 rev 0x02: irq 11 usb0 at ehci0: USB revision 2.0 uhub0 at usb0 Intel EHCI root hub rev 2.00/1.00 addr 1 ppb1 at pci0 dev 30 function 0 Intel 82801BA Hub-to-PCI rev 0xc2 pci2 at ppb1 bus 2 pciide0 at pci2 dev 0 function 0 Promise PDC40718 rev 0x02: DMA wd0 at pciide0 channel 1 drive 0: TOSHIBA MK1652GSX wd0: 16-sector PIO, LBA48, 152627MB, 312581808 sectors wd0(pciide0:1:0): using BIOS timings, Ultra-DMA mode 5 wd1 at pciide0 channel 3 drive 0: TOSHIBA MK1652GSX wd1: 16-sector PIO, LBA48, 152627MB, 312581808 sectors wd1(pciide0:3:0): using BIOS timings, Ultra-DMA mode 5 pciide0: using irq 5 for native-PCI interrupt re0 at pci2 dev 1 function 0 Realtek 8169 rev 0x10: RTL8169S (0x0400), irq 11, address 00:0e:2e:c2:e1:07 rgephy0 at re0 phy 7: RTL8169S/8110S PHY, rev. 0 rl0 at pci2 dev 5 function 0 Realtek 8139 rev 0x10: irq 11, address 00:13:8f:ca:39:3d rlphy0 at rl0 phy 0: RTL internal PHY ichpcib0 at pci0 dev 31 function 0 Intel 82801EB/ER LPC rev 0x02: 24-bit timer at 3579545Hz pciide1 at pci0 dev 31 function 1 Intel 82801EB/ER IDE rev 0x02: DMA, channel 0 configured to compatibility, channel 1 configured to compatibility pciide1: channel 0 disabled (no drives) atapiscsi0 at pciide1 channel 1 drive 0 scsibus0 at atapiscsi0: 2 targets cd0 at scsibus0 targ 0 lun 0: PIONEER, DVD-RW DVR-106D, 1.07 SCSI0 5/cdrom removable wd2 at pciide1 channel 1 drive 1: ST3400620A wd2: 16-sector PIO, LBA48, 381554MB, 781422768 sectors cd0(pciide1:1:0): using PIO mode 4, Ultra-DMA mode 2 wd2(pciide1:1:1): using PIO mode 4, Ultra-DMA mode 5 pciide2 at pci0 dev 31 function 2 Intel 82801EB SATA rev 0x02: DMA, channel 0 configured to native-PCI, channel 1 configured to native-PCI pciide2: using irq 5 for native-PCI interrupt wd3 at pciide2 channel 0 drive 0: Hitachi HDS721616PLA380 wd3: 16-sector PIO, LBA48, 152627MB, 312581808 sectors wd3(pciide2:0:0): using PIO mode 4, Ultra-DMA mode 5 wd4 at pciide2 channel 1 drive 0: Maxtor 6L250M0 wd4: 16-sector PIO, LBA48, 239372MB, 490234752 sectors wd4(pciide2:1:0): using PIO mode 4,
serial console: how to reset terminal in boot.conf?
Hi folks, Short question: Is there some magic in /etc/boot.conf I could use to reset the terminal before booting? Here is the problem: AFAICS the BIOS in my Supermicro board switches to black chars on a black background before disabling console redirection and handing off control to the OpenBSD boot process :-(. (Using script I captured console output: The control sequence sent by the BIOS is ^[[0;30;40m if you are interested. 30 and 40 mean black foreground and background colors.) As a workaround I had set boot.conf to set timeout 30 stty com0 9600 set tty com0 echo ^[[0;30;47m boot , but without luck. Regards Harri
Re: OpenBSD 4.4 installation error: write failed; file system full
On Tue, Nov 4, 2008 at 4:51 AM, Alexander Hall [EMAIL PROTECTED] wrote: I doubt he's trying to install stuff to the ramdisk... Thanks all for your help. My current OpenBSD 4.3 installation is sitting on / (/var, /home, /root and everything else is under /) - only one partition. And I have about 34.7g free in there. So my / is not small and has gigs of space free available. Also, my /etc/hosts file is 666K. Thanks for any further help.
Re: OpenBSD 4.4 installation error: write failed; file system full
On Tue, Nov 04, 2008 at 02:37:40PM -0800, Chris wrote: On Tue, Nov 4, 2008 at 4:51 AM, Alexander Hall [EMAIL PROTECTED] wrote: I doubt he's trying to install stuff to the ramdisk... Thanks all for your help. My current OpenBSD 4.3 installation is sitting on / (/var, /home, /root and everything else is under /) - only one partition. And I have about 34.7g free in there. So my / is not small and has gigs of space free available. Also, my /etc/hosts file is 666K. Thanks for any further help. The upgrade.sh script will copy the hosts file onto the ramdisk. A 666K hosts file is enough to be problematic I suspect. Ken
Re: OpenBSD 4.4 - fdisk issue
On Tue, Nov 04, 2008 at 04:31:57PM +0100, Christophe Rioux wrote: Hi I just try to install OpenBSD 4.4 on a serveur (HP DL120 G5) to test the functionality of the raid (seens it works again .). I configure the first disk without any issue, and then try following commands: disklabel wd0 disklabel.wd1 fdisk -i wd1 disklabel -R -r wd1 disklabel.wd1 newfs /dev/wd1a Error: newfs: /dev/wd1a: block device Same message when I try a mount. Not a problem I continue and made a new installation on wd1 (with the CD) Then I build my raid0 configuration (by compiling the kernel) and try to create the new disk: fdisk -i raid0 disklabel -E -raid0 newfs /dev/raid0a = same error by newfs and mount What do I wrong ? Regards It shouldn't affect your problem, but '-r' doesn't do anything anymore. Ken
Re: dhcpd on 4.4 is problematic
On 2008-11-04, Deraj Puma [EMAIL PROTECTED] wrote: On Tue, Nov 4, 2008 at 2:53 AM, Uwe Dippel [EMAIL PROTECTED] wrote: Nov 4 14:00:23 firewall dhcpd[28296]: DHCPDISCOVER from 00:20:ed:ee:ed:14 via xl0 Nov 4 14:00:23 firewall dhcpd[28296]: DHCPOFFER on 192.168.116.162 to 00:20:ed:ee:ed:14 via xl0 Nov 4 14:01:28 firewall dhcpd[28296]: DHCPDISCOVER from 00:20:ed:ee:ed:14 via xl0 ...snip... Nov 4 15:35:55 firewall dhcpd[2000]: DHCPOFFER on 192.168.116.168 to 00:20:ed:59:2b:a2 via xl0 This same thing happened to me last night between me and my ISP. That's not the same thing, Uwe is talking about OpenBSD dhcpd and OpenSolaris dhcp client. I deleted /var/db/dhclient.leases.if and rebooted which worked. Check you don't have two dhclients running and fighting over the same file, it will get corrupted.
Traffic logging IPsec
I have a simple IPsec setup with both endpoints on OpenBSD firewalls. Everything is working sweetly from day two. Day one was me stuffing around and trying things. We have done some traffic measurements in the past using ipaudit and that's fine for sniffing the LAN and seeing what VoIP was using etc BUT we want to log traffic up and down the tunnel and ipaudit just sees nothing on enc0. This is intended to just gather data for 24 hour chunks for several days so i don't want to explore another fancy app if I can do it simply. Clues? Thanx, *** NOTE *** Please DO NOT CC me. I am subscribed to the list. Mail to the sender address that does not originate at the list server is tarpitted. The reply-to: address is provided for those who feel compelled to reply off list. Thankyou. Rod/ /earth: write failed, file system is full cp: /earth/creatures: No space left on device
Re: OpenBSD 4.4 installation error: write failed; file system full
On Wed, Nov 5, 2008 at 10:38 AM, Kenneth R Westerback [EMAIL PROTECTED] wrote: On Tue, Nov 04, 2008 at 02:37:40PM -0800, Chris wrote: On Tue, Nov 4, 2008 at 4:51 AM, Alexander Hall [EMAIL PROTECTED] wrote: I doubt he's trying to install stuff to the ramdisk... Thanks all for your help. My current OpenBSD 4.3 installation is sitting on / (/var, /home, /root and everything else is under /) - only one partition. And I have about 34.7g free in there. So my / is not small and has gigs of space free available. Also, my /etc/hosts file is 666K. Thanks for any further help. The upgrade.sh script will copy the hosts file onto the ramdisk. A 666K hosts file is enough to be problematic I suspect. Yes, you are right. It was the /etc/hosts file. The installation went smoothly after removing lots of entries from there. Most of the entries of my /etc/hosts file actually come from http://www.mvps.org/winhelp2002/hosts.htm - it basically blackholes unwanted sites. Is there any way I can get around the upgrade issue without having to remove entries from my /etc/hosts file? Thanks.
Re: OpenBSD 4.4 installation error: write failed; file system full
Cheap easy fast way is to move /etc/hosts somewhere else prior to upgrade. Not sure if things like sysmerge will help On 11/4/08, Chris [EMAIL PROTECTED] wrote: On Wed, Nov 5, 2008 at 10:38 AM, Kenneth R Westerback [EMAIL PROTECTED] wrote: On Tue, Nov 04, 2008 at 02:37:40PM -0800, Chris wrote: On Tue, Nov 4, 2008 at 4:51 AM, Alexander Hall [EMAIL PROTECTED] wrote: I doubt he's trying to install stuff to the ramdisk... Thanks all for your help. My current OpenBSD 4.3 installation is sitting on / (/var, /home, /root and everything else is under /) - only one partition. And I have about 34.7g free in there. So my / is not small and has gigs of space free available. Also, my /etc/hosts file is 666K. Thanks for any further help. The upgrade.sh script will copy the hosts file onto the ramdisk. A 666K hosts file is enough to be problematic I suspect. Yes, you are right. It was the /etc/hosts file. The installation went smoothly after removing lots of entries from there. Most of the entries of my /etc/hosts file actually come from http://www.mvps.org/winhelp2002/hosts.htm - it basically blackholes unwanted sites. Is there any way I can get around the upgrade issue without having to remove entries from my /etc/hosts file? Thanks. -- http://www.glumbert.com/media/shift http://www.youtube.com/watch?v=tGvHNNOLnCk This officer's men seem to follow him merely out of idle curiosity. -- Sandhurst officer cadet evaluation. Securing an environment of Windows platforms from abuse - external or internal - is akin to trying to install sprinklers in a fireworks factory where smoking on the job is permitted. -- Gene Spafford learn french: http://www.youtube.com/watch?v=j1G-3laJJP0feature=related
Re: OpenBSD 4.4 installation error: write failed; file system full
On Tue, Nov 4, 2008 at 7:23 PM, Chris [EMAIL PROTECTED] wrote: Most of the entries of my /etc/hosts file actually come from http://www.mvps.org/winhelp2002/hosts.htm - it basically blackholes unwanted sites. Is there any way I can get around the upgrade issue without having to remove entries from my /etc/hosts file? Thanks. adblock in the browser is far more flexible, faster, and just plain works better. If you really feel that giant lists of banned addresses are the way to go, run a nameserver and do it there.
Re: OpenBSD 4.4 installation error: write failed; file system full
On Wed, Nov 05, 2008 at 11:23:20AM +1100, Chris wrote: On Wed, Nov 5, 2008 at 10:38 AM, Kenneth R Westerback [EMAIL PROTECTED] wrote: On Tue, Nov 04, 2008 at 02:37:40PM -0800, Chris wrote: On Tue, Nov 4, 2008 at 4:51 AM, Alexander Hall [EMAIL PROTECTED] wrote: I doubt he's trying to install stuff to the ramdisk... Thanks all for your help. My current OpenBSD 4.3 installation is sitting on / (/var, /home, /root and everything else is under /) - only one partition. And I have about 34.7g free in there. So my / is not small and has gigs of space free available. Also, my /etc/hosts file is 666K. Thanks for any further help. The upgrade.sh script will copy the hosts file onto the ramdisk. A 666K hosts file is enough to be problematic I suspect. Yes, you are right. It was the /etc/hosts file. The installation went smoothly after removing lots of entries from there. Most of the entries of my /etc/hosts file actually come from http://www.mvps.org/winhelp2002/hosts.htm - it basically blackholes unwanted sites. Is there any way I can get around the upgrade issue without having to remove entries from my /etc/hosts file? Thanks. I don't know off the top of my head, but now that you've identified the issue I'll put it on my list to look into. Ken
Re: OpenBSD 4.4 installation error: write failed; file system full
On Tue, Nov 04, 2008 at 08:13:08PM -0500, Ted Unangst wrote: | On Tue, Nov 4, 2008 at 7:23 PM, Chris [EMAIL PROTECTED] wrote: | Most of the entries of my /etc/hosts file actually come from | http://www.mvps.org/winhelp2002/hosts.htm - it basically blackholes | unwanted sites. Is there any way I can get around the upgrade issue | without having to remove entries from my /etc/hosts file? Thanks. | | adblock in the browser is far more flexible, faster, and just plain | works better. If you really feel that giant lists of banned addresses | are the way to go, run a nameserver and do it there. Which gives you the added benefit of being able to share these results with other computers in your network by configuring them to use said nameserver. Saves you from distributing this hosts file to a couple of machines. (I second Ted on the suggestion to use adblockers in your browser though). Cheers, Paul 'WEiRD' de Weerd -- [++-]+++.+++[---].+++[+ +++-].++[-]+.--.[-] http://www.weirdnet.nl/
Multipath to CISCO
Hi all, I am trying to get 4mb/s of IAX2 voice traffic to a single VOIP provider using an IAX2 trunk down here in Australia. One of the options we have is getting a 4mb SHDSL connection with an ISP. The ISP usually want to install a CISCO 1841 with two WIC1-SHDSL cards at a lease rate of $2,400 per annum. I don't want to spend that much money on a router, especially one that I won't own at the end. Unfortunately purchasing a $4,500 router is not really an option right now. So I spoke with the ISP and they are willing to help me work out a more cost effective solution. The plan is to terminate two SHDSL connections on two separate SHDSL ethernet modems, which will just forward the packets to the other end. The network between the OpenBSD box and the modems will be a publicly routeable /29. The ISP will then round robin the packets down to me, and I want to round robin the packets back to them. After reading http://www.openbsd.org/faq/faq6.html it looks that equal cost routing will not do what I want as it looks like each destination is mapped to one possible route out of a pool, which I believe means I'll only ever get 2mb/s per VOIP peer I connect to. The other option I believe would be using PF to round robin the packets on both destinations using route-to rules. Would this work? At the ISP end we will be terminating into the back of a CISCO. The ISP is willing to work out what we need to make it work. I'm really trying to avoid having to buy an 1841. Don't have the budget or inclination to spend that much money for a little green box when I think my OpenBSD box can handle it. Has anyone done something like this? Any pointers? Thanks Mikel
Re: OpenBSD 4.4 installation error: write failed; file system full
* Ted Unangst [EMAIL PROTECTED] [081104 20:18]: On Tue, Nov 4, 2008 at 7:23 PM, Chris [EMAIL PROTECTED] wrote: Most of the entries of my /etc/hosts file actually come from http://www.mvps.org/winhelp2002/hosts.htm - it basically blackholes unwanted sites. Is there any way I can get around the upgrade issue without having to remove entries from my /etc/hosts file? Thanks. adblock in the browser is far more flexible, faster, and just plain works better. If you really feel that giant lists of banned addresses are the way to go, run a nameserver and do it there. I compliment adblock with noscript and privoxy as well as block hole a few domains in my names server. And if you want to go even further, mix in Dans Guardian. Note, both privoxy and dansguardian are in ports. Jim
pkg_add error: +CONTENTS does not exist
I been updating packages from 4.3 to 4.4 but my box rebooted due to a power outage and now I'm getting the following error while updating packages: Warning: couldn't read packing-list from installed package jasper-1.900.1 File /var/db/pkg/jasper-1.900.1/+CONTENTS does not exist /usr/sbin/pkg_add: Can't locate jasper-1.900.1 (pkg_add -ui -F update -F updatedepends) I cd to /var/db/pkg/jasper-1.900.1/ and the directory is empty. Thanks for any help.
Re: newbie network segment routing query
On Wed, Nov 5, 2008 at 3:16 AM, John . [EMAIL PROTECTED] wrote: fxp0 to the speedtouch fxp1 for a network that I want to be unfiltered, in other words, real IPs (wired) fxp2 the top usable real IP - this I want to nat behind, it is for wireless fxp3 is unused. Is this a DMZ for fxp1? I don't need this traffic to be processed by the openbsd box, I just want it to go down the right interface. From what I've read, a DMZ involves some queuing/processing. Not sure if my nomenclature is right for what I'm describing. Is there a howto for what I'm trying to do? Do I have to split the /28? Basically you need to make a bridge between fxp0 and fxp1. I do this exact setup in one of our locations. The basic steps run like this: 1) Put one address from the /28 on the Speedtouch ethernet interface. 2) Put one address from the /28 on the OpenBSD box 3) Disable pf (pfctl -d) 4) Make sure you can ping the speedtouch and get out to the Internet. 5) Setup a bridge on fxp0 to fxp1 per the OpenBSD FAQ 6) Setup a computer on the fxp1 network and give it an IP from the /28 7) Make the default gateway on the computer on the fxp1 network equal the speed touch IP address 8) Make sure you can get out to the Internet on the computer on the fxp1 network. 9) Open your pf.conf file and add 'skip on fxp0 fxp1' for now 10) Put pass all in your pf.conf for now 11) Enable pf and make sure you can still ping the internet from your OpenBSD box and the computer on your network 12) Setup NAT on fxp2 per the FAQs 13) Setup a computer on the fxp2 network and make sure you can ping and get out to the internet 14) Go back through your pf.conf and put in the firewall rules you need. Hope that helps. Mikel -- http://lindsaar.net/ Rails, RSpec and Life blog
Re: Multipath to CISCO
On Wed, Nov 05, 2008 at 01:02:33PM +1100, Mikel Lindsaar wrote: After reading http://www.openbsd.org/faq/faq6.html it looks that equal cost routing will not do what I want as it looks like each destination is mapped to one possible route out of a pool, which I believe means I'll only ever get 2mb/s per VOIP peer I connect to. AFAIK it's done by a hash from the source and destination pair. So, it depends on if you have multiple sources. But what do I know, I didn't read the source... The other option I believe would be using PF to round robin the packets on both destinations using route-to rules. Would this work? Why wouldn't it? At the ISP end we will be terminating into the back of a CISCO. The ISP is willing to work out what we need to make it work. I'm really trying to avoid having to buy an 1841. Don't have the budget or inclination to spend that much money for a little green box when I think my OpenBSD box can handle it. If you have two ethernets and you want to round-robin, trunk(4) might work too. -- Jussi Peltola
Re: dhcpd on 4.4 is problematic
Deraj Puma wrote: This same thing happened to me last night between me and my ISP. I deleted /var/db/dhclient.leases.if and rebooted which worked. No cigar. Of course, I have no /var/db/dhclient.leases, but I did move dhcpd.leases out of the way and rebooted. It was recreated, but no IP dished out. Further, I also 'pfctl -d' the firewall out of the way. Still no success. I tried to find the location of the dhcp leases on Solaris, but no success. I found the only config file for the dhcpagent, and it has only one uncommented line for inet4: # By default, a parameter request list requesting a subnet mask (1), # router (3), DNS server (6), hostname (12), DNS domain (15), broadcast # address (28), and encapsulated vendor options (43), is sent to the DHCP # server when the DHCP agent sends requests. However, if desired, this # can be changed by altering the following parameter-value pair. The # numbers correspond to the values defined in the IANA bootp-dhcp-parameters # registry at the time of this writing. # PARAM_REQUEST_LIST=1,3,6,12,15,28,43 Then I continued debugging on the client side, and that was more promising. Here is the session on the admin side: # ifconfig nge0 dhcp status Interface State Sent Recv Declined Flags nge0 SELECTING7 0 0 # ifconfig nge0 dhcp status Interface State Sent Recv Declined Flags nge0 SELECTING8 0 0 # ifconfig nge0 dhcp drop # ifconfig nge0 dhcp status ifconfig: nge0: interface is not under DHCP control # ifconfig nge0 dhcp start ^C # /sbin/dhcpagent -d 2 -v # ps -eaf | grep dhcp root 319 1 0 11:06:37 ? 0:00 /sbin/dhcpagent # kill 319 # ifconfig nge0 192.168.116.91 # route add default 192.168.116.200 add net default: gateway 192.168.116.200 In the first part, one can see the counter of unsuccessful attempts incrementing. Then I stop dhcpclient, and restart; and stop and ask for verbose output. This is the dmesg, and it clearly shows a compatibility problem; under the default as well as under verbose states: Nov 5 11:07:07 solN /sbin/dhcpagent[319]: [ID 566172 daemon.warning] recv_pkt: bad option overload Nov 5 11:13:18 solN last message repeated 17 times Nov 5 11:13:50 solN /sbin/dhcpagent[319]: [ID 566172 daemon.warning] recv_pkt: bad option overload Nov 5 11:15:50 solN last message repeated 11 times Nov 5 11:16:28 solN /sbin/dhcpagent[1156]: [ID 787751 daemon.error] dhcp_ipc_init: cannot bind to port 4999 (agent already running?) Nov 5 11:16:53 solN /sbin/dhcpagent[319]: [ID 566172 daemon.warning] recv_pkt: bad option overload It is beyond my horizon, what the recv_pkt: bad option overload means, but it shows that Solaris is not going to accept offers from the dhcpd of 4.4. Alas, my fault, I have no backup of 4.3, but exactly the same had worked flawlessly throughout up to and including 4.3. Uwe
Re: dhcpd on 4.4 is problematic
Here is what Stuart requested. I hope the attachment goes through! Uwe 12:10:18.698196 00:20:ed:df:a7:28 ff:ff:ff:ff:ff:ff 0800 342: 0.0.0.0.68 255.255.255.255.67: [udp sum ok] xid:0x8e0c275e vend-rfc1048 DHCP:DISCOVER MSZ:1472 LT:4294967295 VC:83.85.78.87.46.105.56.54.112.99 PR:SM+DG+NS+HN+DN+BR+VO (DF) (ttl 255, id 43389, len 328) : 4500 0148 a97d 4000 ff11 d127 E..H)[EMAIL PROTECTED]' 0010: 0044 0043 0134 0ce5 0101 0600 .D.C.4.e 0020: 8e0c 275e ..'^ 0030: 0020 eddf a728 . m_'(.. 0040: 0050: 0060: 0070: 0080: 0090: 00a0: 00b0: 00c0: 00d0: 00e0: 00f0: 0100: 6382 5363 3501 0139 c.Sc5..9 0110: 0205 c033 04ff ff3c 0a53 554e 572e [EMAIL PROTECTED].SUNW. 0120: 6938 3670 6337 0701 0306 0c0f 1c2b ff00 i86pc7...+. 0130: 0140: 12:10:18.700699 00:60:97:73:55:1a 00:20:ed:df:a7:28 0800 362: 192.168.116.200.67 192.168.116.102.68: [udp sum ok] xid:0x8e0c275e Y:192.168.116.102 S:192.168.116.200 vend-rfc1048 OO:0 DHCP:OFFER SID:192.168.116.200 LT:259200 SM:255.255.255.0 DG:192.168.116.200 NS:192.168.116.200 DN:uwe.uniten.edu.my BR:192.168.116.255 RN:129600 RB:226800 WNS:172.16.3.247 [tos 0x10] (ttl 16, id 0, len 348) : 4510 015c 1011 3f02 c0a8 74c8 E..\..?.@(tH 0010: c0a8 7466 0043 0044 0148 82d5 0201 0600 @(tf.C.D.H.U 0020: 8e0c 275e c0a8 7466 ..'^@(tf 0030: c0a8 74c8 0020 eddf a728 @(tH. m_'(.. 0040: 0050: 0060: 0070: 0080: 0090: 00a0: 00b0: 00c0: 00d0: 00e0: 00f0: 0100: 6382 5363 3401 0035 c.Sc4..5 0110: 0102 3604 c0a8 74c8 3304 0003 f480 0104 ..6.@(tH3...t... 0120: ff00 0304 c0a8 74c8 0604 c0a8 74c8 ...@(tH..@(tH 0130: 0f11 7577 652e 756e 6974 656e 2e65 6475 ..uwe.uniten.edu 0140: 2e6d 791c 04c0 a874 ff3a 0400 01fa 403b .my..@(t:...z@; 0150: 0400 0375 f02c 04ac 1003 f7ff...up,.,..w 12:10:23.217543 00:20:ed:df:a7:28 ff:ff:ff:ff:ff:ff 0800 342: 0.0.0.0.68 255.255.255.255.67: [udp sum ok] xid:0x8e0c275e secs:5 vend-rfc1048 DHCP:DISCOVER MSZ:1472 LT:4294967295 VC:83.85.78.87.46.105.56.54.112.99 PR:SM+DG+NS+HN+DN+BR+VO (DF) (ttl 255, id 43390, len 328) : 4500 0148 a97e 4000 ff11 d126 E..H)[EMAIL PROTECTED] 0010: 0044 0043 0134 0ce0 0101 0600 .D.C.4.` 0020: 8e0c 275e 0005 ..'^ 0030: 0020 eddf a728 . m_'(.. 0040: 0050: 0060: 0070: 0080: 0090: 00a0: 00b0: 00c0: 00d0: 00e0: 00f0: 0100: 6382 5363 3501 0139 c.Sc5..9 0110:
4.4 installer can't see CD drive
Hello, 4.3's installer didn't give me any grief, but 4.4 doesn't give me an option to install from CD. System info: Compaq Evo D510 SFF 512MB RAM / 40GB IDE IDE CD-ROM 4.3 dmesg OpenBSD 4.3 (RAMDISK_CD) #645: Wed Mar 12 11:31:03 MDT 2008 [EMAIL PROTECTED]:/usr/src/sys/arch/i386/compile/RAMDISK_CD cpu0: Intel(R) Pentium(R) 4 CPU 2.53GHz (GenuineIntel 686-class) 2.53 GHz cpu0: FPU,V86,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,SBF,CNXT-ID,xTPR real mem = 527986688 (503MB) avail mem = 504332288 (480MB) mainbus0 at root bios0 at mainbus0: AT/286+ BIOS, date 12/30/02, BIOS32 rev. 0 @ 0xeba00, SMBIOS rev. 2.3 @ 0xfb360 (46 entries) bios0: vendor Compaq version 686O2 v2.20 date 12/30/2002 bios0: Compaq Evo D510 SFF acpi0 at bios0: rev 0, can't enable ACPI bios0: ROM list: 0xc/0xac00! 0xcac00/0x1800 0xe1c00/0x9000! cpu0 at mainbus0 pci at mainbus0 bus 0: configuration mode 1 (no bios) pchb0 at pci0 dev 0 function 0 Intel 82845G Host rev 0x01 agp at pchb0 not configured vga1 at pci0 dev 2 function 0 Intel 82845G Video rev 0x01 wsdisplay0 at vga1 mux 1: console (80x25, vt100 emulation) uhci0 at pci0 dev 29 function 0 Intel 82801DB USB rev 0x01: irq 11 uhci1 at pci0 dev 29 function 1 Intel 82801DB USB rev 0x01: irq 5 ehci0 at pci0 dev 29 function 7 Intel 82801DB USB rev 0x01: irq 10 usb0 at ehci0: USB revision 2.0 uhub0 at usb0 Intel EHCI root hub rev 2.00/1.00 addr 1 ppb0 at pci0 dev 30 function 0 Intel 82801BA Hub-to-PCI rev 0x81 pci1 at ppb0 bus 5 fxp0 at pci1 dev 8 function 0 Intel PRO/100 VM rev 0x81, i82562: irq 5, address 00:0b:cd:43:a0:a6 inphy0 at fxp0 phy 1: i82562EM 10/100 PHY, rev. 0 ichpcib0 at pci0 dev 31 function 0 Intel \^X2801DB LPC rev 0x01: 24-bit timer at 3579545Hz pciide0 at pci0 dev 31 function 1 Intel 82801DB IDE rev 0x01: DMA, channel 0 configured to compatibility, channel 1 configured to compatibility wd0 at pciide0 channel 0 drive 0: ST340017A wd0: 16-sector PIO, LBA, 38166MB, 78165360 sectors wd0(pciide0:0:0): using PIO mode 4, Ultra-DMA mode 5 atapiscsi0 at pciide0 channel 1 drive 0 scsibus0 at atapiscsi0: 2 targets cd0 at scsibus0 targ 0 lun 0: HL-DT-ST, CD-ROM GCR-8480B, 1.03 SCSI0 5/cdrom removable cd0(pciide0:1:0): using PIO mode 4, DMA mode 2 Intel 82801DB AC97 rev 0x01 at pci0 dev 31 function 5 not configured usb1 at uhci0: USB revision 1.0 uhub1 at usb1 Intel UHCI root hub rev 1.00/1.00 addr 1 usb2 at uhci1: USB revision 1.0 uhub2 at usb2 Intel UHCI root hub rev 1.00/1.00 addr 1 isa0 at ichpcib0 isadma0 at isa0 pckbc0 at isa0 port 0x60/5 pckbd0 at pckbc0 (kbd slot) pckbc0: using irq 1 for kbd slot wskbd0 at pckbd0: console keyboard, using wsdisplay0 npx0 at isa0 port 0xf0/16: reported by CPUID; using exception 16 pccom0 at isa0 port 0x3f8/8 irq 4: ns16550a, 16 byte fifo pccom1 at isa0 port 0x2f8/8 irq 3: ns16550a, 16 byte fifo fdc0 at isa0 port 0x3f0/6 irq 6 drq 2 fd0 at fdc0 drive 0: 1.44MB 80 cyl, 2 head, 18 sec biomask ffe5 netmask ffe5 ttymask ffe7 rd0: fixed, 3800 blocks uhub3 at uhub2 port 1 vendor 0x05e3 USB Hub rev 1.01/0.12 addr 2 uhidev0 at uhub3 port 1 configuration 1 interface 0 USB KVM Switch 4 PORT V1.5 USB KVM Switch 4 PORT V1.5 rev 1.10/1.50 addr 3 uhidev0: iclass 3/1 ukbd0 at uhidev0 wskbd1 at ukbd0 mux 1 wskbd1: connecting to wsdisplay0 uhidev1 at uhub3 port 1 configuration 1 interface 1 USB KVM Switch 4 PORT V1.5 USB KVM Switch 4 PORT V1.5 rev 1.10/1.50 addr 3 uhidev1: iclass 3/1, 4 report ids uhid at uhidev1 reportid 1 not configured uhid at uhidev1 reportid 2 not configured uhid at uhidev1 reportid 3 not configured uhid at uhidev1 reportid 4 not configured uhidev2 at uhub3 port 2 configuration 1 interface 0 Microsoft Microsoft 3-Button Mouse with IntelliEye(TM) rev 1.10/3.00 addr 4 uhidev2: iclass 3/1 uhid at uhidev2 not configured uhub4 at uhub3 port 3 Dell Dell USB Keyboard Hub rev 1.10/2.00 addr 5 uhidev3 at uhub4 port 1 configuration 1 interface 0 Dell Dell USB Keyboard rev 1.10/2.00 addr 6 uhidev3: iclass 3/1 ukbd1 at uhidev3 wskbd2 at ukbd1 mux 1 wskbd2: connecting to wsdisplay0 uhidev4 at uhub4 port 1 configuration 1 interface 1 Dell Dell USB Keyboard rev 1.10/2.00 addr 6 uhidev4: iclass 3/0, 3 report ids uhid at uhidev4 reportid 1 not configured uhid at uhidev4 reportid 2 not configured uhid at uhidev4 reportid 3 not configured root on rd0a swap on rd0b dump on rd0b OpenBSD 4.3 (RAMDISK_CD) #645: Wed Mar 12 11:31:03 MDT 2008 [EMAIL PROTECTED]:/usr/src/sys/arch/i386/compile/RAMDISK_CD cpu0: Intel(R) Pentium(R) 4 CPU 2.53GHz (GenuineIntel 686-class) 2.53 GHz cpu0: FPU,V86,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,SBF,CNXT-ID,xTPR real mem = 527986688 (503MB) avail mem = 504332288 (480MB) mainbus0 at root bios0 at mainbus0: AT/286+ BIOS, date 12/30/02, BIOS32 rev. 0 @ 0xeba00, SMBIOS rev. 2.3 @ 0xfb360 (46 entries) bios0: vendor Compaq version 686O2 v2.20 date
Re: 4.4 installer can't see CD drive
hmm, looks like 4th time's a charm. Setup an ftp server to install, tried again, and it gave me the option for CD. On Wed, Nov 5, 2008 at 12:49 AM, Luke Tidd [EMAIL PROTECTED] wrote: Hello, 4.3's installer didn't give me any grief, but 4.4 doesn't give me an option to install from CD. System info: Compaq Evo D510 SFF 512MB RAM / 40GB IDE IDE CD-ROM 4.3 dmesg OpenBSD 4.3 (RAMDISK_CD) #645: Wed Mar 12 11:31:03 MDT 2008 [EMAIL PROTECTED]:/usr/src/sys/arch/i386/compile/RAMDISK_CD cpu0: Intel(R) Pentium(R) 4 CPU 2.53GHz (GenuineIntel 686-class) 2.53 GHz cpu0: FPU,V86,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,SBF,CNXT-ID,xTPR real mem = 527986688 (503MB) avail mem = 504332288 (480MB) mainbus0 at root bios0 at mainbus0: AT/286+ BIOS, date 12/30/02, BIOS32 rev. 0 @ 0xeba00, SMBIOS rev. 2.3 @ 0xfb360 (46 entries) bios0: vendor Compaq version 686O2 v2.20 date 12/30/2002 bios0: Compaq Evo D510 SFF acpi0 at bios0: rev 0, can't enable ACPI bios0: ROM list: 0xc/0xac00! 0xcac00/0x1800 0xe1c00/0x9000! cpu0 at mainbus0 pci at mainbus0 bus 0: configuration mode 1 (no bios) pchb0 at pci0 dev 0 function 0 Intel 82845G Host rev 0x01 agp at pchb0 not configured vga1 at pci0 dev 2 function 0 Intel 82845G Video rev 0x01 wsdisplay0 at vga1 mux 1: console (80x25, vt100 emulation) uhci0 at pci0 dev 29 function 0 Intel 82801DB USB rev 0x01: irq 11 uhci1 at pci0 dev 29 function 1 Intel 82801DB USB rev 0x01: irq 5 ehci0 at pci0 dev 29 function 7 Intel 82801DB USB rev 0x01: irq 10 usb0 at ehci0: USB revision 2.0 uhub0 at usb0 Intel EHCI root hub rev 2.00/1.00 addr 1 ppb0 at pci0 dev 30 function 0 Intel 82801BA Hub-to-PCI rev 0x81 pci1 at ppb0 bus 5 fxp0 at pci1 dev 8 function 0 Intel PRO/100 VM rev 0x81, i82562: irq 5, address 00:0b:cd:43:a0:a6 inphy0 at fxp0 phy 1: i82562EM 10/100 PHY, rev. 0 ichpcib0 at pci0 dev 31 function 0 Intel \^X2801DB LPC rev 0x01: 24-bit timer at 3579545Hz pciide0 at pci0 dev 31 function 1 Intel 82801DB IDE rev 0x01: DMA, channel 0 configured to compatibility, channel 1 configured to compatibility wd0 at pciide0 channel 0 drive 0: ST340017A wd0: 16-sector PIO, LBA, 38166MB, 78165360 sectors wd0(pciide0:0:0): using PIO mode 4, Ultra-DMA mode 5 atapiscsi0 at pciide0 channel 1 drive 0 scsibus0 at atapiscsi0: 2 targets cd0 at scsibus0 targ 0 lun 0: HL-DT-ST, CD-ROM GCR-8480B, 1.03 SCSI0 5/cdrom removable cd0(pciide0:1:0): using PIO mode 4, DMA mode 2 Intel 82801DB AC97 rev 0x01 at pci0 dev 31 function 5 not configured usb1 at uhci0: USB revision 1.0 uhub1 at usb1 Intel UHCI root hub rev 1.00/1.00 addr 1 usb2 at uhci1: USB revision 1.0 uhub2 at usb2 Intel UHCI root hub rev 1.00/1.00 addr 1 isa0 at ichpcib0 isadma0 at isa0 pckbc0 at isa0 port 0x60/5 pckbd0 at pckbc0 (kbd slot) pckbc0: using irq 1 for kbd slot wskbd0 at pckbd0: console keyboard, using wsdisplay0 npx0 at isa0 port 0xf0/16: reported by CPUID; using exception 16 pccom0 at isa0 port 0x3f8/8 irq 4: ns16550a, 16 byte fifo pccom1 at isa0 port 0x2f8/8 irq 3: ns16550a, 16 byte fifo fdc0 at isa0 port 0x3f0/6 irq 6 drq 2 fd0 at fdc0 drive 0: 1.44MB 80 cyl, 2 head, 18 sec biomask ffe5 netmask ffe5 ttymask ffe7 rd0: fixed, 3800 blocks uhub3 at uhub2 port 1 vendor 0x05e3 USB Hub rev 1.01/0.12 addr 2 uhidev0 at uhub3 port 1 configuration 1 interface 0 USB KVM Switch 4 PORT V1.5 USB KVM Switch 4 PORT V1.5 rev 1.10/1.50 addr 3 uhidev0: iclass 3/1 ukbd0 at uhidev0 wskbd1 at ukbd0 mux 1 wskbd1: connecting to wsdisplay0 uhidev1 at uhub3 port 1 configuration 1 interface 1 USB KVM Switch 4 PORT V1.5 USB KVM Switch 4 PORT V1.5 rev 1.10/1.50 addr 3 uhidev1: iclass 3/1, 4 report ids uhid at uhidev1 reportid 1 not configured uhid at uhidev1 reportid 2 not configured uhid at uhidev1 reportid 3 not configured uhid at uhidev1 reportid 4 not configured uhidev2 at uhub3 port 2 configuration 1 interface 0 Microsoft Microsoft 3-Button Mouse with IntelliEye(TM) rev 1.10/3.00 addr 4 uhidev2: iclass 3/1 uhid at uhidev2 not configured uhub4 at uhub3 port 3 Dell Dell USB Keyboard Hub rev 1.10/2.00 addr 5 uhidev3 at uhub4 port 1 configuration 1 interface 0 Dell Dell USB Keyboard rev 1.10/2.00 addr 6 uhidev3: iclass 3/1 ukbd1 at uhidev3 wskbd2 at ukbd1 mux 1 wskbd2: connecting to wsdisplay0 uhidev4 at uhub4 port 1 configuration 1 interface 1 Dell Dell USB Keyboard rev 1.10/2.00 addr 6 uhidev4: iclass 3/0, 3 report ids uhid at uhidev4 reportid 1 not configured uhid at uhidev4 reportid 2 not configured uhid at uhidev4 reportid 3 not configured root on rd0a swap on rd0b dump on rd0b OpenBSD 4.3 (RAMDISK_CD) #645: Wed Mar 12 11:31:03 MDT 2008 [EMAIL PROTECTED]:/usr/src/sys/arch/i386/compile/RAMDISK_CD cpu0: Intel(R) Pentium(R) 4 CPU 2.53GHz (GenuineIntel 686-class) 2.53 GHz cpu0:
Re: Promise SATA 300 TX4 strangeness
I trawled the net yesterday i found these old threads on freebsd: http://lists.freebsd.org/pipermail/freebsd-stable/2006-March/023598.html https://kerneltrap.org/mailarchive/freebsd-hackers/2007/11/1/377849 seems to be an old bug in the hardware? I would like to know whether I should hang on to the card or purchase something affordable but more reliable. regards On Nov 4, 2008, at 23:11, Anathae Townsend wrote: I have one of these cards working in my file server system. Something I noticed is that while I had four drives hooked up to it, I ran into system freezes as well. The system console had some time out errors however. It is working well with just two 500 GB drives hooked up to it. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Joseph A Borg Sent: Tuesday, November 04, 2008 8:16 AM To: Duncan Patton a Campbell Cc: misc@openbsd.org Subject: Re: Promise SATA 300 TX4 strangeness I'm having the same problem. At first i thought it was a failed pci card, then the old bios. Now with a replacement card and updated bios, I tried to copy a hefty multi-Gb gzip file from an other disk to drive on the sata card and the machine is still hanging, hard: I have to switch it off. I just placed an order for 4.4. If this is resolved there I'll wait for it, but in the meantime any pointers would be appreciated. dmesg OpenBSD 4.3 (netatalk) #0: Sun May 18 21:32:08 CEST 2008 [EMAIL PROTECTED]:/usr/src/sys/arch/i386/compile/netatalk cpu0: Intel(R) Celeron(R) CPU 2.53GHz (GenuineIntel 686-class) 2.54 GHz cpu0: FPU ,V86 ,DE ,PSE ,TSC ,MSR ,PAE ,MCE ,CX8 ,APIC ,SEP ,MTRR ,PGE ,MCA ,CMOV ,PAT ,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,SBF,SSE3,MWAIT,DS- CPL,TM2,CNXT-ID,CX16,xTPR real mem = 2146267136 (2046MB) avail mem = 2067304448 (1971MB) mainbus0 at root bios0 at mainbus0: AT/286+ BIOS, date 05/28/07, BIOS32 rev. 0 @ 0xf0010, SMBIOS rev. 2.4 @ 0xfcd70 (22 entries) bios0: vendor American Megatrends Inc. version P3.20 date 05/28/2007 apm0 at bios0: Power Management spec V1.2 apm0: battery life expectancy 0% apm0: AC off, battery charge unknown, estimated 0:00 hours acpi at bios0 function 0x0 not configured pcibios0 at bios0: rev 2.1 @ 0xf/0x1 pcibios0: PCI IRQ Routing Table rev 1.0 @ 0xf4a80/192 (10 entries) pcibios0: PCI Interrupt Router at 000:31:0 (Intel 82801EB/ER LPC rev 0x00) pcibios0: PCI bus #2 is the last bus bios0: ROM list: 0xc/0xf800 0xcf800/0x5000 cpu0 at mainbus0 pci0 at mainbus0 bus 0: configuration mode 1 (no bios) pchb0 at pci0 dev 0 function 0 Intel 82865G Host rev 0x02 agp0 at pchb0: aperture at 0xf800, size 0x400 ppb0 at pci0 dev 1 function 0 Intel 82865G AGP rev 0x02 pci1 at ppb0 bus 1 vga1 at pci1 dev 0 function 0 NVIDIA GeForce FX 5200 rev 0xa1 wsdisplay0 at vga1 mux 1: console (80x25, vt100 emulation) wsdisplay0: screen 1-5 added (80x25, vt100 emulation) uhci0 at pci0 dev 29 function 0 Intel 82801EB/ER USB rev 0x02: irq 10 uhci1 at pci0 dev 29 function 1 Intel 82801EB/ER USB rev 0x02: irq 3 uhci2 at pci0 dev 29 function 2 Intel 82801EB/ER USB rev 0x02: irq 5 uhci3 at pci0 dev 29 function 3 Intel 82801EB/ER USB rev 0x02: irq 10 ehci0 at pci0 dev 29 function 7 Intel 82801EB/ER USB2 rev 0x02: irq 11 usb0 at ehci0: USB revision 2.0 uhub0 at usb0 Intel EHCI root hub rev 2.00/1.00 addr 1 ppb1 at pci0 dev 30 function 0 Intel 82801BA Hub-to-PCI rev 0xc2 pci2 at ppb1 bus 2 pciide0 at pci2 dev 0 function 0 Promise PDC40718 rev 0x02: DMA wd0 at pciide0 channel 1 drive 0: TOSHIBA MK1652GSX wd0: 16-sector PIO, LBA48, 152627MB, 312581808 sectors wd0(pciide0:1:0): using BIOS timings, Ultra-DMA mode 5 wd1 at pciide0 channel 3 drive 0: TOSHIBA MK1652GSX wd1: 16-sector PIO, LBA48, 152627MB, 312581808 sectors wd1(pciide0:3:0): using BIOS timings, Ultra-DMA mode 5 pciide0: using irq 5 for native-PCI interrupt re0 at pci2 dev 1 function 0 Realtek 8169 rev 0x10: RTL8169S (0x0400), irq 11, address 00:0e:2e:c2:e1:07 rgephy0 at re0 phy 7: RTL8169S/8110S PHY, rev. 0 rl0 at pci2 dev 5 function 0 Realtek 8139 rev 0x10: irq 11, address 00:13:8f:ca:39:3d rlphy0 at rl0 phy 0: RTL internal PHY ichpcib0 at pci0 dev 31 function 0 Intel 82801EB/ER LPC rev 0x02: 24-bit timer at 3579545Hz pciide1 at pci0 dev 31 function 1 Intel 82801EB/ER IDE rev 0x02: DMA, channel 0 configured to compatibility, channel 1 configured to compatibility pciide1: channel 0 disabled (no drives) atapiscsi0 at pciide1 channel 1 drive 0 scsibus0 at atapiscsi0: 2 targets cd0 at scsibus0 targ 0 lun 0: PIONEER, DVD-RW DVR-106D, 1.07 SCSI0 5/cdrom removable wd2 at pciide1 channel 1 drive 1: ST3400620A wd2: 16-sector PIO, LBA48, 381554MB, 781422768 sectors cd0(pciide1:1:0): using PIO mode 4, Ultra-DMA mode 2 wd2(pciide1:1:1): using PIO mode 4, Ultra-DMA mode 5 pciide2 at pci0 dev 31 function 2 Intel 82801EB SATA rev 0x02: DMA, channel 0 configured to native-PCI, channel 1 configured to native-PCI pciide2: using irq 5 for native-PCI interrupt wd3 at pciide2
