Re: Developing device driver for parallel lcd dispaly modules
Hi again, Sorry for the delay but it took time to check if the hardware is healthy and check if it is Hitachi-compatible. Lanner INC said that LCM is not Hitachi-compatible. I'm sure that LCM is healthy cause i've tested it under FreeBSD 7.2 i386 Also my boss got permission from the vendor to share LannerINC LCM drivers. Anyone interested can download it from this link: http://speedy.sh/DKraQ/LCM-Linux-DOS-sample-code.zip Here is some output from FreeBSD when i loaded kernel module with kldload plcm_drv: LPTx Address = 378 plcm0: FreeBSD Device Driver on ppbus0 # ls -l /dev/plcm_drv crw-r--r-- 1 root wheel0, 111 Aug 29 11:43 /dev/plcm_drv Also in LCM-Linux-DOS-sample-code.ziphttp://speedy.sh/DKraQ/LCM-Linux-DOS-sample-code.zip file there is FreeBSD driver and sample code. Sample code does some tests and prints some information on LCD display. So back to OpenBSD part. I'm really confused: Should i just do some lpt programming work or for the first do i need to implement/port an LCM driver? Thanks for your interest and help. Denis 2013/8/26 Steve Fairhead st...@fivetrees.com On 26/08/2013 09:41, Denis Maros wrote: Yes, i'm talking about 2*20 character LCD display connected to 24 pin parallel port on motherboard. I've tried to access this device simply via this command: # echo Test /dev/lpt0 ksh: cannot create /dev/lpt0: Device busy Yeah, failed. Do you suggest any other method/code to try if /dev/lpt0 accessable? I had thought that a driver would be needed cause the vendor had Linux and FreeBSD driver included in CD. By the way that the vendor is Lanner INC and device is FW-7581A. I suspect an LCD module is unlikely to work while driving it as if it were a parallel port printer. The issue is the protocol. A printer uses the Centronics interface e.g.: http://retired.beyondlogic.**org/epp/epp.htmhttp://retired.beyondlogic.org/epp/epp.htm LCD modules vary, but tend to use some variation of the following: http://www.newbiehack.com/**MicrocontrollersABeginnersGuid** eIntroductionandInterfacinganL**CD.aspxhttp://www.newbiehack.com/MicrocontrollersABeginnersGuideIntroductionandInterfacinganLCD.aspx For one thing, an LCD module has commands (to set the mode, clear the display, configuration etc) - it doesn't just take ASCII characters. Using the parallel port however is often just a convenient way of getting some logic-level signals in and out... but you're probably going to need to bit-bang them (i.e. control them individually) yourself, rather than using a parallel-port protocol. HTH, Steve
spamd(8) more persistent greytrapping
Hello folks, Here's a suggested improvement to spamlogd(8) which keeps greytrap entries tarpitted while they keep trying. To this end I modified spamlogd.c so that a known greytrapped host is updated as a greytrap entry in /var/db/spamd on every incoming connection to port 8025. This requires a pf(4) rule that logs incoming connections to this port. In spamd(8)'s default mode, also greylisted hosts connect to this port, so we have to look in the database and not interfere with the greylisting process. In spamd(8)'s blacklist-only mode, this idea could be used to add/update greytrap entries for all blacklisted hosts (so also those from spamd.conf(5)). However, these blacklists often contain false positives and legitimate hosts that are blacklisted for a short period, so this is probably not a good idea. Thoughts? $ diff -u spamlogd.c{.54,} --- spamlogd.c.54 Wed Aug 21 18:13:30 2013 +++ spamlogd.c Thu Aug 29 13:30:58 2013 @@ -21,7 +21,7 @@ * OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. */ -/* watch pf log for mail connections, update whitelist entries. */ +/* watch pf log for mail connections, update spamdb entries. */ #include sys/types.h #include sys/socket.h @@ -33,6 +33,7 @@ #include netinet/in.h #include netinet/in_systm.h #include netinet/ip.h +#include netinet/tcp.h #include arpa/inet.h #include net/pfvar.h @@ -64,6 +65,7 @@ int greylist = 1; FILE *grey = NULL; +u_short spamd_port; u_short sync_port; int syncsend; u_int8_tflag_debug = 0; @@ -74,13 +76,14 @@ pcap_t *hpcap = NULL; struct syslog_data sdata = SYSLOG_DATA_INIT; time_t whiteexp = WHITEEXP; +time_t trapexp = TRAPEXP; extern char*__progname; void logmsg(int , const char *, ...); void sighandler_close(int); intinit_pcap(void); void logpkt_handler(u_char *, const struct pcap_pkthdr *, const u_char *); -intdbupdate(char *, char *); +intdbupdate(char *, char *, int); void usage(void); void @@ -110,9 +113,11 @@ init_pcap(void) { struct bpf_program bpfp; - charfilter[PCAPFSIZ] = ip and port 25 and action pass - and tcp[13]0x12=0x2; + charfilter[PCAPFSIZ]; + snprintf(filter, PCAPFSIZ, ip and (port 25 or %d) and action pass + and tcp[13]0x12=0x2, spamd_port); + if ((hpcap = pcap_open_live(pflogif, PCAPSNAP, 1, PCAPTIMO, errbuf)) == NULL) { logmsg(LOG_ERR, Failed to initialize: %s, errbuf); @@ -157,6 +162,11 @@ const struct ip *ip = NULL; const struct pfloghdr *hdr; char ipstraddr[40] = { '\0' }; + int white = 1; + unsigned int off; + const struct tcphdr *tcp; + unsigned int iplen; + unsigned int port; hdr = (const struct pfloghdr *)sp; if (hdr-length MIN_PFLOG_HDRLEN) { @@ -185,26 +195,34 @@ else if (hdr-dir == PF_OUT !flag_inbound) inet_ntop(af, ip-ip_dst, ipstraddr, sizeof(ipstraddr)); + off = ntohs(ip-ip_off); + if ((off 0x1fff) == 0) { + iplen = ip-ip_hl * 4; + tcp = (const struct tcphdr *)(sp + hdrlen + iplen); + port = ntohs(tcp-th_dport); + if (port == spamd_port) + white = 0; + } } if (ipstraddr[0] != '\0') { - if (hdr-dir == PF_IN) - logmsg(LOG_DEBUG,inbound %s, ipstraddr); - else - logmsg(LOG_DEBUG,outbound %s, ipstraddr); - dbupdate(PATH_SPAMD_DB, ipstraddr); + logmsg(LOG_DEBUG, %s %s %s, + hdr-dir == PF_IN ? inbound : outbound, + white ? white : spamd, + ipstraddr); + dbupdate(PATH_SPAMD_DB, ipstraddr, white); } } int -dbupdate(char *dbname, char *ip) +dbupdate(char *dbname, char *ip, int white) { HASHINFOhashinfo; DBT dbk, dbd; DB *db; struct gdatagd; time_t now; - int r; + int r, mod; struct in_addr ia; now = time(NULL); @@ -224,7 +242,7 @@ dbk.data = ip; memset(dbd, 0, sizeof(dbd)); - /* add or update whitelist entry */ + /* add or update entry */ r = db-get(db, dbk, dbd, 0); if (r == -1) { logmsg(LOG_NOTICE, db-get failed (%m)); @@ -237,27 +255,29 @@ gd.first = now; gd.bcount = 1; gd.pass = now; - gd.expire = now + whiteexp; - memset(dbk, 0, sizeof(dbk)); - dbk.size =
OpenBSD 5.3, CARP and IPv6
Hi everyone, I'm hoping someone can help me as I'm not having much luck with adding IPv6 to the mix of our already working IPv4 setup. What should /etc/hostname.carpX look like for an IPv6 setup? Is this correct;? inet 10.0.10.1 255.255.255.0 10.0.10.255 vhid 1 pass temppass advbase 3 advskew 0 inet6 2a00:7e0:0:a::1 64 Or should I have a separate carpX interface for the IPv6? When I do a tcpdump on the master I see; Aug 29 14:36:56.416723 00:00:5e:00:01:01 01:00:5e:00:00:12 0800 70: CARPv2-advertise 36: vhid=1 advbase=3 advskew=0 demote=33 (DF) [tos 0x10] Aug 29 14:36:56.416736 00:00:5e:00:01:01 33:33:00:00:00:12 86dd 90: fe80::a00:27ff:fe71:f4ca ff02::12: CARPv2-advertise 36: vhid=1 advbase=3 advskew=0 demote=33 Aug 29 14:36:56.420823 08:00:27:71:f4:ca 33:33:00:00:00:01 86dd 86: fe80::1 ff02::1: icmp6: neighbor adv: tgt is fe80::200:5eff:fe00:101 Aug 29 14:36:56.420835 08:00:27:71:f4:ca 33:33:00:00:00:01 86dd 86: fe80::1 ff02::1: icmp6: neighbor adv: tgt is 2a00:77e0:0:a::1 Aug 29 14:36:57.638468 00:00:5e:00:01:01 01:00:5e:00:00:12 0800 70: CARPv2-advertise 36: vhid=1 advbase=3 advskew=100 demote=0 (DF) [tos 0x10] Aug 29 14:36:57.641021 00:00:5e:00:01:01 33:33:00:00:00:12 86dd 90: fe80::a00:27ff:fe88:bc8a ff02::12: CARPv2-advertise 36: vhid=1 advbase=3 advskew=100 demote=0 Aug 29 14:37:01.049324 00:00:5e:00:01:01 01:00:5e:00:00:12 0800 70: CARPv2-advertise 36: vhid=1 advbase=3 advskew=100 demote=0 (DF) [tos 0x10] Aug 29 14:37:01.049685 00:00:5e:00:01:01 33:33:00:00:00:12 86dd 90: fe80::a00:27ff:fe88:bc8a ff02::12: CARPv2-advertise 36: vhid=1 advbase=3 advskew=100 demote=0 Aug 29 14:37:04.458514 00:00:5e:00:01:01 01:00:5e:00:00:12 0800 70: CARPv2-advertise 36: vhid=1 advbase=3 advskew=100 demote=0 (DF) [tos 0x10] Aug 29 14:37:04.462013 00:00:5e:00:01:01 33:33:00:00:00:12 86dd 90: fe80::a00:27ff:fe88:bc8a ff02::12: CARPv2-advertise 36: vhid=1 advbase=3 advskew=100 demote=0 Aug 29 14:37:06.648983 00:00:5e:00:01:01 01:00:5e:00:00:12 0800 70: CARPv2-advertise 36: vhid=1 advbase=3 advskew=0 demote=33 (DF) [tos 0x10] Aug 29 14:37:06.648996 00:00:5e:00:01:01 33:33:00:00:00:12 86dd 90: fe80::a00:27ff:fe71:f4ca ff02::12: CARPv2-advertise 36: vhid=1 advbase=3 advskew=0 demote=33 I can see that the IPv6 CARP messages are using the link local address and not the global IPv6 addresses I have configured? Why?? :( This makes it really hard to write PF files as I would have to write filter rules considering the each physical hosts MAC addresses :( I'm also seeing errors stating that the inet6 carp address I have configured is a duplicate address! Although this could be due to the fact the firewalls are flapping between backup and master and there are going to be multi master periods. net.inet.carp.allow=1 net.inet.carp.preempt=1 net.inet.carp.log=3 net.inet6.ip6.forwarding=1 net.inet6.ip6.redirect=0 net.inet6.ip6.accept_rtadv=0 I am also starting to read Firewalling IPv6 with OpenBSD's pf (packet filter). Thanks for your time, Andy.
Re: OpenBSD 5.3, CARP and IPv6
PS; I don't have MLD capable switches in all locations if that is a factor here regarding CARP messages being via IPv6 Multicast. On Thu 29 Aug 2013 15:57:29 BST, Andy wrote: Hi everyone, I'm hoping someone can help me as I'm not having much luck with adding IPv6 to the mix of our already working IPv4 setup. What should /etc/hostname.carpX look like for an IPv6 setup? Is this correct;? inet 10.0.10.1 255.255.255.0 10.0.10.255 vhid 1 pass temppass advbase 3 advskew 0 inet6 2a00:7e0:0:a::1 64 Or should I have a separate carpX interface for the IPv6? When I do a tcpdump on the master I see; Aug 29 14:36:56.416723 00:00:5e:00:01:01 01:00:5e:00:00:12 0800 70: CARPv2-advertise 36: vhid=1 advbase=3 advskew=0 demote=33 (DF) [tos 0x10] Aug 29 14:36:56.416736 00:00:5e:00:01:01 33:33:00:00:00:12 86dd 90: fe80::a00:27ff:fe71:f4ca ff02::12: CARPv2-advertise 36: vhid=1 advbase=3 advskew=0 demote=33 Aug 29 14:36:56.420823 08:00:27:71:f4:ca 33:33:00:00:00:01 86dd 86: fe80::1 ff02::1: icmp6: neighbor adv: tgt is fe80::200:5eff:fe00:101 Aug 29 14:36:56.420835 08:00:27:71:f4:ca 33:33:00:00:00:01 86dd 86: fe80::1 ff02::1: icmp6: neighbor adv: tgt is 2a00:77e0:0:a::1 Aug 29 14:36:57.638468 00:00:5e:00:01:01 01:00:5e:00:00:12 0800 70: CARPv2-advertise 36: vhid=1 advbase=3 advskew=100 demote=0 (DF) [tos 0x10] Aug 29 14:36:57.641021 00:00:5e:00:01:01 33:33:00:00:00:12 86dd 90: fe80::a00:27ff:fe88:bc8a ff02::12: CARPv2-advertise 36: vhid=1 advbase=3 advskew=100 demote=0 Aug 29 14:37:01.049324 00:00:5e:00:01:01 01:00:5e:00:00:12 0800 70: CARPv2-advertise 36: vhid=1 advbase=3 advskew=100 demote=0 (DF) [tos 0x10] Aug 29 14:37:01.049685 00:00:5e:00:01:01 33:33:00:00:00:12 86dd 90: fe80::a00:27ff:fe88:bc8a ff02::12: CARPv2-advertise 36: vhid=1 advbase=3 advskew=100 demote=0 Aug 29 14:37:04.458514 00:00:5e:00:01:01 01:00:5e:00:00:12 0800 70: CARPv2-advertise 36: vhid=1 advbase=3 advskew=100 demote=0 (DF) [tos 0x10] Aug 29 14:37:04.462013 00:00:5e:00:01:01 33:33:00:00:00:12 86dd 90: fe80::a00:27ff:fe88:bc8a ff02::12: CARPv2-advertise 36: vhid=1 advbase=3 advskew=100 demote=0 Aug 29 14:37:06.648983 00:00:5e:00:01:01 01:00:5e:00:00:12 0800 70: CARPv2-advertise 36: vhid=1 advbase=3 advskew=0 demote=33 (DF) [tos 0x10] Aug 29 14:37:06.648996 00:00:5e:00:01:01 33:33:00:00:00:12 86dd 90: fe80::a00:27ff:fe71:f4ca ff02::12: CARPv2-advertise 36: vhid=1 advbase=3 advskew=0 demote=33 I can see that the IPv6 CARP messages are using the link local address and not the global IPv6 addresses I have configured? Why?? :( This makes it really hard to write PF files as I would have to write filter rules considering the each physical hosts MAC addresses :( I'm also seeing errors stating that the inet6 carp address I have configured is a duplicate address! Although this could be due to the fact the firewalls are flapping between backup and master and there are going to be multi master periods. net.inet.carp.allow=1 net.inet.carp.preempt=1 net.inet.carp.log=3 net.inet6.ip6.forwarding=1 net.inet6.ip6.redirect=0 net.inet6.ip6.accept_rtadv=0 I am also starting to read Firewalling IPv6 with OpenBSD's pf (packet filter). Thanks for your time, Andy.
Re: OpenBSD 5.3, CARP and IPv6
Hello Andy, here is on of my working configuration (OpenBSD 5.2) inet 194.199.X.28 255.255.255.240 NONE inet6 2001:660:abcd:1234::1:1 64 description CARP server carpdev vlan603 vhid 62 advskew 1 carppeer 194.199.X.29 pass x -- Best regards, Loïc BLOT, Engineering UNIX Systems, Security and Networks http://www.unix-experience.fr Le jeudi 29 août 2013 à 16:54 +0100, Andy a écrit : PS; I don't have MLD capable switches in all locations if that is a factor here regarding CARP messages being via IPv6 Multicast. On Thu 29 Aug 2013 15:57:29 BST, Andy wrote: Hi everyone, I'm hoping someone can help me as I'm not having much luck with adding IPv6 to the mix of our already working IPv4 setup. What should /etc/hostname.carpX look like for an IPv6 setup? Is this correct;? inet 10.0.10.1 255.255.255.0 10.0.10.255 vhid 1 pass temppass advbase 3 advskew 0 inet6 2a00:7e0:0:a::1 64 Or should I have a separate carpX interface for the IPv6? When I do a tcpdump on the master I see; Aug 29 14:36:56.416723 00:00:5e:00:01:01 01:00:5e:00:00:12 0800 70: CARPv2-advertise 36: vhid=1 advbase=3 advskew=0 demote=33 (DF) [tos 0x10] Aug 29 14:36:56.416736 00:00:5e:00:01:01 33:33:00:00:00:12 86dd 90: fe80::a00:27ff:fe71:f4ca ff02::12: CARPv2-advertise 36: vhid=1 advbase=3 advskew=0 demote=33 Aug 29 14:36:56.420823 08:00:27:71:f4:ca 33:33:00:00:00:01 86dd 86: fe80::1 ff02::1: icmp6: neighbor adv: tgt is fe80::200:5eff:fe00:101 Aug 29 14:36:56.420835 08:00:27:71:f4:ca 33:33:00:00:00:01 86dd 86: fe80::1 ff02::1: icmp6: neighbor adv: tgt is 2a00:77e0:0:a::1 Aug 29 14:36:57.638468 00:00:5e:00:01:01 01:00:5e:00:00:12 0800 70: CARPv2-advertise 36: vhid=1 advbase=3 advskew=100 demote=0 (DF) [tos 0x10] Aug 29 14:36:57.641021 00:00:5e:00:01:01 33:33:00:00:00:12 86dd 90: fe80::a00:27ff:fe88:bc8a ff02::12: CARPv2-advertise 36: vhid=1 advbase=3 advskew=100 demote=0 Aug 29 14:37:01.049324 00:00:5e:00:01:01 01:00:5e:00:00:12 0800 70: CARPv2-advertise 36: vhid=1 advbase=3 advskew=100 demote=0 (DF) [tos 0x10] Aug 29 14:37:01.049685 00:00:5e:00:01:01 33:33:00:00:00:12 86dd 90: fe80::a00:27ff:fe88:bc8a ff02::12: CARPv2-advertise 36: vhid=1 advbase=3 advskew=100 demote=0 Aug 29 14:37:04.458514 00:00:5e:00:01:01 01:00:5e:00:00:12 0800 70: CARPv2-advertise 36: vhid=1 advbase=3 advskew=100 demote=0 (DF) [tos 0x10] Aug 29 14:37:04.462013 00:00:5e:00:01:01 33:33:00:00:00:12 86dd 90: fe80::a00:27ff:fe88:bc8a ff02::12: CARPv2-advertise 36: vhid=1 advbase=3 advskew=100 demote=0 Aug 29 14:37:06.648983 00:00:5e:00:01:01 01:00:5e:00:00:12 0800 70: CARPv2-advertise 36: vhid=1 advbase=3 advskew=0 demote=33 (DF) [tos 0x10] Aug 29 14:37:06.648996 00:00:5e:00:01:01 33:33:00:00:00:12 86dd 90: fe80::a00:27ff:fe71:f4ca ff02::12: CARPv2-advertise 36: vhid=1 advbase=3 advskew=0 demote=33 I can see that the IPv6 CARP messages are using the link local address and not the global IPv6 addresses I have configured? Why?? :( This makes it really hard to write PF files as I would have to write filter rules considering the each physical hosts MAC addresses :( I'm also seeing errors stating that the inet6 carp address I have configured is a duplicate address! Although this could be due to the fact the firewalls are flapping between backup and master and there are going to be multi master periods. net.inet.carp.allow=1 net.inet.carp.preempt=1 net.inet.carp.log=3 net.inet6.ip6.forwarding=1 net.inet6.ip6.redirect=0 net.inet6.ip6.accept_rtadv=0 I am also starting to read Firewalling IPv6 with OpenBSD's pf (packet filter). Thanks for your time, Andy.
Compiling BOINC/Seti@Home for OpenBSD 5.3 Sparc64
My Sun Blade 100, has a fresh install of 5.3, and its very good, much better than 5.1; XFCE is very stable and R is much better than prior ports. you guys did a great job! Now this computer sits running actively, with nothing to do! So lets run Seti on it, but alas, no recent binary for OpenBSD Sparc64 seems to be found. Thus I tried last night to compile my own, but the _autosetup script fails saying it can't find M4 = 1.4 (not true, I have latest), automake( not true I have latest), autoconf (not true I have latest). The only thing it finds is gmake, which passes. Is there some sort of special tailoring necessary for OpenBSD? Or has someone solved all these issues already and could help me out? Thanks, Richard.
Re: OpenBSD 5.3, CARP and IPv6
Thanks, I'll give that a try. I have got it working with separate CARP interfaces for v4 and v6 but was hoping to have it working under one interface. Cheers, Andy. On Thu 29 Aug 2013 17:13:37 BST, Loïc Blot wrote: Hello Andy, here is on of my working configuration (OpenBSD 5.2) inet 194.199.X.28 255.255.255.240 NONE inet6 2001:660:abcd:1234::1:1 64 description CARP server carpdev vlan603 vhid 62 advskew 1 carppeer 194.199.X.29 pass x
Re: Compiling BOINC/Seti at Home for OpenBSD 5.3 Sparc64
Richard Thornton thornton.richard at gmail.com writes: Is there some sort of special tailoring necessary for OpenBSD? yes, there is. you need to create port of boinc.
Re: OpenBSD 5.3, CARP and IPv6
Penned by Andy on 20130829 9:57.29, we have: | Hi everyone, | | I'm hoping someone can help me as I'm not having much luck with adding | IPv6 to the mix of our already working IPv4 setup. | | What should /etc/hostname.carpX look like for an IPv6 setup? Is this | correct;? | | inet 10.0.10.1 255.255.255.0 10.0.10.255 vhid 1 pass temppass advbase 3 | advskew 0 | inet6 2a00:7e0:0:a::1 64 Any 'inet6' except the first link local reference in a given hostname.if(4) file should be followed by 'alias'. Aka you need: inet6 alias 2a00:7e0:0:a::1 The 64 is implicitly default, if you choose to explicitly list it thats ok too. | Or should I have a separate carpX interface for the IPv6? | | When I do a tcpdump on the master I see; | Aug 29 14:36:56.416723 00:00:5e:00:01:01 01:00:5e:00:00:12 0800 70: | CARPv2-advertise 36: vhid=1 advbase=3 advskew=0 demote=33 (DF) [tos 0x10] | Aug 29 14:36:56.416736 00:00:5e:00:01:01 33:33:00:00:00:12 86dd 90: | fe80::a00:27ff:fe71:f4ca ff02::12: CARPv2-advertise 36: vhid=1 | advbase=3 advskew=0 demote=33 | Aug 29 14:36:56.420823 08:00:27:71:f4:ca 33:33:00:00:00:01 86dd 86: | fe80::1 ff02::1: icmp6: neighbor adv: tgt is fe80::200:5eff:fe00:101 | Aug 29 14:36:56.420835 08:00:27:71:f4:ca 33:33:00:00:00:01 86dd 86: | fe80::1 ff02::1: icmp6: neighbor adv: tgt is 2a00:77e0:0:a::1 | Aug 29 14:36:57.638468 00:00:5e:00:01:01 01:00:5e:00:00:12 0800 70: | CARPv2-advertise 36: vhid=1 advbase=3 advskew=100 demote=0 (DF) [tos 0x10] | Aug 29 14:36:57.641021 00:00:5e:00:01:01 33:33:00:00:00:12 86dd 90: | fe80::a00:27ff:fe88:bc8a ff02::12: CARPv2-advertise 36: vhid=1 | advbase=3 advskew=100 demote=0 | Aug 29 14:37:01.049324 00:00:5e:00:01:01 01:00:5e:00:00:12 0800 70: | CARPv2-advertise 36: vhid=1 advbase=3 advskew=100 demote=0 (DF) [tos 0x10] | Aug 29 14:37:01.049685 00:00:5e:00:01:01 33:33:00:00:00:12 86dd 90: | fe80::a00:27ff:fe88:bc8a ff02::12: CARPv2-advertise 36: vhid=1 | advbase=3 advskew=100 demote=0 | Aug 29 14:37:04.458514 00:00:5e:00:01:01 01:00:5e:00:00:12 0800 70: | CARPv2-advertise 36: vhid=1 advbase=3 advskew=100 demote=0 (DF) [tos 0x10] | Aug 29 14:37:04.462013 00:00:5e:00:01:01 33:33:00:00:00:12 86dd 90: | fe80::a00:27ff:fe88:bc8a ff02::12: CARPv2-advertise 36: vhid=1 | advbase=3 advskew=100 demote=0 | Aug 29 14:37:06.648983 00:00:5e:00:01:01 01:00:5e:00:00:12 0800 70: | CARPv2-advertise 36: vhid=1 advbase=3 advskew=0 demote=33 (DF) [tos 0x10] | Aug 29 14:37:06.648996 00:00:5e:00:01:01 33:33:00:00:00:12 86dd 90: | fe80::a00:27ff:fe71:f4ca ff02::12: CARPv2-advertise 36: vhid=1 | advbase=3 advskew=0 demote=33 | | I can see that the IPv6 CARP messages are using the link local address | and not the global IPv6 addresses I have configured? Why?? :( | This makes it really hard to write PF files as I would have to write | filter rules considering the each physical hosts MAC addresses :( Because multicast is on the local link not on the global addresses? Can you not use pf to filter fe80::/8 address space? | I'm also seeing errors stating that the inet6 carp address I have | configured is a duplicate address! Although this could be due to the | fact the firewalls are flapping between backup and master and there are | going to be multi master periods. I thought at one point there was a commit to ignore duplicate v6 ndp due to this issue. I can't find it right now though, so I don't know if it is in 5.3 or not. | net.inet.carp.allow=1 | net.inet.carp.preempt=1 | net.inet.carp.log=3 | net.inet6.ip6.forwarding=1 | net.inet6.ip6.redirect=0 | net.inet6.ip6.accept_rtadv=0 | | I am also starting to read Firewalling IPv6 with OpenBSD's pf (packet | filter). | | Thanks for your time, Andy. Hope the above helps. -- Todd Fries .. t...@fries.net |\ 1.636.410.0632 (voice) | Free Daemon Consulting, LLC\ 1.405.227.9094 (voice) | http://FreeDaemonConsulting.com\ 1.866.792.3418 (FAX) | PO Box 16169, Oklahoma City, OK 73113-2169 \ sip:freedae...@ekiga.net | ..in support of free software solutions. \ sip:4052279...@ekiga.net \ 37E7 D3EB 74D0 8D66 A68D B866 0326 204E 3F42 004A http://todd.fries.net/pgp.txt
Re: Compiling BOINC/Seti@Home for OpenBSD 5.3 Sparc64
When you run autoconf/automake (from ports at least), they usually say that you should export variables like AUTOCONF_VERSION and AUTOMAKE_VERSION to something like 2.11 or 1.9 or so. For me: $ pkg_info | grep auto autoconf-2.59p3 automatically configure source code on many Un*x platforms autoconf-2.69p0 automatically configure source code on many Un*x platforms automake-1.12.6 GNU Standards-compliant Makefile generator automake-1.13.1 GNU Standards-compliant Makefile generator automake-1.9.6p10 GNU Standards-compliant Makefile generator it would be AUTOCONF_VERSION=2.59 or =2.69 and AUTOMAKE_VERSION=1.12, =1.13 and so on. If you have gotten auto* installed by yourself and not via ports, then reading the output/log from the autosetup would be in order. 2013/8/29 Richard Thornton thornton.rich...@gmail.com My Sun Blade 100, has a fresh install of 5.3, and its very good, much better than 5.1; XFCE is very stable and R is much better than prior ports. you guys did a great job! Now this computer sits running actively, with nothing to do! So lets run Seti on it, but alas, no recent binary for OpenBSD Sparc64 seems to be found. Thus I tried last night to compile my own, but the _autosetup script fails saying it can't find M4 = 1.4 (not true, I have latest), automake( not true I have latest), autoconf (not true I have latest). The only thing it finds is gmake, which passes. Is there some sort of special tailoring necessary for OpenBSD? Or has someone solved all these issues already and could help me out? Thanks, Richard. -- May the most significant bit of your life be positive.
Re: OpenBSD 5.3, CARP and IPv6
On Thu 29 Aug 2013 18:37:53 BST, Todd T. Fries wrote: Penned by Andy on 20130829 9:57.29, we have: | Hi everyone, | | I'm hoping someone can help me as I'm not having much luck with adding | IPv6 to the mix of our already working IPv4 setup. | | What should /etc/hostname.carpX look like for an IPv6 setup? Is this | correct;? | | inet 10.0.10.1 255.255.255.0 10.0.10.255 vhid 1 pass temppass advbase 3 | advskew 0 | inet6 2a00:7e0:0:a::1 64 Any 'inet6' except the first link local reference in a given hostname.if(4) file should be followed by 'alias'. Aka you need: inet6 alias 2a00:7e0:0:a::1 The 64 is implicitly default, if you choose to explicitly list it thats ok too. Ah, of course! I have a ton of IPv4 alias', but I didn't think to just add an IPv6 alias :) | Or should I have a separate carpX interface for the IPv6? | | When I do a tcpdump on the master I see; | Aug 29 14:36:56.416723 00:00:5e:00:01:01 01:00:5e:00:00:12 0800 70: | CARPv2-advertise 36: vhid=1 advbase=3 advskew=0 demote=33 (DF) [tos 0x10] | Aug 29 14:36:56.416736 00:00:5e:00:01:01 33:33:00:00:00:12 86dd 90: | fe80::a00:27ff:fe71:f4ca ff02::12: CARPv2-advertise 36: vhid=1 | advbase=3 advskew=0 demote=33 | Aug 29 14:36:56.420823 08:00:27:71:f4:ca 33:33:00:00:00:01 86dd 86: | fe80::1 ff02::1: icmp6: neighbor adv: tgt is fe80::200:5eff:fe00:101 | Aug 29 14:36:56.420835 08:00:27:71:f4:ca 33:33:00:00:00:01 86dd 86: | fe80::1 ff02::1: icmp6: neighbor adv: tgt is 2a00:77e0:0:a::1 | Aug 29 14:36:57.638468 00:00:5e:00:01:01 01:00:5e:00:00:12 0800 70: | CARPv2-advertise 36: vhid=1 advbase=3 advskew=100 demote=0 (DF) [tos 0x10] | Aug 29 14:36:57.641021 00:00:5e:00:01:01 33:33:00:00:00:12 86dd 90: | fe80::a00:27ff:fe88:bc8a ff02::12: CARPv2-advertise 36: vhid=1 | advbase=3 advskew=100 demote=0 | Aug 29 14:37:01.049324 00:00:5e:00:01:01 01:00:5e:00:00:12 0800 70: | CARPv2-advertise 36: vhid=1 advbase=3 advskew=100 demote=0 (DF) [tos 0x10] | Aug 29 14:37:01.049685 00:00:5e:00:01:01 33:33:00:00:00:12 86dd 90: | fe80::a00:27ff:fe88:bc8a ff02::12: CARPv2-advertise 36: vhid=1 | advbase=3 advskew=100 demote=0 | Aug 29 14:37:04.458514 00:00:5e:00:01:01 01:00:5e:00:00:12 0800 70: | CARPv2-advertise 36: vhid=1 advbase=3 advskew=100 demote=0 (DF) [tos 0x10] | Aug 29 14:37:04.462013 00:00:5e:00:01:01 33:33:00:00:00:12 86dd 90: | fe80::a00:27ff:fe88:bc8a ff02::12: CARPv2-advertise 36: vhid=1 | advbase=3 advskew=100 demote=0 | Aug 29 14:37:06.648983 00:00:5e:00:01:01 01:00:5e:00:00:12 0800 70: | CARPv2-advertise 36: vhid=1 advbase=3 advskew=0 demote=33 (DF) [tos 0x10] | Aug 29 14:37:06.648996 00:00:5e:00:01:01 33:33:00:00:00:12 86dd 90: | fe80::a00:27ff:fe71:f4ca ff02::12: CARPv2-advertise 36: vhid=1 | advbase=3 advskew=0 demote=33 | | I can see that the IPv6 CARP messages are using the link local address | and not the global IPv6 addresses I have configured? Why?? :( | This makes it really hard to write PF files as I would have to write | filter rules considering the each physical hosts MAC addresses :( Because multicast is on the local link not on the global addresses? Can you not use pf to filter fe80::/8 address space? Actually yes that would be OK as it's only local to the link... I was thinking I would have to filter the individual EUI64 addresses meaning I would have had to do something with puppet to pull MAC's etc.. But fe80::/8 should be ok thinking about it. Thanks. | I'm also seeing errors stating that the inet6 carp address I have | configured is a duplicate address! Although this could be due to the | fact the firewalls are flapping between backup and master and there are | going to be multi master periods. I thought at one point there was a commit to ignore duplicate v6 ndp due to this issue. I can't find it right now though, so I don't know if it is in 5.3 or not. Now you mention it, I think I saw that in the release notes for -current (so should be 5.4). I'll ignore it for now. Thanks. | net.inet.carp.allow=1 | net.inet.carp.preempt=1 | net.inet.carp.log=3 | net.inet6.ip6.forwarding=1 | net.inet6.ip6.redirect=0 | net.inet6.ip6.accept_rtadv=0 | | I am also starting to read Firewalling IPv6 with OpenBSD's pf (packet | filter). | | Thanks for your time, Andy. Hope the above helps. Thanks Todd, yes it does :) Can you recommend anything else that should be done for IPv6 filtering/forwarding other than the pf rules themselves? First time doing IPv6 on OBSD. Cheers, Andy.
Re: OpenBSD 5.3, CARP and IPv6
On Thu, Aug 29, 2013 at 08:35:48PM +0100, Andy wrote: On Thu 29 Aug 2013 18:37:53 BST, Todd T. Fries wrote: Penned by Andy on 20130829 9:57.29, we have: | I'm also seeing errors stating that the inet6 carp address I have | configured is a duplicate address! Although this could be due to the | fact the firewalls are flapping between backup and master and there are | going to be multi master periods. I thought at one point there was a commit to ignore duplicate v6 ndp due to this issue. I can't find it right now though, so I don't know if it is in 5.3 or not. Now you mention it, I think I saw that in the release notes for -current (so should be 5.4). I'll ignore it for now. Thanks. Probably this commit, which is in 5.4: http://marc.info/?l=openbsd-cvsm=136227095604126w=2
Re: Compiling BOINC/Seti@Home for OpenBSD 5.3 Sparc64
Richard Thornton thornton.rich...@gmail.com wrote: My Sun Blade 100, has a fresh install of 5.3, and its very good, much better than 5.1; XFCE is very stable and R is much better than prior ports. you guys did a great job! Now this computer sits running actively, with nothing to do! Use apm -L or -C and save 10 W. -- Christian naddy Weisgerber na...@mips.inka.de
Re: Compiling BOINC/Seti@Home for OpenBSD 5.3 Sparc64
On 08/29/13 22:11, Christian Weisgerber wrote: Richard Thornton thornton.rich...@gmail.com wrote: My Sun Blade 100, has a fresh install of 5.3, and its very good, much better than 5.1; XFCE is very stable and R is much better than prior ports. you guys did a great job! Now this computer sits running actively, with nothing to do! Use apm -L or -C and save 10 W. Or power it off entirely? :-P
Re: Compiling BOINC/Seti at Home for OpenBSD 5.3 Sparc64
Christian Weisgerber naddy at mips.inka.de writes: Richard Thornton thornton.richard at gmail.com wrote: My Sun Blade 100, has a fresh install of 5.3, and its very good, much better than 5.1; XFCE is very stable and R is much better than prior ports. you guys did a great job! Now this computer sits running actively, with nothing to do! Use apm -L or -C and save 10 W. Wonder why keep running something doing nothing ;)
Re: OpenBSD 5.3, CARP and IPv6
Penned by Andy on 20130829 14:35.48, we have: | On Thu 29 Aug 2013 18:37:53 BST, Todd T. Fries wrote: | Penned by Andy on 20130829 9:57.29, we have: | | Hi everyone, | | | | I'm hoping someone can help me as I'm not having much luck with adding | | IPv6 to the mix of our already working IPv4 setup. | | | | What should /etc/hostname.carpX look like for an IPv6 setup? Is this | | correct;? | | | | inet 10.0.10.1 255.255.255.0 10.0.10.255 vhid 1 pass temppass advbase 3 | | advskew 0 | | inet6 2a00:7e0:0:a::1 64 | | Any 'inet6' except the first link local reference in a given hostname.if(4) | file should be followed by 'alias'. | | Aka you need: | | inet6 alias 2a00:7e0:0:a::1 | | The 64 is implicitly default, if you choose to explicitly list it thats ok too. | | | Ah, of course! I have a ton of IPv4 alias', but I didn't think to | just add an IPv6 alias :) | | | Or should I have a separate carpX interface for the IPv6? | | | | When I do a tcpdump on the master I see; | | Aug 29 14:36:56.416723 00:00:5e:00:01:01 01:00:5e:00:00:12 0800 70: | | CARPv2-advertise 36: vhid=1 advbase=3 advskew=0 demote=33 (DF) [tos 0x10] | | Aug 29 14:36:56.416736 00:00:5e:00:01:01 33:33:00:00:00:12 86dd 90: | | fe80::a00:27ff:fe71:f4ca ff02::12: CARPv2-advertise 36: vhid=1 | | advbase=3 advskew=0 demote=33 | | Aug 29 14:36:56.420823 08:00:27:71:f4:ca 33:33:00:00:00:01 86dd 86: | | fe80::1 ff02::1: icmp6: neighbor adv: tgt is fe80::200:5eff:fe00:101 | | Aug 29 14:36:56.420835 08:00:27:71:f4:ca 33:33:00:00:00:01 86dd 86: | | fe80::1 ff02::1: icmp6: neighbor adv: tgt is 2a00:77e0:0:a::1 | | Aug 29 14:36:57.638468 00:00:5e:00:01:01 01:00:5e:00:00:12 0800 70: | | CARPv2-advertise 36: vhid=1 advbase=3 advskew=100 demote=0 (DF) [tos 0x10] | | Aug 29 14:36:57.641021 00:00:5e:00:01:01 33:33:00:00:00:12 86dd 90: | | fe80::a00:27ff:fe88:bc8a ff02::12: CARPv2-advertise 36: vhid=1 | | advbase=3 advskew=100 demote=0 | | Aug 29 14:37:01.049324 00:00:5e:00:01:01 01:00:5e:00:00:12 0800 70: | | CARPv2-advertise 36: vhid=1 advbase=3 advskew=100 demote=0 (DF) [tos 0x10] | | Aug 29 14:37:01.049685 00:00:5e:00:01:01 33:33:00:00:00:12 86dd 90: | | fe80::a00:27ff:fe88:bc8a ff02::12: CARPv2-advertise 36: vhid=1 | | advbase=3 advskew=100 demote=0 | | Aug 29 14:37:04.458514 00:00:5e:00:01:01 01:00:5e:00:00:12 0800 70: | | CARPv2-advertise 36: vhid=1 advbase=3 advskew=100 demote=0 (DF) [tos 0x10] | | Aug 29 14:37:04.462013 00:00:5e:00:01:01 33:33:00:00:00:12 86dd 90: | | fe80::a00:27ff:fe88:bc8a ff02::12: CARPv2-advertise 36: vhid=1 | | advbase=3 advskew=100 demote=0 | | Aug 29 14:37:06.648983 00:00:5e:00:01:01 01:00:5e:00:00:12 0800 70: | | CARPv2-advertise 36: vhid=1 advbase=3 advskew=0 demote=33 (DF) [tos 0x10] | | Aug 29 14:37:06.648996 00:00:5e:00:01:01 33:33:00:00:00:12 86dd 90: | | fe80::a00:27ff:fe71:f4ca ff02::12: CARPv2-advertise 36: vhid=1 | | advbase=3 advskew=0 demote=33 | | | | I can see that the IPv6 CARP messages are using the link local address | | and not the global IPv6 addresses I have configured? Why?? :( | | This makes it really hard to write PF files as I would have to write | | filter rules considering the each physical hosts MAC addresses :( | | Because multicast is on the local link not on the global addresses? | | Can you not use pf(4) to filter fe80::/8 address space? | Actually yes that would be OK as it's only local to the link... I | was thinking I would have to filter the individual EUI64 addresses | meaning I would have had to do something with puppet to pull MAC's | etc.. But fe80::/8 should be ok thinking about it. Thanks. | | | | I'm also seeing errors stating that the inet6 carp address I have | | configured is a duplicate address! Although this could be due to the | | fact the firewalls are flapping between backup and master and there are | | going to be multi master periods. | | I thought at one point there was a commit to ignore duplicate v6 ndp | due to this issue. I can't find it right now though, so I don't know | if it is in 5.3 or not. | Now you mention it, I think I saw that in the release notes for | -current (so should be 5.4). I'll ignore it for now. Thanks. | | | | net.inet.carp.allow=1 | | net.inet.carp.preempt=1 | | net.inet.carp.log=3 | | net.inet6.ip6.forwarding=1 | | net.inet6.ip6.redirect=0 | | net.inet6.ip6.accept_rtadv=0 | | | | I am also starting to read Firewalling IPv6 with OpenBSD's pf(4) (packet | | filter). | | | | Thanks for your time, Andy. | | Hope the above helps. | | Thanks Todd, yes it does :) Can you recommend anything else that | should be done for IPv6 filtering/forwarding other than the pf(4) rules | themselves? First time doing IPv6 on OBSD. You have to be careful to not filter icmp6(4) on the link local multicast subnets. Aka ff02::/8 .. both source and destination. If you wish to filter out some icmp6(4) messages be sure you permit those that make ndp work (neighbrsol/neighbradv specifically) then there's toobig, unrach, echoreq, echorep, fqndreq
Re: Compiling BOINC/Seti at Home for OpenBSD 5.3 Sparc64
On 8/29/2013 4:15 PM, Alexey E. Suslikov wrote: Christian Weisgerber naddy at mips.inka.de writes: Richard Thornton thornton.richard at gmail.com wrote: My Sun Blade 100, has a fresh install of 5.3, and its very good, much better than 5.1; XFCE is very stable and R is much better than prior ports. you guys did a great job! Now this computer sits running actively, with nothing to do! Use apm -L or -C and save 10 W. Wonder why keep running something doing nothing ;) Still happily married I see. (:
submit.cf sendmail.cf configuration
I have a simple OpenBSD 5.3 Sparc 64 box, which runs very well, given it is 12+ years old. I would like to set it up so I could send email from it, and receive email, since I do have a personal domain name,which I could point to my house IP, if desired. The documentation is wonderful, somehow it should be relatively simple,to edit the proper config files. Any help from anyone, or is there a good link you could provide, which explainshow to do this? In years past, I used to use other systems even Solaris 9, and I knew nothing, but was able tofigure out what to do, but OpenBSD seems harder to me for this problem. Thanks for any pleasant help.
Watchdog timeout with MSI and Realtek 8101E on Dell Inspiron 3521 (amd64)
After upgrading from the July 25 to the August 24 snapshot (amd64), I started getting re0: watchdog timeout messages from the system when sending files via re0. This seems to be caused by MSI being enabled in sys/dev/pci/if_re_pci.c beginning of August. Upgrading the BIOS to the latest version (A09) did not solve the issue. As a quick fix I am currently running a GENERIC.MP kernel (CVS from two days ago) with the following patch, disabling MSI for the device. The re0 interface behaves properly again. --- sys/dev/pci/if_re_pci.c.origThu Aug 29 21:46:24 2013 +++ sys/dev/pci/if_re_pci.c Thu Aug 29 21:59:21 2013 @@ -135,10 +135,7 @@ re_pci_attach(struct device *parent, struct device *se pci_intr_handle_t ih; const char *intrstr = NULL; - /* Only enable MSI on RT810xE for now. */ - if (PCI_VENDOR(pa-pa_id) != PCI_VENDOR_REALTEK || - PCI_PRODUCT(pa-pa_id) != PCI_PRODUCT_REALTEK_RT8101E) - pa-pa_flags = ~PCI_FLAGS_MSI_ENABLED; + pa-pa_flags = ~PCI_FLAGS_MSI_ENABLED; pci_set_powerstate(pa-pa_pc, pa-pa_tag, PCI_PMCSR_STATE_D0); I only have one computer of this model, and no other with the Realtek 8101E, so I cannot confirm that my hardware is not partly broken. Has anyone experienced this problem with this computer model / chipset? Below some more information: # details about the timeouts # dmesg for July 25 snapshot # dmesg for August 24 snapshot # pcidump # details about the timeouts The timeouts messages coincide with a period of unavailability of the network - roughly 5 to 7 seconds - and occur when data is sent to the network (e.g. uploading files to a remote host). For the same quantity of data being sent, tests indicate that the number of watchdog timeouts increases with the transfer speed. Some figures: 3165 MB file @ 8MB/s : avg. 14 watchdog timeouts 3165 MB file @ 1MB/s : avg. 3 watchdog timeouts 3165 MB file @ 128KB/s : no timeout (yet) So far I have not seen such timeout occurring when receiving files, regardless of the quantity of data or the transfer speed. # dmesg for July 25 snapshot OpenBSD 5.4 (GENERIC.MP) #37: Thu Jul 25 18:51:42 MDT 2013 dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP real mem = 4147896320 (3955MB) avail mem = 4029747200 (3843MB) mainbus0 at root bios0 at mainbus0: SMBIOS rev. 2.7 @ 0xe6c00 (70 entries) bios0: vendor Dell Inc. version A04 date 11/21/2012 bios0: Dell Inc. Inspiron 3521 acpi0 at bios0: rev 2 acpi0: sleep states S0 S3 S4 S5 acpi0: tables DSDT FACP SLIC UEFI ASF! HPET APIC MCFG SLIC SSDT BOOT ASPT DBGP FPDT MSDM SSDT SSDT acpi0: wakeup devices P0P1(S0) EHC1(S0) XHC_(S0) RP01(S3) RP02(S0) PEG0(S4) PEGP(S4) PEG1(S4) PEG2(S4) PEG3(S4) LID0(S3) acpitimer0 at acpi0: 3579545 Hz, 24 bits acpihpet0 at acpi0: 14318179 Hz acpimadt0 at acpi0 addr 0xfee0: PC-AT compat cpu0 at mainbus0: apid 0 (boot processor) cpu0: Intel(R) Core(TM) i3-3217U CPU @ 1.80GHz, 1696.41 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,PCLMUL,DTES64,MWAIT,DS-CPL,VMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,x2APIC,POPCNT,DEADLINE,XSAVE,AVX,F16C,NXE,LONG,LAHF,PERF,ITSC,FSGSBASE,SMEP,ERMS cpu0: 256KB 64b/line 8-way L2 cache cpu0: smt 0, core 0, package 0 cpu0: apic clock running at 99MHz cpu1 at mainbus0: apid 1 (application processor) cpu1: Intel(R) Core(TM) i3-3217U CPU @ 1.80GHz, 1696.15 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,PCLMUL,DTES64,MWAIT,DS-CPL,VMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,x2APIC,POPCNT,DEADLINE,XSAVE,AVX,F16C,NXE,LONG,LAHF,PERF,ITSC,FSGSBASE,SMEP,ERMS cpu1: 256KB 64b/line 8-way L2 cache cpu1: smt 1, core 0, package 0 cpu2 at mainbus0: apid 2 (application processor) cpu2: Intel(R) Core(TM) i3-3217U CPU @ 1.80GHz, 1696.15 MHz cpu2: 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,PCLMUL,DTES64,MWAIT,DS-CPL,VMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,x2APIC,POPCNT,DEADLINE,XSAVE,AVX,F16C,NXE,LONG,LAHF,PERF,ITSC,FSGSBASE,SMEP,ERMS cpu2: 256KB 64b/line 8-way L2 cache cpu2: smt 0, core 1, package 0 cpu3 at mainbus0: apid 3 (application processor) cpu3: Intel(R) Core(TM) i3-3217U CPU @ 1.80GHz, 1696.15 MHz cpu3: 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,PCLMUL,DTES64,MWAIT,DS-CPL,VMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,x2APIC,POPCNT,DEADLINE,XSAVE,AVX,F16C,NXE,LONG,LAHF,PERF,ITSC,FSGSBASE,SMEP,ERMS cpu3: 256KB 64b/line 8-way L2 cache cpu3: smt 1, core 1, package 0 ioapic0 at mainbus0: apid 0 pa 0xfec0, version 20, 24 pins acpimcfg0 at acpi0 addr 0xe000, bus 0-255 acpiprt0 at acpi0: bus 0 (PCI0) acpiprt1 at acpi0: bus -1 (P0P1) acpiprt2 at acpi0: bus 1 (RP01) acpiprt3 at acpi0:
Re: submit.cf sendmail.cf configuration
On 08/27/13 16:30, rich...@thornton.net wrote: I have a simple OpenBSD 5.3 Sparc 64 box, which runs very well, given it is 12+ years old. I would like to set it up so I could send email from it, and receive email, since I do have a personal domain name,which I could point to my house IP, if desired. (assuming they don't block port 25 at home, like they do to me) The documentation is wonderful, somehow it should be relatively simple,to edit the proper config files. Any help from anyone, or is there a good link you could provide, which explainshow to do this? In years past, I used to use other systems even Solaris 9, and I knew nothing, but was able tofigure out what to do, but OpenBSD seems harder to me for this problem. Thanks for any pleasant help. Actually, the basic OpenBSD sendmail config is very easy. Maybe too easy. Running a mail server is not easy, and the sendmail config is not the hardest part. See rc.conf, set the line in rc.conf.local as indicated for normal use. Add domain(s) to /etc/mail/local-host-domains. Restart. Done. It's a moderately safe and sound default config. See /etc/mail/README. The rest is standard sendmail, which ain't easy at all (but it isn't your biggest problem) Even easier is opensmtpd. See man smtpd and man smtpd.conf That being said... unless you are trying to keep in practice for debugging e-mail problems, you don't want to run your own mail service. Really, you don't. I run my own, I've run mail for the previous two jobs I had, and it just isn't fun anymore. Nick.
Re: submit.cf sendmail.cf configuration
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 08/27/2013 01:30 PM, rich...@thornton.net wrote: I have a simple OpenBSD 5.3 Sparc 64 box, which runs very well, given it is 12+ years old. I would like to set it up so I could send email from it, and receive email, since I do have a personal domain name,which I could point to my house IP, if desired. The documentation is wonderful, somehow it should be relatively simple,to edit the proper config files. Any help from anyone, or is there a good link you could provide, which explainshow to do this? In years past, I used to use other systems even Solaris 9, and I knew nothing, but was able tofigure out what to do, but OpenBSD seems harder to me for this problem. Thanks for any pleasant help. Just check your rc.d, related to sendmail. Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iQEcBAEBAgAGBQJSIAkOAAoJEP15gZz9zQxwRxoIAJhRAN5aSoFoe8s7xJOfKP+Y /YJ8HhBNVLb1L+Ht6VXXw3KNllLNah06H70FMOk98yMnDC673gcUd6h+C0tyR5aV KBn659zi7db++KkDXU8h5YMQAIB93IWe6tBeBggRRbC+qk0WtX31yLPnOoSRN/xH zRAUZ95s3DB3MIbZM44a24gEd3Nsw37j6LfPrGfWSa2sbIKIzRPrdjHPXLZVT4d9 hl4hjgGW+3eNVhBFPNUex7H6MO78IjcRkY0FT3GMxA4xyel6FOmIRBF04FGTI6/p s8+DcpXugCciafgLOUY5OeOEVlloiGRnZpii1TbsgLN10J4iUoH2w4QOlQm4eBo= =YdNr -END PGP SIGNATURE-
Re: submit.cf sendmail.cf configuration
rich...@thornton.net wrote: I have a simple OpenBSD 5.3 Sparc 64 box, which runs very well, given it is 12+ years old. I would like to set it up so I could send email from it, and receive email, since I do have a personal domain name,which I could point to my house IP, if desired. The documentation is wonderful, somehow it should be relatively simple,to edit the proper config files. Any help from anyone, or is there a good link you could provide, which explainshow to do this? In years past, I used to use other systems even Solaris 9, and I knew nothing, but was able tofigure out what to do, but OpenBSD seems harder to me for this problem. Thanks for any pleasant help. man smtpd Really. And, like Nick points out, make sure port 25 isn't blocked. Here, it's blocked for outgoing but not incoming, whis is fair enough. /Alexander