OpenBSD 4.1 and NFS and PF trouble
Hi guys. I have a problem with nfs and pf. When PF is on , then nfs not work. I put the hole for portmap and nfs in pf... but i think that the problem is in mountd, because mountd every time when I restart the server change his own port: # #rpcinfo -p mars program vers proto port 102 tcp111 portmapper 102 udp111 portmapper 151 udp883 mountd 153 udp883 mountd 151 tcp767 mountd 153 tcp767 mountd 132 udp 2049 nfs 133 udp 2049 nfs 132 tcp 2049 nfs 133 tcp 2049 nfs Sometimes 773 .. 762 ... 995, Ok . the question is how to set a static ports for mountd? (and then I will open the firewall (pf) for this port ..for the client machine.) BR and thanks in advance! -- View this message in context: http://www.nabble.com/OpenBSD-4.1-and-NFS-and-PF-trouble-tf4869532.html#a13933886 Sent from the openbsd user - misc mailing list archive at Nabble.com.
Re: OpenBSD 4.1 and NFS and PF trouble
I have a problem with nfs and pf. When PF is on , then nfs not work. I put the hole for portmap and nfs in pf... but i think that the problem is in mountd, because mountd every time when I restart the server change his own port: # #rpcinfo -p mars program vers proto port 102 tcp111 portmapper 102 udp111 portmapper 151 udp883 mountd 153 udp883 mountd 151 tcp767 mountd 153 tcp767 mountd 132 udp 2049 nfs 133 udp 2049 nfs 132 tcp 2049 nfs 133 tcp 2049 nfs Sometimes 773 .. 762 ... 995, Ok . the question is how to set a static ports for mountd? (and then I will open the firewall (pf) for this port ..for the client machine.) There is no way to do that. We do random port allocation. You could hand-patch mountd to pick a specific port at startup and bind() to it, but I would be averse to that going into the tree. There is a bit of a myth here, I should point out. You can't do NFS security, or more specifically RPC security, via packet filtering a the port level. Your file handles are going to be flying all over the place, and that is a massive problem. NFS is the biggest risk factor of them all, so why bother blocking anything else? I suppose there could be very specific reasons, but .. not everything can do everything. I did look before at having portmap tell pf which ports it was allocating, but gave up because (1) it was difficult to do, (2) it had basically no security benefit, and (3) it would only work on for pf running _on_ the portmap machine...
Re: 7800GS + 2 monitors under 4.2-release
Just thought I'd let people know xenocara has just had a big update (according to CVS mailing list) to a more recent code including nv and server. I will let you know if I have any success with the new update. -Chris On 24/11/2007, Paulo Rodriguez [EMAIL PROTECTED] wrote: Hey there, so far I haven't been successful with the snapshots. I suggest we keep an eye on xenocara and keep trying snapshots! :) Chris Harper schreef: I was just wondering if anyone has made any progress? I'm still using one monitor and it feels like I lost a finger. On 11/11/2007, Paulo Rodriguez [EMAIL PROTECTED] wrote: Hi Chris, I confirm again. The xenocara build from the last snapshop gave me zero results. I still have the garbled screen on the monitor plugged using a VGA connector. Funny thing is, it sets the correct resolution for the 22 screen but only ID's the AL1717 monitor. Very odd. Chris Harper schreef: Hi Paul Just wondering if you have had any success ? I updated to -current and also xenocara but it hasn't worked. I have managed to get some form of dual screen through nv(4)'s Option DualHead Yes. I could not set a resolution suitable for my dual 19W (1440x900) monitors thou, it also treats the pair of monitors as one giant monitor which makes opening windows 'fully' span the pair. On Nov 6, 2007 9:32 AM, Paulo Rodriguez [EMAIL PROTECTED] wrote: Hi Chris, Those are exactly the same symptoms I'm experiencing as well. I'll be trying -current later tonight to see how it goes. I'll keep you informed. Thanks, P Chris Harper schreef: Im currently attempting to get my 7900GTX to run dual screens under 4.2 release without success. I can only seem to get green and orange squares on the second monitor which are some how linked to the first as they change colour as the mouse moves around. Any progress you make would be appareciated. On Nov 5, 2007 10:46 PM, Paulo Rodriguez [EMAIL PROTECTED] wrote: Hi misc, Just wondering about any success stories getting dual-screen/xinerama running under OpenBSD 4.2-release with nVidia cards (G73) under X. If I read correctly the necessary code for this was imported by matthieu@ after 4.2-release code was frozen, so it should be in -current. Kind regards, Paulo
Re: How to track down a suspected memory leak?
On Sun, Nov 25, 2007 at 08:03:11AM +0100, Rolf Sommerhalder wrote: Hello list, I am looking for suggestions how to identify the source(s) of what appears to be a memory leak of approx. 10 MByte/day on a clustered pair of filtering bridges. These bridges are running i386 -current snapshot from Nov 2nd. They form outer, Internet-facing stage of a two stage firewall in an enterprise setup. [...] If i were you, i would collect a few vmstat -m outputs, probably using cron, at a time where the machines are pretty much idle and then compare them with the previous ones and see what's growing. If you're lucky, it gives you a pretty good indication in which subsystem the memory leak is. Then use the source :) Tobias
Re: adjusting the mtu with vr(4)
On Sunday 25 November 2007 00:00:45 Sevan / Venture37 wrote: Is the support for adjusting the mtu with VIA Rhine-II chipset based interfaces missing because of hardware limitations or because support for it hasn't been written yet?? # ifconfig vr0 mtu 1492 ifconfig: SIOCSIFMTU: Inappropriate ioctl for device Sevan / Venture37 _ The next generation of MSN Hotmail has arrived - Windows Live Hotmail http://www.newhotmail.co.uk Appears to me that via hands out specs on a nda case-by-case basis. Not sure why soekris decided to use those chips in the net-5501. Actually they use via rhine-III but they behave the same. If you're routing to dsl you can workaround in pf.conf by putting a line like scrub out on $ext_if max-mss 1452 in the normalization section. Regards, Dorian
Is memory remapped above 4GB recognised ? (e.g. MCH3000)
I've got a PC with an Intel MCH3000 chipset and 4GB of RAM running amd64 4.2-current (~1 week old). The 3.5-4GB area is reserved for mapping devices into memory. The missing 512 MB of RAM is remapped to the 4GB-4.5GB area by the chipset. Though 512MB of memory starting at address 0x1 can be seen on the boot prompt using machine memory the OS doesn't seem to use / report it. dmesg excerpt: real mem = 3753455616 (3579MB) avail mem = 3631599616 (3463MB) So the question is simple, does OpenBSD recognise the remapped memory at all ?
dd:ing an image created on Linux?
Hi, I have an image file of a Linux bootable CF-card. The image is created with 'dd if=/dev/sdc of=imagefile.bin' on a machine running Linux. When I try to write that image to another CF-card with 'dd if=imagefile.bin of=/dev/sd1c' from OpenBSD I get the following error after approximately 2 hours dd: /dev/sd1c: Invalid argument 2001893+0 records in 2001892+0 records out 1024968704 bytes transferred in 7009.618 secs (146223 bytes/sec) I've also tried with of=/dev/rsd1c with the same result. The image is writeable from the Linux machine so the image should be ok. The CF-cards (src and dst) are of same type and size. Any suggestions on what I'm doing wrong? /Markus
Re: OpenBSD 4.1 and NFS and PF trouble
Hi guys. I have a problem with nfs and pf. When PF is on , then nfs not work. I put the hole for portmap and nfs in pf... but i think that the problem is in mountd, because mountd every time when I restart the server change his own port: # #rpcinfo -p mars program vers proto port 102 tcp111 portmapper 102 udp111 portmapper 151 udp883 mountd 153 udp883 mountd 151 tcp767 mountd 153 tcp767 mountd 132 udp 2049 nfs 133 udp 2049 nfs 132 tcp 2049 nfs 133 tcp 2049 nfs Sometimes 773 .. 762 ... 995, Ok . the question is how to set a static ports for mountd? (and then I will open the firewall (pf) for this port ..for the client machine.) BR and thanks in advance! Also, don't forget to set no-df on your NFS rule. NFS sometimes fragments packets and sets the DF flag. PF will drop these packets if they are set in such a way unless you specify no-df in your rule.
Intel DG33 Support
Hi I have a Intel DG33FB with a Core Quad Processor and I have the followings problems - This chip has an Intel 82566DC-2 Network Card. According to em(4) driver. It support 82566DC but 82566DC-2 doesn't. The dmesg output was: vendor Intel, unknown product 0x294c (class network subclass ethernet, rev 0x02) at pci0 dev 25 function 0 not configured In FreeBSD 7.0 the em(4) driver works on this network card. Somebody can help me? The current OpenBDS CVS support it? - I have a IDE HardDisk and one SATA HardDisk. When OpenBSD 4.2 Installation startup it freeze :-(. OpenBSD detect two hardisk but doesn't start the installation script. if in the BIOS, I update the following option SATA as IDE to (SATA as ACHI) The OpenBSD 4.2 installation works fine but only detect the IDE Harddisk. The dmesg has the following message. ahci0 at pci0 dev 31 function 2 vendor Intel, unknown product 0x2922 rev 0x02: irq 11, unsupported AHCI revision 0x00010200 Somebody can help me? The SATA harddisk is the main data disk. - When I startup with bsd.mp It crash. How I can send to OpenBSD the trace and ps? PD: The dmesg output was: OpenBSD 4.2 (GENERIC) #375: Tue Aug 28 10:38:44 MDT 2007 [EMAIL PROTECTED]:/usr/src/sys/arch/i386/compile/GENERIC RTC BIOS diagnostic error 80clock_battery cpu0: Intel(R) Core(TM)2 Quad CPU Q6600 @ 2.40GHz (GenuineIntel 686-class) 2.41 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,VMX,EST,TM2,CX16,xTPR real mem = 2118729728 (2020MB) avail mem = 2041049088 (1946MB) RTC BIOS diagnostic error 80clock_battery mainbus0 at root bios0 at mainbus0: AT/286+ BIOS, date 05/02/07, SMBIOS rev. 2.4 @ 0xe33a0 (35 entries) bios0: vendor Intel Corp. version DPP3510J.86A.0216.2007.0502.1916 date 05/02/2007 bios0: Intel Corporation DG33FB apm0 at bios0: Power Management spec V1.2 apm0: battery life expectancy 0% apm0: AC off, battery charge unknown, estimated 0:00 hours apm0: flags 30102 dobusy 0 doidle 1 pcibios at bios0 function 0x1a not configured bios0: ROM list: 0xc/0xb400! 0xcb800/0x1e00! 0xcd800/0x1000 0xce800/0x1000 cpu0 at mainbus0 pci0 at mainbus0 bus 0: configuration mode 1 (no bios) pchb0 at pci0 dev 0 function 0 vendor Intel, unknown product 0x29c0 rev 0x02 vga1 at pci0 dev 2 function 0 vendor Intel, unknown product 0x29c2 rev 0x02: aperture at 0x9040, size 0x800 wsdisplay0 at vga1 mux 1: console (80x25, vt100 emulation) wsdisplay0: screen 1-5 added (80x25, vt100 emulation) vendor Intel, unknown product 0x29c4 (class communications subclass miscellaneous, rev 0x02) at pci0 dev 3 function 0 not configured vendor Intel, unknown product 0x294c (class network subclass ethernet, rev 0x02) at pci0 dev 25 function 0 not configured uhci0 at pci0 dev 26 function 0 vendor Intel, unknown product 0x2937 rev 0x02: irq 10 uhci1 at pci0 dev 26 function 1 vendor Intel, unknown product 0x2938 rev 0x02: irq 11 uhci2 at pci0 dev 26 function 2 vendor Intel, unknown product 0x2939 rev 0x02: irq 9 ehci0 at pci0 dev 26 function 7 vendor Intel, unknown product 0x293c rev 0x02: irq 9 usb0 at ehci0: USB revision 2.0 uhub0 at usb0: Intel EHCI root hub, rev 2.00/1.00, addr 1 azalia0 at pci0 dev 27 function 0 vendor Intel, unknown product 0x293e rev 0x02: irq 10 azalia0: host: High Definition Audio rev. 1.0 azalia0: codec: Realtek/0x0888 (rev. 0.1), HDA version 1.0 audio0 at azalia0 ppb0 at pci0 dev 28 function 0 vendor Intel, unknown product 0x2940 rev 0x02 pci1 at ppb0 bus 1 ppb1 at pci0 dev 28 function 1 vendor Intel, unknown product 0x2942 rev 0x02 pci2 at ppb1 bus 2 pciide0 at pci2 dev 0 function 0 Marvell 88SE6101 IDE rev 0xb2: DMA (unsupported), channel 0 configured to native-PCI, channel 1 configured to native-PCI pciide0: using irq 9 for native-PCI interrupt atapiscsi0 at pciide0 channel 0 drive 0 scsibus0 at atapiscsi0: 2 targets cd0 at scsibus0 targ 0 lun 0: HL-DT-ST, DVDRAM GSA-4165B, DL03 SCSI0 5/cdrom removable wd0 at pciide0 channel 0 drive 1: Maxtor 6Y120L0 wd0: 16-sector PIO, LBA, 117246MB, 240121728 sectors pciide0: channel 1 ignored (not responding; disabled or no drives?) ppb2 at pci0 dev 28 function 2 vendor Intel, unknown product 0x2944 rev 0x02 pci3 at ppb2 bus 3 ppb3 at pci0 dev 28 function 3 vendor Intel, unknown product 0x2946 rev 0x02 pci4 at ppb3 bus 4 ppb4 at pci0 dev 28 function 4 vendor Intel, unknown product 0x2948 rev 0x02 pci5 at ppb4 bus 5 uhci3 at pci0 dev 29 function 0 vendor Intel, unknown product 0x2934 rev 0x02: irq 11 uhci4 at pci0 dev 29 function 1 vendor Intel, unknown product 0x2935 rev 0x02: irq 11 uhci5 at pci0 dev 29 function 2 vendor Intel, unknown product 0x2936 rev 0x02: irq 10 ehci1 at pci0 dev 29 function 7 vendor Intel, unknown product 0x293a rev 0x02: irq 11 usb1 at ehci1: USB revision 2.0 uhub1 at usb1: Intel EHCI root hub, rev 2.00/1.00, addr 1 ppb5 at pci0 dev 30 function 0 Intel 82801BA AGP rev 0x92 pci6 at ppb5 bus 6 acx0 at pci6
fdisk manual page missing
Hello, There is no man page for fdisk in 4.2. http://www.openbsd.org/cgi-bin/man.cgi?query=fdiskapropos=0sektion=0manpath=OpenBSD+4.2arch=i386format=html Best regards, Mitja
updating source code from updated tarballs
I have a 4.2 master system which I intend to use to quickly install new systems. I have rebuilt the master system with updated sources; made the release sets; and made tarballs of /usr/src. I installed a client system with the sets over ftp. All is well. I want to eventually be able to update the client source code once in the field so I unpacked the master tarballs. The trouble is that when I performed a test update of this code there was a immense amount of downloading taking place. This should not have been the case. Given that I may have committed a mistake with the creation of the tarball is my method sound? It seems like a typical operation. Comments? // juan Looking for the perfect gift? Give the gift of Flickr! http://www.flickr.com/gift/
Re: dd:ing an image created on Linux?
On 11/25/07, Markus Bergkvist [EMAIL PROTECTED] wrote: Hi, I have an image file of a Linux bootable CF-card. The image is created with 'dd if=/dev/sdc of=imagefile.bin' on a machine running Linux. When I try to write that image to another CF-card with 'dd if=imagefile.bin of=/dev/sd1c' from OpenBSD I get the following error after approximately 2 hours dd: /dev/sd1c: Invalid argument 2001893+0 records in 2001892+0 records out 1024968704 bytes transferred in 7009.618 secs (146223 bytes/sec) I've also tried with of=/dev/rsd1c with the same result. The image is writeable from the Linux machine so the image should be ok. The CF-cards (src and dst) are of same type and size. Any suggestions on what I'm doing wrong? check disklabel to make sure the detected geometry is big enough to hold the imagefile. also, using rsd1 is the better device, and you should specify a block size bigger than the default 512 to make it faster.
Re: OpenBSD 4.1 and NFS and PF trouble
Brian Morton-5 wrote: Hi guys. I have a problem with nfs and pf. When PF is on , then nfs not work. I put the hole for portmap and nfs in pf... but i think that the problem is in mountd, because mountd every time when I restart the server change his own port: # #rpcinfo -p mars program vers proto port 102 tcp111 portmapper 102 udp111 portmapper 151 udp883 mountd 153 udp883 mountd 151 tcp767 mountd 153 tcp767 mountd 132 udp 2049 nfs 133 udp 2049 nfs 132 tcp 2049 nfs 133 tcp 2049 nfs Sometimes 773 .. 762 ... 995, Ok . the question is how to set a static ports for mountd? (and then I will open the firewall (pf) for this port ..for the client machine.) BR and thanks in advance! Also, don't forget to set no-df on your NFS rule. NFS sometimes fragments packets and sets the DF flag. PF will drop these packets if they are set in such a way unless you specify no-df in your rule. Hi Brian, The problem is not that. I use no-df in my pf. Phanks for your opinion Kind Regards -- View this message in context: http://www.nabble.com/OpenBSD-4.1---NFS-and-PF-trouble-tf4869532.html#a139371 03 Sent from the openbsd user - misc mailing list archive at Nabble.com.
Re: fdisk manual page missing
On Sun, Nov 25, 2007 at 03:31:16PM +0100, Mitja wrote: Hello, There is no man page for fdisk in 4.2. http://www.openbsd.org/cgi-bin/man.cgi?query=fdiskapropos=0sektion=0manpath=OpenBSD+4.2arch=i386format=html that's odd. maybe a 4.2 user can confirm it's missing, or maybe it's a blip in man.cgi. jmc
Re: fdisk manual page missing
On Nov 25, 2007 5:48 PM, Jason McIntyre [EMAIL PROTECTED] wrote: On Sun, Nov 25, 2007 at 03:31:16PM +0100, Mitja wrote: Hello, There is no man page for fdisk in 4.2. http://www.openbsd.org/cgi-bin/man.cgi?query=fdiskapropos=0sektion=0manpath=OpenBSD+4.2arch=i386format=html that's odd. maybe a 4.2 user can confirm it's missing, or maybe it's a blip in man.cgi. jmc It exists on my 4.2-current amd64 at least. No i386 around so don't know about that. br dunceor
Re: fdisk manual page missing
Mitja [EMAIL PROTECTED] wrote: Hello, There is no man page for fdisk in 4.2. http://www.openbsd.org/cgi-bin/man.cgi?query=fdiskapropos=0sektion=0manpath=OpenBSD \ +4.2arch=i386format=html Best regards, Mitja This is a little odd, but only that online manual page viewer is effected... The manual page does exist on all of my OpenBSD 4.2 systems. -Nix Fan.
Re: fdisk manual page missing
On 11/25/07, Jason McIntyre [EMAIL PROTECTED] wrote: On Sun, Nov 25, 2007 at 03:31:16PM +0100, Mitja wrote: Hello, There is no man page for fdisk in 4.2. http://www.openbsd.org/cgi-bin/man.cgi?query=fdiskapropos=0sektion=0manpath=OpenBSD+4.2arch=i386format=html that's odd. maybe a 4.2 user can confirm it's missing, or maybe it's a blip in man.cgi. jmc My i386 install has the manpage for fdisk(8). Digging through the man.cgi I find that only 4.2 is missing, -current and previous versions seem to exist. Interesting. --Kenny
Re: fdisk manual page missing
On Sun, Nov 25, 2007 at 06:01:50PM +0100, Karl Sjodahl - dunceor wrote: It exists on my 4.2-current amd64 at least. No i386 around so don't know about that. It's here on my 4.2-current i386, which was installed fresh from snap, so it's not a leftover. Must be something with the cgi. -- Darrin Chandler| Phoenix BSD User Group | MetaBUG [EMAIL PROTECTED] | http://phxbug.org/ | http://metabug.org/ http://www.stilyagin.com/ | Daemons in the Desert | Global BUG Federation
Re: How to track down a suspected memory leak?
On Nov 25, 2007 5:22 PM, David Higgs [EMAIL PROTECTED] wrote: Is this possibly the same memory leak mentioned below? http://marc.info/?l=openbsd-miscm=119572453509542w=2 Thanks David for this pointer. It may very well be the same issue. Even though the two bridged interfaces are em(4) (1 Gb/s), the Out-of-Band Management (OOBM) interface is fxp(4) that carries two VLANs, one for pfsync(4), and one for commandcontrol/monitoring. Interestingly, I observe memory depletion at the same rate on both nodes of these active-passive filtering bridge clusters (both the sparc64 and i386), e.g. free memory on the passive bridge depletes at the same rate as on the one that is active. This may hint that the problem is rather with the fxp(4) than with the em(4) which are bridged. Unless it is somehow related to Rapid Spanning Tree (RSTP) which is running on both the internal and external em(4)s on both the active and the passive node. Maybe it's worth mentioning that on the previous sparc64 platforms (Sun Blade 100), where I observed slow memory depletion first, the bridging was between two ports of a quad hme(4) NIC, and the OOBM was on a third port of the same quad NIC. Still, I will given Henning's patch a try, while waiting for results of the instrumentation with 'vmstat -m', as suggested by the previous responder. Thanks again, Rolf [EMAIL PROTECTED]:home]# ifconfig lo0: flags=8049UP,LOOPBACK,RUNNING,MULTICAST mtu 33208 groups: lo inet 127.0.0.1 netmask 0xff00 inet6 ::1 prefixlen 128 inet6 fe80::1%lo0 prefixlen 64 scopeid 0x6 em0: flags=8943UP,BROADCAST,RUNNING,PROMISC,SIMPLEX,MULTICAST mtu 1500 lladdr 00:10:f3:0c:fa:d6 description: brExt_InternetEx media: Ethernet autoselect (1000baseT full-duplex) status: active inet6 fe80::210:f3ff:fe0c:fad6%em0 prefixlen 64 scopeid 0x1 em1: flags=8943UP,BROADCAST,RUNNING,PROMISC,SIMPLEX,MULTICAST mtu 1500 lladdr 00:10:f3:0c:fa:d7 description: brInt_InternetInt media: Ethernet autoselect (1000baseT full-duplex) status: active inet6 fe80::210:f3ff:fe0c:fad7%em1 prefixlen 64 scopeid 0x2 fxp0: flags=8802BROADCAST,SIMPLEX,MULTICAST mtu 1500 lladdr 00:10:f3:0c:fa:d8 media: Ethernet autoselect (none) status: no carrier fxp1: flags=8843UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST mtu 1500 lladdr 00:10:f3:0c:fa:d9 description: VLAN trunk OOBMgtExt, brSync media: Ethernet autoselect (100baseTX full-duplex) status: active inet6 fe80::210:f3ff:fe0c:fad9%fxp1 prefixlen 64 scopeid 0x4 enc0: flags=0 mtu 1536 vlan21: flags=8843UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST mtu 1500 lladdr 00:10:f3:0c:fa:d9 description: brSync vlan: 21 priority: 0 parent interface: fxp1 groups: vlan inet6 fe80::210:f3ff:fe0c:fad9%vlan21 prefixlen 64 scopeid 0x7 inet 192.168.7.13 netmask 0xff00 broadcast 192.168.7.255 vlan71: flags=8843UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST mtu 1500 lladdr 00:10:f3:0c:fa:d9 description: OOBMgtExt vlan: 71 priority: 0 parent interface: fxp1 groups: vlan egress inet6 fe80::210:f3ff:fe0c:fad9%vlan71 prefixlen 64 scopeid 0x8 inet 172.16.71.13 netmask 0xff00 broadcast 172.16.71.255 pfsync0: flags=41UP,RUNNING mtu 1460 description: pfSync pfsync: syncdev: vlan21 syncpeer: 224.0.0.240 maxupd: 128 groups: carp pfsync bridge0: flags=41UP,RUNNING mtu 1500 groups: bridge pflog0: flags=141UP,RUNNING,PROMISC mtu 33208 groups: pflog [EMAIL PROTECTED]:home]# bridge0: flags=41UP,RUNNING priority 28672 hellotime 2 fwddelay 15 maxage 20 holdcnt 6 proto rstp em1 flags=cbLEARNING,DISCOVER,STP,PTP,AUTOPTP port 2 ifpriority 128 ifcost 2 forwarding role designated em0 flags=cfLEARNING,DISCOVER,BLOCKNONIP,STP,PTP,AUTOPTP port 1 ifpriority 128 ifcost 2 forwarding role root Addresses (max cache: 100, timeout: 240): 00:00:5e:00:01:0b em1 1 flags=0 00:11:20:2f:09:54 em0 1 flags=0 00:1d:46:97:5f:0d em1 1 flags=0 00:1d:46:97:5f:03 em0 1 flags=0 [EMAIL PROTECTED]:home]# [EMAIL PROTECTED]:home]# dmesg OpenBSD 4.2-current (GENERIC) #476: Fri Nov 2 14:41:26 MDT 2007 [EMAIL PROTECTED]:/usr/src/sys/arch/i386/compile/GENERIC cpu0: Intel(R) Pentium(R) 4 CPU 2.80GHz (GenuineIntel 686-class) 2.80 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 = 1072197632 (1022MB) avail mem = 1028968448 (981MB) mainbus0 at root bios0 at mainbus0: AT/286+ BIOS, date 06/29/06, BIOS32 rev. 0 @ 0xfb250, SMBIOS rev. 2.2 @ 0xf0800 (34 entries) bios0: vendor Phoenix Technologies, LTD version 6.00 PG date 06/29/2006 apm0 at bios0: Power Management spec V1.2 apm0: AC on, battery
Re: xterm color issues
does not work. On Nov 25, 2007 3:17 AM, Marcin Wilk [EMAIL PROTECTED] wrote: Jon pisze: hi I have installed OpenBSD 4.2 on a 32 bit x86 platform. full install/ all packages. When I start a xterm on a VNC # xterm -fg green Warning: Color name green is not defined does not understand any of the colors. Please help. Try xterm-color -- Marcin Nicram Wilk Homepage: http://nicram.sytes.net/
Re: rxvt / aterm etc.. cannot open due to Colour issue
After trying a few more things - this only happens on VNC that I installed from the 4.2 package repository. tightvnc-1.2.9p0.tgz tightvnc-viewer-1.2.9.tgz This does not happen on console. Help On Nov 24, 2007 8:01 PM, Jon [EMAIL PROTECTED] wrote: hi I did a new install of OpenBSD 4.2 on a 32bit i386 box. I then pkg_add rxvt, but it wont start with a color error. Error www# rxvt rxvt: can't determine colour: Black rxvt: can't determine colour: Black rxvt: aborting This seems to be an issue with the rgb.txt file and Xorg etc.. Can some one direct me as to what is rxvt looking for in the OS and where should it be.. I think it needs to look for the rgb.txt file - not sure where.. I need rxvt. please help. www# uname -a OpenBSD www 4.2 GENERIC#375 i386 www# rxvt -version rxvt: bad option -version Rxvt v2.7.10 - released: 26 MARCH 2003 Options: XPM,transparent,utmp,menubar,XIM,multichar_languages,scrollbars=rxvt,XGetDe-f aults www# Xorg X Window System Version 7.2.0 Release Date: 22 January 2007 X Protocol Version 11, Revision 0, Release 7.2 Build Operating System: OpenBSD 4.2 i386 Current Operating System: OpenBSD www 4.2 GENERIC#375 i386
IP over Simulated Radio/Satellite Channels
In an effort to port a Performance Enhancing Proxy (PEP, see scps.org) to OpenBSD, I am looking at ways to simulate radio channels at IP level with loss rate, delay and jitter. Has anyone worked on, for example, extending ALTQ to add delay and/or jitter capability to OpenBSD? Would I waste my time diving into the source of ALTQ? Two years back, I wrote an extension plugin for m0n0wall.ch which uses ipfw and dummynet in FreeBSD for traffic shaping. Actually, dummynet started off as an IP channel simulator that provides delay and jitter options besides loss rate, and then was also used for shaping/queuing. A search of the archives revealed that others asked also about extended IP channel simulation in OpenBSD. But I could not find anything ready to use yet. OpenBSD's IP stack parameter setting for high bandwidth-delay satellite channels were apparently tested using externally supplied simulation data. Apparently, others also worked on porting the SCPS (TP?) PEP to OpenBSD, but I am unclear if they ever succeeded to make it work, and if they published their work. I am grateful for any pointers towards IP channel simulation and/or PEPs such as SCPS TP in OpenBSD. Thanks, Rolf
Re: rxvt / aterm etc.. cannot open due to Colour issue
ok.. so I edit vncserver file and add $colorPath = /usr/X11R6/share/X11/rgb and things work.. On Nov 25, 2007 10:28 AM, Jon [EMAIL PROTECTED] wrote: After trying a few more things - this only happens on VNC that I installed from the 4.2 package repository. tightvnc-1.2.9p0.tgz tightvnc-viewer-1.2.9.tgz This does not happen on console. Help On Nov 24, 2007 8:01 PM, Jon [EMAIL PROTECTED] wrote: hi I did a new install of OpenBSD 4.2 on a 32bit i386 box. I then pkg_add rxvt, but it wont start with a color error. Error www# rxvt rxvt: can't determine colour: Black rxvt: can't determine colour: Black rxvt: aborting This seems to be an issue with the rgb.txt file and Xorg etc.. Can some one direct me as to what is rxvt looking for in the OS and where should it be.. I think it needs to look for the rgb.txt file - not sure where.. I need rxvt. please help. www# uname -a OpenBSD www 4.2 GENERIC#375 i386 www# rxvt -version rxvt: bad option -version Rxvt v2.7.10 - released: 26 MARCH 2003 Options: XPM,transparent,utmp,menubar,XIM,multichar_languages,scrollbars=rxvt,XGetDe-f aults www# Xorg X Window System Version 7.2.0 Release Date: 22 January 2007 X Protocol Version 11, Revision 0, Release 7.2 Build Operating System: OpenBSD 4.2 i386 Current Operating System: OpenBSD www 4.2 GENERIC#375 i386
Re: updating source code from updated tarballs
On Sun, Nov 25, 2007 at 10:31:30AM -0500, Juan Miscaro wrote: I have a 4.2 master system which I intend to use to quickly install new systems. I have rebuilt the master system with updated sources; made the release sets; and made tarballs of /usr/src. I installed a client system with the sets over ftp. All is well. I want to eventually be able to update the client source code once in the field so I unpacked the master tarballs. The trouble is that when I performed a test update of this code there was a immense amount of downloading taking place. This should not have been the case. Given that I may have committed a mistake with the creation of the tarball is my method sound? It seems like a typical operation. What's an 'update' in this context? And exactly what was doing the downloading? Joachim
Re: updating source code from updated tarballs
--- Joachim Schipper [EMAIL PROTECTED] wrote: On Sun, Nov 25, 2007 at 10:31:30AM -0500, Juan Miscaro wrote: I have a 4.2 master system which I intend to use to quickly install new systems. I have rebuilt the master system with updated sources; made the release sets; and made tarballs of /usr/src. I installed a client system with the sets over ftp. All is well. I want to eventually be able to update the client source code once in the field so I unpacked the master tarballs. The trouble is that when I performed a test update of this code there was a immense amount of downloading taking place. This should not have been the case. Given that I may have committed a mistake with the creation of the tarball is my method sound? It seems like a typical operation. What's an 'update' in this context? And exactly what was doing the downloading? I use cvsup to update my sources (to STABLE): *default release=cvs *default tag=OPENBSD_4_2 *default host=cvsup.no.openbsd.org *default base=/var/cvsup *default prefix=/usr *default delete use-rel-suffix *default compress OpenBSD-ports OpenBSD-src OpenBSD-xenocara // juan Ask a question on any topic and get answers from real people. Go to Yahoo! Answers and share what you know at http://ca.answers.yahoo.com
Re: updating source code from updated tarballs
On Sun, Nov 25, 2007 at 03:12:09PM -0500, Juan Miscaro wrote: --- Joachim Schipper [EMAIL PROTECTED] wrote: On Sun, Nov 25, 2007 at 10:31:30AM -0500, Juan Miscaro wrote: I have a 4.2 master system which I intend to use to quickly install new systems. I have rebuilt the master system with updated sources; made the release sets; and made tarballs of /usr/src. I installed a client system with the sets over ftp. All is well. I want to eventually be able to update the client source code once in the field so I unpacked the master tarballs. The trouble is that when I performed a test update of this code there was a immense amount of downloading taking place. This should not have been the case. Given that I may have committed a mistake with the creation of the tarball is my method sound? It seems like a typical operation. What's an 'update' in this context? And exactly what was doing the downloading? I use cvsup to update my sources (to STABLE): *default release=cvs *default tag=OPENBSD_4_2 *default host=cvsup.no.openbsd.org *default base=/var/cvsup *default prefix=/usr *default delete use-rel-suffix *default compress And was it downloading more files than on your 'master' server? -stable doesn't receive that many updates, but that can still be quite a few files. Joachim -- TFMotD: netstart (8) - command scripts for network startup
ntpd doesn't sync clock reliably anymore on 4.2
Hello, list! I've a problem with the clock of an old AMD K6-2 machine (dmesg below) since the 4.2-release upgrade. The clock worked fine before with 4.1. Because of this problem I upgraded to 4.2-current, but that didn't help. 192.168.0.21 and 192.168.0.22 are local routers, ntpd can sync their clock without problems, and other local machines sync fine using them. I tried also with pool.ntp.org on the problematic machine, with same results. I see this in the log after removing /var/db/ntpd.drift and setting the clock correctly via BIOS menu while rebooting: 23 04:13:49 darkone ntpd[15666]: ntp engine ready Nov 23 04:14:08 darkone ntpd[15666]: peer 192.168.0.22 now valid Nov 23 04:14:13 darkone ntpd[15666]: peer 192.168.0.21 now valid Nov 23 04:15:06 darkone ntpd[19117]: adjusting local clock by 0.290352s Nov 23 04:18:44 darkone ntpd[19117]: adjusting local clock by 0.175437s Nov 23 04:20:19 darkone ntpd[19117]: adjusting local clock by 0.115706s Nov 23 04:26:40 darkone ntpd[15666]: clock is now synced Nov 23 04:54:07 darkone ntpd[19117]: adjusting clock frequency by -60.029035 to -60.029035ppm Nov 23 05:11:20 darkone ntpd[19117]: adjusting clock frequency by -4.753364 to -64.782399ppm Nov 23 05:38:03 darkone ntpd[19117]: adjusting clock frequency by 4.342937 to -60.439462ppm Nov 23 15:37:50 darkone ntpd[19117]: adjusting clock frequency by 0.427949 to -60.011513ppm Nov 23 18:24:32 darkone ntpd[15666]: reply from 192.168.0.22: negative delay -0.012752s, next query 3082s Nov 23 18:24:48 darkone ntpd[15666]: reply from 192.168.0.21: negative delay -0.005866s, next query 3144s Nov 23 19:45:35 darkone ntpd[15666]: reply from 192.168.0.21: negative delay -0.019764s, next query 3014s Nov 23 20:16:04 darkone ntpd[15666]: reply from 192.168.0.22: negative delay -0.023478s, next query 3113s Nov 23 20:36:04 darkone ntpd[19117]: adjusting local clock by -61.662375s Nov 23 21:07:57 darkone ntpd[19117]: adjusting local clock by -261.236635s Nov 23 21:07:57 darkone ntpd[15666]: clock is now unsynced Nov 23 21:11:08 darkone ntpd[19117]: adjusting local clock by -407.747600s Nov 23 21:14:48 darkone ntpd[19117]: adjusting local clock by -406.641659s Nov 23 21:18:04 darkone ntpd[19117]: adjusting local clock by -405.661457s Nov 23 21:20:12 darkone ntpd[19117]: adjusting local clock by -405.015764s Nov 23 21:22:51 darkone ntpd[19117]: adjusting local clock by -404.219649s Nov 23 21:25:01 darkone ntpd[19117]: adjusting local clock by -403.563826s Nov 23 21:27:38 darkone ntpd[19117]: adjusting local clock by -402.774064s Nov 23 21:31:30 darkone ntpd[19117]: adjusting local clock by -401.608460s Nov 23 21:34:06 darkone ntpd[19117]: adjusting local clock by -400.822696s Nov 23 21:36:48 darkone ntpd[19117]: adjusting local clock by -400.011870s Nov 23 21:38:25 darkone ntpd[19117]: adjusting local clock by -399.520853s ...and so on. Sometimes ntpd can't sync the clock even if the clock is set correctly via BIOS menu and with /var/db/ntpd.drift removed before rebooting, but if I'm lucky, it works for maybe a day. Unfortunately there's no second time source and the BIOS has no ACPI: $ sysctl kern.timecounter kern.timecounter.tick=1 kern.timecounter.timestepwarnings=0 kern.timecounter.hardware=i8254 kern.timecounter.choice=i8254(0) dummy(-100) In fact the clock of that machine isn't that bad, it might be off a few seconds or even a minute per day without ntpd running, but not as much as with ntpd running. Is this simply a problem with broken hardware, or is it possible to fix this with the existing clock and software somehow? Thank you for your help! Tas. OpenBSD 4.2-current (GENERIC) #548: Sat Nov 17 22:47:27 MST 2007 [EMAIL PROTECTED]:/usr/src/sys/arch/i386/compile/GENERIC cpu0: AMD-K6(tm) 3D processor (AuthenticAMD 586-class) 502 MHz cpu0: FPU,V86,DE,PSE,TSC,MSR,MCE,CX8,PGE,MMX real mem = 536440832 (511MB) avail mem = 510857216 (487MB) mainbus0 at root bios0 at mainbus0: AT/286+ BIOS, date 08/05/99, BIOS32 rev. 0 @ 0xfb390, SMBIOS rev. 2.1 @ 0xf0800 (29 entries) bios0: vendor Award Software International, Inc. version 4.51 PG date 08/05/99 apm0 at bios0: Power Management spec V1.2 (slowidle) apm0: AC on, battery charge unknown pcibios0 at bios0: rev 2.1 @ 0xf/0xb80c pcibios0: PCI IRQ Routing Table rev 1.0 @ 0xfdde0/112 (5 entries) pcibios0: PCI Exclusive IRQs: 7 9 10 11 pcibios0: PCI Interrupt Router at 000:07:0 (VIA VT82C586 ISA rev 0x00) pcibios0: PCI bus #1 is the last bus bios0: ROM list: 0xc/0x8000 cpu0 at mainbus0 pci0 at mainbus0 bus 0: configuration mode 1 (no bios) pchb0 at pci0 dev 0 function 0 VIA VT82C598 PCI rev 0x04 ppb0 at pci0 dev 1 function 0 VIA VT82C598 AGP rev 0x00 pci1 at ppb0 bus 1 pcib0 at pci0 dev 7 function 0 VIA VT82C586 ISA rev 0x47 pciide0 at pci0 dev 7 function 1 VIA VT82C571 IDE rev 0x06: ATA33, channel 0 configured to compatibility, channel 1 configured to compatibility wd0 at pciide0 channel 0 drive 0: Maxtor 6Y120L0 wd0: 16-sector PIO, LBA, 117246MB, 240121728 sectors
Re: updating source code from updated tarballs
Hi Juan, Juan Miscaro wrote on Sun, Nov 25, 2007 at 10:31:30AM -0500: I have a 4.2 master system which I intend to use to quickly install new systems. This does make sense. You do not tell us whether you are using 4.2-stable or 4.2-current. Both are good choices; in any case, make sure you know which one you are using, and stick to it. Also read: http://www.openbsd.org/faq/faq5.html#Flavors I have rebuilt the master system with updated sources; made the release sets; So far, this is standard practice for both -stable and -current. and made tarballs of /usr/src. What are you going to with a src tarball? I suspect you won't need that kind of beast at all. Besides, why are you using the plural tarball*s*? I installed a client system with the sets over ftp. All is well. I want to eventually be able to update the client source code once in the field so I unpacked the master tarballs. Here i'm losing track of what you are doing. I suppose you are referring to your src tarball(s)? I suspect you won't need source code on the client machines. The standard way to handle upgrades is to update the src on the master only, to build new release sets on the master, and to use the official upgrade process to install these new release sets on the clients. That way, none of the clients will ever need source code. The trouble is that when I performed a test update of this code there was a immense amount of downloading taking place. This should not have been the case. Unless you tell us what you mean by test update (cvs update? which server? which command, exactly?) even guessing is difficult. In case you are talking about cd /usr/src; cvs up -dP this will take some time, even with a quick network link, using a public mirror in your own country and without many changes. For the above command, five minutes would seem normal even using a 100 Mbit/s internet connection. But probably this whole discussion is moot. I fail to see the point in copying /usr/src to several machines. If you just want to be able to read the source from all machines, you might want to use NFS, possibly in read-only mode. If you really need to copy the source to many machines, you should probably set up your own internal cvs mirror - but what for? Given that I may have committed a mistake with the creation of the tarball Hard to say - you did not tell us the command you used. On the other hand, this is not rocket science. cd /usr/src; tar -czf /tmp/src.tgz . should be sufficient to copy a source tree from one machine to another. is my method sound? It seems like a typical operation. Comments? Part of what you say looks sound and standard, but part of it does not. Yours, Ingo -- Ingo Schwarze [EMAIL PROTECTED] Serverbetrieb usta.de / studis.de
Re: dd:ing an image created on Linux?
the detected geometry was not big enough to hold the imagefile. I guess I'll have to have a chat with the guy who made the imagefile to see if the image could be shrinked. Thanks for the advice. Btw, what limitations are there on the block size, and what drawbacks should I expect with a too large block size? $ disklabel -p b sd1 disklabel: warning, DOS partition table with no valid OpenBSD partition # /dev/rsd1c: type: SCSI disk: SCSI disk label: CF Card flags: bytes/sector: 512 sectors/track: 63 tracks/cylinder: 255 sectors/cylinder: 16065 cylinders: 124 total bytes: 1024966656B rpm: 3600 interleave: 1 trackskew: 0 cylinderskew: 0 headswitch: 0 # microseconds track-to-track seek: 0 # microseconds drivedata: 0 16 partitions: #size offset fstype [fsize bsize cpg] c: 1024966656B 0B unused 0 0 $ ls -l total 8064096 -rw-r--r-- 1 markus markus 1039417344 Nov 21 18:37 1GBdisk.bin Ted Unangst wrote: check disklabel to make sure the detected geometry is big enough to hold the imagefile. also, using rsd1 is the better device, and you should specify a block size bigger than the default 512 to make it faster.
Re: dd:ing an image created on Linux?
If you own any other ~1G SD cards, perhaps you should try using one of them?... for reasons unknown, not all cards are created equal. :( -Nix Fan.
Re: dd:ing an image created on Linux?
On 11/25/07, Markus Bergkvist [EMAIL PROTECTED] wrote: the detected geometry was not big enough to hold the imagefile. I guess I'll have to have a chat with the guy who made the imagefile to see if the image could be shrinked. Thanks for the advice. Btw, what limitations are there on the block size, and what drawbacks should I expect with a too large block size? if your block size is too big, it will get chopped down for you, but 64k is the biggest supported by the kernel.
Re: fxp changes between 4.2 and earlier releases causing stability problems?
I do believe this has solved the problems I was having.
Cheers :)
sounds like you hit the memory leak we just found fixed.
Index: pf.c
===
RCS file: /cvs/src/sys/net/pf.c,v
retrieving revision 1.564
diff -u -p -r1.564 pf.c
--- pf.c18 Nov 2007 21:53:47 - 1.564
+++ pf.c22 Nov 2007 01:15:47 -
@@ -816,6 +816,8 @@ pf_insert_state(struct pfi_kif *kif, str
TAILQ_FOREACH(sp, cur-states, next)
if (sp-kif == kif) {/* collision! */
pf_stateins_err(tree_lan_ext, s, kif);
+ pf_detach_state(s,
+ PF_DT_SKIP_LANEXT|PF_DT_SKIP_EXTGWY);
return (-1);
}
pf_detach_state(s, PF_DT_SKIP_LANEXT|PF_DT_SKIP_EXTGWY);
@@ -958,10 +960,8 @@ pf_src_tree_remove_state(struct pf_state
u_int32_t timeout;
if (s-src_node != NULL) {
- if (s-state_key-proto == IPPROTO_TCP) {
- if (s-src.tcp_est)
- --s-src_node-conn;
- }
+ if (s-src.tcp_est)
+ --s-src_node-conn;
if (--s-src_node-states = 0) {
timeout = s-rule.ptr-timeout[PFTM_SRC_NODE];
if (!timeout)
Re: How to track down a suspected memory leak?
* Rolf Sommerhalder [EMAIL PROTECTED] [2007-11-25 18:44]: On Nov 25, 2007 5:22 PM, David Higgs [EMAIL PROTECTED] wrote: Is this possibly the same memory leak mentioned below? http://marc.info/?l=openbsd-miscm=119572453509542w=2 Thanks David for this pointer. It may very well be the same issue. Even though the two bridged interfaces are em(4) (1 Gb/s), the Out-of-Band Management (OOBM) interface is fxp(4) that carries two VLANs, one for pfsync(4), and one for commandcontrol/monitoring. the leak had nothing to do with fxp. it's simply a generic memory leak in a state insertion error path that single firewalls tend to trigger seldom if at all, but pfsync regularily hits. Still, I will given Henning's patch a try, while waiting for results of the instrumentation with 'vmstat -m', as suggested by the previous responder. if you're running pfsync i make bets it is that. if you look at vmstat -m and pfstatekeypl has more objects in use than pfstatepl you know it is that. -- Henning Brauer, [EMAIL PROTECTED], [EMAIL PROTECTED] BS Web Services, http://bsws.de Full-Service ISP - Secure Hosting, Mail and DNS Services Dedicated Servers, Rootservers, Application Hosting - Hamburg Amsterdam
Re: updating source code from updated tarballs
--- Ingo Schwarze [EMAIL PROTECTED] wrote: Hi Juan, Juan Miscaro wrote on Sun, Nov 25, 2007 at 10:31:30AM -0500: I have a 4.2 master system which I intend to use to quickly install new systems. This does make sense. You do not tell us whether you are using 4.2-stable or 4.2-current. Both are good choices; in any case, make sure you know which one you are using, and stick to it. Also read: http://www.openbsd.org/faq/faq5.html#Flavors I have rebuilt the master system with updated sources; made the release sets; So far, this is standard practice for both -stable and -current. and made tarballs of /usr/src. What are you going to with a src tarball? I suspect you won't need that kind of beast at all. Besides, why are you using the plural tarball*s*? I made a tarball of /usr/src and of /usr/ports I installed a client system with the sets over ftp. All is well. I want to eventually be able to update the client source code once in the field so I unpacked the master tarballs. Here i'm losing track of what you are doing. I suppose you are referring to your src tarball(s)? I suspect you won't need source code on the client machines. The standard way to handle upgrades is to update the src on the master only, to build new release sets on the master, and to use the official upgrade process to install these new release sets on the clients. That way, none of the clients will ever need source code. I'm embarrassed to say that I was intending to build my client systems locally. The ports tree can be useful though. The trouble is that when I performed a test update of this code there was a immense amount of downloading taking place. This should not have been the case. Unless you tell us what you mean by test update (cvs update? which server? which command, exactly?) even guessing is difficult. In case you are talking about cd /usr/src; cvs up -dP this will take some time, even with a quick network link, using a public mirror in your own country and without many changes. For the above command, five minutes would seem normal even using a 100 Mbit/s internet connection. But why should there be such a change if I just finished updating those same sources on the master? But probably this whole discussion is moot. I fail to see the point in copying /usr/src to several machines. If you just want to be able to read the source from all machines, you might want to use NFS, possibly in read-only mode. If you really need to copy the source to many machines, you should probably set up your own internal cvs mirror - but what for? Actually, the master is inside my company network whereas the clients are remote systems (in the field). [snip] Thanks for the advice. // juan Looking for a X-Mas gift? Everybody needs a Flickr Pro Account. http://www.flickr.com/gift/
Re: updating source code from updated tarballs
Juan Miscaro wrote: --- Ingo Schwarze [EMAIL PROTECTED] wrote: ... The standard way to handle upgrades is to update the src on the master only, to build new release sets on the master, and to use the official upgrade process to install these new release sets on the clients. That way, none of the clients will ever need source code. I'm embarrassed to say that I was intending to build my client systems locally. Save yourself time and work, make a release. The ports tree can be useful though. eh. I keep telling myself that, but I hardly ever use it 'cept on a couple machines. Those are usually NOT machines I'm installing packages to. (i.e., I use the ports tree on my management console machines, but on actual production machines, I never use it. I can look at the tree on my machine I'm sitting at, rather than the machine I'm sshed into, find what I need to know, then pkg_add -i whatever...) The trouble is that when I performed a test update of this code there was a immense amount of downloading taking place. This should not have been the case. Unless you tell us what you mean by test update (cvs update? which server? which command, exactly?) even guessing is difficult. unanswered important question. In case you are talking about cd /usr/src; cvs up -dP this will take some time, even with a quick network link, using a public mirror in your own country and without many changes. For the above command, five minutes would seem normal even using a 100 Mbit/s internet connection. But why should there be such a change if I just finished updating those same sources on the master? Because you either did or expect something wrong. What, we don't know. :) Even with a local CVS repository, a cvs update will take time, as it compares a lot of data. IF you use the right/wrong options, it produces a lot of output, which you may be misinterpreting as changes, even though it was just a progress report. (-q is your friend. usually). If you really are getting large numbers of actual changes, you probably aren't working with a -stable tree. If you didn't intend to, that's life, lots of changes are made to the tree every day. If you did intend to, your process is wrong, because you aren't. :) Nick.
OpenBSD on VMware
Hi *, I'm running a 4.1-GENERIC on a VMware server (the VMare host runs a Microsoft Windows OS). I've no access to the VMware server. At random time, the server is just powered off (that's the feedback I always received from the VMware server administrator). There is nothing in logs and as the server is off, the console is not available anymore. :( Does somebody already experienced such issue? Any tips to run OBSD as VMware guest? Regards, Xavier PS: I'm using pcn as network driver. Maybe vmnet could increase performance and/or stability?
Re: OpenBSD on VMware
It's a VMware server 1.0.3. I've no more info about the config. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of PowerBSD Sent: lundi 26 novembre 2007 8:17 To: misc@openbsd.org Subject: Re: OpenBSD on VMware On Mon, Nov 26, 2007 at 07:56:16AM +0100, Xavier Mertens wrote: Hi *, I'm running a 4.1-GENERIC on a VMware server (the VMare host runs a Microsoft Windows OS). I've no access to the VMware server. At random time, the server is just powered off (that's the feedback I always received from the VMware server administrator). There is nothing in logs and as the server is off, the console is not available anymore. :( Does somebody already experienced such issue? Any tips to run OBSD as VMware guest? Regards, Xavier PS: I'm using pcn as network driver. Maybe vmnet could increase performance and/or stability? I always runs openbsd on vmware , but the vware version is workstation 6.0.2.59824 . you may post your vmware server version.
Re: IP over Simulated Radio/Satellite Channels
Rolf Sommerhalder wrote: In an effort to port a Performance Enhancing Proxy (PEP, see scps.org) to OpenBSD, I am looking at ways to simulate radio channels at IP level with loss rate, delay and jitter. [...] I am grateful for any pointers towards IP channel simulation and/or PEPs such as SCPS TP in OpenBSD. You could try tunbridge, which does loss, delay but not (I think) jitter. tunbridge(1) emulate a long, possibly lossy, link using the tun device. tunbridge(1) reads packets from the tun(4) device, creates a delay, packet loss, and packet shaping, and then, reinjects the packets to the same tun device. http://www.iijlab.net/~kjc/software/dist/tunbridge-0.1.tar.gz -- Darren Tucker (dtucker at zip.com.au) GPG key 8FF4FA69 / D9A3 86E9 7EEE AF4B B2D4 37C9 C982 80C7 8FF4 FA69 Good judgement comes with experience. Unfortunately, the experience usually comes from bad judgement.
Re: OpenBSD on VMware
On Mon, Nov 26, 2007 at 08:15:03AM +0100, Xavier Mertens wrote: It's a VMware server 1.0.3. I've no more info about the config. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of PowerBSD Sent: lundi 26 novembre 2007 8:17 To: misc@openbsd.org Subject: Re: OpenBSD on VMware On Mon, Nov 26, 2007 at 07:56:16AM +0100, Xavier Mertens wrote: Hi *, I'm running a 4.1-GENERIC on a VMware server (the VMare host runs a Microsoft Windows OS). I've no access to the VMware server. At random time, the server is just powered off (that's the feedback I always received from the VMware server administrator). There is nothing in logs and as the server is off, the console is not available anymore. :( Does somebody already experienced such issue? Any tips to run OBSD as VMware guest? Regards, Xavier PS: I'm using pcn as network driver. Maybe vmnet could increase performance and/or stability? I always runs openbsd on vmware , but the vware version is workstation 6.0.2.59824 . you may post your vmware server version. you need upgrade vmware server to VMware Server 1.0.4
Re: OpenBSD on VMware
Ok, the only fix that explains my issue is this one: This release fixes a problem that resulted from a conflict between Linux guest operating systems with kernel version 2.6.21 and RTC-related processes on the host. This problem caused the virtual machine to quit unexpectedly. Could you give me more details? As the VMware server is not under my control, I need to have good arguments to ask them to upgrade! :( /x -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of PowerBSD Sent: lundi 26 novembre 2007 8:33 To: misc@openbsd.org Subject: Re: OpenBSD on VMware On Mon, Nov 26, 2007 at 08:15:03AM +0100, Xavier Mertens wrote: It's a VMware server 1.0.3. I've no more info about the config. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of PowerBSD Sent: lundi 26 novembre 2007 8:17 To: misc@openbsd.org Subject: Re: OpenBSD on VMware On Mon, Nov 26, 2007 at 07:56:16AM +0100, Xavier Mertens wrote: Hi *, I'm running a 4.1-GENERIC on a VMware server (the VMare host runs a Microsoft Windows OS). I've no access to the VMware server. At random time, the server is just powered off (that's the feedback I always received from the VMware server administrator). There is nothing in logs and as the server is off, the console is not available anymore. :( Does somebody already experienced such issue? Any tips to run OBSD as VMware guest? Regards, Xavier PS: I'm using pcn as network driver. Maybe vmnet could increase performance and/or stability? I always runs openbsd on vmware , but the vware version is workstation 6.0.2.59824 . you may post your vmware server version. read this link : http://www.vmware.com/support/server/doc/releasenotes_server.html#resolved
