Re: Tricks for install OpenBSD under Virtualbox, host Windows XP
On Tue, Jan 8, 2013 at 6:40 AM, Kevin Chadwick ma1l1i...@yahoo.co.uk wrote: Hi, I installed Virtualbox 2.2.4 and everything is 100%. You hope so but make it clear if you ever hit problems that you are not on bare metal as bug reports have been looked at and been found to be the fault of Virtualbox in the past with Theo commenting on their forum that he couldn't believe any OS would allow what it was doing with memory. I didn't speak up because others have said it's fixed, I wonder now if it is just the VT-X that fixed Virtualbox. Also, Windows XP (which the original poster is using) is very old, and very close to end-of-life. Hosting virtualization on it, for an inherited non-commercial project which Oracle inherited from Sun, is unlikely to be a long-term stable solution for anything, especially on XP. Not that Virtualbox is bad, I use it extensively myself for personal virtualization. But it means that he should make sure that his disk images are compatible with other vortia;ozatopm tpp;s, and that his backups of his OpenBSD system or of the disk image are working well, in case VirtualBox fails with new releases and he needs to host it elsewhere.
Re: new computer
You do realize the typical life of a battery is about a year? The life of a battery, when it has reached its expected and standard life does not reflect the quality of a pc. At any rate, it's not my intention to debate the quality of a particular brand or OEM. But, I like to defend a product when misguided information is posted as an absolute or as fact. On Thu, Jan 10, 2013 at 1:11 AM, K.André Braselmann k...@braselmann.orgwrote: Buy a refurbished ThinkPad, still better older ThinkPad than shitty plastic Acer/Asus crapbook. jirib I've got 3 pieces of them in the basement. After 1095 days (warranty in germany: 3 yrs) battery is dead (spare 100) and the rest will also give up in the next half year. Seems to be the El cheapo Canon printer business model. Usually they got exactly ONE BIOS update. Bought several used ThinkPads and everyone is happy. In Germany about 200-300 André
Re: new computer
Buy a refurbished ThinkPad, still better older ThinkPad than shitty plastic Acer/Asus crapbook. Not an option. At my place there is no market of that type. Further people do not buy laptops of business kind. I will change the subject, to closely match questions I have. Best regards all Zoran
integrated graphics
I found it too hard to find proper laptop for sane sum of green papers, to run openbsd amd64. In a haze of quest, I set my eyes on two lovely comp cases: chieftec bt-02b-180 silverstone sg05 Digested question would be: what integrated cpu works on 5.2 amd64? Better to go after intel or amd? There are posts of both sandybridge and amd fusion with gra- phics working. I will get the lower end of one this list recommends as a choice. If amd, probably fm1 socket, asus with realtek 8111 e/f ethernet. Simple: what cpu? Zoran
Re: new computer
Buy a refurbished ThinkPad, still better older ThinkPad Anyone know of a good place to look for and what model the latest thinkpad with fullscreen/without widescreen would be. I'm guessing fullscreen and usb3 and pci express is an impossible mix never minding throwing in running superbly on OpenBSD but how about fullscreen and pci express and OpenBSD? -- ___ 'Write programs that do one thing and do it well. Write programs to work together. Write programs to handle text streams, because that is a universal interface' (Doug McIlroy) ___
Re: tftp - no route to host
On 05/01/2011 10:13 AM, Henning Brauer wrote: * Emille Blancsar...@sarlok.com [2011-04-30 19:56]: since TFTP uses UDP, pf won't create a state wrong. Hello, I'm stuck again with no route to host # uname -a OpenBSD gw 5.2 GENERIC.MP#339 i386 # ls -la /usr/tftpboot/ total 12728 drwxrwxrwx 2 root wheel 512 Jan 10 15:36 . drwxr-xr-x 18 root wheel 512 Jan 10 14:48 .. -rwxrwxrwx 1 root wheel3 Jan 10 15:35 1.txt -rwxrwxrwx 1 root wheel 6427696 Feb 13 2012 bsd.rd -rwxrwxrwx 1 root wheel53732 Feb 13 2012 pxeboot # pfctl -sr | grep 69 pass in quick on em0 inet proto udp from any to any port = 69 pass out quick on em0 inet proto udp from any to any port = 69 from localhost: # tftp tftp connect 192.168.5.254 tftp get 1.txt Received 3 bytes in 0.0 seconds tftp get pxeboot Received 54044 bytes in 0.0 seconds tftp quit # ls -la | grep 1.txt -rw-r--r-- 1 root wheel3 Jan 10 17:14 1.txt # ls -la | grep pxeboot -rw-r--r-- 1 root wheel53732 Jan 10 17:14 pxeboot from remote PC: admin:~/Downloads$ tftp tftp connect gw tftp status Connected to gw. Mode: netascii Verbose: off Tracing: off Rexmt-interval: 5 seconds, Max-timeout: 25 seconds tftp mode binary tftp status Connected to gw. Mode: octet Verbose: off Tracing: off Rexmt-interval: 5 seconds, Max-timeout: 25 seconds tftp get 1.txt ^C tftp on tftpd host: # ping 192.168.5.1 PING 192.168.5.1 (192.168.5.1): 56 data bytes 64 bytes from 192.168.5.1: icmp_seq=0 ttl=64 time=0.524 ms ... # tftpd -4dv -l 192.168.5.254 /usr/tftpboot tftpd: 192.168.5.254: read request for '1.txt' # can get files locally tftpd: 192.168.5.254: read request for 'pxeboot' # can get files locally tftpd: 192.168.5.1: read request for '1.txt' # can get files remotely tftpd: send(block): No route to host tftpd: 192.168.5.1: read request for '1.txt' tftpd: send(block): No route to host tftpd: 192.168.5.1: read request for '1.txt' tftpd: send(block): No route to host # tcpdump -i em0 -p udp 'port 69' tcpdump: listening on em0, link-type EN10MB 17:21:38.462907 admin.40154 gw.tftp: 14 RRQ 1.txt (DF) 17:21:43.462961 admin.40154 gw.tftp: 14 RRQ 1.txt (DF) 17:21:48.463020 admin.40154 gw.tftp: 14 RRQ 1.txt (DF) ^C 8554 packets received by filter 0 packets dropped by kernel # fstat | grep internet | grep tftpd _tftpd tftpd 181603* internet dgram udp 192.168.5.254:69
Re: tftp - no route to host (Solved)
On 01/10/2013 05:24 PM, lilit-aibolit wrote: On 05/01/2011 10:13 AM, Henning Brauer wrote: * Emille Blancsar...@sarlok.com [2011-04-30 19:56]: since TFTP uses UDP, pf won't create a state wrong. Hello, I'm stuck again with no route to host # uname -a OpenBSD gw 5.2 GENERIC.MP#339 i386 # ls -la /usr/tftpboot/ total 12728 drwxrwxrwx 2 root wheel 512 Jan 10 15:36 . drwxr-xr-x 18 root wheel 512 Jan 10 14:48 .. -rwxrwxrwx 1 root wheel3 Jan 10 15:35 1.txt -rwxrwxrwx 1 root wheel 6427696 Feb 13 2012 bsd.rd -rwxrwxrwx 1 root wheel53732 Feb 13 2012 pxeboot # pfctl -sr | grep 69 pass in quick on em0 inet proto udp from any to any port = 69 pass out quick on em0 inet proto udp from any to any port = 69 from localhost: # tftp tftp connect 192.168.5.254 tftp get 1.txt Received 3 bytes in 0.0 seconds tftp get pxeboot Received 54044 bytes in 0.0 seconds tftp quit # ls -la | grep 1.txt -rw-r--r-- 1 root wheel3 Jan 10 17:14 1.txt # ls -la | grep pxeboot -rw-r--r-- 1 root wheel53732 Jan 10 17:14 pxeboot from remote PC: admin:~/Downloads$ tftp tftp connect gw tftp status Connected to gw. Mode: netascii Verbose: off Tracing: off Rexmt-interval: 5 seconds, Max-timeout: 25 seconds tftp mode binary tftp status Connected to gw. Mode: octet Verbose: off Tracing: off Rexmt-interval: 5 seconds, Max-timeout: 25 seconds tftp get 1.txt ^C tftp on tftpd host: # ping 192.168.5.1 PING 192.168.5.1 (192.168.5.1): 56 data bytes 64 bytes from 192.168.5.1: icmp_seq=0 ttl=64 time=0.524 ms ... # tftpd -4dv -l 192.168.5.254 /usr/tftpboot tftpd: 192.168.5.254: read request for '1.txt' # can get files locally tftpd: 192.168.5.254: read request for 'pxeboot' # can get files locally tftpd: 192.168.5.1: read request for '1.txt' # can get files remotely tftpd: send(block): No route to host tftpd: 192.168.5.1: read request for '1.txt' tftpd: send(block): No route to host tftpd: 192.168.5.1: read request for '1.txt' tftpd: send(block): No route to host # tcpdump -i em0 -p udp 'port 69' tcpdump: listening on em0, link-type EN10MB 17:21:38.462907 admin.40154 gw.tftp: 14 RRQ 1.txt (DF) 17:21:43.462961 admin.40154 gw.tftp: 14 RRQ 1.txt (DF) 17:21:48.463020 admin.40154 gw.tftp: 14 RRQ 1.txt (DF) ^C 8554 packets received by filter 0 packets dropped by kernel # fstat | grep internet | grep tftpd _tftpd tftpd 181603* internet dgram udp 192.168.5.254:69 I fix this by changing from pass out quick on em0 inet proto udp from any to any port = 69 to pass out quick on em0 inet proto udp from $int_if to $local_net Is this right? Maybe I don't want to allow all udp traffic from my gateway.
is nat to (egress) possible ?
I'm running multi-homed firewal. at every single moment only one interface belongs to egress group. is it possible to do something like that match out from 192.168.0.0/16 to ! 192.168.0.0/16 nat-to (egress) ? Cheers, Ilya Shipitsin
Re: Foxconn NanoPC nT-i1250 fails to boot after install
On Wed, Jan 9, 2013 at 5:34 PM, Stefan Sperling s...@openbsd.org wrote: Shot in the dark: Does it not hang if you disable the pms driver via boot -c? See the boot_config(8) man page. The RAMDISK_CD kernel doesn't have pms compiled in, and it might be the next thing pckbd0 is trying to initialise in the GENERIC kernel. You must have night-vision goggles -- that did the trick. If there's anything I can do to help debug this further, let me know. Otherwise, I'm happy with the workaround.
Re: Foxconn NanoPC nT-i1250 fails to boot after install
On Thu, Jan 10, 2013 at 08:56:15AM -0800, Kent Fritz wrote:
On Wed, Jan 9, 2013 at 5:34 PM, Stefan Sperling s...@openbsd.org wrote:
Shot in the dark: Does it not hang if you disable the pms driver
via boot -c? See the boot_config(8) man page.
The RAMDISK_CD kernel doesn't have pms compiled in, and it might be
the next thing pckbd0 is trying to initialise in the GENERIC kernel.
You must have night-vision goggles -- that did the trick. If there's
anything I can do to help debug this further, let me know. Otherwise,
I'm happy with the workaround.
Can you please try to find out which protocol probe routine is
responsible for hanging the machine?
There is a table of protocols in /usr/src/sys/dev/pckbc/pms.c.
In -current, it looks like this:
const struct pms_protocol pms_protocols[] = {
/* Generic PS/2 mouse */
{
PMS_STANDARD, 3,
NULL, pms_ioctl_mouse,
pms_sync_mouse,
pms_proc_mouse,
NULL
},
/* Microsoft IntelliMouse */
{
PMS_INTELLI, 4,
pms_enable_intelli,
pms_ioctl_mouse,
pms_sync_mouse,
pms_proc_mouse,
NULL
},
/* Synaptics touchpad */
{
PMS_SYNAPTICS, 6,
pms_enable_synaptics,
pms_ioctl_synaptics,
pms_sync_synaptics,
pms_proc_synaptics,
pms_disable_synaptics
},
/* ALPS touchpad */
{
PMS_ALPS, 6,
pms_enable_alps,
pms_ioctl_alps,
pms_sync_alps,
pms_proc_alps,
NULL
},
#ifdef notyet
/* Elantech touchpad (hardware version 1) */
{
PMS_ELANTECH_V1, 4,
pms_enable_elantech_v1,
pms_ioctl_elantech,
pms_sync_elantech_v1,
pms_proc_elantech_v1,
NULL
},
/* Elantech touchpad (hardware version 2) */
{
PMS_ELANTECH_V2, 6,
pms_enable_elantech_v2,
pms_ioctl_elantech,
pms_sync_elantech_v2,
pms_proc_elantech_v2,
NULL
},
#endif
/* Elantech touchpad (hardware version 3) */
{
PMS_ELANTECH_V3, 6,
pms_enable_elantech_v3,
pms_ioctl_elantech,
pms_sync_elantech_v3,
pms_proc_elantech_v3,
NULL
},
};
Perhaps start by removing the touchpad protocols first, since
they're most likely to be the cause of this problem.
You could comment out all the touchpad protocols like this:
const struct pms_protocol pms_protocols[] = {
/* Generic PS/2 mouse */
{
PMS_STANDARD, 3,
NULL, pms_ioctl_mouse,
pms_sync_mouse,
pms_proc_mouse,
NULL
},
/* Microsoft IntelliMouse */
{
PMS_INTELLI, 4,
pms_enable_intelli,
pms_ioctl_mouse,
pms_sync_mouse,
pms_proc_mouse,
NULL
},
#if 0 -- add this here
/* Synaptics touchpad */
{
...skipping all the lines in-between...
pms_sync_elantech_v3,
pms_proc_elantech_v3,
NULL
},
#endif -- add this here
};
If that doesn't hang it, move the #if 0 further down to the next
protocol, and try again.
Note that elantech v1 and elantech v2 are currently disabled
anyway (via #ifdef notyet) because the code hasn't yet been
tested on real hardware. (BTW, in case an eeepc owner is reading
this, you might have such a touchpad, so please try enabling
the v1 and v2 protocols to see if that makes the synaptics
driver attach in X and if the touchpad then works properly).
Once we know which protocol probe routine is causing the
problem we can dig further.
Re: is nat to (egress) possible ?
Илья Шипицин chipits...@gmail.com wrote: I'm running multi-homed firewal. at every single moment only one interface belongs to egress group. I don't think that matters. is it possible to do something like that match out from 192.168.0.0/16 to ! 192.168.0.0/16 nat-to (egress) IIRC that's about how I've been doing it for ages. Why don't you just try it? /Alexander ? Cheers, Ilya Shipitsin
Arpresolve route without link local address
Hi, After upgrade to 08.01.2013 snapshot, I get a lot of /bsd: arpresolve: XX.XX.XX.33: route without link local address in /var/log/messages. XX.XX.XX.33 is my default gateway. [ns]~$ cat /etc/hostname.em0 up dhcp -inet6 [ns]~$ tail /var/log/messages ... Jan 10 20:31:47 ns /bsd: arpresolve: 94.26.7.33: route without link local address Jan 10 20:31:47 ns /bsd: arpresolve: 94.26.7.33: route without link local address ... Jan 10 20:36:47 ns /bsd: arpresolve: XX.XX.X.33: route without link local address Jan 10 20:36:47 ns last message repeated 7 times I can provide more info if it's needed. dmesg: OpenBSD 5.2-current (GENERIC) #14: Tue Jan 8 14:13:14 MST 2013 dera...@i386.openbsd.org:/usr/src/sys/arch/i386/compile/GENERIC cpu0: AMD Athlon(TM) XP1600+ (AuthenticAMD 686-class, 256KB L2 cache) 1.42 GHz cpu0: FPU,V86,DE,PSE,TSC,MSR,PAE,MCE,CX8,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,MMX,FXSR,SSE,MMXX,3DNOW2,3DNOW real mem = 402112512 (383MB) avail mem = 384561152 (366MB) mainbus0 at root bios0 at mainbus0: AT/286+ BIOS, date 03/03/03, BIOS32 rev. 0 @ 0xf0d00, SMBIOS rev. 2.3 @ 0xf2bc0 (46 entries) bios0: vendor Award Software, Inc. version ASUS A7V266-C ACPI BIOS Rev 1014 date 03/03/2003 bios0: ASUSTeK Computer INC. A7V266-C apm0 at bios0: Power Management spec V1.2 acpi at bios0 function 0x0 not configured pcibios0 at bios0: rev 2.1 @ 0xf/0x1572 pcibios0: PCI IRQ Routing Table rev 1.0 @ 0xf14b0/192 (10 entries) pcibios0: PCI Interrupt Router at 000:17:0 (VIA VT82C586 ISA rev 0x00) pcibios0: PCI bus #1 is the last bus bios0: ROM list: 0xc/0x8000 0xc8000/0x1000 0xcc000/0x1000 cpu0 at mainbus0: (uniprocessor) pci0 at mainbus0 bus 0: configuration mode 1 (bios) pchb0 at pci0 dev 0 function 0 VIA VT8366 PCI rev 0x00 viaagp0 at pchb0: v2 agp0 at viaagp0: aperture at 0xfe80, size 0xe40 ppb0 at pci0 dev 1 function 0 VIA VT8366 AGP rev 0x00 pci1 at ppb0 bus 1 vga1 at pci0 dev 12 function 0 S3 ViRGE DX/GX rev 0x01 wsdisplay0 at vga1 mux 1: console (80x25, vt100 emulation) wsdisplay0: screen 1-5 added (80x25, vt100 emulation) em0 at pci0 dev 13 function 0 Intel PRO/1000MT (82540EM) rev 0x02: irq 11, address 00:07:e9:10:32:a8 em1 at pci0 dev 15 function 0 Intel PRO/1000MT (82540EM) rev 0x02: irq 10, address 00:07:e9:10:2a:20 viapm0 at pci0 dev 17 function 0 VIA VT8233A ISA rev 0x00: SMI iic0 at viapm0 lm1 at iic0 addr 0x2d: AS99127F viapm0: 24-bit timer at 3579545Hz pciide0 at pci0 dev 17 function 1 VIA VT82C571 IDE rev 0x06: ATA133, channel 0 configured to compatibility, channel 1 confi gured to compatibility wd0 at pciide0 channel 0 drive 0: WDC WD800JB-00ETA0 wd0: 16-sector PIO, LBA48, 76319MB, 156301488 sectors wd0(pciide0:0:0): using PIO mode 4, Ultra-DMA mode 5 pciide0: channel 1 disabled (no drives) uhci0 at pci0 dev 17 function 2 VIA VT83C572 USB rev 0x23: irq 12 uhci1 at pci0 dev 17 function 3 VIA VT83C572 USB rev 0x23: irq 12 usb0 at uhci0: USB revision 1.0 uhub0 at usb0 VIA UHCI root hub rev 1.00/1.00 addr 1 usb1 at uhci1: USB revision 1.0 uhub1 at usb1 VIA UHCI root hub rev 1.00/1.00 addr 1 isa0 at mainbus0 isadma0 at isa0 com0 at isa0 port 0x3f8/8 irq 4: ns16550a, 16 byte fifo com0: console com1 at isa0 port 0x2f8/8 irq 3: ns16550a, 16 byte fifo pckbc0 at isa0 port 0x60/5 pckbd0 at pckbc0 (kbd slot) pckbc0: using irq 1 for kbd slot wskbd0 at pckbd0: console keyboard, using wsdisplay0 pcppi0 at isa0 port 0x61 spkr0 at pcppi0 npx0 at isa0 port 0xf0/16: reported by CPUID; using exception 16 mtrr: Pentium Pro MTRR support vscsi0 at root scsibus0 at vscsi0: 256 targets softraid0 at root scsibus1 at softraid0: 256 targets root on wd0a swap on wd0b dump on wd0b
Re: Foxconn NanoPC nT-i1250 fails to boot after install
On Thu, Jan 10, 2013 at 9:26 AM, Stefan Sperling s...@openbsd.org wrote: Can you please try to find out which protocol probe routine is responsible for hanging the machine? None of them. I tried as you suggested, then just #if'd out every entry in that structure. No change in behavior. (BTW: First time compiling my own kernel. The FAQ rocks!)
PF filtering on MAC address
Is it possible to have PF filter on MAC address on a machine with only one physical nic? I'm aware that MAC filtering can only be done on a machine configured as a bridge, but how to configure such a bridge? ---8--- # /etc/hostname.bridge0 add bge0 add ?? rule pass in on bge0 src f8:db:7f:4d:bb:10 tag WWW rule pass in on bge0 src 00:08:02:85:6c:90 tag SSH rule pass in on bge0 src 00:16:ea:b3:65:d0 tag SSH ---8--- Regards, Erling
Re: PF filtering on MAC address
On Thu, Jan 10, 2013 at 6:54 PM, Erling Westenvik erling.westen...@gmail.com wrote: Is it possible to have PF filter on MAC address on a machine with only one physical nic? I'm aware that MAC filtering can only be done on a machine configured as a bridge, but how to configure such a bridge? Add the single interface to the bridge. Tag the packets from a specific MAC. Filter the tag. ---8--- # /etc/hostname.bridge0 add bge0 add ?? rule pass in on bge0 src f8:db:7f:4d:bb:10 tag WWW rule pass in on bge0 src 00:08:02:85:6c:90 tag SSH rule pass in on bge0 src 00:16:ea:b3:65:d0 tag SSH ---8--- Regards, Erling
