Re: CCD
first: YOU WROTE: "-> creating one partition of type ccd spanning entire disk" i take you're word then you should have a close look at 'man ccd' "Note that the `raw' partitions of the disks should not be combined. Each component partition should be offset at least one cylinder from the beginning of the component disk." this is not what you said you did. second: i would use disklabel to create explicitly a partition on ccd0 (not using 'c'). but i'm not sure if this is really necessary. On Wednesday 17 January 2007 19:11, Chris Mika wrote: > I'm trying to get CCD working correctly, but it just doesn't want to. > > I have two identical 300GB disks that I'm trying to interleave. > > Here's exactly what I'm doing: > # fdisk -i wd1 > # fdisk -i wd3 > # disklabel -E wd1 >-> creating one partition of type ccd spaning entire disk > # disklabel -E wd3 >-> creating one partition of type ccd spaning entire disk > # ccdconfig ccd0 32 0 /dev/wd1a /dev/wd3a > # newfs /dev/ccd0c > > When I run newfs it only creates a 300GB filesystem, whereas it SHOULD > create a 600GB file system. > > Any ideas? I can send the dmesg or any output if that helps (I didn't to > save space). > > -Chris Mika
Re: CCD
On Wednesday 17 January 2007 22:30, Chris Mika wrote: > I sat down and calculated one cylinder, and it's not 63 sectors, it's > 1008. So I redid the disklabel and it seems to be working. I ran newfs and > it's reporting 600GB. > > You can't create a partition on ccd0, you must use ccd0c. i don't know what makes you thing so. but it's wrong. from the FAQ - 14.18.1 - CCD: " Just use disklabel on it like you normally would to make the partition or partitions you want to use. Again, don't use the 'c' partition as an actual partition that you put stuff on." > > On Wed, 17 Jan 2007, Chris Mika wrote: > > I've read that. That's why I began the offset using disklabel's default > > setting, which is 63. Sorry, that's why I said you can ask for > > clarification. > > > > As for the second part, it wasn't so clear, but with FreeBSD's ccd you > > create the file system on /dev/ccd0c so I assumed it was the same. If you > > use disklabel -E ccd0 it can't get the approrpriate geometry. > > > > On Wed, 17 Jan 2007, christian widmer wrote: > >> first: > >> YOU WROTE: "-> creating one partition of type ccd spanning entire disk" > >> > >> i take you're word then you should have a close look at 'man ccd' > >> > >> "Note that the `raw' partitions of the disks should not be combined. > >> Each component partition should be offset at least one cylinder from the > >> beginning > >> of the component disk." > >> > >> this is not what you said you did. > >> > >> second: > >> i would use disklabel to create explicitly a partition on ccd0 (not > >> using 'c'). but i'm not sure if this is really necessary. > >> > >> On Wednesday 17 January 2007 19:11, Chris Mika wrote: > >>> I'm trying to get CCD working correctly, but it just doesn't want to. > >>> > >>> I have two identical 300GB disks that I'm trying to interleave. > >>> > >>> Here's exactly what I'm doing: > >>> # fdisk -i wd1 > >>> # fdisk -i wd3 > >>> # disklabel -E wd1 > >>>-> creating one partition of type ccd spaning entire disk > >>> # disklabel -E wd3 > >>>-> creating one partition of type ccd spaning entire disk > >>> # ccdconfig ccd0 32 0 /dev/wd1a /dev/wd3a > >>> # newfs /dev/ccd0c > >>> > >>> When I run newfs it only creates a 300GB filesystem, whereas it SHOULD > >>> create a 600GB file system. > >>> > >>> Any ideas? I can send the dmesg or any output if that helps (I didn't > >>> to save space). > >>> > >>> -Chris Mika
Re: ccd, disklabel and partition 'a'
On Sunday 28 January 2007 11:02, Patrick Useldinger wrote: > I am currently experimenting with ccd(4) and although it appears to > work, I am uncomfortable with one point. > > I have configured 2 partitions as a JBOD (interleave 0). However, the > first of these partitions is partition 'a' of one disk. So the first > effect I had was that ccd0 appeared to have the same disklabel as the > first disk. man ccd: "Note that the `raw' partitions of the disks should not be combined. Each component partition should be offset at least one cylinder from the beginning of the component disk." see also thread on misc: CCD: started on 17 jan 2007 by Chris Mika how much one cylinder is, can be calculated with the numbers given by disklabel. ight about the following point but: i would not use partition 'a' for anything else then my boot partition. thus i never used 'a' as a member of a ccd, nor did i create an 'a' on a ccd. unfortunatly disklabel -E ccd0 did not work for me after 'fdisk -i ccd0', since 'ccd0c' had type '4.2BSD' not 'unused' as for raw devices. since the FAQ sais: "Just use disklabel on it like you normally would to make the partition or partitions you want to use. Again, don't use the 'c' partition as an actual partition that you put stuff on." i used 'disklabel -e ccd0' to change the type to 'unused'. after that i created one big partition 'd' on the ccd0 drive. //llx > > I read through the mailing list archives and found a thread explaining > that the disklabel is stored around the beginning of partition 'a' and > that one should allocate a small partition 'a' which should not be made > part of the JBOD. > > What I am uncomfortable with is that > > 1) this does not appear to be documented in the man pages anywhere > > 2) that the size and position of the disklabel of partition 'a' is not > clearly stated anywhere so that I can be certain that it doesn't get > overwritten and that I am not wasting too much space. > > Can anybody please shed some light on this? > > Regards, > -pu
Re: ccd, disklabel and partition 'a'
On Sunday 28 January 2007 15:19, Kenneth R Westerback wrote: > On Sun, Jan 28, 2007 at 12:14:00PM +0100, christian widmer wrote: > > On Sunday 28 January 2007 11:02, Patrick Useldinger wrote: > > > I am currently experimenting with ccd(4) and although it appears to > > > work, I am uncomfortable with one point. > > > > > > I have configured 2 partitions as a JBOD (interleave 0). However, the > > > first of these partitions is partition 'a' of one disk. So the first > > > effect I had was that ccd0 appeared to have the same disklabel as the > > > first disk. > > > > man ccd: > > "Note that the `raw' partitions of the disks should not be combined. > > Each component partition should be offset at least one cylinder from the > > beginning of the component disk." > > > > see also thread on misc: > > CCD: started on 17 jan 2007 by Chris Mika > > > > > > how much one cylinder is, can be calculated with the numbers given by > > disklabel. ight about the following point but: > > i would not use partition 'a' for anything else then my boot partition. > > thus i never used 'a' as a member of a ccd, nor did i create an 'a' on > > a ccd. > > > > unfortunatly disklabel -E ccd0 did not work for me after 'fdisk -i ccd0', > > since 'ccd0c' had type '4.2BSD' not 'unused' as for raw devices. since > > the > > What version of OpenBSD are you using? On -current ccd0c should no > longer appear as 4.2BSD. 4.0 > Ken > > > FAQ sais: > > "Just use disklabel on it like you normally would to make the partition > > or partitions you want to use. Again, don't use the 'c' partition as an > > actual partition that you put stuff on." > > i used 'disklabel -e ccd0' to change the type to 'unused'. after that i > > created one big partition 'd' on the ccd0 drive. > > > > //llx > > > > > I read through the mailing list archives and found a thread explaining > > > that the disklabel is stored around the beginning of partition 'a' and > > > that one should allocate a small partition 'a' which should not be made > > > part of the JBOD. > > > > > > What I am uncomfortable with is that > > > > > > 1) this does not appear to be documented in the man pages anywhere > > > > > > 2) that the size and position of the disklabel of partition 'a' is not > > > clearly stated anywhere so that I can be certain that it doesn't get > > > overwritten and that I am not wasting too much space. > > > > > > Can anybody please shed some light on this? > > > > > > Regards, > > > -pu
Re: ccd, disklabel and partition 'a'
On Sunday 28 January 2007 17:47, Patrick Useldinger wrote: > christian widmer wrote: > > man ccd: > > "Note that the `raw' partitions of the disks should not be combined. > > Each component partition should be offset at least one cylinder from the > > beginning of the component disk." > > What is a "raw" partition in that case? In the examples I found, the > members of the ccd disk were always wdxy such as wd1a, wd1b, which is > exactly what I did. the 'raw' partition of /dev/wd1d is /dev/rwd1d > > see also thread on misc: > > CCD: started on 17 jan 2007 by Chris Mika > > I did. But in that thread it doesn't become clear how much space to skip. but i did mention it in my first reply. 1. man page sais 'one cylinder' 2. you need to look at the output of disklabel o calculate how much this is. > > i used 'disklabel -e ccd0' to change the type to 'unused'. after that i > > created one big partition 'd' on the ccd0 drive. > > Does the name really matter? Whether your partition is called 'a' or > 'd', doesn't the disklabel get stored into the beginning of the first > partition anyway? the name at least matters sometimes. as a said i'm not sure if it matters in your case - i did not read the code. but the `a' partition of the boot disk is the root partition, and the `b' partition of the boot disk is the swap partition and the 'c' partition is the whole drive. this does not say it is not possible to use 'a' on wd1 as long a it is not your boot disk. never the less i never play with the a, b, c's where not explicitly required. //llx > > -pu
error while building jdk1.5 from ports
building jdk15 with:
env FLAVOR="native_bootstrap" make package
terminates with:
xOperatingSystem_md.c: In function
`Java_com_sun_management_UnixOperatingSystem_getTotalPhysicalMemorySize':
../../../src/solaris/native/com/sun/management/UnixOperatingSystem_md.c:287:
having a lock at line 287 in the given file show that the 4. argument is a
int*. the man page of sysctl shows it should be a size_t*. grepping in the
/usr/includes shows that size_t is a unsinged long.
dmesg:
OpenBSD 4.0 (GENERIC.MP) #936: Sat Sep 16 19:27:28 MDT 2006
[EMAIL PROTECTED]:/usr/src/sys/arch/i386/compile/GENERIC.MP
cpu0: Intel Pentium III ("GenuineIntel" 686-class) 1.01 GHz
cpu0:
FPU,V86,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,MMX,FXSR,SSE
real mem = 1073295360 (1048140K)
avail mem = 970997760 (948240K)
using 4256 buffers containing 53768192 bytes (52508K) of memory
mainbus0 (root)
bios0 at mainbus0: AT/286+(95) BIOS, date 06/18/02, BIOS32 rev. 0 @ 0xf0b20,
SMBIOS rev. 2.3 @ 0xf2ab0 (49 entries)
bios0: ASUSTeK Computer INC. CUV4X-D
apm at bios0 function 0x15 not configured
pcibios0 at bios0: rev 2.1 @ 0xf/0x1362
pcibios0: PCI IRQ Routing Table rev 1.0 @ 0xf12d0/144 (7 entries)
pcibios0: PCI Interrupt Router at 000:04:0 ("VIA VT82C586 ISA" rev 0x00)
pcibios0: PCI bus #1 is the last bus
bios0: ROM list: 0xc/0xd000
mainbus0: Intel MP Specification (Version 1.4) (OEM0 PROD)
cpu0 at mainbus0: apid 3 (boot processor)
cpu0: apic clock running at 133 MHz
cpu1 at mainbus0: apid 0 (application processor)
cpu1: Intel Pentium III ("GenuineIntel" 686-class) 1.01 GHz
cpu1:
FPU,V86,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,MMX,FXSR,SSE
mainbus0: bus 0 is type PCI
mainbus0: bus 1 is type PCI
mainbus0: bus 2 is type ISA
ioapic0 at mainbus0: apid 2 pa 0xfec0, version 11, 24 pins
ioapic0: conflicting map entries for pin 0
pci0 at mainbus0 bus 0: configuration mode 1 (no bios)
pchb0 at pci0 dev 0 function 0 "VIA VT82C691 PCI" rev 0xc4
ppb0 at pci0 dev 1 function 0 "VIA VT82C598 AGP" rev 0x00
pci1 at ppb0 bus 1
vga1 at pci1 dev 0 function 0 "ATI Radeon 9500 Pro" rev 0x00
wsdisplay0 at vga1 mux 1: console (80x25, vt100 emulation)
wsdisplay0: screen 1-5 added (80x25, vt100 emulation)
vendor "ATI", unknown product 0x4e65 (class display subclass miscellaneous,
rev 0x00) at pci1 dev 0 function 1 not configured
pcib0 at pci0 dev 4 function 0 "VIA VT82C686 ISA" rev 0x40
pciide0 at pci0 dev 4 function 1 "VIA VT82C571 IDE" rev 0x06: ATA100, channel
0 configured to compatibility, channel 1 configured to compatibility
wd0 at pciide0 channel 0 drive 0:
wd0: 16-sector PIO, LBA48, 117800MB, 241254720 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: <, ATAPI CDROM.48X, 130Y> SCSI0 5/cdrom
removable
atapiscsi1 at pciide0 channel 1 drive 1
scsibus1 at atapiscsi1: 2 targets
cd1 at scsibus1 targ 0 lun 0: SCSI0 5/cdrom
removable
cd0(pciide0:1:0): using PIO mode 4, Ultra-DMA mode 2
cd1(pciide0:1:1): using PIO mode 4, DMA mode 2
uhci0 at pci0 dev 4 function 2 "VIA VT83C572 USB" rev 0x16: apic 2 int 18 (irq
5)
usb0 at uhci0: USB revision 1.0
uhub0 at usb0
uhub0: VIA UHCI root hub, rev 1.00/1.00, addr 1
uhub0: 2 ports with 2 removable, self powered
uhci1 at pci0 dev 4 function 3 "VIA VT83C572 USB" rev 0x16: apic 2 int 18 (irq
5)
usb1 at uhci1: USB revision 1.0
uhub1 at usb1
uhub1: VIA UHCI root hub, rev 1.00/1.00, addr 1
uhub1: 2 ports with 2 removable, self powered
viaenv0 at pci0 dev 4 function 4 "VIA VT82C686 SMBus" rev 0x40: HWM disabled
uhci2 at pci0 dev 9 function 0 "VIA VT83C572 USB" rev 0x50: apic 2 int 19 (irq
9)
usb2 at uhci2: USB revision 1.0
uhub2 at usb2
uhub2: VIA UHCI root hub, rev 1.00/1.00, addr 1
uhub2: 2 ports with 2 removable, self powered
uhci3 at pci0 dev 9 function 1 "VIA VT83C572 USB" rev 0x50: apic 2 int 16 (irq
11)
usb3 at uhci3: USB revision 1.0
uhub3 at usb3
uhub3: VIA UHCI root hub, rev 1.00/1.00, addr 1
uhub3: 2 ports with 2 removable, self powered
ehci0 at pci0 dev 9 function 2 "VIA VT6202 USB" rev 0x51: apic 2 int 17 (irq
10)
usb4 at ehci0: USB revision 2.0
uhub4 at usb4
uhub4: VIA EHCI root hub, rev 2.00/1.00, addr 1
uhub4: 4 ports with 4 removable, self powered
skc0 at pci0 dev 10 function 0 "D-Link Systems DGE-530T A1" rev 0x11, Marvell
Yukon (0x1): apic 2 int 18 (irq 5)
sk0 at skc0 port A, address 00:11:95:d7:ab:e4
eephy0 at sk0 phy 0: Marvell 88E1011 Gigabit PHY, rev. 3
eso0 at pci0 dev 11 function 0 "ESS SOLO-1 AudioDrive" rev 0x02: ES1946 rev E,
apic 2 int 17 (irq 10)
audio0 at eso0
opl0 at eso0: model OPL3
midi0 at opl0:
isa0 at pcib0
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
pmsi0 at pckbc0 (aux slot)
pckbc0: using irq 12 for aux slot
wsmouse0 at pmsi0 mux 0
pcppi0 at isa0 port 0x61
midi1 at pcppi0:
spk
apu1d4 loosing network with 6.0-stable
I am loosing network connectivity since i installed 6.0-stable on my apu1d4. Previously with 5.9-stable i haven't noticed any issues. apu1d4 [1] has 3 nics re0 -> wan -> direct connected to nucleus connect -> fiber re1 -> wifi -> direct connected to access point re2 -> lan -> connected to switch What is happening: Shortly after i boot (30sec - 5min) i can't reach the internet anymore - i still can ping my apu1d4 through the lan-interface (re1) and the wifi-interface (re2) - but i cant ping the internet anymore; not from through the lan-interface nor from the apu1d4 itself The system works again for 30sec to 5 min when - I unplug and plug the ethernet cable on re0 - i do 'ifconfig down re0 && dhclient re0' I don't face any problems when I reconfigure the apu1d4 and switch the wifi and wan interface re0 -> wifi -> direct connected to access point re1 -> wan -> direct connected to nucleus connect -> fiber re2 -> lan -> connected to switch Any idea what could possibly be wrong? As mentioned above with 5.9-stable i didn't face any issue. Also does the exact same configuration work fine on a apu2d4 [2] which has intel nics. Some more info on what is configured who - wifi and lan interfaces have static IPs assigned - wan get's its IP via dhcpd - dhcpd-server is running on wifi and lan interface - ubound is running (authoritative DNS server for local network) - httpd, dhcpd and tftpd are running for netboot installations - pf (see rules below) # rcctl ls on apmd check_quotas cron dhcpd ftpproxy httpd ntpd pf pflogd smtpd sndiod sshd syslogd tftpd unbound # dmesg OpenBSD 6.0-stable (GENERIC.MP) #12: Sun Sep 11 21:39:13 SGT 2016 r...@talgo.coreid.ch: /local/build/OpenBSD/6.0/src/sys/arch/amd64/compile/GENERIC.MP RTC BIOS diagnostic error ff real mem = 4246003712 (4049MB) avail mem = 4112846848 (3922MB) mpath0 at root scsibus0 at mpath0: 256 targets mainbus0 at root bios0 at mainbus0: SMBIOS rev. 2.7 @ 0xdf16d820 (7 entries) bios0: vendor coreboot version "4.0" date 09/08/2014 bios0: PC Engines APU acpi0 at bios0: rev 0 acpi0: sleep states S0 S1 S3 S4 S5 acpi0: tables DSDT FACP SPCR HPET APIC HEST SSDT SSDT SSDT acpi0: wakeup devices AGPB(S4) HDMI(S4) PBR4(S4) PBR5(S4) PBR6(S4) PBR7(S4) PE20(S4) PE21(S4) PE22(S4) PE23(S4) PIBR(S4) UOH1(S3) UOH2(S3) UOH3(S3) UOH4(S3) UOH5(S3) [...] acpitimer0 at acpi0: 3579545 Hz, 32 bits acpihpet0 at acpi0: 14318180 Hz acpimadt0 at acpi0 addr 0xfee0: PC-AT compat cpu0 at mainbus0: apid 0 (boot processor) cpu0: AMD G-T40E Processor, 1000.15 MHz cpu0: FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,MMX,FXSR,SSE,SSE2,HTT,SSE3,MWAIT,SSSE3,CX16,POPCNT,NXE,MMXX,FFXSR,PAGE1GB,LONG,LAHF,CMPLEG,SVM,EAPICSP,AMCR8,ABM,SSE4A,MASSE,3DNOWP,IBS,SKINIT,ITSC cpu0: 32KB 64b/line 2-way I-cache, 32KB 64b/line 8-way D-cache, 512KB 64b/line 16-way L2 cache cpu0: 8 4MB entries fully associative cpu0: DTLB 40 4KB entries fully associative, 8 4MB entries fully associative cpu0: smt 0, core 0, package 0 mtrr: Pentium Pro MTRR support, 8 var ranges, 88 fixed ranges cpu0: apic clock running at 200MHz cpu0: mwait min=64, max=64, IBE cpu1 at mainbus0: apid 1 (application processor) cpu1: AMD G-T40E Processor, 1000.00 MHz cpu1: FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,MMX,FXSR,SSE,SSE2,HTT,SSE3,MWAIT,SSSE3,CX16,POPCNT,NXE,MMXX,FFXSR,PAGE1GB,LONG,LAHF,CMPLEG,SVM,EAPICSP,AMCR8,ABM,SSE4A,MASSE,3DNOWP,IBS,SKINIT,ITSC cpu1: 32KB 64b/line 2-way I-cache, 32KB 64b/line 8-way D-cache, 512KB 64b/line 16-way L2 cache cpu1: 8 4MB entries fully associative cpu1: DTLB 40 4KB entries fully associative, 8 4MB entries fully associative cpu1: smt 0, core 1, package 0 ioapic0 at mainbus0: apid 2 pa 0xfec0, version 21, 24 pins acpiprt0 at acpi0: bus -1 (AGPB) acpiprt1 at acpi0: bus -1 (HDMI) acpiprt2 at acpi0: bus 1 (PBR4) acpiprt3 at acpi0: bus 2 (PBR5) acpiprt4 at acpi0: bus 3 (PBR6) acpiprt5 at acpi0: bus -1 (PBR7) acpiprt6 at acpi0: bus 5 (PE20) acpiprt7 at acpi0: bus -1 (PE21) acpiprt8 at acpi0: bus -1 (PE22) acpiprt9 at acpi0: bus -1 (PE23) acpiprt10 at acpi0: bus 0 (PCI0) acpiprt11 at acpi0: bus 4 (PIBR) acpicpu0 at acpi0: C2(0@100 io@0x841), C1(@1 halt!), PSS acpicpu1 at acpi0: C2(0@100 io@0x841), C1(@1 halt!), PSS acpibtn0 at acpi0: PWRB cpu0: 1000 MHz: speeds: 1000 800 MHz pci0 at mainbus0 bus 0 pchb0 at pci0 dev 0 function 0 "AMD AMD64 14h Host" rev 0x00 ppb0 at pci0 dev 4 function 0 "AMD AMD64 14h PCIE" rev 0x00: msi pci1 at ppb0 bus 1 re0 at pci1 dev 0 function 0 "Realtek 8168" rev 0x06: RTL8168E/8111E (0x2c00), msi, address 00:0d:b9:3e:b9:34 rgephy0 at re0 phy 7: RTL8169S/8110S/8211 PHY, rev. 4 ppb1 at pci0 dev 5 function 0 "AMD AMD64 14h PCIE" rev 0x00: msi pci2 at ppb1 bus 2 re1 at pci2 dev 0 function 0 "Realtek 8168" rev 0x06: RTL8168E/8111E (0x2c00), msi, address 00:0d:b9:3e:b9:35 rgephy1 at re1 phy 7: RTL8169S/8110S/8211 PHY, rev. 4 ppb2 at pci0 dev 6 function 0 "AMD AMD64 14h PCIE" rev 0x00: msi pci3 at ppb2 bu
apu1d4 loosing network with 6.0-stable
I am loosing network connectivity since i installed 6.0-stable on my apu1d4. Previously with 5.9-stable i haven't noticed any issues. apu1d4 [1] has 3 nics re0 -> wan -> direct connected to nucleus connect -> fiber re1 -> wifi -> direct connected to access point re2 -> lan -> connected to switch What is happening: Shortly after i boot (30sec - 5min) i can't reach the internet anymore - i still can ping my apu1d4 through the lan-interface (re1) and the wifi-interface (re2) - but i cant ping the internet anymore; not from through the lan-interface nor from the apu1d4 itself The system works again for 30sec to 5 min when - I unplug and plug the ethernet cable on re0 - i do 'ifconfig down re0 && dhclient re0' I don't face any problems when I reconfigure the apu1d4 and switch the wifi and wan interface re0 -> wifi -> direct connected to access point re1 -> wan -> direct connected to nucleus connect -> fiber re2 -> lan -> connected to switch Any idea what could possibly be wrong? As mentioned above with 5.9-stable i didn't face any issue. Also does the exact same configuration work fine on a apu2d4 [2] which has intel nics. Some more info on what is configured who - wifi and lan interfaces have static IPs assigned - wan get's its IP via dhcpd - dhcpd-server is running on wifi and lan interface - ubound is running (authoritative DNS server for local network) - httpd, dhcpd and tftpd are running for netboot installations - pf (see rules below) # rcctl ls on apmd check_quotas cron dhcpd ftpproxy httpd ntpd pf pflogd smtpd sndiod sshd syslogd tftpd unbound # dmesg OpenBSD 6.0-stable (GENERIC.MP) #12: Sun Sep 11 21:39:13 SGT 2016 r...@talgo.coreid.ch:/local/build/OpenBSD/6.0/src/sys/ arch/amd64/compile/GENERIC.MP RTC BIOS diagnostic error ff real mem = 4246003712 (4049MB) avail mem = 4112846848 (3922MB) mpath0 at root scsibus0 at mpath0: 256 targets mainbus0 at root bios0 at mainbus0: SMBIOS rev. 2.7 @ 0xdf16d820 (7 entries) bios0: vendor coreboot version "4.0" date 09/08/2014 bios0: PC Engines APU acpi0 at bios0: rev 0 acpi0: sleep states S0 S1 S3 S4 S5 acpi0: tables DSDT FACP SPCR HPET APIC HEST SSDT SSDT SSDT acpi0: wakeup devices AGPB(S4) HDMI(S4) PBR4(S4) PBR5(S4) PBR6(S4) PBR7(S4) PE20(S4) PE21(S4) PE22(S4) PE23(S4) PIBR(S4) UOH1(S3) UOH2(S3) UOH3(S3) UOH4(S3) UOH5(S3) [...] acpitimer0 at acpi0: 3579545 Hz, 32 bits acpihpet0 at acpi0: 14318180 Hz acpimadt0 at acpi0 addr 0xfee0: PC-AT compat cpu0 at mainbus0: apid 0 (boot processor) cpu0: AMD G-T40E Processor, 1000.15 MHz cpu0: FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA, CMOV,PAT,PSE36,CFLUSH,MMX,FXSR,SSE,SSE2,HTT,SSE3,MWAIT, SSSE3,CX16,POPCNT,NXE,MMXX,FFXSR,PAGE1GB,LONG,LAHF, CMPLEG,SVM,EAPICSP,AMCR8,ABM,SSE4A,MASSE,3DNOWP,IBS,SKINIT,ITSC cpu0: 32KB 64b/line 2-way I-cache, 32KB 64b/line 8-way D-cache, 512KB 64b/line 16-way L2 cache cpu0: 8 4MB entries fully associative cpu0: DTLB 40 4KB entries fully associative, 8 4MB entries fully associative cpu0: smt 0, core 0, package 0 mtrr: Pentium Pro MTRR support, 8 var ranges, 88 fixed ranges cpu0: apic clock running at 200MHz cpu0: mwait min=64, max=64, IBE cpu1 at mainbus0: apid 1 (application processor) cpu1: AMD G-T40E Processor, 1000.00 MHz cpu1: FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA, CMOV,PAT,PSE36,CFLUSH,MMX,FXSR,SSE,SSE2,HTT,SSE3,MWAIT, SSSE3,CX16,POPCNT,NXE,MMXX,FFXSR,PAGE1GB,LONG,LAHF, CMPLEG,SVM,EAPICSP,AMCR8,ABM,SSE4A,MASSE,3DNOWP,IBS,SKINIT,ITSC cpu1: 32KB 64b/line 2-way I-cache, 32KB 64b/line 8-way D-cache, 512KB 64b/line 16-way L2 cache cpu1: 8 4MB entries fully associative cpu1: DTLB 40 4KB entries fully associative, 8 4MB entries fully associative cpu1: smt 0, core 1, package 0 ioapic0 at mainbus0: apid 2 pa 0xfec0, version 21, 24 pins acpiprt0 at acpi0: bus -1 (AGPB) acpiprt1 at acpi0: bus -1 (HDMI) acpiprt2 at acpi0: bus 1 (PBR4) acpiprt3 at acpi0: bus 2 (PBR5) acpiprt4 at acpi0: bus 3 (PBR6) acpiprt5 at acpi0: bus -1 (PBR7) acpiprt6 at acpi0: bus 5 (PE20) acpiprt7 at acpi0: bus -1 (PE21) acpiprt8 at acpi0: bus -1 (PE22) acpiprt9 at acpi0: bus -1 (PE23) acpiprt10 at acpi0: bus 0 (PCI0) acpiprt11 at acpi0: bus 4 (PIBR) acpicpu0 at acpi0: C2(0@100 io@0x841), C1(@1 halt!), PSS acpicpu1 at acpi0: C2(0@100 io@0x841), C1(@1 halt!), PSS acpibtn0 at acpi0: PWRB cpu0: 1000 MHz: speeds: 1000 800 MHz pci0 at mainbus0 bus 0 pchb0 at pci0 dev 0 function 0 "AMD AMD64 14h Host" rev 0x00 ppb0 at pci0 dev 4 function 0 "AMD AMD64 14h PCIE" rev 0x00: msi pci1 at ppb0 bus 1 re0 at pci1 dev 0 function 0 "Realtek 8168" rev 0x06: RTL8168E/8111E (0x2c00), msi, address 00:0d:b9:3e:b9:34 rgephy0 at re0 phy 7: RTL8169S/8110S/8211 PHY, rev. 4 ppb1 at pci0 dev 5 function 0 "AMD AMD64 14h PCIE" rev 0x00: msi pci2 at ppb1 bus 2 re1 at pci2 dev 0 function 0 "Realtek 8168" rev 0x06: RTL8168E/8111E (0x2c00), msi, address 00:0d:b9:3e:b9:35 rgephy1 at re1 phy 7: RTL8169S/8110S/8211 PHY, rev. 4 ppb2 at pci0 dev 6 function 0 "AMD AMD64 14h PCIE" rev 0x00: msi pci3 at
Re: system not using second entry in $PKG_PATH
ask yourself why do you use ':' as a separator? you have ':' in you PKG_PATH_LAN1 and PKG_PATH_LAN2. this is by the way the reason why you can't do what you're trying to. On Monday 19 November 2007 14.21:17 Juan Miscaro wrote: > On two OpenBSD 4.2 systems I have a (master) system that contains two > repositories - one of regular packages and one of packages derived from > ports. On the client (slave) system I have a script with a PKG_PATH > containing both repositories: > > PKG_PATH_LAN1=ftp://$MASTER/$VERSION/packages/ > PKG_PATH_LAN2=ftp://$MASTER/$VERSION/packages/by_port/i386/all/ > PKG_PATH=$PKG_PATH_LAN1:$PKG_PATH_LAN2 > > However the second one (PKG_PATH_LAN2) is never consulted. If I remove > the first one then packages are found and installed with no problem. > > Why is this happening? > > // juan > > > > Be smarter than spam. See how smart SpamGuard is at giving junk email > the boot with the All-new Yahoo! Mail. Click on Options in Mail and switch > to New Mail today or register for free at http://mail.yahoo.ca
Re: OpenVPN very high ping times to server
i've got a similar issue with virtual machines running within qemu. i get terribly high ping times as high with huge variation between guest and host. between guest an any other machine in the lan is ok. probably the combination of tun and lo which triggers this behavior? //llx On Saturday 01 December 2007 23.57:47 Bryan S. Leaman wrote: > I have a simple OpenVPN bridge environment set up: > >-[OpenBSD]- > > > > * bridge0 contains tun0 and hme1 > > Connectivity and routing work as expected, but when I ping from the client > to the OpenBSD server, I get terribly high ping times as high as 3000ms > with huge variation. Yet the ping times from the client to a host on the > internal lan are <10ms. Basically any packets going between the VPN > client and the server itself have this problem. Packets passing through > the bridge from client to internal lan are not affected. > > I am using OpenBSD 4.2 on sparc64, and I've tried OpenVPN 2.0.9 and > 2.1rc4. But I also have the same issue on an older 3.8 box with OpenVPN > 2.0.5, also sparc64. > > Because of this problem, using the VPN server also as a default gateway to > the Internet is nearly impossible, as the response times are terrible. > Any idea what is going on? I've only seen one other report of this issue > but there was no solution discussed: > > http://thread.gmane.org/gmane.network.openvpn.user/20541 > > Here are some sample pings: > > C:\temp>ping -t 192.168.222.1 (pinging server from vpn client) > > Pinging 192.168.222.1 with 32 bytes of data: > > Reply from 192.168.222.1: bytes=32 time=140ms TTL=255 > Reply from 192.168.222.1: bytes=32 time=821ms TTL=255 > Reply from 192.168.222.1: bytes=32 time=271ms TTL=255 > Reply from 192.168.222.1: bytes=32 time=648ms TTL=255 > Reply from 192.168.222.1: bytes=32 time=447ms TTL=255 > Reply from 192.168.222.1: bytes=32 time=18ms TTL=255 > Reply from 192.168.222.1: bytes=32 time=45ms TTL=255 > Reply from 192.168.222.1: bytes=32 time=414ms TTL=255 > Reply from 192.168.222.1: bytes=32 time=649ms TTL=255 > Reply from 192.168.222.1: bytes=32 time=1094ms TTL=255 > Reply from 192.168.222.1: bytes=32 time=131ms TTL=255 > Reply from 192.168.222.1: bytes=32 time=91ms TTL=255 > Reply from 192.168.222.1: bytes=32 time=619ms TTL=255 > Reply from 192.168.222.1: bytes=32 time=2154ms TTL=255 > Reply from 192.168.222.1: bytes=32 time=3179ms TTL=255 > Reply from 192.168.222.1: bytes=32 time=2310ms TTL=255 > Reply from 192.168.222.1: bytes=32 time=1147ms TTL=255 > Reply from 192.168.222.1: bytes=32 time=233ms TTL=255 > Reply from 192.168.222.1: bytes=32 time=3030ms TTL=255 > Reply from 192.168.222.1: bytes=32 time=4085ms TTL=255 > Reply from 192.168.222.1: bytes=32 time=1500ms TTL=255 > Reply from 192.168.222.1: bytes=32 time=845ms TTL=255 > Reply from 192.168.222.1: bytes=32 time=64ms TTL=255 > Reply from 192.168.222.1: bytes=32 time=611ms TTL=255 > > Ping statistics for 192.168.222.1: > Packets: Sent = 24, Received = 24, Lost = 0 (0% loss), > Approximate round trip times in milli-seconds: > Minimum = 18ms, Maximum = 4085ms, Average = 1022ms > > C:\temp>ping -t 192.168.222.10 (pinging internal host from vpn client) > > Pinging 192.168.222.10 with 32 bytes of data: > > Reply from 192.168.222.10: bytes=32 time=6ms TTL=254 > Reply from 192.168.222.10: bytes=32 time=3ms TTL=254 > Reply from 192.168.222.10: bytes=32 time=4ms TTL=254 > Reply from 192.168.222.10: bytes=32 time=3ms TTL=254 > Reply from 192.168.222.10: bytes=32 time=9ms TTL=254 > Reply from 192.168.222.10: bytes=32 time=3ms TTL=254 > Reply from 192.168.222.10: bytes=32 time=3ms TTL=254 > Reply from 192.168.222.10: bytes=32 time=4ms TTL=254 > Reply from 192.168.222.10: bytes=32 time=3ms TTL=254 > Reply from 192.168.222.10: bytes=32 time=3ms TTL=254 > Reply from 192.168.222.10: bytes=32 time=3ms TTL=254 > Reply from 192.168.222.10: bytes=32 time=4ms TTL=254 > Reply from 192.168.222.10: bytes=32 time=4ms TTL=254 > Reply from 192.168.222.10: bytes=32 time=3ms TTL=254 > Reply from 192.168.222.10: bytes=32 time=3ms TTL=254 > Reply from 192.168.222.10: bytes=32 time=3ms TTL=254 > Reply from 192.168.222.10: bytes=32 time=5ms TTL=254 > Reply from 192.168.222.10: bytes=32 time=4ms TTL=254 > Reply from 192.168.222.10: bytes=32 time=3ms TTL=254 > > Ping statistics for 192.168.222.10: > Packets: Sent = 19, Received = 19, Lost = 0 (0% loss), > Approximate round trip times in milli-seconds: > Minimum = 3ms, Maximum = 9ms, Average = 3ms > > Bryan
