Re: Blocking facebook.com: PF or squid?
On 10/18/13 18:27, Stefan Wollny wrote: Hi there, having a personal dislike of Facebook (and the MeeToo-systems alike) for their impertinent sniffing for private data I tried on my laptop to block facebook.com via hosts-file. Interestingly this failed: Calling "http://www.facebook.com"; always resulted in a lookup for "httpS://www.facebook.com" and the respective site showed up in the browser (tried firefox and xombrero). Well: Beside excepting the fact that those facebook engineers did a fine job circumventing the entrys in /etc/hosts I felt immediatly insecure: The reports on this company's attitude towards even non-customers privacy are legendary. Their respective track record earns them the honorable title of "NSA's fittest supporter"... Anyway: I think I finally managed to block all their IPs via PF and on this laptop I now feel a little less 'observed'. [Yes, I know - this is just today's snapshot of IPs!] My question is on the squid-server I have running at home: What would make more sense - blocking facebook.com via pf.conf alike or are there reasons to use squid's ACL instead? Performance? Being ultra-paranoid and implementing both (or even additionally the hosts-file-block?)? From my understanding squid should not be able to block https-traffic as it is encrypted - or am I wrong here? Curious if there is a particular (Open)BSD solution or simply how you 'guys and gals' would do it. Thank you for sharing your thoughts. Cheers, STEFAN If you're handling DHCP for all of the traffic for your site, why not just set up a dns server, point your dhcp clients to this DNS server and create an authoritative zone for facebook.com that points to somewhere other than facebook? That's traditionally how I block traffic from our network from our users trying to go to places other than where I wish them to. The more savvy users could get around this altering their dns servers manually which you can stop blocking DNS traffic out of your network, this has the added bonus of cutting down bandwidth out of your network. If they get really sneaky and try to put host entries in for facebook, you can do as you've been doing, blocking IPs, and maybe creat a script that does an hourly lookup of all facebook IPs and having it update your pf config and then reloading pf. Aaron
Re: Best OpenBSD cloud hosting?
On 10/08/13 21:16, openda...@hushmail.com wrote: Hi, Can anyone recommend a decent OpenBSD cloud hosting provider? Digital Ocean looks nice but they don't yet offer OpenBSD (https://digitalocean.uservoice.com/forums/136585-digital-ocean/suggestions/3232571-support-bsd-os-). There's ARP Networks and TransIP but they don't offer clouds. Thanks. O.D. Hi O.D. Although I haven't tried spinning up a BSD machine, terramark has an option to spin up a "blank server", essentially it's supposed to emulate a hardware system with no os. You can then attach a cd (which can be an iso), reboot the system and boot from OpenBSD media. You might give that a look. Aaron
MBR Mishap!
Hi All, I have a system with a sata disk or the OS and a areca pcie raid card with 4 1.5 Tb drives in a raid5 configuration. The raid has data on it and the OS drive was blank. I was doing a fresh install on the OS, unfortuntately I forgot that the OpenBSD install sees the OS drive as sd1. I chose sd0 and got some message, wasn't on a console so didn't capture it, about drive too large for fdisk. I went on and then saw the number of sectors and realized immediately I chose the wrong disk. I did a control+C, rebooted and then installed on the sd1 drive. Now that i'm back in the OS I went to mount the raid and got a device not configured message for /dev/sd0a. I did a disklable -E sd0 and to my horror there is no a partition left on the raid. :-( Is there any way to get this back? Can I simply use disklable to use all space on the drive to recreate the mbr and my data will be available? I'm desperate, ANY help will be GREATLY appreciated. Thanks in advance, Aaron # dmesg OpenBSD 5.4 (GENERIC.MP) #41: Tue Jul 30 15:30:02 MDT 2013 dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP real mem = 2129526784 (2030MB) avail mem = 2065170432 (1969MB) mainbus0 at root bios0 at mainbus0: SMBIOS rev. 2.51 @ 0x7feeb000 (33 entries) bios0: vendor Phoenix Technologies LTD version "6.00" date 12/29/2010 bios0: Supermicro PDSM4+ acpi0 at bios0: rev 0 acpi0: sleep states S0 S1 S4 S5 acpi0: tables DSDT FACP MCFG APIC BOOT SSDT SSDT SSDT SSDT SSDT SSDT SSDT SSDT SSDT acpi0: wakeup devices PXHA(S5) PXHB(S5) DEV3(S5) EXP1(S5) EXP5(S5) EXP6(S5) PCIB(S5) KBC0(S1) MSE0(S1) COM1(S5) COM2(S5) USB1(S4) USB2(S4) USB3(S4) USB4(S4) EUSB(S4) acpitimer0 at acpi0: 3579545 Hz, 24 bits acpimcfg0 at acpi0 addr 0xf000, bus 0-19 acpimadt0 at acpi0 addr 0xfee0: PC-AT compat cpu0 at mainbus0: apid 0 (boot processor) cpu0: Intel(R) Xeon(R) CPU 3060 @ 2.40GHz, 2400.10 MHz cpu0: FPU,VME,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,PBE,SSE3,DTES64,MWAIT,DS-CPL,VMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,NXE,LONG,LAHF,PERF cpu0: 4MB 64b/line 16-way L2 cache cpu0: smt 0, core 0, package 0 cpu0: apic clock running at 266MHz cpu1 at mainbus0: apid 1 (application processor) cpu1: Intel(R) Xeon(R) CPU 3060 @ 2.40GHz, 2399.74 MHz cpu1: FPU,VME,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,PBE,SSE3,DTES64,MWAIT,DS-CPL,VMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,NXE,LONG,LAHF,PERF cpu1: 4MB 64b/line 16-way L2 cache cpu1: smt 0, core 1, package 0 ioapic0 at mainbus0: apid 2 pa 0xfec0, version 20, 24 pins ioapic1 at mainbus0: apid 3 pa 0xfecc, version 20, 24 pins ioapic2 at mainbus0: apid 4 pa 0xfecc0400, version 20, 24 pins acpiprt0 at acpi0: bus 0 (PCI0) acpiprt1 at acpi0: bus 2 (PXHA) acpiprt2 at acpi0: bus 3 (PXHB) acpiprt3 at acpi0: bus 10 (DEV3) acpiprt4 at acpi0: bus 14 (EXP1) acpiprt5 at acpi0: bus 18 (EXP5) acpiprt6 at acpi0: bus 19 (EXP6) acpiprt7 at acpi0: bus 20 (PCIB) acpicpu0 at acpi0 acpicpu1 at acpi0 acpibtn0 at acpi0: PWRB ipmi at mainbus0 not configured pci0 at mainbus0 bus 0 pchb0 at pci0 dev 0 function 0 "Intel E7230 Host" rev 0xc0 ppb0 at pci0 dev 1 function 0 "Intel E7230 PCIE" rev 0xc0: msi pci1 at ppb0 bus 1 ppb1 at pci1 dev 0 function 0 "Intel 6700PXH PCIE-PCIX" rev 0x09 pci2 at ppb1 bus 2 "Intel IOxAPIC" rev 0x09 at pci1 dev 0 function 1 not configured ppb2 at pci1 dev 0 function 2 "Intel 6700PXH PCIE-PCIX" rev 0x09 pci3 at ppb2 bus 3 "Intel IOxAPIC" rev 0x09 at pci1 dev 0 function 3 not configured ppb3 at pci0 dev 3 function 0 "Intel 82975X PCIE" rev 0xc0: msi pci4 at ppb3 bus 10 ppb4 at pci4 dev 0 function 0 "Intel IOP332 PCIE-PCIX" rev 0x07 pci5 at ppb4 bus 11 arc0 at pci5 dev 14 function 0 "Areca ARC-1210" rev 0x00: apic 2 int 18 arc0: 4 ports, 256MB SDRAM, firmware V1.47 2009-07-02 scsibus0 at arc0: 16 targets sd0 at scsibus0 targ 0 lun 0: SCSI3 0/direct fixed eui.0004d927f800 sd0: 4291533MB, 512 bytes/sector, 8789061120 sectors ppb5 at pci4 dev 0 function 2 "Intel IOP332 PCIE-PCIX" rev 0x07 pci6 at ppb5 bus 12 ppb6 at pci0 dev 28 function 0 "Intel 82801GB PCIE" rev 0x01: msi pci7 at ppb6 bus 14 ppb7 at pci0 dev 28 function 4 "Intel 82801G PCIE" rev 0x01: msi pci8 at ppb7 bus 18 em0 at pci8 dev 0 function 0 "Intel 82573E" rev 0x03: msi, address 00:30:48:8c:4e:80 ppb8 at pci0 dev 28 function 5 "Intel 82801G PCIE" rev 0x01: msi pci9 at ppb8 bus 19 em1 at pci9 dev 0 function 0 "Intel 82573L" rev 0x00: msi, address 00:30:48:8c:4e:81 uhci0 at pci0 dev 29 function 0 "Intel 82801GB USB" rev 0x01: apic 2 int 23 uhci1 at pci0 dev 29 function 1 "Intel 82801GB USB" rev 0x01: apic 2 int 19 uhci2 at pci0 dev 29 function 2 "Intel 82801GB USB" rev 0x01: apic 2 int 18 uhci3 at pci0 dev 29 function 3 "Intel 82801GB USB" rev 0x01: apic 2 int 16 ehci0 at pci0 dev 29 function 7 "Intel 82801GB USB" rev 0x01: apic 2 int 23 usb0 at ehci0: USB revision 2.0 uhub0 at usb0 "Inte
Re: MBR Mishap!
On 11/02/13 22:35, Nick Holland wrote: On 11/02/13 14:18, mia wrote: Hi All, I have a system with a sata disk or the OS and a areca pcie raid card with 4 1.5 Tb drives in a raid5 configuration. The raid has data on it and the OS drive was blank. I was doing a fresh install on the OS, unfortuntately I forgot that the OpenBSD install sees the OS drive as sd1. I chose sd0 and got some message, wasn't on a console so didn't capture it, about drive too large for fdisk. I went on and then saw the number of sectors and realized immediately I chose the wrong disk. I did a control+C, rebooted and then installed on the sd1 drive. Now that i'm back in the OS I went to mount the raid and got a device not configured message for /dev/sd0a. I did a disklable -E sd0 and to my horror there is no a partition left on the raid. :-( Is there any way to get this back? Can I simply use disklable to use all space on the drive to recreate the mbr and my data will be available? I'm desperate, ANY help will be GREATLY appreciated. ok, if I followed this, you changed the MBR with fdisk -- AND NOTHING ELSE. IF that's true...and you know what and where partitions were, yes, you are in not bad shape. I'd start by using fdisk to recreate the OpenBSD partition as it was (hopefully, whole disk. probably starting at either sector 64 (if "newer") or sector 63 (if "older"). Do that, reboot (I'm not sure that's needed, but it prolongs the suspense), and you should see your disklabel partitions just come back from the not-quite-dead. If you aren't sure about your starting partition, try both 64 and 63, see which one brings back your disklabel. A few more tips here: http://www.openbsd.org/faq/faq14.html#OhBugger Good luck. Nick. Hi Nick, Thanks for the reply, I didn't directly use fdisk. This was part of a fresh install of 5.4. I chose the wrong disk, fdisk looked at the drive, complained about it being too big, I hit enter and then did a ctrl+c to get out before it did any damage/write (i thought). I'm guessing when it warned about the partition being too big and I hit enter, it did something that wiped my mbr at that point. The partition was originally W (WHOLE DISK), yes, with a single partition. This raid drive was just for data and usually mounted ro unless I need to add something. The old system was 5.3, so it is newer (weird that current does 63 on my ssd). So if i'm following you, I should use fdisk and not use disklable at all? I thought I'd go into disklable -E do an "a a" with no newfs afterward and I should be able to just do a "mount /dev/sd0a /mnt/point" (I'm glad i didn't proceed.) I'm really hoping to not lose this data.. mostly centimental stuff that I can't replace. Thanks again, Aaron Thanks in advance, Aaron # dmesg OpenBSD 5.4 (GENERIC.MP) #41: Tue Jul 30 15:30:02 MDT 2013 dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP real mem = 2129526784 (2030MB) avail mem = 2065170432 (1969MB) mainbus0 at root bios0 at mainbus0: SMBIOS rev. 2.51 @ 0x7feeb000 (33 entries) bios0: vendor Phoenix Technologies LTD version "6.00" date 12/29/2010 bios0: Supermicro PDSM4+ acpi0 at bios0: rev 0 acpi0: sleep states S0 S1 S4 S5 acpi0: tables DSDT FACP MCFG APIC BOOT SSDT SSDT SSDT SSDT SSDT SSDT SSDT SSDT SSDT acpi0: wakeup devices PXHA(S5) PXHB(S5) DEV3(S5) EXP1(S5) EXP5(S5) EXP6(S5) PCIB(S5) KBC0(S1) MSE0(S1) COM1(S5) COM2(S5) USB1(S4) USB2(S4) USB3(S4) USB4(S4) EUSB(S4) acpitimer0 at acpi0: 3579545 Hz, 24 bits acpimcfg0 at acpi0 addr 0xf000, bus 0-19 acpimadt0 at acpi0 addr 0xfee0: PC-AT compat cpu0 at mainbus0: apid 0 (boot processor) cpu0: Intel(R) Xeon(R) CPU 3060 @ 2.40GHz, 2400.10 MHz cpu0: FPU,VME,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,PBE,SSE3,DTES64,MWAIT,DS-CPL,VMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,NXE,LONG,LAHF,PERF cpu0: 4MB 64b/line 16-way L2 cache cpu0: smt 0, core 0, package 0 cpu0: apic clock running at 266MHz cpu1 at mainbus0: apid 1 (application processor) cpu1: Intel(R) Xeon(R) CPU 3060 @ 2.40GHz, 2399.74 MHz cpu1: FPU,VME,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,PBE,SSE3,DTES64,MWAIT,DS-CPL,VMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,NXE,LONG,LAHF,PERF cpu1: 4MB 64b/line 16-way L2 cache cpu1: smt 0, core 1, package 0 ioapic0 at mainbus0: apid 2 pa 0xfec0, version 20, 24 pins ioapic1 at mainbus0: apid 3 pa 0xfecc, version 20, 24 pins ioapic2 at mainbus0: apid 4 pa 0xfecc0400, version 20, 24 pins acpiprt0 at acpi0: bus 0 (PCI0) acpiprt1 at acpi0: bus 2 (PXHA) acpiprt2 at acpi0: bus 3 (PXHB) acpiprt3 at acpi0: bus 10 (DEV3) acpiprt4 at acpi0: bus 14 (EXP1) acpiprt5 at acpi0: bus 18 (EXP5) acpiprt6 at acpi0: bus 19 (EXP6) acpiprt7 at acpi0: bus 20 (PCIB) acpicpu0 at acpi0 acpic
Re: MBR Mishap!
On 11/03/13 10:35, Nick Holland wrote: On 11/02/13 20:38, mia wrote: On 11/02/13 22:35, Nick Holland wrote: On 11/02/13 14:18, mia wrote: Hi All, I have a system with a sata disk or the OS and a areca pcie raid card with 4 1.5 Tb drives in a raid5 configuration. The raid has data on it and the OS drive was blank. I was doing a fresh install on the OS, unfortuntately I forgot that the OpenBSD install sees the OS drive as sd1. I chose sd0 and got some message, wasn't on a console so didn't capture it, about drive too large for fdisk. I went on and then saw the number of sectors and realized immediately I chose the wrong disk. I did a control+C, rebooted and then installed on the sd1 drive. Now that i'm back in the OS I went to mount the raid and got a device not configured message for /dev/sd0a. I did a disklable -E sd0 and to my horror there is no a partition left on the raid. :-( Is there any way to get this back? Can I simply use disklable to use all space on the drive to recreate the mbr and my data will be available? I'm desperate, ANY help will be GREATLY appreciated. ok, if I followed this, you changed the MBR with fdisk -- AND NOTHING ELSE. IF that's true...and you know what and where partitions were, yes, you are in not bad shape. I'd start by using fdisk to recreate the OpenBSD partition as it was (hopefully, whole disk. probably starting at either sector 64 (if "newer") or sector 63 (if "older"). Do that, reboot (I'm not sure that's needed, but it prolongs the suspense), and you should see your disklabel partitions just come back from the not-quite-dead. If you aren't sure about your starting partition, try both 64 and 63, see which one brings back your disklabel. A few more tips here: http://www.openbsd.org/faq/faq14.html#OhBugger Good luck. Nick. Hi Nick, Thanks for the reply, I didn't directly use fdisk. This was part of a fresh install of 5.4. I chose the wrong disk, fdisk looked at the drive, complained about it being too big, I hit enter and then did a ctrl+c to get out before it did any damage/write (i thought). I'm guessing when it warned about the partition being too big and I hit enter, it did something that wiped my mbr at that point. The partition was originally W (WHOLE DISK), yes, with a single partition. This raid drive was just for data and usually mounted ro unless I need to add something. The old system was 5.3, so it is newer (weird that current does 63 on my ssd). So if i'm following you, I should use fdisk and not use disklable at all? I thought I'd go into disklable -E do an "a a" with no newfs afterward and I should be able to just do a "mount /dev/sd0a /mnt/point" (I'm glad i didn't proceed.) I'm really hoping to not lose this data.. mostly centimental stuff that I can't replace. Thanks again, Aaron definitely start with fdisk, NOT disklabel. The hope is that by defining a proper MBR, you will end up with your (untouched) disklabel "just appearing" where OpenBSD expects it to be. Nick. Hi Nick, Thanks, I'm not sure what I would do with fdisk, it appears as though it's how it should be. # fdisk sd0 fdisk: disk too large (8789061120 sectors). size truncated. Disk: sd0 geometry: 267349/255/63 [4294961685 Sectors] Offset: 0 Signature: 0xAA55 Starting Ending LBA Info: #: id C H S - C H S [ start:size ] --- 0: 00 0 0 0 - 0 0 0 [ 0: 0 ] unused 1: 00 0 0 0 - 0 0 0 [ 0: 0 ] unused 2: 00 0 0 0 - 0 0 0 [ 0: 0 ] unused *3: A6 0 1 2 - 267348 254 63 [ 64: 4294961621 ] OpenBSD # disklabel sd0 # /dev/rsd0c: type: SCSI disk: SCSI disk label: ARC-1210-VOL#00 duid: flags: bytes/sector: 512 sectors/track: 63 tracks/cylinder: 255 sectors/cylinder: 16065 cylinders: 547093 total sectors: 8789061120 boundstart: 64 boundend: 4294961685 drivedata: 0 16 partitions: #size offset fstype [fsize bsize cpg] c: 87890611200 unused I have the backup for the old disklable and it looks like this: # cat disklabel.sd0.current # /dev/rsd0c: type: SCSI disk: SCSI disk label: ARC-1210-VOL duid: b040b4952bec09ff flags: bytes/sector: 512 sectors/track: 63 tracks/cylinder: 255 sectors/cylinder: 16065 cylinders: 547093 total sectors: 8789061120 boundstart: 512 boundend: 199019008 drivedata: 0 16 partitions: #size offset fstype [fsize bsize cpg] a: 8789060608 512 4.2BSD 8192 655361 c: 87890611200 unused I ran scan_ffs as the link you provided suggested and got the following: # scan_ffs sd0 ff
Re: MBR Mishap!
On 11/05/13 08:41, Kenneth R Westerback wrote: On Mon, Nov 04, 2013 at 06:12:15PM -0500, mia wrote: On 11/03/13 10:35, Nick Holland wrote: On 11/02/13 20:38, mia wrote: On 11/02/13 22:35, Nick Holland wrote: On 11/02/13 14:18, mia wrote: Hi All, I have a system with a sata disk or the OS and a areca pcie raid card with 4 1.5 Tb drives in a raid5 configuration. The raid has data on it and the OS drive was blank. I was doing a fresh install on the OS, unfortuntately I forgot that the OpenBSD install sees the OS drive as sd1. I chose sd0 and got some message, wasn't on a console so didn't capture it, about drive too large for fdisk. I went on and then saw the number of sectors and realized immediately I chose the wrong disk. I did a control+C, rebooted and then installed on the sd1 drive. Now that i'm back in the OS I went to mount the raid and got a device not configured message for /dev/sd0a. I did a disklable -E sd0 and to my horror there is no a partition left on the raid. :-( Is there any way to get this back? Can I simply use disklable to use all space on the drive to recreate the mbr and my data will be available? I'm desperate, ANY help will be GREATLY appreciated. ok, if I followed this, you changed the MBR with fdisk -- AND NOTHING ELSE. IF that's true...and you know what and where partitions were, yes, you are in not bad shape. I'd start by using fdisk to recreate the OpenBSD partition as it was (hopefully, whole disk. probably starting at either sector 64 (if "newer") or sector 63 (if "older"). Do that, reboot (I'm not sure that's needed, but it prolongs the suspense), and you should see your disklabel partitions just come back from the not-quite-dead. If you aren't sure about your starting partition, try both 64 and 63, see which one brings back your disklabel. A few more tips here: http://www.openbsd.org/faq/faq14.html#OhBugger Good luck. Nick. Hi Nick, Thanks for the reply, I didn't directly use fdisk. This was part of a fresh install of 5.4. I chose the wrong disk, fdisk looked at the drive, complained about it being too big, I hit enter and then did a ctrl+c to get out before it did any damage/write (i thought). I'm guessing when it warned about the partition being too big and I hit enter, it did something that wiped my mbr at that point. The partition was originally W (WHOLE DISK), yes, with a single partition. This raid drive was just for data and usually mounted ro unless I need to add something. The old system was 5.3, so it is newer (weird that current does 63 on my ssd). So if i'm following you, I should use fdisk and not use disklable at all? I thought I'd go into disklable -E do an "a a" with no newfs afterward and I should be able to just do a "mount /dev/sd0a /mnt/point" (I'm glad i didn't proceed.) I'm really hoping to not lose this data.. mostly centimental stuff that I can't replace. Thanks again, Aaron definitely start with fdisk, NOT disklabel. The hope is that by defining a proper MBR, you will end up with your (untouched) disklabel "just appearing" where OpenBSD expects it to be. Nick. Hi Nick, Thanks, I'm not sure what I would do with fdisk, it appears as though it's how it should be. # fdisk sd0 fdisk: disk too large (8789061120 sectors). size truncated. Disk: sd0 geometry: 267349/255/63 [4294961685 Sectors] Offset: 0 Signature: 0xAA55 Starting Ending LBA Info: #: id C H S - C H S [ start:size ] --- 0: 00 0 0 0 - 0 0 0 [ 0: 0 ] unused 1: 00 0 0 0 - 0 0 0 [ 0: 0 ] unused 2: 00 0 0 0 - 0 0 0 [ 0: 0 ] unused *3: A6 0 1 2 - 267348 254 63 [ 64: 4294961621 ] OpenBSD # disklabel sd0 # /dev/rsd0c: type: SCSI disk: SCSI disk label: ARC-1210-VOL#00 duid: flags: bytes/sector: 512 sectors/track: 63 tracks/cylinder: 255 sectors/cylinder: 16065 cylinders: 547093 total sectors: 8789061120 boundstart: 64 boundend: 4294961685 drivedata: 0 16 partitions: #size offset fstype [fsize bsize cpg] c: 87890611200 unused I have the backup for the old disklable and it looks like this: # cat disklabel.sd0.current # /dev/rsd0c: type: SCSI disk: SCSI disk label: ARC-1210-VOL duid: b040b4952bec09ff flags: bytes/sector: 512 sectors/track: 63 tracks/cylinder: 255 sectors/cylinder: 16065 cylinders: 547093 total sectors: 8789061120 boundstart: 512 boundend: 199019008 drivedata: 0 16 partitions: #size offset fstype [fsize bsize cpg] a: 8789060608 512 4.2BSD 8192 655361 c: 8789061120
Re: Recommended laptop
On 12/17/13 16:57, Gabriel Marchi wrote: Hi there, I'm looking for an laptop that everything supported and compatible with OpenBSD 5.4 straight out of the box (graphics/sound, wireless card, etc.) Is a good choice ? Lenovo G400S http://shopap.lenovo.com/my/en/laptops/essential/g-series/g400s/#features Thanks I have had really good luck with my lenovo w530. I have the nvidia k2000m card but when using OBSD I switch the video in the bios as it also has intel 4000. You still can't do a dual head setup connecting to the vga or mDP (I think you can however if you have a docking station). wireless works flawlessly, usb3 worked in current but isn't in 5.4, sound is fine. Battery life isn't great but I haven't tried playing with anything to improve it. Aaron
Re: Bizarre pf/sendmail interaction
On 12/17/13 21:11, Tethys wrote: On Tue, Dec 17, 2013 at 7:51 PM, Jan Stary wrote: block in log block out log on $ext How could anyone help you knowing just these two lines? Show your pf.conf I was trying to show that I only had two block lines and that they both should log when blocking packets. My rules are actually very simple: match out on $ext from $int_ip to any nat-to $loki_ext block in log block out log on $ext pass in quick on $int flags any pass out on $ext from $lokisafe pass in on $ext inet proto tcp to port 4334 rdr-to 127.0.0.1 port ssh pass in on $ext inet proto tcp from $mx to $loki_ext port smtp rdr-to $riva port smtp flags any pass out on $int inet proto tcp from $mx port smtp flags any $int and $ext are interfaces on the firewall (loki). $loki_ext is the external IP, $int_ip is the internal /24. $lokisafe is a selection of /24s that I've sometimes used, including the internal network. $riva is my home mail server. $mx is the IP addresses of my hosted MX servers. With tcpdump, I can see the response to the EHLO greeting leaving riva, arriving on $int, but never making it to $ext. Using HELO instead doesn't prompt the same behaviour. Tet this shouldn't be this hard.. can we see output from "netstat -rnf inet", "pfctl -vvsr", maybe output from dmesg? You never indicated what MX server you're running. postfix, actual sendmail, opensmtpd... ?? Your config from the smtp server would be helpful as well. The fact that you're getting different responses from HELO and EHLO would indicate that something odd is going on with your MX server but the fact that you get one reply from ping and no more would indicate something else. A
