Magistral Curso de "Como Pagar y Motivar a la Fuerza de Ventas"
¡Muy Importante! Si no puede visualizar correctamente este correo, le pedimos que lo arrastre a su Bandeja de Entrada Apreciable Ejecutivo: TIEM de México Empresa LÃder en Capacitación y Actualización de Capital Humano Pone a su disposición este Excelente Curso denominado: "Como Pagar y Motivar a la Fuerza de Ventas" Está Programado para el dÃa: 24 de Julio de 2012 en la Ciudad de México InscrÃbase 5 dÃas antes de la fecha del Curso y obtenga un descuento del 15% con Inversión Inmediata No deje pasar esta oportunidad e Invierta en su Desarrollo Personal y Profesional Corren tiempos difÃciles para los equipos de venta. El desequilibrio entre la oferta y la demanda, hacen que sea cada vez más necesario Âmarcar la diferenciaÂ, lo cual resulta indispensable, tanto para conseguir clientes potenciales como para proporcionarles buenas razones para que permanezcan fieles a nuestra empresa. Cuando los productos y los servicios son similares, los clientes más codiciados (y por tanto, los más solicitados) son muy sensibles a los detalles que diferencian a una oferta de otra. ¿Qué es lo que permite marcar la diferencia a un vendedor, hoy en dÃa, delante de un cliente? En primer lugar el estado de ánimo, dato subjetivo y difÃcilmente apreciable que no está suficientemente valorado en la evaluación de los factores de éxito de una empresa y que depende principalmente de la motivación. Objetivo General del Curso: Proporcionar a los participantes una visión integral y actual para evaluar y/o diseñar un esquema de pago a vendedores, a través de evaluar los diferentes modelos de pago, con el fin de instrumentar un esquema que motive al equipo de ventas y permita alcanzar los objetivos de venta establecidos. Beneficios: Revisar diferentes modelos, evaluando pros y contras de cada uno Ponderar las tendencias actuales en materia de pago a vendedores Definir programas de motivación, fundamentadas en incentivos no económicos Alinear los objetivos y situación de la empresa, definiendo polÃticas para el manejo de la compensación para el equipo comercial Si al momento de recibir este correo ya realizo su confirmación le pedimos haga caso omiso. De lo contrario, favor de responder este correo con los siguientes datos:  Empresa:  Nombre:  Ciudad:  Teléfono: O si lo prefiere comunÃquese a los teléfonos: Del DF al 5611-0969 con 10 lÃneas Interior del PaÃs Lada sin Costo 01 800 900 TIEM (8436) Aceptamos todas las TDC y Débito. **Promoción: 3 meses sin Intereses pagando con American Express **Aplica solo con Inversión Normal ®Todos los Derechos Reservados ©2011 TIEM Talento e Innovación Empresarial de México Este Mensaje le ha sido enviado como usuario de TIEM de México o bien un usuario le refirió para recibir este boletÃn. Como usuario de TIEM de México, en este acto autoriza de manera expresa que TIEM de México le puede contactar vÃa correo electrónico u otros medios. Si usted ha recibido este mensaje por error, haga caso omiso de él y reporte su cuenta respondiendo este correo con el asunto BAJABD Tenga en cuenta que la gestión de nuestras bases de datos es de suma importancia y no es intención de la empresa la inconformidad del receptor.
Bridge randomly stops replying to ARP requests
Hello, I am currently trying to build a small OpenBSD home-router using a Nexcom 2120 appliance. The setup looks like this: Computer (192.168.1.99) > Router > Modem > Internet The router has 6 Intel 82583V GbE interfaces - em0 to em5. - em0 is configured as the PPPoE uplink. - em1 is not used yet - em2 to em5 are configured as a bridge. - There is a WIFI AP on em3 - My test computer (Linux) is plugged into em4 There is a serial console I use to debug. The bridge has an ip address that is set on em2: 192.168.1.1/24 IP forwarding is enabled, there is also a small pf firewall for scrubbing / NAT. Everything is working well - for a few hours, until em2 decides not to reply to ARP requests anymore. Doing an ARP request from my computer to 192.168.1.1 will not get me any reply - although I can see the requests coming in on em2 on the router with tcpdump. The tcpdump running on the router also shows that no reply is being sent via that interface. Interestingly: I can add an ARP cache entry manually on my computer, which allows me to browse the web again - but the interface still won't reply to ARP requests (done using arping). Taking the interface down and up again via ifconfig em2 down ; ifconfig em2 up gets it to reply to ARP requests again. I've seen a similar problem already posted here: http://old.nabble.com/CARP-interfaces-randomly-stop-answering-ARP-requests-td33622854.html But the answers seem to imply a relation to CARP, which I am not using. I am very new to OpenBSD, so I might be missing something obvious - all my apologies if that's the case. Thanks in advance for your help. Here are a few additional infos: * My PF configuration: set skip on lo pass match in all scrub (no-df max-mss 1440) block drop in on pppoe0 pass in on pppoe0 proto tcp to port 2208 pass out on pppoe0 from em2:network to any nat-to (pppoe0) * A full ifconfig: # ifconfig lo0: flags=8049 mtu 33152 priority: 0 groups: lo inet6 ::1 prefixlen 128 inet6 fe80::1%lo0 prefixlen 64 scopeid 0x8 inet 127.0.0.1 netmask 0xff00 em0: flags=8843 mtu 1500 lladdr 00:10:f3:21:ab:1e priority: 0 media: Ethernet autoselect (100baseTX full-duplex,rxpause,txpause) status: active inet6 fe80::210:f3ff:fe21:ab1e%em0 prefixlen 64 scopeid 0x1 em1: flags=8802 mtu 1500 lladdr 00:10:f3:21:ab:1f priority: 0 media: Ethernet autoselect (none) status: no carrier em2: flags=8b43 mtu 1500 lladdr 00:10:f3:21:ab:20 priority: 0 media: Ethernet autoselect (none) status: no carrier inet 192.168.1.1 netmask 0xff00 broadcast 192.168.1.255 inet6 fe80::210:f3ff:fe21:ab20%em2 prefixlen 64 scopeid 0x3 em3: flags=8b43 mtu 1500 lladdr 00:10:f3:21:ab:21 priority: 0 media: Ethernet autoselect (100baseTX full-duplex,rxpause,txpause) status: active inet6 fe80::210:f3ff:fe21:ab21%em3 prefixlen 64 scopeid 0x4 em4: flags=8b43 mtu 1500 lladdr 00:10:f3:21:ab:22 priority: 0 media: Ethernet autoselect (1000baseT full-duplex,master,rxpause,txpause) status: active inet6 fe80::210:f3ff:fe21:ab22%em4 prefixlen 64 scopeid 0x5 em5: flags=8b43 mtu 1500 lladdr 00:10:f3:21:ab:23 priority: 0 media: Ethernet autoselect (none) status: no carrier inet6 fe80::210:f3ff:fe21:ab23%em5 prefixlen 64 scopeid 0x6 enc0: flags=0<> priority: 0 groups: enc status: active pppoe0: flags=8851 mtu 1492 priority: 0 dev: em0 state: session sid: 0x166e PADI retries: 1 PADR retries: 0 time: 12:32:43 sppp: phase network authproto pap authname "03053096355" groups: pppoe egress status: active inet6 fe80::210:f3ff:fe21:ab1e%pppoe0 -> prefixlen 64 scopeid 0x9 inet [commented out] --> [commented out] netmask 0x bridge0: flags=41 groups: bridge priority 32768 hellotime 2 fwddelay 15 maxage 20 holdcnt 6 proto rstp em5 flags=3 port 6 ifpriority 0 ifcost 0 em4 flags=3 port 5 ifpriority 0 ifcost 0 em3 flags=3 port 4 ifpriority 0 ifcost 0 em2 flags=3 port 3 ifpriority 0 ifcost 0 pflog0: flags=141 mtu 33152 priority: 0 groups: pflog
Re: Smtpd.conf(5) %a and %u
On Sat, Jul 07, 2012 at 11:46:30AM +0100, percy piper wrote: > Hi all. > Smtpd.conf(5) states that %a expands to the user before alias resolution > and %u after. Is it the other way round? I am probably missing something > but on the latest i386 snap it seems %a and %u do the opposite to what > smtpd.conf(5) claims? > Can anyone clarify? > Many thanks > Percy I think we will clarify the man page because this one seems to confuse everyone and ultimately it confuses me too :-) Gilles -- Gilles Chehade https://www.poolp.org @poolpOrg
Re: OpenBSD - UEFI Secure Boot
Remember SOPA/ACTA? If somebody is planning to have a regulation, this somebody should take care about tools which guarantee direct, not circumstantial, evidence of somebody else broke this regulation. UEFI implements network stack so it can be a long-standing strategy. UEFI is about remote monitoring without you even knowing about it, or your corporate firewall sniffing for somebody else. You buying UEFI hardware will be a sponsor of somebody sniffing on you. What an irony. Also, UEFI will possibly take down a dozens of Linux/BSD-oriented hardware suppliers businesses because their customers will deny to run security critical tasks on UEFI hardware. Good support for stagnating world economy. IMO, it is smarter to spent on Raspberry Pi port than UEFI bullshit. And don't blame Amiga. It is UEFI free, isn't it? ;) llemikebyw wrote: > Tomas (and David and E.V.R. Else-Body) > > Yes - I'd read the thread(s) (Gentoo too..) - but the > ultimate conclusion of much of the discussion is > "buy different hardware". > > I bought Betamax (because it was the best)... until... > I bought SAAB (because it was the best)... until... > I bought Amiga (because it was the best)... until... > > I don't want to be saying... > > I bou.. erm.. got... OpenBSD (because it was the best)... > > Mike
missing /etc/fstab
Hello! I remember some early 5.1 snapshot which installed and successfully run without /etc/fstab however, 5.1-RELEASE came with /etc/fstab it would be nice to move system from one server to another without having to bother about /etc/fstab (I moved several of them due to buggy hardware). is it possible to run without /etc/fstab ? is it supported configuration ? Cheers, Ilya Shipitsin
Re: missing /etc/fstab
> I remember some early 5.1 snapshot which installed and successfully run > without /etc/fstab > however, 5.1-RELEASE came with /etc/fstab > > it would be nice to move system from one server to another without having > to bother about /etc/fstab (I moved several of them due to buggy hardware). > is it possible to run without /etc/fstab ? is it supported configuration ? Sorry, but you are wrong. A system must have a /etc/fstab file, and it is created by the installer.
Re: missing /etc/fstab
On Sunday 08 July 2012 14:07:44 Илья Шипицин wrote: > Hello! > > I remember some early 5.1 snapshot which installed and successfully run > without /etc/fstab > however, 5.1-RELEASE came with /etc/fstab > > it would be nice to move system from one server to another without having > to bother about /etc/fstab (I moved several of them due to buggy hardware). > is it possible to run without /etc/fstab ? is it supported configuration ? > > Cheers, > Ilya Shipitsin > > As Theo pointed out there always is a fstab needed and present. If you mean by "move system", moving the "harddisk" to another system, look at DUID's if you don't use them yet. gr Renzo
Re: SIL 3512 sata card dma errors
Hi, I had similar problems with a SiI3512A card some time ago, and ended up using just the internal ports. Since I had some time today, I installed i386/mp-current on a spare computer and tested with two SATA disks. Writing 300GB of zeros (dd) in parallel to both disks showed no error. So I assume they stability of the 3512 depends on other factors (mainboard, IRQs, moon phase...). I also tested two other cards: 1) VIA VT6421 This chipset is not listed in "man pciide", but a quick "grep" showed that it's mentioned in the code. The system froze during boot after detecting the first disk, no matter if one or two disks were attached. pciide1 at pci2 dev 4 function 0 "VIA VT6421 SATA" rev 0x50: DMA pciide1: using apic 1 int 20 for native-PCI interrupt wd0 at pciide1 channel 0 drive 0: wd0: 16-sector PIO, LBA48, 476940MB, 976773168 sectors wd0(pciide1:0:0): using PIO mode 4, Ultra-DMA mode 6 2) jmb0 at pci1 dev 0 function 0 "JMicron JMB363 IDE/SATA" rev 0x03 Worked nicely. According to systat it provided around 30MB/sec write speed, whereas the SiI3512A only had around 20MB/sec. kind regards, Robert
Re: SIL 3512 sata card dma errors
On v, júl 08, 2012 at 21:37:47 +0200, Robert wrote: > Hi, > > I had similar problems with a SiI3512A card some time ago, and ended up > using just the internal ports. > > Since I had some time today, I installed i386/mp-current on a spare > computer and tested with two SATA disks. Writing 300GB of zeros (dd) in > parallel to both disks showed no error. So I assume they stability of > the 3512 depends on other factors (mainboard, IRQs, moon phase...). My errors were triggered when I was copying from disk1 to disk2, both connected to the SIL card. (in this case this was a 2 port card), not when copying something in parallel to both disks from a separate location. I think this makes the difference. [...] > 2) jmb0 at pci1 dev 0 function 0 "JMicron JMB363 IDE/SATA" rev 0x03 > Worked nicely. According to systat it provided around 30MB/sec write > speed, whereas the SiI3512A only had around 20MB/sec. This is good to know, I'm sure I'll prefer this kind of device in the future. Daniel -- LÉVAI Dániel PGP key ID = 0x83B63A8F Key fingerprint = DBEC C66B A47A DFA2 792D 650C C69B BE4C 83B6 3A8F
Re: missing /etc/fstab
On Sun, Jul 8, 2012 at 8:29 AM, Theo de Raadt wrote: >> I remember some early 5.1 snapshot which installed and successfully run >> without /etc/fstab >> however, 5.1-RELEASE came with /etc/fstab >> >> it would be nice to move system from one server to another without having >> to bother about /etc/fstab (I moved several of them due to buggy hardware). >> is it possible to run without /etc/fstab ? is it supported configuration ? > > Sorry, but you are wrong. > > A system must have a /etc/fstab file, and it is created by the installer. To "move" or replicate a system to other hardware, the /etc/fstab aneeds to be reviewed and edited for any partition layout, or it will not be able to find the partitions for "/" or other partitions you happen to need. Some folks get cute and do NFS or similar targets with automounting of varous sorts, so those aren't in fstab on such systems. I've never seen anyone using that on OpenBSD. I've done this sort of replicate-and-edit-config-files stunt for roughly 20,000 hosts in my careerm, espcially 15,000 Linux hosts in one month, so I know the approach can be much faster than installing from normal installation media. /etc/fstab can also be deleted after a system is up and running with all the UNIX or UNIX like operating systems, I've seen people accidentally do that. But woe betide them when they try to reboot!
Re: missing /etc/fstab
On Sun, Jul 8, 2012 at 7:41 PM, Nico Kadel-Garcia wrote: > On Sun, Jul 8, 2012 at 8:29 AM, Theo de Raadt wrote: >>> I remember some early 5.1 snapshot which installed and successfully run >>> without /etc/fstab >>> however, 5.1-RELEASE came with /etc/fstab >>> >>> it would be nice to move system from one server to another without having >>> to bother about /etc/fstab (I moved several of them due to buggy hardware). >>> is it possible to run without /etc/fstab ? is it supported configuration ? >> >> Sorry, but you are wrong. >> >> A system must have a /etc/fstab file, and it is created by the installer. > > To "move" or replicate a system to other hardware, the /etc/fstab > aneeds to be reviewed and edited for any partition layout, or it will > not be able to find the partitions for "/" or other partitions you > happen to need. Some folks get cute and do NFS or similar targets with > automounting of varous sorts, so those aren't in fstab on such > systems. I've never seen anyone using that on OpenBSD. afaik, the duid is stored on the disklabel, so if you're making images of the media there's no need to edit fstab > > I've done this sort of replicate-and-edit-config-files stunt for > roughly 20,000 hosts in my careerm, espcially 15,000 Linux hosts in > one month, so I know the approach can be much faster than installing > from normal installation media. your sites are extremely heterogeneous
Re: missing /etc/fstab
On Sun, Jul 8, 2012 at 8:18 PM, Andres Perera wrote: > On Sun, Jul 8, 2012 at 7:41 PM, Nico Kadel-Garcia wrote: >> On Sun, Jul 8, 2012 at 8:29 AM, Theo de Raadt >> wrote: I remember some early 5.1 snapshot which installed and successfully run without /etc/fstab however, 5.1-RELEASE came with /etc/fstab it would be nice to move system from one server to another without having to bother about /etc/fstab (I moved several of them due to buggy hardware). is it possible to run without /etc/fstab ? is it supported configuration ? >>> >>> Sorry, but you are wrong. >>> >>> A system must have a /etc/fstab file, and it is created by the installer. >> >> To "move" or replicate a system to other hardware, the /etc/fstab >> aneeds to be reviewed and edited for any partition layout, or it will >> not be able to find the partitions for "/" or other partitions you >> happen to need. Some folks get cute and do NFS or similar targets with >> automounting of varous sorts, so those aren't in fstab on such >> systems. I've never seen anyone using that on OpenBSD. > > afaik, the duid is stored on the disklabel, so if you're making images > of the media there's no need to edit fstab I wasn't making disk images, which are unsuitable if you're re-arrangig partitions or altering partition sizes (which I was doing). I made compressed tarballs of the mounted filesystems from installation media: *MUCH* more efficient. >> I've done this sort of replicate-and-edit-config-files stunt for >> roughly 20,000 hosts in my careerm, espcially 15,000 Linux hosts in >> one month, so I know the approach can be much faster than installing >> from normal installation media. > > your sites are extremely heterogeneous Amen, brother! My predecessor used disk images, which created all sorts of unnecessary storage and image update problems.
Re: OpenBSD - UEFI Secure Boot
On Sun, Jul 8, 2012 at 6:18 AM, Alexey Suslikov wrote: > Remember SOPA/ACTA? If somebody is planning to have a regulation, > this somebody should take care about tools which guarantee direct, not > circumstantial, evidence of somebody else broke this regulation. > > UEFI implements network stack so it can be a long-standing strategy. > > UEFI is about remote monitoring without you even knowing about it, or > your corporate firewall sniffing for somebody else. It's not the only thing it's about. The old Palladium project, now known as "Trusted Computing", is designed to have "secured" access to each level of hardware and software. Since every step individually can be circumvented with known technologies if not part of the secure stack, they've tried very hard to embed it at every level: CPU, boot loader, kernel, applications, data, and hardware. Expect to see this whole stack pushed for secure storage media and private information, because some of the primary goals are portable storage media and backup data. By "securing" every stage, it's also effectively digital rights managed, and for that to work, it needs to exist at every stage rom motherboard chipsets on up. Where it's going to be problematic for OpenBSD is on "Windows 8" certified hardware, which has the UEFI enabled by default. It's theoretically possible for OpenBSD's boot loaders to emulate what Red Hat has done for Fedora: buy a signature for UEFI compatible shim that will load the kernel. The problem then, will be locally compiled kernels, which all my OpenBSD managing peers create as a matter of course. Many of us can comfortably disable UEFI, but it's going to be problematic for our less skilled colleagues. > You buying UEFI hardware will be a sponsor of somebody sniffing on you. > What an irony. Or saving $100 on buying the latest hot box, or of graciously accepting a gift, or of doing a successful dumpster dive for laptops, desktops, and server grade hardware. > Also, UEFI will possibly take down a dozens of Linux/BSD-oriented > hardware suppliers businesses because their customers will deny to run > security critical tasks on UEFI hardware. Good support for stagnating > world economy. Go look at what Fedora is doing to handle this. OpenBSD boot loaders are going to have to make some kind of accomodation with this in the next 5 years, or throw in the towel for new hardware and go directly to virtualization only. (That's admittedly how I use it these days, mostly for testing components like OpenSSH before 6.0p1 was bundled.) > IMO, it is smarter to spent on Raspberry Pi port than UEFI bullshit. Good luck with that.
dmesg reporting different clock speeds on different cores
I am just curious.
Would someone mind explaining why the clock speed reports
as different for cpu1? Both cores are on the same cpu.
dmesg|grep ^cpu[0-9]*:
cpu0: Intel(R) Atom(TM) CPU D525 @ 1.80GHz ("GenuineIntel" 686-class) 1.81 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,NXE,LONG,SSE3,MWAIT,DS-CPL,TM2,SSSE3,CX16,xTPR,PDCM,MOVBE,LAHF
cpu0: apic clock running at 389MHz
cpu1: Intel(R) Atom(TM) CPU D525 @ 1.80GHz ("GenuineIntel" 686-class) 3.51 GHz
cpu1:
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,NXE,LONG,SSE3,MWAIT,DS-CPL,TM2,SSSE3,CX16,xTPR,PDCM,MOVBE,LAHF
Re: dmesg reporting different clock speeds on different cores
Sorry,
OpenBSD generic , 5.1 release.
On Mon, Jul 09, 2012 at 03:20:19PM +1000, David Diggles wrote:
> I am just curious.
>
> Would someone mind explaining why the clock speed reports
> as different for cpu1? Both cores are on the same cpu.
>
> dmesg|grep ^cpu[0-9]*:
> cpu0: Intel(R) Atom(TM) CPU D525 @ 1.80GHz ("GenuineIntel" 686-class) 1.81 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,NXE,LONG,SSE3,MWAIT,DS-CPL,TM2,SSSE3,CX16,xTPR,PDCM,MOVBE,LAHF
> cpu0: apic clock running at 389MHz
> cpu1: Intel(R) Atom(TM) CPU D525 @ 1.80GHz ("GenuineIntel" 686-class) 3.51 GHz
> cpu1:
> 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,NXE,LONG,SSE3,MWAIT,DS-CPL,TM2,SSSE3,CX16,xTPR,PDCM,MOVBE,LAHF
Re: partitioning with more mount points on obsd51
On Tue, 26 Jun 2012, Norman Golisz wrote: Hi Darrel, On Tue Jun 26 2012 14:58, Darrel wrote: We have less limitation on partitioning these days, so /usr/obj was obvious- actually had that one before. I chose /usr/src and /usr/local as well, and expect that this was unimportant unless moving into NFS or some special circumstance. no, this isn't necessarily true. Think of FFS' block alignment feature, using different mount options, file system optimisations, etc. I have looked at some of the things that folks are doing with /var on ZFS. I understand that ZFS is not within the scope of this list; however, does anyone have some neat ideas about partitions under /var? Particularly, I am interested in /var/crash, /var/tmp, and /tmp. I would not personally have any use for a crashdump, unless it would be to pass it along to someone who could make use of it. I basically want the partitions to be set up logically. Typically etc, usr, tmp, var, home, and / have been enough. /usr/obj is an excellent addition and so does someone have recommendations of further refining my scheme for OpenBSD51? I used /altroot for the first time on OpenBSD50, but had to modify fstab like this: #bb128e900f20094a.d /altroot ffs xx 0 0 /dev/wd0d /altroot ffs xx 0 0 I guess that /var/crash should be crafted to memory and that Hmm. No. Be aware that the kernel dumps the entire physical memory to swap. When rebooting, savecore(8) copies the dump to /var/crash. Therefore, it needs to be at least as big as available system RAM + a few bits more. You see why mfs is not suited for this. /var/tmp as well as /tmp can actually be very small? Yes, they can. But it depends on your setup. See, /tmp can become scarce when your web browser stores its temporary data there, e.g. video data. And, one further hint, you should place /var/tmp on non-volatile storage, as it is supposed to hold temporary data between reboots, whereas /tmp can safely be an mfs. My imperfect configuration looks like this: ~ $ df -h Filesystem SizeUsed Avail Capacity Mounted on /dev/sd2a 509M 64.0M420M13%/ /dev/sd2p 44.8G 29.1G 13.5G68%/home /dev/sd2d 1001M793M158M83%/usr /dev/sd2e 502M196M281M41%/usr/X11R6 /dev/sd2f 6.9G2.7G3.8G42%/usr/local /dev/sd2i 2.0G1.1G812M58%/usr/obj /dev/sd2k 4.9G384M4.3G 8%/usr/ports /dev/sd2l 3.9G 87.4M3.7G 2%/usr/ports/pobj /dev/sd2g 2.9G890M1.9G31%/usr/src /dev/sd2h 2.0G552M1.3G29%/usr/xenocara /dev/sd2j 2.0G495M1.4G26%/usr/xobj /dev/sd2m 123M 17.4M 99.8M15%/var /dev/sd2o 246M5.1M229M 2%/var/log /dev/sd2n 123M 96.0K117M 0%/var/tmp mfs:4517 495M109K470M 0%/tmp Thank you, Norman. I plan to borrow some of this. I have been slow this time- most machines are getting a fresh reinstall. My 5.0 boxes have 3g on /usr/obj and 2g on /usr/src. I tend to get old computers from folks that upgrade and actually have a DNS Server running on an Intel built for windows95. :) And for the sake of comparison, I have a FreeBSD machine with ZFS filesystem mostly backup up video and it looks like this: (70) @ 23:39:38> zfs list NAME USED AVAIL REFER MOUNTPOINT bigD32.8G 37.6G 672M / bigD/swap 4.13G 41.7G 57.1M - bigD/tmp 44K 37.6G44K /tmp bigD/usr27.8G 37.6G 312M /usr bigD/usr/distfiles31K 37.6G31K /usr/distfiles bigD/usr/home 23.9G 37.6G 23.9G /usr/home bigD/usr/local 421M 37.6G 421M /usr/local bigD/usr/obj2.44G 37.6G 2.44G /usr/obj bigD/usr/packages 31K 37.6G31K /usr/packages bigD/usr/ports 435M 37.6G 435M /usr/ports bigD/usr/src 351M 37.6G 351M /usr/src bigD/var 156M 37.6G 1.28M /var bigD/var/backups1.04M 37.6G 1.04M /var/backups bigD/var/crash 31.5K 37.6G 31.5K /var/crash bigD/var/db 153M 37.6G 152M /var/db bigD/var/db/pkg 1.30M 37.6G 1.30M /var/db/pkg bigD/var/empty31K 37.6G31K /var/empty bigD/var/mail 31K 37.6G31K /var/mail bigD/var/run 55K 37.6G55K /var/run bigD/var/tmp 32K 37.6G32K /var/tmp Darrel
"simple" PF rule? redirect port without touching address
I am trying to achieve something I thought would be simple, but haven't had any luck. I have an OpenBSD 5.0 router/firewall with public IP X.X.X.A Behind it are a mix of OpenBSD and Linux systems, all with public IP. NO NAT. I run ssh on an alternate port, XXX22. However, from a certain location I am dealing with a firewall that will not allow outbound connections on XXX22 only on 22 I have already set up a rule like this, and it works: pass in on egress proto tcp from $location1 to any port ssh rdr-to X.X.X.A port XXX22 But i was wondering if I could achieve something that would work for ALL the addresses behind the router as well without creating individual rules for each address. Something like this: pass in on egress proto tcp from $location1 to any port ssh rdr-to (original destination IP) port XXX22
