Re: Looking for good, small, canadian version laptop suggestions
On 10/14/2013 10:53 PM, Adam Thompson wrote: On 2013-10-12 06:01, g.lister wrote: Interesting. I always feel that I am getting ripped off when buying something refurbished but then again I find my stuff which I bought many years ago still works and is easier to install stuff on (things I care about anyway) and now when looking around I find the new stuff has some major improvements which might come in handy (graphics, CPU, faster RAM) if I settle for the off the shelf stuff (Win* or OS X) but since I don't I have to poke around more to find what I like. I guess I should look as well on refurbished stuff and they come with a warranty, isn't it usually shorter? Replacing a hard drive and adding some more ram plus the right OS may make it into a livable solution. At the end one uses the software. My old Sony is kind of like that lots of things will never work, read webcam, but overall it has proven to be a well made laptop. I also got a more recent Dell, XPS I think, for my significant other and that one is also quite good it has sustained mass impact from some kid handling and is still running. As I said already, buying a consumer-grade laptop new from your local big box retailer generally gets you a one-year warranty. Whereas buying a refurb laptop from a reputable supplier (such as Dell Financial Services, in both Canada USA) gets you a ... one-year warranty :-). You are not getting cutting-edge equipment. But in the case of running *anything* other than OS that comes loaded on the laptop, that's a *good* thing, not a bad thing. I can't even run Windows 7 properly on the vast majority of laptops I can buy at Best Buy today, why would I expect to be able to run OpenBSD? Whereas anything refurb is generally far enough behind the trailing edge that the drivers are already built-in to the OS. I can install Win7 onto a Latitude E4500 and 99% of the drivers will work out of the box. Maybe I don't get the absolute maximum set of functionality, but everything works. I can also install OpenBSD onto a Latitude E4500 and get the same level of functionality. (Assuming you connect to Ethernet at first, to auto-download the Broadcom wireless firmware during first boot.) Keep in mind that although you aren't getting the latest CPU, that's mostly irrelevant today - and especially so for OpenBSD. You aren't getting ripped off when buying from DFS, because they're only charging you (roughly) 1/n of the original price, where n = laptop_age_in_years. Those $299 deals they have for 3-year-old laptops are mostly for units that cost around $1500 brand new! Right now, DFS Canada has several laptops with 8GB of RAM for under $800. How much more would you like to put into it?!? Only the very newest laptops can take more than that anyway! Also, buying business-grade laptops is a sound investment because you don't have to replace them as often. In my experience, the average consumer-grade laptop (including Dell Inspiron and Lenovo IdeaPad) lasts one year, or maybe two if you don't carry it around and don't abuse it at all. The average business-grade laptop (Dell Latitude, Lenovo ThinkPad) lasts about three years under heavy use and abuse, and can last up to five years if handled gently. I do recommend switching out the HDD and installing an SSD just so you never have to worry about crashing the disk if you drop it. Also, a Core 2 Duo with an SSD and enough RAM (4Gb+) usually feels like a quad-core i7 with a 5400rpm HDD and 2Gb RAM... reinforcing my point about CPU horsepower, above. I *prefer* to buy refurb because I know I'm not going to get ripped open on the cutting edge, especially when it comes to running various UNIXes on the hardware. Good luck with your quest, regardless. (FYI: that solar-powered laptop, while nifty, is unlikely to work 100% with OpenBSD - the components will likely be too new and support will be lacking. OTOH, the screenshots show Ubuntu Linux, so I could be wrong here.) Thanks Adam. No I do not need a super power thing, lower battery life and higher weight plus noise, that is what it usually translates to anyway. Your proposition is very sound and confirms my findings and experience so I will just take your advice and check-out some of the older machines instead and the dfs link is a find. The solar laptop should run Ubuntu so maybe it will run OpenBSD or another BSD. Thanks for your input! Cheers, George
Re: Sorry OpenBSD people, been a bit busy
Op Wed, 09 Oct 2013 00:01:13 +0200 schreef Scott McEachern sc...@blackstaff.ca: On 10/08/13 16:41, Kevin Chadwick wrote: Back in the pre-WW2 days, Belgium (or was it the Netherlands? I forget.) kept detailed census and medical data on their citizens, including their religious affiliation. It was useful data for a friendly government, never to be abused. I don't know about Belgium, but certainly in the Netherlands local authorities were required to keep resident registration, except at that time not medical data. Then WW2 happened, and Hitler's Nazis invaded. They found that data, especially the religion part, quite useful, and we all know how that turned out. The problem was not that the data existed, the problem was that there wasn't a general preparedness to hide, evacuate or destroy it when justified. -- (Remove the obvious prefix to reply privately.) Gemaakt met Opera's e-mailprogramma: http://www.opera.com/mail/
Re: Sorry OpenBSD people, been a bit busy
Yes, the US government has a long history of abusing its Constitutional powers. That's why we must all hide all of our personal data from them as much as possible. Of course Google, Bing, Facebook and all those selfies we take are excepted. BWAAHHAHAHAHAHAHAHAHAHAHAH morons! On Wed, Oct 16, 2013, at 06:19 AM, Boudewijn Dijkstra wrote: Op Wed, 09 Oct 2013 00:01:13 +0200 schreef Scott McEachern sc...@blackstaff.ca: On 10/08/13 16:41, Kevin Chadwick wrote: Back in the pre-WW2 days, Belgium (or was it the Netherlands? I forget.) kept detailed census and medical data on their citizens, including their religious affiliation. It was useful data for a friendly government, never to be abused. I don't know about Belgium, but certainly in the Netherlands local authorities were required to keep resident registration, except at that time not medical data. Then WW2 happened, and Hitler's Nazis invaded. They found that data, especially the religion part, quite useful, and we all know how that turned out. The problem was not that the data existed, the problem was that there wasn't a general preparedness to hide, evacuate or destroy it when justified. -- (Remove the obvious prefix to reply privately.) Gemaakt met Opera's e-mailprogramma: http://www.opera.com/mail/
Re: Sorry OpenBSD people, been a bit busy
Please stop.
Re: Looking for good, small, canadian version laptop suggestions
I have purchased over 20 machines (about 50% laptop) from dfsdirectsales.com over the last 5 years, and most of them had next day business support still in effect from Dell. I had only one machine that needed service (a Latitude E6510,) and it was repaired at no charge within 2 days. Also, please use your favorite search engine to look for dfs coupon codes. I have saved as much as 50% (usually 25 - 30%) using the code at checkout. Retail me not has legitimate codes. I copy the code I want to use and paste and apply it when I check out. The discount will show, if the code is valid. A nice customer service rep at DFS Direct Sales told me about the coupons, so it's not a scam. I have been shopping at the US site. Good luck with your purchase, Gilbert
npppd / pppoe server troubles
Hello,
I meet some troubles on setup a PPPOE server with npppd daemon. I've
done some
test on release and snaptshot and had differents problems.
First my config files..
#/etc/nppp/npppd-users :
taro:\
:password=taro:\
:framed-ip-address=10.0.0.101:
#/etc/npppd/npppd.conf :
authentication LOCAL type local {
users-file /etc/npppd/npppd-users
}
tunnel POE_ipv4 protocol pppoe {
listen on interface em0
}
ipcp IPCP {
pool-address 10.0.0.2-10.0.0.254
dns-servers 8.8.8.8
}
interface tun0 address 10.0.0.1 ipcp IPCP
bind tunnel from POE_ipv4 authenticated by LOCAL to tun0
### On OBSD 5.3 release :
network logs :
11:46:15.756957 PPPoE-Discovery
code Initiation, version 1, type 1, id 0x, length 12
tag Service-Name, length 0
tag Host-Uniq, length 4 \005\024G\212
npppd logs :
2013-10-16 11:52:09:NOTICE: Starting npppd pid=14540 version=5.0.0
2013-10-16 11:52:09:NOTICE: Load configuration
from='/etc/npppd/npppd.conf' successfully.
2013-10-16 11:52:09:INFO: tun0 Started ip4addr=10.0.0.1
2013-10-16 11:52:09:INFO: Listening /var/run/npppd_ctl (npppd_ctl)
2013-10-16 11:52:09:INFO: ipcp=IPCP pool
dyn_pool=[10.0.0.2/31,10.0.0.4/30,10.0.0.8/29,10.0.0.16/28,10.0.0.32/27,10.0.0.64/26,10.0.0.128/26,10.0.0.192/27,10.0.0.224/28,10.0.0.240/29,10.0.0.248/30,10.0.0.252/31,10.0.0.254/32] pool=[10.0.0.2/31,10.0.0.4/30,10.0.0.8/29,10.0.0.16/28,10.0.0.32/27,10.0.0.64/26,10.0.0.128/26,10.0.0.192/27,10.0.0.224/28,10.0.0.240/29,10.0.0.248/30,10.0.0.252/31,10.0.0.254/32]
2013-10-16 11:52:09:INFO: Added 13 routes for new pool addresses
2013-10-16 11:52:09:INFO: Loading pool config successfully.
2013-10-16 11:52:09:INFO: pppoed Listening on em0 (PPPoE) [POE_ipv4]
using=/dev/bpf1 address=18:03:73:2e:cc:62
Segmentation fault
After de DISCOVERY message the server crash with Segmentation fault
### On OBSD 5.3 snapshot (2weeks ago version) :
I'm doing some tests last night and got other problems. I don't have
my snapshots stations here but the symptom is :
npppd logs side somthings like that :
...unable to agree auth proto...
Network side :
request.reject when client propose pap or chap or whatever.
I 'll give you full log tonight.
Is someone have some idea ?
Thanks
Bruno
virtio network driver multicast support
Hello, folks! Is IP multicast supported by virtio network driver on OpenBSD 5.3? pfsync is not working when using vio interface with IP multicast. When I set pfsync using syncpeer it works fine. pfsync works when using em interface with IP multicast. The test bed is a couple of virtual machine running on Linux KVM. Thank you! Jorge Peixoto
new queueing subsystem
Hello misc, The changes in the pf queueing subsystem (for some reason not mentioned in the http://openbsd.org/faq/upgrade54.html) are getting me worried. Couldn't find the word altq in the http://www.openbsd.org/cgi-bin/man.cgi?query=pf.confapropos=0sektion=0manpath=OpenBSD+Currentarch=i386format=html. Is the old queueing gone? Is existing pf.conf not going to work with 5.4? How is the new queueing work? The manual gives the syntax (quite limited comparing to the altq - in my opinion), but doesn't really explain anything. For example - is there a bandwidth borrowing and how is it prioritizing? -- Best regards, Boris mailto:bo...@twopoint.com
Re: new queueing subsystem
On Wed, Oct 16, 2013 at 8:08 AM, Boris Goldberg bo...@twopoint.com wrote: Hello misc, The changes in the pf queueing subsystem (for some reason not mentioned in the http://openbsd.org/faq/upgrade54.html) are getting me worried. Couldn't find the word altq in the http://www.openbsd.org/cgi-bin/man.cgi?query=pf.confapropos=0sektion=0manpath=OpenBSD+Currentarch=i386format=html. Is the old queueing gone? Is existing pf.conf not going to work with 5.4? How is the new queueing work? The manual gives the syntax (quite limited comparing to the altq - in my opinion), but doesn't really explain anything. For example - is there a bandwidth borrowing and how is it prioritizing? Fear not - http://article.gmane.org/gmane.os.openbsd.cvs/123353 altq stays in parallel for a migration phase. -- Best regards, Boris mailto:bo...@twopoint.com
Re: new queueing subsystem
2013/10/16 Boris Goldberg bo...@twopoint.com Is the old queueing gone? Is existing pf.conf not going to work with 5.4? The new queueing doesn't appear until 5.5, so 5.4 will most certainly work without you doing anything related to your pf.conf. -- May the most significant bit of your life be positive.
Re: new queueing subsystem
On Wed, Oct 16, 2013 at 09:08:55AM -0500, Boris Goldberg wrote: Hello misc, The changes in the pf queueing subsystem (for some reason not mentioned in the http://openbsd.org/faq/upgrade54.html) are getting me worried. Couldn't find the word altq in the http://www.openbsd.org/cgi-bin/man.cgi?query=pf.confapropos=0sektion=0manpath=OpenBSD+Currentarch=i386format=html. Is the old queueing gone? Is existing pf.conf not going to work with 5.4? How is the new queueing work? The manual gives the syntax (quite limited comparing to the altq - in my opinion), but doesn't really explain anything. For example - is there a bandwidth borrowing and how is it prioritizing? -- Best regards, Boris mailto:bo...@twopoint.com This will not be in 5.4, it wil be in 5.5. If you see shortcomings in the docs explain in more detail. -Otto
Re: new queueing subsystem
On Oct 16, 2013, at 8:05, Otto Moerbeek o...@drijf.net wrote: This will not be in 5.4, it wil be in 5.5. If you see shortcomings in the docs explain in more detail. I just read the QUEUEING section in the man page. Seems fairly clear to me, and in some ways more clear. One thing I'd like to see is a suggestion for how to figure out your actual bandwidth, to better define the queues. For example, I've got a 10Mbit outbound link, and three priority queues. The only reason I define a total bandwidth is that altq requires it, so I've set it at 9.5Mbit. With the move to HFSC, do I have to break down major queues, and the children? Or cam I still just do very basic priority queueing in 5.5?
Re: new queueing subsystem
Boris Goldberg bo...@twopoint.com writes: The changes in the pf queueing subsystem (for some reason not mentioned in the http://openbsd.org/faq/upgrade54.html) are getting me worried. The new queueing system was only committed on October 12th 2013, well after 5.4 was cut and sent off to the CD printers. But it will be in 5.5. As will altq 'for a transition period'. See the commits starting with http://marc.info/?l=openbsd-cvsm=138160448112859w=2. If you want to help test the new queues, the easiest way to get started is to install recent snapshot and take it from there. - P -- Peter N. M. Hansteen, member of the first RFC 1149 implementation team http://bsdly.blogspot.com/ http://www.bsdly.net/ http://www.nuug.no/ Remember to set the evil bit on all malicious network traffic delilah spamd[29949]: 85.152.224.147: disconnected after 42673 seconds.
Re: npppd / pppoe server troubles
Hi, On Wed, 16 Oct 2013 13:39:31 +0200 Gruel Bruno b.gr...@sdnet.info wrote: ### On OBSD 5.3 release : (snip) Segmentation fault After de DISCOVERY message the server crash with Segmentation fault This bug had been fixed on April 16. PPPoE server (by npppd) on 5.3 is completely broken. ### On OBSD 5.3 snapshot (2weeks ago version) : I'm doing some tests last night and got other problems. I don't have my snapshots stations here but the symptom is : I believe this will work. npppd logs side somthings like that : ...unable to agree auth proto... As your config, CHAP or MS-CHAP-V2 must be accepted, Network side : request.reject when client propose pap or chap or whatever. I 'll give you full log tonight. Is someone have some idea ? The log will help me. Adding authentication-method pap chap to the tunnel block on npppd.conf may avoid the problem. --yasuoka
usb key performance decrease
hi there, i think the usb subsystem is in certain circumstances starving the writes... i have this great working sandisk ultra backup 32G usb key, that was consistently achieving ~10MB/s in writing big files (movies). in windows, it can pack even 15MB/s. now i have this: $ time dd if=1.mp4 of=/mnt/1.mp4 bs=1m 268+0 records in 267+0 records out 279969792 bytes transferred in 401.012 secs (698156 bytes/sec) 295+0 records in 294+0 records out 308281344 bytes transferred in 440.531 secs (699795 bytes/sec) 620+1 records in 620+1 records out 650617965 bytes transferred in 949.335 secs (685340 bytes/sec) 950.23 real 0.01 user 5.59 sys first i thought, this might be some file system issue (fat32). but i tried this is: $ sudo dd if=/dev/zero of=/dev/rsd3a bs=1m count=300 300+0 records in 300+0 records out 314572800 bytes transferred in 42.414 secs (7416611 bytes/sec) some might say ~7.5MB/s is not bad, but please note: this is RAW, sequential write from /dev/zero. it should be higher. creating the file system takes _very_ long time: $ sudo fdisk -i /dev/rsd3c Do you wish to write new MBR and partition table? [n] y Writing MBR at offset 0. $ sudo disklabel -E sd3 Label editor (enter '?' for help at any prompt) a partition: [a] offset: [64] size: [62557046] FS type: [4.2BSD] Rounding size to bsize (32 sectors): 62557024 w q No label changes. $ sudo time newfs /dev/rsd3a /dev/rsd3a: 30545.4MB in 62557024 sectors of 512 bytes 151 cylinder groups of 202.47MB, 12958 blocks, 25984 inodes each super-block backups (for fsck -b #) at: 32, 414688, 829344, 1244000, 1658656, 2073312, 2487968, 2902624, 3317280, 3731936, 4146592, 4561248, 4975904, 5390560, 5805216, 6219872, 6634528, 7049184, 7463840, 7878496, 8293152, 8707808, 9122464, 9537120, 9951776, 10366432, 10781088, 11195744, 11610400, 12025056, 12439712, 12854368, 13269024, 13683680, 14098336, 14512992, 14927648, 15342304, 15756960, 16171616, 16586272, 17000928, 17415584, 17830240, 18244896, 18659552, 19074208, 19488864, 19903520, 20318176, 20732832, 21147488, 21562144, 21976800, 22391456, 22806112, 23220768, 23635424, 24050080, 24464736, 24879392, 25294048, 25708704, 26123360, 26538016, 26952672, 27367328, 27781984, 28196640, 28611296, 29025952, 29440608, 29855264, 30269920, 30684576, 31099232, 31513888, 31928544, 32343200, 32757856, 33172512, 33587168, 34001824, 34416480, 34831136, 35245792, 35660448, 36075104, 36489760, 36904416, 37319072, 37733728, 38148384, 38563040, 38977696, 39392352, 39807008, 40221664, 40636320, 41050976, 41465632, 41880288, 42294944, 42709600, 43124256, 43538912, 43953568, 44368224, 44782880, 45197536, 45612192, 46026848, 46441504, 46856160, 47270816, 47685472, 48100128, 48514784, 48929440, 49344096, 49758752, 50173408, 50588064, 51002720, 51417376, 51832032, 52246688, 52661344, 53076000, 53490656, 53905312, 54319968, 54734624, 55149280, 55563936, 55978592, 56393248, 56807904, 57222560, 57637216, 58051872, 58466528, 58881184, 59295840, 59710496, 60125152, 60539808, 60954464, 61369120, 61783776, 62198432, 848.35 real 3.11 user 5.36 sys that's 14 minutes for a 32G file system :-( iostat sheds a bit of light, when i start copying the same file on ffs (similar on fat32): $ iostat -w1 sd3 tty sd3 cpu tin tout KB/t t/s MB/s us ni sy in id 5 103 55.492 0.12 2 0 2 0 95 1 509 0.000 0.00 1 0 0 0 99 1 115 0.000 0.00 0 0 0 1 99 14 114 0.000 0.00 1 0 0 0 99 4 718 0.000 0.00 1 0 1 0 98 4 232 11.003 0.03 1 0 0 0 99 1 44 16.00 44 0.68 0 0 0 1 99 6 44 16.00 43 0.67 0 0 0 0100 13 43 16.00 42 0.66 0 0 0 2 98 5 1309 16.00 43 0.67 1 0 1 0 98 0 119 16.008 0.12 0 0 0 1 99 0 120 16.00 44 0.69 0 0 0 1 99 0 119 16.00 43 0.67 0 0 0 1 99 0 118 16.00 43 0.67 0 0 1 0 99 0 119 16.00 43 0.67 1 0 0 0 99 0 119 16.00 44 0.68 0 0 0 0100 0 119 16.00 46 0.71 0 0 0 0100 0 119 16.00 21 0.32 0 0 0 0100 0 119 32.502 0.06 0 0 0 0100 0 121 64.001 0.06 0 0 1 0 99 it seems every write operation is capped at 700KB/s... notice how it gets starved even on that. to check that the usb port is not busted, i have tried other usb keys (cheaper and slower) and paradoxically they worked better, here is pushing the same file to softraid encrypted sandisk cruzer fit 32G (sd3): tty sd0 sd1 sd2 sd3 cpu tin tout KB/t t/s MB/s KB/t t/s MB/s KB/t t/s MB/s KB/t t/s MB/s us ni sy in id 0 291 64.00 64 4.00 0.000 0.00 16.00 213 3.33 16.00 213 3.33 0 0 17 9 74 0 703 61.18 17 1.00 0.000 0.00 16.00 119 1.85 16.00 119 1.85 1 0 14 4 81 0 291 63.33 48 2.97 0.000 0.00
Re: new queueing subsystem
On Wed Oct 16 2013 08:54, Johan Beisser wrote: Or cam I still just do very basic priority queueing in 5.5? See pf.conf(5), 'set prio'. This doesn't even require you to define queues, etc.
Re: new queueing subsystem
On Wed, Oct 16, 2013 at 11:04 AM, Norman Golisz li...@zcat.de wrote:
On Wed Oct 16 2013 08:54, Johan Beisser wrote:
Or cam I still just do very basic priority queueing in 5.5?
See pf.conf(5), 'set prio'. This doesn't even require you to define
queues, etc.
Right. I guess if I want to define multiple queues for matching
traffic, I need to either redo the filter rules to use tagging*, or
simply do it per outbound bit of traffic.
The change is a pretty powerful one.
*
match on FOO inet proto tcp from BAR to BAZ port {X,Y} tag PRIO_Z
[...]
pass out on egress tagged PRIO_X set prio 4
pass out on egress tagged PRIO_Z set prio (3, 7)
Re: npppd / pppoe server troubles
Le 16-10-2013 18:36, YASUOKA Masahiko a écrit :
Hi,
On Wed, 16 Oct 2013 13:39:31 +0200
Gruel Bruno b.gr...@sdnet.info wrote:
### On OBSD 5.3 release :
(snip)
Segmentation fault
After de DISCOVERY message the server crash with Segmentation fault
This bug had been fixed on April 16. PPPoE server (by npppd) on 5.3
is completely broken.
### On OBSD 5.3 snapshot (2weeks ago version) :
I'm doing some tests last night and got other problems. I don't have
my snapshots stations here but the symptom is :
I believe this will work.
npppd logs side somthings like that :
...unable to agree auth proto...
As your config, CHAP or MS-CHAP-V2 must be accepted,
Network side :
request.reject when client propose pap or chap or whatever.
I 'll give you full log tonight.
Is someone have some idea ?
The log will help me.
Adding
authentication-method pap chap
to the tunnel block on npppd.conf may avoid the problem.
Thank's for your reply and advise.
Even if it's not necessary i updated my laptop (pppoe server in my lab)
today.
As i thought that it's doesn't read my users file i changed the username
password but nothing else.
My config files:
###npppd.conf
tunnel PPPOE protocol pppoe {
listen on interface re0
pppoe-desc-in-pktdump yes
pppoe-desc-out-pktdump yes
pppoe-session-in-pktdump yes
pppoe-session-out-pktdump yes
authentication-method pap chap
}
ipcp IPCP {
pool-address 10.0.0.2-10.0.0.254
dns-servers 192.168.0.1
}
interface tun1 address 10.0.0.1 ipcp IPCP
authentication LOCAL type local {
users-file /etc/npppd/npppd-users
}
bind tunnel from PPPOE authenticated by LOCAL to tun1 (I'm using tun1
because i using qemu on tun0.)
###npppd-users
toto:\
:password=toto:\
:framed-ip-address=10.0.0.101:
And logs:
** npppd daemon:
2013-10-16 20:49:55:INFO: pppoed RecvPADI from=52:54:00:12:34:56
service-name= host-uniq=361b90c8 if=re0
2013-10-16 20:49:55:INFO: pppoed SendPADO to=52:54:00:12:34:56
serviceName= acName=3c:97:0e:3e:b2:8b hostUniq=361b90c8 eol if=re0
2013-10-16 20:49:55:INFO: pppoed RecvPADI from=52:54:00:12:34:56
service-name= host-uniq=361b90c8 if=re0
2013-10-16 20:49:55:INFO: pppoed SendPADO to=52:54:00:12:34:56
serviceName= acName=3c:97:0e:3e:b2:8b hostUniq=361b90c8 eol if=re0
2013-10-16 20:49:55:INFO: pppoed if=re0 session=47899 SendPADS
serviceName= hostUniq=361b90c8
2013-10-16 20:49:55:NOTICE: pppoed if=re0 session=47899 logtype=PPPBind
ppp=1
2013-10-16 20:49:55:ERR: ppp id=1 layer=base getnameinfo() failed at
ppp_set_tunnel_label
2013-10-16 20:49:55:INFO: ppp id=1 layer=base logtype=Started
tunnel=PPPOE(0.0.0.0)
2013-10-16 20:49:55:INFO: ppp id=1 layer=lcp logtype=Opened
mru=1492/1492 auth=PAP magic=912adabc/a4d9f488
2013-10-16 20:49:55:DEBUG: ppp id=1 layer=pap pap_start
2013-10-16 20:49:55:ALERT: ppp id=1 layer=pap logtype=Failure
username=toto realm=LOCAL
2013-10-16 20:49:55:INFO: pppoed if=re0 session=47899 SendPADT
2013-10-16 20:49:55:ERR: ppp id=1 layer=base getnameinfo() failed at
ppp_set_tunnel_label
2013-10-16 20:49:55:NOTICE: ppp id=1 layer=base logtype=TUNNELUSAGE
user=unknown duration=0sec layer2=PPPOE layer2from=0.0.0.0 auth=none
data_in=63bytes
,4packets data_out=121bytes,5packets error_in=0 error_out=0 mppe=no
iface=(not binding)
** network capture:
20:49:55.239930 PPPoE-Discovery
code Initiation, version 1, type 1, id 0x, length 12
tag Service-Name, length 0
tag Host-Uniq, length 4 6\033\220\310
20:49:55.240578 PPPoE-Discovery
code Request, version 1, type 1, id 0x, length 20
tag Service-Name, length 0
tag AC-Cookie, length 4 \370\255\360\270
tag Host-Uniq, length 4 6\033\220\310
20:49:55.240854 PPPoE-Session
code Session, version 1, type 1, id 0xbb1b, length 16
LCP: Configure-Request, Magic-Number=-1529219960,
Max-Rx-Unit=1492[|lcp]
20:49:55.241084 PPPoE-Session
code Session, version 1, type 1, id 0xbb1b, length 11
LCP: Configure-Nak, Auth-Prot PAP[|lcp]
20:49:55.241370 PPPoE-Session
code Session, version 1, type 1, id 0xbb1b, length 20
LCP: Configure-Ack, Max-Rx-Unit=1492, Magic-Number=-1859462468,
Auth-Prot PAP[|lcp]
20:49:55.241380 PPPoE-Session
code Session, version 1, type 1, id 0xbb1b, length 16
PAP: Authenticate-Request, Peer-Id=toto, Passwd=toto
20:49:55.241836 PPPoE-Session
code Session, version 1, type 1, id 0xbb1b, length 6
LCP: Terminate-Ack
I try with chap on the client side but it's the same.
If you need more logs tel me.
Thank's
Bruno
signals under openbsd
Hi folks,
i am writing a program that:
0) manages to handle sigchld signals,
1) creates 100 process
2) put the childs to sleep 1 second
3) loops (the parent process) until 100 child process have been died.
It is not working, why ?
Thanks for you time and cooperation.
Best regards,
Fried.
PS: the source code below:
#include sys/types.h
#include sys/wait.h
#include signal.h
#include stdio.h
#include unistd.h
unsigned long c;
void
hdlchld(const int s)
{
unsigned long p;
int x;
p = waitpid(-1, x, WNOHANG | WCONTINUED | WUNTRACED);
fprintf(stdout, %lu\n, p);
if (p + 1) {
c++;
fprintf(stdout, pid: %lu\n died, p);
}
}
int
main(int argc, char **argv)
{
struct sigactions;
unsigned long i, p;
int x;
s.sa_handler = hdlchld;
sigemptyset(s.sa_mask);
sigaddset(s.sa_mask, SIGCHLD);
s.sa_flags = 0;
if (sigaction(SIGCHLD, s, NULL) == -1) return 110;
for (i = 0; i 100; i++) {
p = fork();
if (p == -1ul) break;
if (!p) break; /* child */
}
if (p == -1ul) return 1;
if (p) while (c i) sleep(1); /* parent */
else sleep (1); /* child */
return 0;
}
Re: signals under openbsd
On Wed, Oct 16, 2013 at 5:15 PM, Friedrich Locke
friedrich.lo...@gmail.comwrote:
Hi folks,
i am writing a program that:
0) manages to handle sigchld signals,
1) creates 100 process
2) put the childs to sleep 1 second
3) loops (the parent process) until 100 child process have been died.
It is not working, why ?
Thanks for you time and cooperation.
Best regards,
Fried.
PS: the source code below:
#include sys/types.h
#include sys/wait.h
#include signal.h
#include stdio.h
#include unistd.h
unsigned long c;
void
hdlchld(const int s)
{
unsigned long p;
int x;
p = waitpid(-1, x, WNOHANG | WCONTINUED | WUNTRACED);
fprintf(stdout, %lu\n, p);
if (p + 1) {
c++;
fprintf(stdout, pid: %lu\n died, p);
}
}
int
main(int argc, char **argv)
{
struct sigactions;
unsigned long i, p;
int x;
s.sa_handler = hdlchld;
sigemptyset(s.sa_mask);
sigaddset(s.sa_mask, SIGCHLD);
s.sa_flags = 0;
if (sigaction(SIGCHLD, s, NULL) == -1) return 110;
for (i = 0; i 100; i++) {
p = fork();
if (p == -1ul) break;
if (!p) break; /* child */
}
if (p == -1ul) return 1;
if (p) while (c i) sleep(1); /* parent */
else sleep (1); /* child */
return 0;
}
- Declare p as pid_t in both functions.
- Check fork's return value against -1 (not -1ul)
- If you spawn n childs don't expect hdlchld to be called n times. I ran
your program under linux (here, in my work, I don't have OpenBSD) and it
run forever. Whth the following change the program works like, I suposse,
you expect:
void
hdlchld(const int s)
{
pid_t p;
int x;
while(1){
p = waitpid(-1, x, WNOHANG | WCONTINUED | WUNTRACED);
fprintf(stdout, %d\n, p);
if (p 0) {
c++;
fprintf(stdout, pid: %d died (%lu)\n, p, c);
}
else
break;
}
}
Regards
Re: apache bug?
On 2013-10-15, Nick Holland n...@holland-consulting.net wrote: BTW: I have no idea what your picture is, I'm not clicking on it. It's a screenshot of a directory listing, with some bits blanked out, of Linux ISOs *wink* *wink*. On 10/15/2013 11:43 AM, obsd, cgi wrote: In the directory listing the ISO file looks like ~40 MByte, but the reality is 4 GBytes. What could the problem be? storing file sizes in insufficiently sized data types.. httpd in base was patched to allow larger files to be sent, but that didn't extend to directory listings. Or I should use nginx since apache will be obsolete? :) That might be one way to work-around it.
crypto softraid DUID's
hi there, if i have a usb key, that is softraid encrypted, it has 2 DUID's. the first one (before bioctl) can be used to script bioctl when the key is inserted. when the SR CRYPTO drive is attached, it has another DUID. this can be used for mounting/unmounting. my question is, is that a security threat to have this 2nd DUID in /etc/fstab? could it be used as cleartext for brute forcing the SR CRYPTO drive? i also noticed that bioctl -c C -l accepts DUID's, but bioctl -d does not. it this by design? -f -- i'm weird, but i'm saving up to be eccentric.
