ADSL with german t-online
Hi, i have a problem with PPPoE and t-online. Right now i'm using userspace pppd with the following ppp.conf: default: set log Phase Chat IPCP CCP tun command set redial 20+10-8 0 set reconnect 15 5 pppoe: set device !/usr/sbin/pppoe -i ep2 disable acfcomp protocomp deny acfcomp set mtu max 1454 set crtscts off set speed sync enable lqr set lqrperiod 5 set dial set login set timeout 0 set authname x set authkey x add! default HISADDR enable dns resolv readonly enable mssfixup set urgent tcp 22 set socket /var/run/pppctl.%d 600 everything works fine - except when the link dies. After that, I get the following in ppp.log: [...] Jul 8 12:03:14 plato ppp[25280]: tun0: IPCP: IPADDR[6] 217.0.116.36 Jul 8 12:03:14 plato ppp[25280]: tun0: IPCP: deflink: Oops, RCR in Initial. Jul 8 12:03:17 plato ppp[25280]: tun0: IPCP: deflink: RecvConfigReq(119) state = Initial Jul 8 12:03:17 plato ppp[25280]: tun0: IPCP: IPADDR[6] 217.0.116.36 Jul 8 12:03:17 plato ppp[25280]: tun0: IPCP: deflink: Oops, RCR in Initial. Jul 8 12:03:18 plato ppp[25280]: tun0: Phase: Clearing choked output queue [... and more of the same ...] I am starting pppd this way: # cat /etc/hostname.tun0 !/usr/sbin/ppp -ddial -unit 0 pppoe Any ideas what the problem might be? note: i also tried using kernel pppoe when setting up the system, but that did not work at all. Benno -- Sebastian Benoit [EMAIL PROTECTED]
logserver configuration
This is not an OBSD specific question, but I have tried other sources and did not get very far. Guys; Just set up an OBSD logserver that will be receiving logs from several clients (2 OBSD and 3 linux clients). Currently, all clients log to /var/log/messages on the logserver. What I really want to do is is have each client send it's messages to a specific file on the logserver. For example client-A will send logs to /var/log/clientA and client be to /var/log/clientB on the logserver, etc. I'm stumped on how to configure this set up. Any clues will be appreciated. -- Qv6
Re: SVG Puffy?
On 7/10/05, Sitsofe Wheeler [EMAIL PROTECTED] wrote: I was just wondering whether there has been any discussion of a SVG version of Cartoon Puffy and logo ( http://www.openbsd.org/art/puffy/puflogh200X50.gif ) . I only ask because sometimes it is nice to have project logos in a friendly scalable format (I know there is the PDF version but that isn't very friendly). You should try converting the pdf to svg with pstoedit http://www.pstoedit.net/pstoedit -- Thomas Leveille
Re: ADSL with german t-online
Hi,
I use the following with T-Online for few years already
and it works stable, but I don't know how correct is this:
pref:afarber {1005} sudo crontab -l
32 * * * * /usr/local/sbin/check-ppp.sh
pref:afarber {1006} cat /usr/local/sbin/check-ppp.sh
#!/bin/sh
TIMEOUT=180
WEBPAGES=http://www.heise.de \
http://www.spiegel.de \
http://www.slashdot.org
# If at least one of the web pages works, then the net connection is alive
for url in $WEBPAGES; do
/usr/local/bin/curl --max-time $TIMEOUT --proxy '' --silent \
--output /dev/null $url exit 0
done
# Otherwise kill ppp, wait $TIMEOUT seconds and then restart ppp again
echo 2 Fetching web pages failed: $?
echo 2 'Killing ppp:'
pppctl /var/run/ppp/tdsl quit all
echo 2 Waiting for $TIMEOUT seconds...
sleep $TIMEOUT
echo 2 'Starting ppp:'
ppp -ddial tdsl
pref:afarber {1008} head /etc/rc.local
if [ -e /etc/ppp/ppp.conf ]; then
echo 'Connecting to T-DSL...'
mkdir -p /var/run/ppp
/usr/sbin/ppp -ddial tdsl
sleep 10
fi
pref:afarber {1010} cat /etc/ppp/ppp.conf
default:
set log phase chat lcp ipcp ccp tun command warning error alert filter
tdsl:
accept lqr
deny acfcomp
disable acfcomp protocomp ipv6cp
enable mssfixup
set authkey XX
set authname [EMAIL PROTECTED]
set device !/usr/sbin/pppoe -i fxp0
set ifaddr 10.0.0.1/0 10.0.0.2/0 0.0.0.0 0.0.0.0
set mru max 1454
set mtu max 1454
set redial 120.120 0
set speed sync
set socket /var/run/ppp/tdsl 0177
add default HISADDR
pref:afarber {1011} cat /etc/ppp/ppp.linkup
tdsl:
shell /sbin/pfctl -f /etc/pf.conf
bg su afarber -c '/usr/local/bin/fetchmail -a -e 10 -n'
pref:afarber {1012} cat /etc/ppp/ppp.linkdown
tdsl:
bg su afarber -c '/usr/local/bin/fetchmail -q'
HTH
Alex
2005/7/11, Sebastian Benoit [EMAIL PROTECTED]:
i have a problem with PPPoE and t-online. Right now i'm using userspace pppd
with the following ppp.conf:
default:
set log Phase Chat IPCP CCP tun command
set redial 20+10-8 0
set reconnect 15 5
pppoe:
set device !/usr/sbin/pppoe -i ep2
disable acfcomp protocomp
deny acfcomp
set mtu max 1454
set crtscts off
set speed sync
enable lqr
set lqrperiod 5
set dial
set login
set timeout 0
set authname x
set authkey x
add! default HISADDR
enable dns
resolv readonly
enable mssfixup
set urgent tcp 22
set socket /var/run/pppctl.%d 600
everything works fine - except when the link dies. After that, I get the
following in ppp.log:
[...]
Jul 8 12:03:14 plato ppp[25280]: tun0: IPCP: IPADDR[6] 217.0.116.36
Jul 8 12:03:14 plato ppp[25280]: tun0: IPCP: deflink: Oops, RCR in Initial.
Jul 8 12:03:17 plato ppp[25280]: tun0: IPCP: deflink: RecvConfigReq(119)
state = Initial
Jul 8 12:03:17 plato ppp[25280]: tun0: IPCP: IPADDR[6] 217.0.116.36
Jul 8 12:03:17 plato ppp[25280]: tun0: IPCP: deflink: Oops, RCR in Initial.
Jul 8 12:03:18 plato ppp[25280]: tun0: Phase: Clearing choked output queue
[... and more of the same ...]
I am starting pppd this way:
# cat /etc/hostname.tun0
!/usr/sbin/ppp -ddial -unit 0 pppoe
Any ideas what the problem might be?
note: i also tried using kernel pppoe when setting up the system, but that
did not work at all.
Re: logserver configuration
--On 11 July 2005 02:15 -0500, Qv6 wrote: This is not an OBSD specific question, but I have tried other sources and did not get very far. It's a syslogd-specific question.. From looking at syslogd.conf(5), it doesn't look like OpenBSD's standard syslogd supports this. Some other OS do (+hostname on fbsd), or syslog-ng might be useful.
vpncsetting routes problem
Hi everyone I'm trying out vpnc to connect to the cisco concentrator at my workplace. The connect itself works without a problem. Only the setting of the routes didn't work at all. I took /usr/local/share/examples/vpnc/vpnc.sh as an example and sat the routes accordingly. (the 3 last lines of the start function) Before doing so my routing table lookes as follows: Internet: DestinationGatewayFlagsRefs UseMtu Interface default141.12.239.248 UGS 0 11 - fxp0 127/8 127.0.0.1 UGRS00 33224 lo0 127.0.0.1127.0.0.1 UH 00 33224 lo0 141.12.110.1 141.12.110.1 UH 00 - tun0 141.12.239/24link#1 UC 00 - fxp0 141.12.239.2000:50:04:3e:d3:3e UHLc0 197 - fxp0 141.12.239.21127.0.0.1 UGHS00 33224 lo0 141.12.239.248 00:00:0c:07:ac:27 UHLc00 - fxp0 224/4 127.0.0.1 URS 00 33224 lo0 After setting the new routes: Internet: DestinationGatewayFlagsRefs UseMtu Interface default141.12.110.1 US 06 - tun0 127/8 127.0.0.1 UGRS00 33224 lo0 127.0.0.1127.0.0.1 UH 00 33224 lo0 141.12.110.1 141.12.110.1 UH 00 - tun0 141.12.128.10141.12.239.248 UGHS06 - fxp0 141.12.239/24link#1 UC 00 - fxp0 141.12.239.2000:50:04:3e:d3:3e UHLc0 1073 - fxp0 141.12.239.21127.0.0.1 UGHS00 33224 lo0 141.12.239.248 00:00:0c:07:ac:27 UHLc00 - fxp0 224/4 127.0.0.1 URS 00 33224 lo0 Which seems to be correct (though I must admit the line 141.12.110.1 141.12.110.1 looks somehow weid) The problem is that nothing works... No traffic seems to pass... Though when trying with a win machine and the cisco vpn client it works without a problem. So it can't be because of some firewall... I need to admit it's the first time for me to work with vpns at all. In the above example 141.12.239.248 is the default router 141.12.110.1 the tun_ip and 141.12.128.10 the vpn gateway I hope someone can enlighten me as I'm already trying to get this to work for too long now.. Thanks
Re: logserver configuration
Hi, For example client-A will send logs to /var/log/clientA and client be to /var/log/clientB on the logserver, etc. I'm stumped on how to configure this set up. To da that you have to configure your syslogger to do that kind of work. This link maybe helpful http://www.campin.net/syslog-ng/faq.html /bossk
Re: logserver configuration
On Mon, 11 Jul 2005 02:15:01 -0500 Qv6 [EMAIL PROTECTED] wrote: For example client-A will send logs to /var/log/clientA and client be to /var/log/clientB on the logserver, etc. I'm stumped on how to configure this set up. Any clues will be appreciated. I use socklog (from ports) on my log server. --- Lars Hansson
Re: ADSL with german t-online [SOLVED]
disable acfcomp protocomp ipv6cp The solution was to add disable ipv6cp. Thanks to Stefan and Alex, /Benno -- Sebastian Benoit [EMAIL PROTECTED] My mail is GnuPG signed -- Unsigned ones are bogus -- http://www.gnupg.org/ GnuPG 0xD777DBA7 2003-09-10 D02B D0E0 3790 1AA1 DA3A B508 BF48 87BF D777 DBA7 Never make a technical decision based upon the politics of the situation. Never make a political decision based upon technical issues. The only place these realms meet is in the mind of the unenlightened. -- Geoffrey James, The Zen of Programming
Re: hw.setperf not available
On 7/11/05, bossk [EMAIL PROTECTED] wrote: The Pentium 3 mobile supports Intel's SpeedStep and the Ultra-Low-Voltage-Version supports the Enhanced Intel SpeedStep Technology. Thanks for telling me something new; I didn't know the Intel made those chips. My apologies for the confusion. My BIOS has some switches to configure various basic options, but afaik the dynamic cpu scaling is part of the OS. Given the archives on hw.setperf and the various CPU types involved, I suspect your P3's throttling is different from that on the AMD K7 (Powernow) and Pentium M and thus not included in the code. You're right on trying to use hw.setperf though. Sorry to not be of more help, Rogier -- If you don't know where you're going, any road will get you there.
Re: hw.setperf not available
* Rogier Krieger [EMAIL PROTECTED] [2005-07-11 12:21]: On 7/11/05, bossk [EMAIL PROTECTED] wrote: The Pentium 3 mobile supports Intel's SpeedStep and the Ultra-Low-Voltage-Version supports the Enhanced Intel SpeedStep Technology. Thanks for telling me something new; I didn't know the Intel made those chips. My apologies for the confusion. but it is controlled via the chipset, thus many more drivers had to be written than just the one codepath we have for p4/p-M and nobody did that. -- BS Web Services, http://www.bsws.de/ OpenBSD-based Webhosting, Mail Services, Managed Servers, ... Unix is very simple, but it takes a genius to understand the simplicity. (Dennis Ritchie)
NX support in VIA C7 ?
Hi misc@: From what I read in the specs of the new VIA C7 Esther core (http://www.via.com.tw/en/products/processors/c7/), it seems it supports NX bit protection, but it seems NX hardware protection is only supported with PAE enabled. Searching a bit in the archives, I've found a patch from tedu@ (http://marc.theaimsgroup.com/?l=openbsd-techm=108631046324027w=2) that tries to improve the i386 pmap in order to get PAE support. This patch seems that never get commited, so I'd like to ask if are there any advances in this aspect. Regards
Re: hw.setperf not available
On Mon, Jul 11, 2005 at 12:43:28PM +0200, Henning Brauer wrote: * Rogier Krieger [EMAIL PROTECTED] [2005-07-11 12:21]: On 7/11/05, bossk [EMAIL PROTECTED] wrote: The Pentium 3 mobile supports Intel's SpeedStep and the Ultra-Low-Voltage-Version supports the Enhanced Intel SpeedStep Technology. Thanks for telling me something new; I didn't know the Intel made those chips. My apologies for the confusion. but it is controlled via the chipset, thus many more drivers had to be written than just the one codepath we have for p4/p-M and nobody did that. actually we have one driver: ichpcib(4). -- BS Web Services, http://www.bsws.de/ OpenBSD-based Webhosting, Mail Services, Managed Servers, ... Unix is very simple, but it takes a genius to understand the simplicity. (Dennis Ritchie) -- Alexander Yurchenko (aka grange)
Re: Cross-Compiling OpenBSD
On Sun, Jul 10, 2005 at 03:38:29PM -0400, Nick Holland wrote: If your machine is too slow to do what you need it to do, you need a faster machine. Cross compiling is not the answer to your problem. Not so Nick. There may be some cases where you deliberately have a slow machine for reasons of power consumption/heat disappation, perhaps a fanless machine, you want to update. Or just that the fastest machine in the architecture you are targeting falls way behind current machines (SPARC vs current P4, say). Telling someone to use a faster machine is a trite answer but, in some cases, it is simply infeasible. Which would you rather have developers doing...adding new features, cleaning up code, improving existing operation...or helping insert adjective here users do silly things with no value added to the project? improving existing operation you just said it there. Cross building means that you are not bound by the limitations of the target hardware. This actually impacts the developers more than anyone else, especially during the release cycle. Imagine having to restart a build that takes literally days to complete because what seemed to be a benign change that fixes a bug causes an architecture specific build error. In a cross build environment the impact could be as little as a hour or two instead of days. It means developers can do more stuff because they are not waiting for the slower processors to grind through a compile. -- Brett Lymn
Improving routing performance
Hi! A few days ago I got my home internet connection upgraded to 8/1 Mbit/s, and then I realised that my OpenBSD router and firewall wasn't able to work that fast. I have used TPTEST (tptest.sourceforge.net) to measure the available bandwith and got the following results: TPTEST running on Linux workstation directly connected to cable modem: TCP download 8 Mbit/s, TCP upload 1 Mbit/s UDP download 8 Mbit/s, UDP upload 1 Mbit/s TPTEST running on OpenBSD router directly connected to cable modem: TCP download 2 Mbit/s, TCP upload 1 Mbit/s UDP download 2 Mbit/s, UDP upload 1 Mbit/s TPTEST running on Linux workstation connected to OpenBSD router: TCP download 1 Mbit/s, TCP upload 1 Mbit/s UDP download 2 Mbit/s, UDP upload 1 Mbit/s So my old OpenBSD router is clearly not up to handling my new 8 Mbit/s downlink speed. Could anyone here help guiding me to find out the worst hardware (and maybe software) bottlenecks in my system? I have attached the output of dmesg. Any tips on what the most important things to investigate are? Is there any other information I should post? Cheers // Fredrik Roubert -- Mvllevengsvdgen 6b | +46 46 188127 SE-222 40 Lund | http://www.df.lth.se/~roubert/ OpenBSD 3.5 (GENERIC) #34: Mon Mar 29 12:24:55 MST 2004 [EMAIL PROTECTED]:/usr/src/sys/arch/i386/compile/GENERIC cpu0: Intel Pentium (P54C) (GenuineIntel 586-class) 133 MHz cpu0: FPU,V86,DE,PSE,TSC,MSR,MCE,CX8 cpu0: F00F bug workaround installed real mem = 16363520 (15980K) avail mem = 9117696 (8904K) using 225 buffers containing 921600 bytes (900K) of memory mainbus0 (root) bios0 at mainbus0: AT/286+(7d) BIOS, date 09/06/96, BIOS32 rev. 0 @ 0xfb310 apm0 at bios0: Power Management spec V1.1 apm0: APM engage (device 1): power management disabled (1) apm0: AC on, battery charge unknown pcibios0 at bios0: rev. 2.1 @ 0xf/0xb838 pcibios0: PCI BIOS has 6 Interrupt Routing table entries pcibios0: no compatible PCI ICU found pcibios0: Warning, unable to fix up PCI interrupt routing pcibios0: PCI bus #0 is the last bus bios0: ROM list: 0xc/0x8000 0xef000/0x1000! pci0 at mainbus0 bus 0: configuration mode 1 (bios) pchb0 at pci0 dev 0 function 0 Acer Labs M1523 PCI rev 0x1c pcib0 at pci0 dev 2 function 0 Acer Labs M1523 ISA rev 0x07 pciide0 at pci0 dev 2 function 1 Acer Labs M5219 UDMA IDE rev 0x20: DMA (unsupported), channel 0 configured to compatibility, channel 1 configured to compatibility wd0 at pciide0 channel 0 drive 0: Maxtor 91010D6 wd0: 16-sector PIO, LBA, 9641MB, 19746720 sectors pciide0: channel 1 ignored (not responding; disabled or no drives?) vga1 at pci0 dev 3 function 0 Cirrus Logic CL-GD5446 rev 0x00 wsdisplay0 at vga1: console (80x25, vt100 emulation) wsdisplay0: screen 1-5 added (80x25, vt100 emulation) isa0 at pcib0 isadma0 at isa0 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 midi0 at pcppi0: PC speaker sysbeep0 at pcppi0 lpt0 at isa0 port 0x378/4 irq 7 lpt1 at isa0 port 0x278/4: polled npx0 at isa0 port 0xf0/16: using exception 16 pccom0 at isa0 port 0x3f8/8 irq 4: ns16550a, 16 byte fifo pccom1 at isa0 port 0x2f8/8 irq 3: ns16550a, 16 byte fifo pccom2 at isa0 port 0x3e8/8 irq 5: ns16550a, 16 byte fifo fdc0 at isa0 port 0x3f0/6 irq 6 drq 2 isapnp0 at isa0 port 0x279: read port 0x203 ep1 at isapnp0 3Com 3C509B EtherLink III, TCM5095, PNP80F7, port 0x210/16 irq 9: address 00:60:97:39:50:2d, utp (default utp) ep2 at isapnp0 3Com 3C509B EtherLink III, TCM5095, PNP80F7, port 0x220/16 irq 10: address 00:60:97:12:1d:a6, utp (default utp) biomask 4040 netmask 4640 ttymask 46c2 pctr: 586-class performance counters and user-level cycle counter enabled dkcsum: wd0 matched BIOS disk 80 root on wd0a rootdev=0x0 rrootdev=0x300 rawdev=0x302
Re: Cross-Compiling OpenBSD
Brett Lymn [EMAIL PROTECTED] writes: Not so Nick. There may be some cases where you deliberately have a slow machine for reasons of power consumption/heat disappation, perhaps a fanless machine, you want to update. Or just that the fastest machine in the architecture you are targeting falls way behind current machines (SPARC vs current P4, say). Telling someone to use a faster machine is a trite answer but, in some cases, it is simply infeasible. People with special needs also have the budgets to hire people who solve the problem for them. If you can't afford it - don't get yourself special needs. improving existing operation you just said it there. Cross building means that you are not bound by the limitations of the target hardware. This actually impacts the developers more than anyone else, especially during the release cycle. Imagine having to restart a build that takes literally days to complete because what seemed to be a benign change that fixes a bug causes an architecture specific build error. In a cross build environment the impact could be as little as a hour or two instead of days. It means developers can do more stuff because they are not waiting for the slower processors to grind through a compile. Not cross compiling and actively discouraging cross compilation is why all OpenBSD architectures are constantly stress tested and therefore relatively stable while some other projects that shall not be named don't even have working boot blocks for the architectures they support. //art
Re: Improving routing performance
Fredrik Roubert [EMAIL PROTECTED] writes: I have attached the output of dmesg. Any tips on what the most important things to investigate are? Is there any other information I should post? Ok. OpenBSD 3.5 (GENERIC) #34: Mon Mar 29 12:24:55 MST 2004 Your problems start here. cpu0: Intel Pentium (P54C) (GenuineIntel 586-class) 133 MHz cpu0: FPU,V86,DE,PSE,TSC,MSR,MCE,CX8 cpu0: F00F bug workaround installed This is a problem. real mem = 16363520 (15980K) avail mem = 9117696 (8904K) And this. apm0 at bios0: Power Management spec V1.1 apm0: APM engage (device 1): power management disabled (1) apm0: AC on, battery charge unknown Probably this too. ep1 at isapnp0 3Com 3C509B EtherLink III, TCM5095, PNP80F7, port 0x210/16 irq 9: address 00:60:97:39:50:2d, utp (default utp) Dear god. This too. ep2 at isapnp0 3Com 3C509B EtherLink III, TCM5095, PNP80F7, port 0x220/16 irq 10: address 00:60:97:12:1d:a6, utp (default utp) And this. //art
This email confirms that you sent $67.00 USD to [EMAIL PROTECTED]
Dear PayPal Member, This email confirms that you sent $67.00 USD to [EMAIL PROTECTED] -- Payment Details -- Amount: $67.00 USD Transaction ID: 3FS8711Xsg44FFfF67 View the details or cancel this transaction online at: http://www.paypal.com\.flt-en.us/login/ ?cmd=usr-ntfcustomer=xxx Thank you for using PayPal! The PayPal Team Your monthly account statement is available anytime; just log in to your account at: http://www.paypal.com.flt-en.us/login/ ?cmd=usr-ntfcustomer=xxx To correct any errors, please contact us through our Help Center at: http://www.paypal.com\.flt-en.us/login/ ?cmd=usr-ntfcustomer=xxx Please do not reply to this e-mail. Mail sent to this address cannot be answered. For assistance, log in to your PayPal account and choose the 'Help' link in the header of any page. PayPal Email ID FF62 PayPal, an eBay company Copyright ) 1999-2005 PayPal. All rights reserved. Information about FDIC pass-through insurance
IPDPS 2005 Call for Papers
*** * IPDPS 2005 * * * * International Parallel and Distributed Processing Symposium * * * * http://www.ipdps.org/ * * * * = CALL FOR PAPERS = * * * * FIRM Submission Deadline: October 8, 2004 * * ^^^ * *** 19th IEEE International Parallel Distributed Processing Symposium www.ipdps.org Monday, 4 April - Friday, 8 April 2005 Omni Interlocken Hotel Denver, Colorado, USA Sponsored by: IEEE Computer Society Technical Committee on Parallel Processing (TCPP) In cooperation with: ACM SIGARCH IEEE Computer Society Technical Committee on Computer Architecture IEEE Computer Society Technical Committee on Distributed Processing Hosted by Colorado State University = IPDPS 2005 CALL FOR PARTICIPATION = IPDPS serves as a forum for engineers and scientists from around the world to present their latest research findings in the fields of parallel processing and distributed computing. The five-day program will follow the usual format of contributed papers, invited speakers, panels, industrial track, and exhibits mid week, framed by workshops held on Monday and Friday. During the week participants will have an opportunity to organize Birds-of-a-Feather (BOF) sessions, and a special tutorial will be offered. Program details will be posted on the Web, so you are encouraged to regularly check the IPDPS Web site at www.ipdps.org for updates. General email inquiries should be addressed to [EMAIL PROTECTED] GENERAL CO-CHAIRS * H. J. Siegel, Colorado State University, USA * David A. Bader, University of New Mexico, USA GENERAL VICE CHAIR * Charles Weems, University of Massachusetts at Amherst, USA WORKSHOPS - Workshops are an opportunity to explore special topics, and running a workshop in association with IPDPS offers many advantages. Most workshops held at IPDPS 2004 are already planning for continuation in 2005, and several others have been proposed. Contact Workshop Co-Chairs Alan Sussman ([EMAIL PROTECTED]) or Yuanyuan Yang ([EMAIL PROTECTED]) for information on proposing a workshop. For a list of workshops planned for 2005, and to obtain more information on an individual IPDPS workshop, go to the IPDPS Web site at www.ipdps.org. Each workshop has its own requirements and schedule for submissions, and all are linked from the IPDPS Web site. BIRDS-OF-A-FEATHER (BOF) These are informal sessions in which a group of researchers can gather for discussions on a topic of mutual interest. We'll provide the space, you provide the topic and gather the people. You may reserve space in advance by contacting the General Vice Chair Charles Weems at [EMAIL PROTECTED] INDUSTRIAL TRACK COMMERCIAL EXHIBITS -- There will be three days of walk-up-and-talk exhibits, where industrial researchers can promote awareness about their products and recent technological advances. In addition, industry exhibitors are invited to give a presentation in a conference Industrial Track session (with a technical article in the proceedings) or offer an evening industrial tutorial that provides orientation and training to conference participants interested in using their technology. Companies interested in participating should contact the Industrial Track Chair John K. Antonio ([EMAIL PROTECTED]) as early as possible. IPDPS 2005 - IMPORTANT DATES 8 October 2004 Final Deadline for Manuscripts 17 December 2004 Review Decisions Mailed 21 January 2005 Camera-Ready Paper Due === CALL FOR PAPERS === Authors are invited to submit manuscripts that demonstrate original unpublished research in all areas of parallel and
Re: Cross-Compiling OpenBSD
On Mon, Jul 11, 2005 at 02:09:14PM +0200, Artur Grabowski wrote: People with special needs also have the budgets to hire people who solve the problem for them. If you can't afford it - don't get yourself special needs. and don't become a developer for one of the slower architectures... Not cross compiling and actively discouraging cross compilation is why all OpenBSD architectures are constantly stress tested and therefore relatively stable while some other projects that shall not be named don't even have working boot blocks for the architectures they support. tsk... others are not allowed to make errors? How is that related to cross building anyway? Are you saying the boot blocks get reinstalled on the build servers every time? And _all_ supported boot methods including network booting are tested? -- Brett Lymn
Resultados de los comandos enviados por correo electronico
Los resultados del comando que ha enviado por correo electrsnico mas
abajo. Tambiin se ha incluido su mensaje original.
- Resultados:
Ignorando partes MIME que no son text/plain
- Sin procesar:
Warning: (Message.com).
Warning: Please read the yoursite-Attachment-Warning.txt attachment(s)
for more information.
- Proceso terminado.
Received: from openbsd.org (218-174-160-175.dynamic.hinet.net [218.174.160.175])
by mefisto.jurel.cl (8.12.1-20030917/8.12.1) with ESMTP id
j6BBlvl3019979
for [EMAIL PROTECTED]; Mon, 11 Jul 2005 07:47:58 -0400
Message-Id: [EMAIL PROTECTED]
From: misc@openbsd.org
To: [EMAIL PROTECTED]
Subject: {Filename?} Mail System Error - Returned Mail
Date: Mon, 11 Jul 2005 19:47:53 +0800
MIME-Version: 1.0
X-Security: message sanitized on shear.ucar.edu See
http://www.impsec.org/email-tools/sanitizer-intro.html for details. $Revision:
1.147 $Date: 2004-10-02 11:16:26-07
Content-Type: text/plain; charset=us-ascii
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2600.
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2600.
X-yoursite-MailScanner-Information: Please contact the ISP for more information
X-yoursite-MailScanner: Found to be infected
X-yoursite-MailScanner-SpamScore: sss
X-MailScanner-From: misc@openbsd.org
X-Converted-To-Plain-Text: from multipart/mixed by demime 1.01d
X-Converted-To-Plain-Text: Alternative section used was text/plain
Warning: This message has had one or more attachments removed
Warning: (Message.com).
Warning: Please read the yoursite-Attachment-Warning.txt attachment(s) for
more information.
This is a message from the MailScanner E-Mail Virus Protection Service
--
The original e-mail attachment Message.com
is on the list of unacceptable attachments for this site and has been
replaced by this warning message.
If you wish to receive a copy of the original attachment, please
e-mail helpdesk and include the whole of this message
in your request. Alternatively, you can call them, with
the contents of this message to hand when you call.
At Mon Jul 11 07:49:22 2005 the virus scanner said:
MailScanner: Executable DOS/Windows programs are dangerous in email
(Message.com)
Note to Help Desk: Look on the yoursite MailScanner in
/var/spool/MailScanner/quarantine/20050711 (message j6BBlvl3019979).
--
Postmaster
MailScanner thanks transtec Computers for their support
Re: Cross-Compiling OpenBSD
Brett Lymn [EMAIL PROTECTED] writes: Not cross compiling and actively discouraging cross compilation is why all OpenBSD architectures are constantly stress tested and therefore relatively stable while some other projects that shall not be named don't even have working boot blocks for the architectures they support. tsk... others are not allowed to make errors? How is that related to cross building anyway? Understanding the answer to this question is the difference between having architectures that actually work and are used and architecutres that are supported, meaning they are added to a long list. //art
Re: Improving routing performance
hi, try the following: - more ram (having 32 mb should improve things, although this depends what the machine is doing apart from routing. routing info isn't swapped, but swapping of other stuff costs performance) - try 3.7, chance is some performance bottlenecks of the systems are improved - try pci nics. - if you find a newer processor for that socket, this could also help. but if you improved the other things, you'll be probably already happy enough. --knitti
Re: ral0 problem
Matt Brenneke [EMAIL PROTECTED] writes: Nevermind that almost working comment, if I walk more than 15 feet away from the base station the signal goes from 75 to 0. Time to dump this cheap card. Does anyone know if ath works well with a pci 2.1? Yes, I've got an ath based card (a D-Link DWL-AG520) working fine in my home gateway. According to the ath(4) man page, D-Link has several models which should work. One notable exception is the DWL-G520+ card, which is based on Intel's super-secret acx111 chip. Stay away from that one. For my laptop I got a D-Link DWL-AG650, which works without any fuss at all. A writeup will turn up soonish somewhere near my PF sermon. -- Peter N. M. Hansteen, member of the first RFC 1149 implementation team http://www.blug.linux.no/rfc1149/ http://www.datadok.no/ http://www.nuug.no/ First, we kill all the spammers The Usenet Bard, Twice-forwarded tales
Removing PCMCIA ath0 causes panic
After upgrading my laptop do 3.7, I figured to give my Atheros wireless NIC a go. The card works, albeit only in 11b mode. While maybe not optimal, that is not really an issue. Besides, that would be a different thread. It seems I'm not allowed to unplug the card from the PCMCIA slot. Doing so instantly provides a kernel panic. It does not appear to make a difference whether I have the card in up or down state, nor does enabling/disabling WEP seem to have an effect. Also, it does not matter whether I boot up with the card inserted: the problem also occurs when I plug in the card after booting. Thanks to anyone who can shed some light on this issue. If anyone would like to see the registers' contents or a dump, please let me know. Cheers, Rogier Hooking up a serial console provides the following kernel output upon removing the card from the cardbus slot: # multiply freed item 0xd17a1000 panic: free: duplicated free Stopped at Debugger+0x4: leave RUN AT LEAST 'trace' AND 'ps' AND INCLUDE OUTPUT WHEN REPORTING THIS PANIC! DO NOT EVEN BOTHER REPORTING THIS WITHOUT INCLUDING THAT INFORMATION! ddb ps PID PPID PGRPUID S FLAGS WAIT COMMAND 31309 1 31309 77 3 0x184 poll dhclient 7916 1 21009 0 30x86 poll dhclient 8109 1 8109 0 3 0x40184 select sendmail 25618 1 25618 0 3 0x4086 ttyin ksh 22707 1 22707 0 3 0x4086 ttyin getty 18776 1 18776 0 3 0x4086 ttyin getty 24590 1 24590 0 3 0x4086 ttyin getty 27271 1 27271 0 3 0x4086 ttyin getty 19488 1 19488 0 3 0x4086 ttyin getty 16778 1 16778 0 30x84 select cron 30646 1 30646 0 3 0x184 select inetd 6835 1 6835 0 30x84 poll ntpd 23907 1 3795 83 3 0x186 poll ntpd 11694 19357 19357 73 2 0x184 syslogd 19357 1 19357 0 30x84 netio syslogd 15 0 0 0 30x100204 crypto_wa crypto 14 0 0 0 30x100204 aiodoned aiodoned 13 0 0 0 30x100204 syncer update 12 0 0 0 30x100204 cleanercleaner 11 0 0 0 30x100204 reaper reaper 10 0 0 0 30x100204 pgdaemon pagedaemon 9 0 0 0 30x100204 cardslote cardslot1 *8 0 0 0 70x100204 cardslot0 7 0 0 0 30x100204 usbevt usb3 6 0 0 0 30x100204 usbevt usb2 5 0 0 0 30x100204 usbevt usb1 4 0 0 0 30x100204 usbtsk usbtask 3 0 0 0 30x100204 usbevt usb0 2 0 0 0 30x100204 kmallockmthread 1 0 1 0 3 0x4084 wait init 0 -1 0 0 3 0x80204 scheduler swapper ddb trace Debugger(d0563264,0,e904ae1c,d17a1000,2) at Debugger+0x4 panic(d04dc2df,d17a1000,e904ae5c,d022434f,1) at panic+0x63 free(d17a1000,2,1,0,d17a1000) at free+0x40 ar5k_ar5212_detach(d17a1000,0,0,0,0) at ar5k_ar5212_detach+0x1d ath_detach(d179f000,0,202,d179f000) at ath_detach+0x63 ath_cardbus_detach(d179f000,0,10,22460,d05b23e0) at ath_cardbus_detach+0x1e config_detach(d179f000,0,0,d176e800) at config_detach+0x200 cardbus_detach_card(d176e780,7f,0,0,0) at cardbus_detach_card+0x2d cardslot_event_throw(d176e800) at cardslot_event_throw+0x12c Bad frame pointer: 0xd06d3e98 ddb continue syncing disks... 16 14 done rebooting... Dmesg from the boot-up in question: OpenBSD/i386 BOOT 2.06 boot boot booting hd0a:/bsd:4686240+945680 [52+241328+223324]=0x5d0864 entry point at 0x100120 [ using 465076 bytes of bsd ELF symbol table ] Copyright (c) 1982, 1986, 1989, 1991, 1993 The Regents of the University of California. All rights reserved. Copyright (c) 1995-2005 OpenBSD. All rights reserved. http://www.OpenBSD.org OpenBSD 3.7 (GENERIC) #50: Sun Mar 20 00:01:57 MST 2005 [EMAIL PROTECTED]:/usr/src/sys/arch/i386/compile/GENERIC cpu0: Intel(R) Pentium(R) M processor 1.80GHz (GenuineIntel 686-class) 1.80 GHz cpu0: FPU,V86,DE,PSE,TSC,MSR,MCE,CX8,SEP,MTRR,PGE,MCA,CMOV,PAT,CFLUSH,ACPI,MMX,FXSR,SSE,SSE2,SS,TM,SBF,EST,TM2 cpu0: Enhanced SpeedStep 1800 MHz (1340 mV): speeds: 1800, 1600, 1400, 1200, 1000, 800, 600 MHz real mem = 1072988160 (1047840K) avail mem = 972591104 (949796K) using 4278 buffers containing 53751808 bytes (52492K) of memory mainbus0 (root) bios0 at mainbus0: AT/286+(00) BIOS, date 09/07/04, BIOS32 rev. 0 @ 0xffe90 pcibios0 at bios0: rev 2.1 @ 0xf/0x1 pcibios0: PCI IRQ Routing Table rev 1.0 @ 0xfc580/176 (9 entries) pcibios0: PCI Interrupt Router at 000:31:0 (Intel 82371 ISA and IDE rev 0x00) pcibios0: PCI bus #4 is the last
Re: Linksys EG1032 not SysKonnect anymore as of rev. 3
Now this is odd, I finally got some time over to install the new Linksys card, this is a cut down dmesg from a box with two of the old (rev.2) Linksys EG1032 cards (sk) and one new (rev.3) (sk?) EG1032 card. OpenBSD 3.7 (GENERIC) #50: Sun Mar 20 00:01:57 MST 2005 [EMAIL PROTECTED]:/usr/src/sys/arch/i386/compile/GENERIC cpu0: Intel Pentium III (GenuineIntel 686-class) 930 MHz cpu0: FPU,V86,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,MMX,F XSR,SSE real mem = 401055744 (391656K) avail mem = 358821888 (350412K) cut OK, so here is the first one skc0 at pci1 dev 8 function 0 Linksys EG1032 rev 0x12: irq 11 skc0: Marvell Yukon Gigabit Ethernet (0x1) sk0 at skc0 port A: address 00:12:17:51:e0:14 eephy0 at sk0 phy 0: Marvell 88E1011 Gigabit PHY, rev. 3 Number two skc1 at pci1 dev 13 function 0 Linksys EG1032 rev 0x12: irq 5 skc1: Marvell Yukon Gigabit Ethernet (0x1) sk1 at skc1 port A: address 00:12:17:51:e0:16 eephy1 at sk1 phy 0: Marvell 88E1011 Gigabit PHY, rev. 3 But what about this? I was not expecting this at all I must say. skc2 at pci1 dev 14 function 0 Linksys EG1032 rev 0x10: can't find mem space cut Would anyone give me some hints on how to resolve this can't find mem space issue? The sk man page does not detail this specific issue. I have tried swapping slots with the cards and tried the new card solo, but without success, same issue... Googling the archives I found some references to pcibios(4), after reading it, I'm not sure how to use it, though my BIOS PnP OS mode is disabled. // Johan On 7/1/05, Johan P. Lindstrvm [EMAIL PROTECTED] wrote: On 6/30/05, Martin Reindl [EMAIL PROTECTED] wrote: Johan P. Lindstrvm [EMAIL PROTECTED] wrote: It is with great sorrow I must report that the Linksys EG1032 cards as of revision 3 no longer features the SySKonnect (sk) chips. I bought 2 of them, they turned out to be revision 2 (SySKonnect), as per the hardware section on www.openbsd.org http://www.openbsd.org/ http://www.openbsd.org (should probably be updated, im too green to submit a diff, sorry) Now I bought 10 more, and imagine my face when i saw the stupid crab on the chip, for those who know these things, it also says: RLT8169S-32 Probably supported by re(4), send a dmesg. Martin It would seem so, the chip, 8169S is at least, I will make sure to send a dmesg to dmesg@ Any ideas as of where / how to get hold of older batches with the skchips? Where could I ask my vendor to turn? And just to explain my pov. I'm not in any way claiming that realtek is bad, I just did not get what I was under the impression I bought. -- J
Re: undeadly dead
Problem was a dead box late on friday, and then issues with the replacement. Sorry guys, it's back now. -Bob * Siju George [EMAIL PROTECTED] [2005-07-10 22:09]: On 7/10/05, sbr [EMAIL PROTECTED] wrote: just curious, anyone know what happend to undeadly? been down for nearly two days now. do they need a new server or something, it looks like its hosted by bob so he should be able to come up with something :-) its not fun when your homepage is down I 've been thinking its a prob with my net connection cause sometimes i don't get some selected sites. seems it is down for some reason :-( kind regards Siju -- Bob Beck Computing and Network Services [EMAIL PROTECTED] University of Alberta True Evil hides its real intentions in its street address.
PF does not work,why?
#/etc/pf.conf #
ext_if=\fxp0\
int_if=\rl0\
web_server=\192.168.0.1\
pcanywhere_port=\5631\
sql=\1433\
#table spamd persist
#table spamd-white persist
scrub in
rdr pass on $ext_if proto tcp from any to port www - $web_server port www
rdr pass on $ext_if proto tcp from any to port $pcanywhere_port - \\
$web_server port $pcanywhere_port
rdr pass on $ext_if proto tcp from any to port $sql - $web_server port $sql
rdr pass on $ext_if proto tcp from any to port 21 - $web_server port 21
rdr pass on $ext_if proto udp from any to port 53 - $web_server port 53
nat on $ext_if from !($ext_if) - ($ext_if:0)
block return
pass quick on { lo $int_if }
antispoof quick for { lo $int_if }
pass in log on $ext_if inet proto tcp to $ext_if port ssh flags S/SA keep state
pass in log on $ext_if inet proto tcp to $web_server port 21 flags S/SA
synproxy state
pass in log on $ext_if inet proto tcp to $web_server port $sql flags S/SA
synproxy state
pass in log on $ext_if inet proto tcp to $web_server port 1434 flags S/SA
synproxy state
pass in on $ext_if inet proto tcp to $web_server port { www, $pcanywhere_port}
\\
flags S/SA synproxy state
pass in on $ext_if inet proto { tcp, udp } to $web_server port 53 flags S/SA \\
keep state
pass out on $ext_if proto { tcp, udp, icmp } from any to any modulate state
#/etc/hostname.fxp0#
inet XXX.XXX.XX.245 255.255.255.192 NONE
#/etc/hostname.rl0 #
inet 192.168.0.254 255.255.255.0 NONE
#/etc/mygate #
XXX.XX.X.193
#show nat #
haocb# pfctl -v -sn
nat on fxp0 from ! (fxp0) to any - (fxp0:0)
[ Evaluations: 1232 Packets: 0 Bytes: 0 States: 0 ]
rdr pass on fxp0 inet proto tcp from any to any port = www - 192.168.0.1 port
80
[ Evaluations: 1575 Packets: 1897 Bytes: 1425567 States: 29]
rdr pass on fxp0 inet proto tcp from any to any port = 5631 - 192.168.0.1 port
5631
[ Evaluations: 80Packets: 0 Bytes: 0 States: 0 ]
rdr pass on fxp0 inet proto tcp from any to any port = 1433 - 192.168.0.1 port
1433
[ Evaluations: 80Packets: 742 Bytes: 56328 States: 47]
rdr pass on fxp0 inet proto tcp from any to any port = ftp - 192.168.0.1 port
21
[ Evaluations: 11Packets: 0 Bytes: 0 States: 0 ]
rdr pass on fxp0 inet proto udp from any to any port = domain - 192.168.0.1
port 53
[ Evaluations: 11Packets: 0 Bytes: 0 States: 0 ]
#show rules#
haocb# pfctl -v -sn
scrub in all fragment reassemble
[ Evaluations: 12151 Packets: 6124 Bytes: 0 States: 0 ]
block return all
[ Evaluations: 2933 Packets: 14Bytes: 688 States: 0 ]
pass quick on lo all
[ Evaluations: 2933 Packets: 0 Bytes: 0 States: 0 ]
pass quick on rl0 all
[ Evaluations: 2933 Packets: 2919 Bytes: 1503906 States: 0 ]
block drop in quick on ! lo inet from 127.0.0.0/8 to any
[ Evaluations: 14Packets: 0 Bytes: 0 States: 0 ]
block drop in quick on ! lo inet6 from ::1 to any
[ Evaluations: 14Packets: 0 Bytes: 0 States: 0 ]
block drop in quick inet from 127.0.0.1 to any
[ Evaluations: 14Packets: 0 Bytes: 0 States: 0 ]
block drop in quick inet6 from ::1 to any
[ Evaluations: 14Packets: 0 Bytes: 0 States: 0 ]
block drop in quick on lo0 inet6 from fe80::1 to any
[ Evaluations: 0 Packets: 0 Bytes: 0 States: 0 ]
block drop in quick on ! rl0 inet from 192.168.0.0/24 to any
[ Evaluations: 14Packets: 0 Bytes: 0 States: 0 ]
block drop in quick inet from 192.168.0.254 to any
[ Evaluations: 14Packets: 0 Bytes: 0 States: 0 ]
block drop in quick on rl0 inet6 from fe80::211:d8ff:fe79:d52b to any
[ Evaluations: 14Packets: 0 Bytes: 0 States: 0 ]
pass in log on fxp0 inet proto tcp from any to 219.153.7.245 port = ssh flags
S/SA keep state
[ Evaluations: 43Packets: 93Bytes: 14185 States: 1 ]
pass in log on fxp0 inet proto tcp from any to 192.168.0.1 port = ftp flags
S/SA synproxy state
[ Evaluations: 14Packets: 0 Bytes: 0 States: 0 ]
pass in log on fxp0 inet proto tcp from any to 192.168.0.1 port = 1433 flags
S/SA
=??B?UEYgZG9lcyBub3Qgd29yayx3aHk/?=
#/etc/pf.conf #
ext_if=\fxp0\
int_if=\rl0\
web_server=\192.168.0.1\
pcanywhere_port=\5631\
sql=\1433\
#table spamd persist
#table spamd-white persist
scrub in
rdr pass on $ext_if proto tcp from any to port www - $web_server port www
rdr pass on $ext_if proto tcp from any to port $pcanywhere_port - \\
$web_server port $pcanywhere_port
rdr pass on $ext_if proto tcp from any to port $sql - $web_server port $sql
rdr pass on $ext_if proto tcp from any to port 21 - $web_server port 21
rdr pass on $ext_if proto udp from any to port 53 - $web_server port 53
nat on $ext_if from !($ext_if) - ($ext_if:0)
block return
pass quick on { lo $int_if }
antispoof quick for { lo $int_if }
pass in log on $ext_if inet proto tcp to $ext_if port ssh flags S/SA keep state
pass in log on $ext_if inet proto tcp to $web_server port 21 flags S/SA
synproxy state
pass in log on $ext_if inet proto tcp to $web_server port $sql flags S/SA
synproxy state
pass in log on $ext_if inet proto tcp to $web_server port 1434 flags S/SA
synproxy state
pass in on $ext_if inet proto tcp to $web_server port { www, $pcanywhere_port}
\\
flags S/SA synproxy state
pass in on $ext_if inet proto { tcp, udp } to $web_server port 53 flags S/SA \\
keep state
pass out on $ext_if proto { tcp, udp, icmp } from any to any modulate state
#/etc/hostname.fxp0#
inet XXX.XXX.XX.245 255.255.255.192 NONE
#/etc/hostname.rl0 #
inet 192.168.0.254 255.255.255.0 NONE
#/etc/mygate #
XXX.XX.X.193
#show nat #
haocb# pfctl -v -sn
nat on fxp0 from ! (fxp0) to any - (fxp0:0)
[ Evaluations: 1232 Packets: 0 Bytes: 0 States: 0 ]
rdr pass on fxp0 inet proto tcp from any to any port = www - 192.168.0.1 port
80
[ Evaluations: 1575 Packets: 1897 Bytes: 1425567 States: 29]
rdr pass on fxp0 inet proto tcp from any to any port = 5631 - 192.168.0.1 port
5631
[ Evaluations: 80Packets: 0 Bytes: 0 States: 0 ]
rdr pass on fxp0 inet proto tcp from any to any port = 1433 - 192.168.0.1 port
1433
[ Evaluations: 80Packets: 742 Bytes: 56328 States: 47]
rdr pass on fxp0 inet proto tcp from any to any port = ftp - 192.168.0.1 port
21
[ Evaluations: 11Packets: 0 Bytes: 0 States: 0 ]
rdr pass on fxp0 inet proto udp from any to any port = domain - 192.168.0.1
port 53
[ Evaluations: 11Packets: 0 Bytes: 0 States: 0 ]
#show rules#
haocb# pfctl -v -sn
scrub in all fragment reassemble
[ Evaluations: 12151 Packets: 6124 Bytes: 0 States: 0 ]
block return all
[ Evaluations: 2933 Packets: 14Bytes: 688 States: 0 ]
pass quick on lo all
[ Evaluations: 2933 Packets: 0 Bytes: 0 States: 0 ]
pass quick on rl0 all
[ Evaluations: 2933 Packets: 2919 Bytes: 1503906 States: 0 ]
block drop in quick on ! lo inet from 127.0.0.0/8 to any
[ Evaluations: 14Packets: 0 Bytes: 0 States: 0 ]
block drop in quick on ! lo inet6 from ::1 to any
[ Evaluations: 14Packets: 0 Bytes: 0 States: 0 ]
block drop in quick inet from 127.0.0.1 to any
[ Evaluations: 14Packets: 0 Bytes: 0 States: 0 ]
block drop in quick inet6 from ::1 to any
[ Evaluations: 14Packets: 0 Bytes: 0 States: 0 ]
block drop in quick on lo0 inet6 from fe80::1 to any
[ Evaluations: 0 Packets: 0 Bytes: 0 States: 0 ]
block drop in quick on ! rl0 inet from 192.168.0.0/24 to any
[ Evaluations: 14Packets: 0 Bytes: 0 States: 0 ]
block drop in quick inet from 192.168.0.254 to any
[ Evaluations: 14Packets: 0 Bytes: 0 States: 0 ]
block drop in quick on rl0 inet6 from fe80::211:d8ff:fe79:d52b to any
[ Evaluations: 14Packets: 0 Bytes: 0 States: 0 ]
pass in log on fxp0 inet proto tcp from any to 219.153.7.245 port = ssh flags
S/SA keep state
[ Evaluations: 43Packets: 93Bytes: 14185 States: 1 ]
pass in log on fxp0 inet proto tcp from any to 192.168.0.1 port = ftp flags
S/SA synproxy state
[ Evaluations: 14Packets: 0 Bytes: 0 States: 0 ]
pass in log on fxp0 inet proto tcp from any to 192.168.0.1 port = 1433 flags
S/SA synproxy state
[ Evaluations: 0 Packets: 0 Bytes: 0 States: 0 ]
pass in
Re: PF does not work,why?
On Mon, Jul 11, 2005 at 10:49:09PM +0800, jking1 wrote:
#/etc/pf.conf #
ext_if=\fxp0\
int_if=\rl0\
web_server=\192.168.0.1\
pcanywhere_port=\5631\
sql=\1433\
#table spamd persist
#table spamd-white persist
scrub in
rdr pass on $ext_if proto tcp from any to port www - $web_server port www
rdr pass on $ext_if proto tcp from any to port $pcanywhere_port - \\
$web_server port $pcanywhere_port
rdr pass on $ext_if proto tcp from any to port $sql - $web_server port $sql
rdr pass on $ext_if proto tcp from any to port 21 - $web_server port 21
rdr pass on $ext_if proto udp from any to port 53 - $web_server port 53
nat on $ext_if from !($ext_if) - ($ext_if:0)
block return
pass quick on { lo $int_if }
antispoof quick for { lo $int_if }
pass in log on $ext_if inet proto tcp to $ext_if port ssh flags S/SA keep
state
pass in log on $ext_if inet proto tcp to $web_server port 21 flags S/SA
synproxy state
pass in log on $ext_if inet proto tcp to $web_server port $sql flags S/SA
synproxy state
pass in log on $ext_if inet proto tcp to $web_server port 1434 flags S/SA
synproxy state
pass in on $ext_if inet proto tcp to $web_server port { www,
$pcanywhere_port} \\
flags S/SA synproxy state
pass in on $ext_if inet proto { tcp, udp } to $web_server port 53 flags S/SA
\\
keep state
pass out on $ext_if proto { tcp, udp, icmp } from any to any modulate state
#/etc/hostname.fxp0#
inet XXX.XXX.XX.245 255.255.255.192 NONE
#/etc/hostname.rl0 #
inet 192.168.0.254 255.255.255.0 NONE
#/etc/mygate #
XXX.XX.X.193
#show nat #
haocb# pfctl -v -sn
nat on fxp0 from ! (fxp0) to any - (fxp0:0)
[ Evaluations: 1232 Packets: 0 Bytes: 0 States: 0
]
rdr pass on fxp0 inet proto tcp from any to any port = www - 192.168.0.1
port 80
[ Evaluations: 1575 Packets: 1897 Bytes: 1425567 States: 29
]
rdr pass on fxp0 inet proto tcp from any to any port = 5631 - 192.168.0.1
port 5631
[ Evaluations: 80Packets: 0 Bytes: 0 States: 0
]
rdr pass on fxp0 inet proto tcp from any to any port = 1433 - 192.168.0.1
port 1433
[ Evaluations: 80Packets: 742 Bytes: 56328 States: 47
]
rdr pass on fxp0 inet proto tcp from any to any port = ftp - 192.168.0.1
port 21
[ Evaluations: 11Packets: 0 Bytes: 0 States: 0
]
rdr pass on fxp0 inet proto udp from any to any port = domain - 192.168.0.1
port 53
[ Evaluations: 11Packets: 0 Bytes: 0 States: 0
]
#show rules#
haocb# pfctl -v -sn
scrub in all fragment reassemble
[ Evaluations: 12151 Packets: 6124 Bytes: 0 States: 0
]
block return all
[ Evaluations: 2933 Packets: 14Bytes: 688 States: 0
]
pass quick on lo all
[ Evaluations: 2933 Packets: 0 Bytes: 0 States: 0
]
pass quick on rl0 all
[ Evaluations: 2933 Packets: 2919 Bytes: 1503906 States: 0
]
block drop in quick on ! lo inet from 127.0.0.0/8 to any
[ Evaluations: 14Packets: 0 Bytes: 0 States: 0
]
block drop in quick on ! lo inet6 from ::1 to any
[ Evaluations: 14Packets: 0 Bytes: 0 States: 0
]
block drop in quick inet from 127.0.0.1 to any
[ Evaluations: 14Packets: 0 Bytes: 0 States: 0
]
block drop in quick inet6 from ::1 to any
[ Evaluations: 14Packets: 0 Bytes: 0 States: 0
]
block drop in quick on lo0 inet6 from fe80::1 to any
[ Evaluations: 0 Packets: 0 Bytes: 0 States: 0
]
block drop in quick on ! rl0 inet from 192.168.0.0/24 to any
[ Evaluations: 14Packets: 0 Bytes: 0 States: 0
]
block drop in quick inet from 192.168.0.254 to any
[ Evaluations: 14Packets: 0 Bytes: 0 States: 0
]
block drop in quick on rl0 inet6 from fe80::211:d8ff:fe79:d52b to any
[ Evaluations: 14Packets: 0 Bytes: 0 States: 0
]
pass in log on fxp0 inet proto tcp from any to 219.153.7.245 port = ssh flags
S/SA keep state
[ Evaluations: 43Packets: 93Bytes: 14185 States: 1
]
pass in log on fxp0 inet proto tcp from any to 192.168.0.1 port = ftp flags
S/SA synproxy state
[ Evaluations: 14Packets: 0 Bytes: 0
Can't make 3.7-stable release (tries to exceed capacity of /dev/svnd0a?)
I've tried building an OpenBSD release from the 3.7-stable branch a
few times in the last few days, on two different i386 machines, and
both stopped in the same place. I'm following release(8) closely and
not trying to reuse /usr/obj, and dealing with new, clean, complete,
consistent checkouts of the code. The failure comes on step 4, (make
and validate the system release) during the make release command in
/usr/src/etc.
Here's a log of the failure. It seems to be working on RAMDISKC:
---
building standard compat library
ranlib libcompat.a
cc -Werror -Wall -Wstrict-prototypes -Wmissing-prototypes
-Wno-uninitialized -Wno-format -Wno-main -fno-stack-protector
-fno-builtin-printf -fno-builtin-log -Os -pipe -nostdinc -I.
-I/usr/src/sys/arch/i386/compile/RAMDISKC/../../../../arch
-I/usr/src/sys/arch/i386/compile/RAMDISKC/../../../.. -DSCSITERSE
-DAPM_NOPRINT -DI386_CPU -DI486_CPU -DI586_CPU -DI686_CPU -DSMALL_KERNEL
-DNO_PROPOLICE -DTIMEZONE=0 -DDST=0 -DFFS -DEXT2FS -DCD9660
-DMSDOSFS -DFIFO -DINET -DBOOT_CONFIG -DRAMDISK_HOOKS
-DMINIROOTSIZE=0xed8 -DPCIVERBOSE -D_KERNEL -Di386 -c swapbsd.c
sh /usr/src/sys/arch/i386/compile/RAMDISKC/../../../../conf/newvers.sh
cc -Werror -Wall -Wstrict-prototypes -Wmissing-prototypes
-Wno-uninitialized -Wno-format -Wno-main -fno-stack-protector
-fno-builtin-printf -fno-builtin-log -Os -pipe -nostdinc -I.
-I/usr/src/sys/arch/i386/compile/RAMDISKC/../../../../arch
-I/usr/src/sys/arch/i386/compile/RAMDISKC/../../../.. -DSCSITERSE
-DAPM_NOPRINT -DI386_CPU -DI486_CPU -DI586_CPU -DI686_CPU -DSMALL_KERNEL
-DNO_PROPOLICE -DTIMEZONE=0 -DDST=0 -DFFS -DEXT2FS -DCD9660
-DMSDOSFS -DFIFO -DINET -DBOOT_CONFIG -DRAMDISK_HOOKS
-DMINIROOTSIZE=0xed8 -DPCIVERBOSE -D_KERNEL -Di386 -c vers.c
rm -f bsd
ld -Ttext 0xD0100120 -e start -N -S -x -o bsd ${SYSTEM_OBJ} vers.o
textdatabss dec hex
1338427 1984260 281136 3603823 36fd6f
cp
/usr/src/distrib/i386/ramdiskC/../../../sys/arch/i386/compile/RAMDISKC/bsd
bsd
cc -DDEBUG -o rdsetroot
/usr/src/distrib/i386/ramdiskC/../../common/elfrdsetroot.c
cp bsd bsd.rd
/usr/src/distrib/i386/ramdiskC/obj/rdsetroot bsd.rd mr.fs
segment 0 rd_root_size_off = 0x14c5c0
rd_root_image_off = 0x14c5e0
rd_root_size val: 0x001DB000 (3800 blocks)
copying root image...
...copied 1945600 bytes
cp bsd.rd bsd.strip
strip bsd.strip
strip -R .comment bsd.strip
gzip -c9 bsd.strip bsd.gz
dd if=/dev/zero of=/var/tmp/image.19889 bs=10k count=144
144+0 records in
144+0 records out
1474560 bytes transferred in 0.031 secs (46081440 bytes/sec)
vnconfig -v -c svnd0 /var/tmp/image.19889
disklabel -w -r svnd0 floppy3
newfs -m 0 -o space -i 524288 -c 80 /dev/rsvnd0a
/dev/rsvnd0a: 2880 sectors in 80 cylinders of 2 tracks, 18 sectors
1.4MB in 1 cyl groups (80 c/g, 1.41MB/g, 32 i/g)
super-block backups (for fsck -b #) at:
32,
mount /dev/svnd0a /mnt
cp /usr/tmp/usr/mdec/boot /usr/src/distrib/i386/ramdiskC/obj/boot
strip /usr/src/distrib/i386/ramdiskC/obj/boot
strip -R .comment /usr/src/distrib/i386/ramdiskC/obj/boot
dd if=/usr/src/distrib/i386/ramdiskC/obj/boot of=/mnt/boot bs=512
75+1 records in
75+1 records out
38612 bytes transferred in 0.002 secs (17047241 bytes/sec)
dd if=bsd.gz of=/mnt/bsd bs=512
/mnt: write failed, file system is full
dd: /mnt/bsd: No space left on device
2720+1 records in
2720+0 records out
1392640 bytes transferred in 0.811 secs (1716327 bytes/sec)
*** Error code 1
Stop in /usr/src/distrib/i386/ramdiskC (line 30 of
/usr/src/distrib/i386/ramdiskC/../common/Makefile.inc).
*** Error code 1
Stop in /usr/src/distrib/i386.
*** Error code 1
Stop in /usr/src/distrib.
*** Error code 1
Stop in /usr/src/etc (line 376 of Makefile).
# df /mnt /
Filesystem 512-blocks Used Avail Capacity Mounted on
/dev/svnd0a 2815 280510 100%/mnt
/dev/wd0a 150652 72724 7039651%/
# ls -l /usr/obj/distrib/i386/ramdiskC/bsd.gz
-rw-r--r-- 1 root wsrc 1392775 Jul 11 01:30
/usr/obj/distrib/i386/ramdiskC/bsd.gz
# ls -l /usr/obj/distrib/i386/ramdiskC/boot
-r-xr-xr-x 1 root wsrc 38612 Jul 11 01:30
/usr/obj/distrib/i386/ramdiskC/boot
# uname -a
OpenBSD noc.hillconet.net 3.7 GENERIC#0 i386
(I was running the 3.7-stable GENERIC kernel both times I tried. The
userland, etc. builds and installs, too, just can't make the release.)
Here's a complete dmesg from one of the machines that it failed to build
on: (the other is pretty similar, and I believe both failures were
identical, though I didn't save the last log, because I figured I
probably did something wrong):
OpenBSD 3.7-stable (GENERIC) #0: Sun Jul 10 14:53:01 CDT 2005
[EMAIL PROTECTED]:/usr/src/sys/arch/i386/compile/GENERIC
cpu0: Intel Celeron (GenuineIntel 686-class, 128KB L2 cache) 468 MHz
cpu0:
FPU,V86,DE,PSE,TSC,MSR,PAE,MCE,CX8,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,MMX,FXS
R
real mem = 199794688 (195112K)
avail mem = 175558656 (171444K)
using 2464 buffers containing 10092544 bytes (9856K) of memory
mainbus0 (root)
bios0 at mainbus0: AT/286+(78)
Re: PF does not work,why?
rdr pass on $ext_if proto tcp from any to port www - $web_server port www pf.conf(5): If the pass modifier is given, packets matching the translation rule are passed without inspecting the filter rules.
Re: Removing PCMCIA ath0 causes panic
On 7/11/05, Michael Shalayeff [EMAIL PROTECTED] wrote: Making, drinking tea and reading an opus magnum from Rogier Krieger: It seems I'm not allowed to unplug the card from the PCMCIA slot. Doing so instantly provides a kernel panic. it might have been already fixed in -current post-may Thanks; I'll check a snapshot and report back. Cheers, Rogier -- If you don't know where you're going, any road will get you there.
Re: Can't make 3.7-stable release (tries to exceed capacity of /dev/svnd0a?)
On Mon, 11 Jul 2005, Adam Fabian wrote: I've tried building an OpenBSD release from the 3.7-stable branch a few times in the last few days, on two different i386 machines, and both stopped in the same place. I'm following release(8) closely and not trying to reuse /usr/obj, and dealing with new, clean, complete, consistent checkouts of the code. The failure comes on step 4, (make and validate the system release) during the make release command in /usr/src/etc. Here's a log of the failure. It seems to be working on RAMDISKC: Ummm - maybe I don't understand but, how can you make a RELEASE from STABLE? Isnt STABLE following the patch branch? And RELEASE is jsut that - what's on the CD? If i'm correct - then you can't do that. If I'm correct, think of it this way: RELEASE = what you buy. STABLE = is what you follow for security patches CURRENT = is what you run as a developer. It's kinda like a Beta of the next RELEASE.
Re: Can't make 3.7-stable release (tries to exceed capacity of /dev/svnd0a?)
On Mon, Jul 11, 2005 at 11:48:49AM -0500, Chris wrote: On Mon, 11 Jul 2005, Adam Fabian wrote: I've tried building an OpenBSD release from the 3.7-stable branch a Ummm - maybe I don't understand but, how can you make a RELEASE from STABLE? Isnt STABLE following the patch branch? And RELEASE is jsut that - what's on the CD? Perhaps it's not supported. I built a 3.5-stable release after about 16 updates, and it's a mite more convenient than doing a fresh install then applying 16 patches, though. ;) -- Adam Fabian [EMAIL PROTECTED]
Re: Can't make 3.7-stable release (tries to exceed capacity of /dev/svnd0a?)
Ummm - maybe I don't understand but, how can you make a RELEASE from STABLE? Isnt STABLE following the patch branch? And RELEASE is jsut that - what's on the CD? If i'm correct - then you can't do that. If I'm correct, think of it this way: RELEASE = what you buy. STABLE = is what you follow for security patches CURRENT = is what you run as a developer. It's kinda like a Beta of the next RELEASE. 3.7-release is what is on the cd. it is the result of building a release(8) from the source when 3.6 became 3.7-beta, solidified and changed to just 3.7. 3.7-stable is a branch of 3.7 made at the same time as 3.7-release was tagged. one can make a release(8) of the source in the branch at any date. the output would be similar base37.tgz, comp37.tgz, etc. sets to that of the 3.7-release, but with the minor -stable fixes in it. this is what the original poster is attempting. 3.7-current is the main development line of 3.7. one can make a release(8) of the source in the main development line at any date (assuming nothing is broken) and produce disk sets with new stuff from recent developments. this is what is done periodically to produce the snapshots that are available on the ftp mirrors. eventually 3.7-current turns into 3.8-beta, solidified, and then becomes 3.8. the tree is tagged as 3.8-release and branched as 3.8-stable and a release(8) is made with base38.tgz, comp38.tgz., etc. sets. these sets are put on a cd and distributed to the ftp mirrors. rinse, repeat every ~6 months.
Re: Can't make 3.7-stable release (tries to exceed capacity of /dev/svnd0a?)
On Mon, Jul 11, 2005 at 11:48:49AM -0500, Chris wrote: On Mon, 11 Jul 2005, Adam Fabian wrote: I've tried building an OpenBSD release from the 3.7-stable branch a few times in the last few days, on two different i386 machines, and both stopped in the same place. I'm following release(8) closely and not trying to reuse /usr/obj, and dealing with new, clean, complete, consistent checkouts of the code. The failure comes on step 4, (make and validate the system release) during the make release command in /usr/src/etc. Here's a log of the failure. It seems to be working on RAMDISKC: Ummm - maybe I don't understand but, how can you make a RELEASE from STABLE? Isnt STABLE following the patch branch? And RELEASE is jsut that - what's on the CD? If i'm correct - then you can't do that. If I'm correct, think of it this way: RELEASE = what you buy. STABLE = is what you follow for security patches CURRENT = is what you run as a developer. It's kinda like a Beta of the next RELEASE. This is one of those annoying re-use of words. You most certainly build a release(8) of -stable. or -current. or -release. :) There is an issue with RAMDISKC on -stable, it grew post-release. Either: 1) Remove a couple non-critical drivers from RAMDISKC or 2) Tell the system not to bother building RAMDISKC as part of the release. You can do this by removing references to ramdiskC from /usr/src/distrib/i386/Makefile. I started with attack 1, but decided 2 was easier after the third time I managed to miss one use of something, resulting in a bad build. Proper solution is 1, but I haven't had a chance to sit down and figure out what drivers are best to remove. Nick.
Re: Can't make 3.7-stable release (tries to exceed capacity of /dev/svnd0a?)
On 7/11/05, Chris [EMAIL PROTECTED] wrote: On Mon, 11 Jul 2005, Adam Fabian wrote: I've tried building an OpenBSD release from the 3.7-stable branch a few times in the last few days, on two different i386 machines, and both stopped in the same place. I'm following release(8) closely and not trying to reuse /usr/obj, and dealing with new, clean, complete, consistent checkouts of the code. The failure comes on step 4, (make and validate the system release) during the make release command in /usr/src/etc. Here's a log of the failure. It seems to be working on RAMDISKC: Ummm - maybe I don't understand but, how can you make a RELEASE from You aren't understanding. Read the release(8) manpage, it'll explain. It is fully supported. STABLE? Isnt STABLE following the patch branch? And RELEASE is jsut that - what's on the CD? If i'm correct - then you can't do that. If I'm correct, think of it this way: RELEASE = what you buy. STABLE = is what you follow for security patches CURRENT = is what you run as a developer. It's kinda like a Beta of the next RELEASE. Basically, you take the stable source branch, and build a CD release from that source. the release branch is what's on the cds, but building a release is just making a CD that's like the CD release, but from different sources if you so choose. The problem the OP is having was caused by one of the stable patches to the 3.7 kernel, making it just too big to fit on a floppy, which has been talked about in at least one previous thread. Jason
Re: Can't make 3.7-stable release (tries to exceed capacity of /dev/svnd0a?)
On Mon, Jul 11, 2005 at 01:24:01PM -0400, Jason Crawford wrote: from different sources if you so choose. The problem the OP is having was caused by one of the stable patches to the 3.7 kernel, making it just too big to fit on a floppy, which has been talked about in at least one previous thread. ::blushes.:: I suppose I should've found that. Thanks for the help, though! -- Adam Fabian [EMAIL PROTECTED]
Virus notification ...
SecureSynergy VirusScreen ASaP detected virus in attachment you sent to [EMAIL PROTECTED] with the subject header 'Mail Delivery (failure [EMAIL PROTECTED])'. The file has been processed with the following result: MSG-TEXT: Exploit-MIME.gen.c(cleaned) message.scr: W32/[EMAIL PROTECTED](cleaned)
Re: Cross-Compiling OpenBSD
On Mon, Jul 11, 2005 at 08:28:05PM +0930, Brett Lymn wrote:
On Sun, Jul 10, 2005 at 03:38:29PM -0400, Nick Holland wrote:
If your machine is too slow to do what you need it to do, you need a
faster machine. Cross compiling is not the answer to your problem.
Not so Nick. There may be some cases where you deliberately have a
slow machine for reasons of power consumption/heat disappation,
perhaps a fanless machine, you want to update.
A fanless machine.
uh-huh.
Let's see...what possibly fanless, low-power platforms do we have?
cats..ok, sure, but not very slow.
i386..ok, but you can native build on on Really Fast Stuff.
zaurus..almost defendable. but not really.
The lowest power machines ('cept for cats/Zaurus) can be native built on
another machine easily. And cats/zaurus just isn't that slow. If you
were foolish enough to install a machine that you can not maintain to
your satisfaction, you deserve what you get.
Or just that the
fastest machine in the architecture you are targeting falls way behind
current machines (SPARC vs current P4, say).
What isn't obvious is why this means it is good to cross build.
Telling someone to use a
faster machine is a trite answer but, in some cases, it is simply
infeasible.
Unproven.
Some machines are too slow to have in production use. Cross-building
doesn't change that.
My employeer is currently throwing away machines faster than the fastest
single CPU SPARC system (and lower power draw, too)...if you are running
on a slow SPARC, you are doing it out of love of the machine, not out of
best machine for the job. Nothing wrong with that, but if you love
the machine, you might as well love the whole machine. If you can't
stand the compile time, it is time to move on.
Which would you rather have developers doing...adding new
features, cleaning up code, improving existing operation...or helping
insert adjective here users do silly things with no value added to the
project?
improving existing operation you just said it there. Cross building
means that you are not bound by the limitations of the target
hardware. This actually impacts the developers more than anyone else,
especially during the release cycle. Imagine having to restart a
build that takes literally days to complete because what seemed to be
a benign change that fixes a bug causes an architecture specific build
error.
Why imagine? Been there, done that. Repeatedly. DAYS.
If I couldn't stand it, I'd toss all the mac68k stuff out.
Working on an old, slow machine is not a necessity anymore. If you
aren't doing it for fun, move on. If you can't laugh at release time
when someone hands you the SECOND after the last minute security fix
for an app requiring a rebuild and re-release, you are using the wrong
platform.
In a cross build environment the impact could be as little as
a hour or two instead of days. It means developers can do more stuff
because they are not waiting for the slower processors to grind
through a compile.
Funny, from what I've seen, when our good developers are waiting for a
slow machine, they work on something else on a different machine or a
different platform. Some of our best people work on very slow systems.
Pretending for a moment your argument had merit, what if the cross build
works but the native build does not? What if your slow platform has a
platform-specific instability that shows itself on native building?
Been there, done that, too.
We've seen what cross-building means for other projects. We've seen
what native building does for OpenBSD. We rather like our choice. We
have seen what it does for quality.
Nick.
Openbsd 3.7's GAS assembler gave me a sh: hello: Operation not permitted =/
Hello, I'm interested in learning gas (gnu assembler) on the openbsd platform. i started getting some intro documentation at www.linuxassembly.org and try out a Hello World code below. on a openbsd 3.7 GENERIC. $ cat hello.s .data msg: .ascii Hello, World!\n len = . - msg .text .global _start _start: movl$len,%edx movl$msg,%ecx movl$1,%ebx movl$4,%eax int $0x80 movl$0,%ebx movl$1,%eax int $0x80 and compiled it as indicated on the www.linuxassembly.org site $ as -o hello.o hello.s $ ld -s -o hello hello.o $ hello sh: hello: Operation not permitted i got a Operation not Permitted .. i tried building it as root but it didn't help =/ same result. i tried checking the openbsd files for some clue and i found this $ file /bin/ls --- openbsd ls file /bin/ls: ELF 32-bit LSB executable, Intel 80386, version 1, for OpenBSD, statically linked, stripped $ file hello my test program hello: ELF 32-bit LSB executable, Intel 80386, version 1, statically linked, stripped i tried running the code on a linux box and it worked.. my linux box: [EMAIL PROTECTED]:~/pfunix$ as -o hello.o hello.s [EMAIL PROTECTED]:~/pfunix$ ld -s -o hello hello.o [EMAIL PROTECTED]:~/pfunix$ hello Hello, World! [EMAIL PROTECTED]:~/pfunix$ file hello hello: ELF 32-bit LSB executable, Intel 80386, version 1 (SYSV), statically linked, stripped it is true that since I'm a beginner and it worked on linux .. it's a normal reaction to go where the first trial works (linux) ... but as for me .. i really want it to work on OpenBSD (eager) =) so any help, suggestions.. or just point me to a ton of docs will be greatly appreciated.. i noticed that the results of file hello and file ls are almost identical except for the file ls having the for OpenBSD on it .. is there a setting that will make OpenBSD do this for you automatically? (let openbsd stamp the file with for OpenBSD) or do i need to put it manually? Thanks In Advance, Edgar
Re: Can't make 3.7-stable release (tries to exceed capacity of /dev/svnd0a?)
Adam Fabian wrote: I've tried building an OpenBSD release from the 3.7-stable branch a few times in the last few days, on two different i386 machines, and both stopped in the same place. --8-- dd if=bsd.gz of=/mnt/bsd bs=512 /mnt: write failed, file system is full dd: /mnt/bsd: No space left on device --8-- # uname -a OpenBSD noc.hillconet.net 3.7 GENERIC#0 i386 (I was running the 3.7-stable GENERIC kernel both times I tried. The userland, etc. builds and installs, too, just can't make the release.) Here's a complete dmesg from one of the machines that it failed to build on: (the other is pretty similar, and I believe both failures were identical, though I didn't save the last log, because I figured I probably did something wrong): OpenBSD 3.7-stable (GENERIC) #0: Sun Jul 10 14:53:01 CDT 2005 [EMAIL PROTECTED]:/usr/src/sys/arch/i386/compile/GENERIC cpu0: Intel Celeron (GenuineIntel 686-class, 128KB L2 cache) 468 MHz cpu0: FPU,V86,DE,PSE,TSC,MSR,PAE,MCE,CX8,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,MMX,FXS R real mem = 199794688 (195112K) avail mem = 175558656 (171444K) This is really something for the archives. A problem description with really good info, and a dmesg too, even though it actually wasn't needed. Newbies, see how this guy did *not* get flamed for including both relevant, and irrelevant info and got his problem solved really quick. If one could only get coming generations to see this problem report too... -- Janne Johansson Sektionen fvr IT Media, Stockholms Universitet Frescati Hagvdg 10 106 91 STOCKHOLM http://www.it.su.se
Re: Removing PCMCIA ath0 causes panic
On 7/11/05, Rogier Krieger [EMAIL PROTECTED] wrote: On 7/11/05, Michael Shalayeff [EMAIL PROTECTED] wrote: Making, drinking tea and reading an opus magnum from Rogier Krieger: It seems I'm not allowed to unplug the card from the PCMCIA slot. Doing so instantly provides a kernel panic. it might have been already fixed in -current post-may Thanks; I'll check a snapshot and report back. The problem vanished using a -current snapshot of July 8th. The card now detaches cleanly (whether active or not). In addition, it also appears to work better in that it now automatically selects 11b mode. In 3.7, I got the idea that I had to manually tell it to do 11b. Cheers, Rogier -- If you don't know where you're going, any road will get you there.
sk gigabit NICs
Does anyone know if the Syskonnect SK-9S22 (dual port gigabit PCI-X nic) works well with OpenBSD? I know that the SK-9822 is supported, but I can't seem to find those for sale anymore. I think they are no longer made. The two cards are significantly different, but I think the main things are that the 9S22 is PCI-X and the 9822 is PCI, and the Yukon II vs. Yukon chipsets. If anyone knows if the new line of cards is supported, and/or knows where to get the SK-9822 nics, I'd appreciate a response. Thanks, -Adam
Delivery reports about your e-mail
ALERT! This e-mail, in its original form, contained one or more attached files that were infected with a virus, worm, or other type of security threat. This e-mail was sent from a Road Runner IP address. As part of our continuing initiative to stop the spread of malicious viruses, Road Runner scans all outbound e-mail attachments. If a virus, worm, or other security threat is found, Road Runner cleans or deletes the infected attachments as necessary, but continues to send the original message content to the recipient. Further information on this initiative can be found at http://help.rr.com/faqs/e_mgsp.html. Please be advised that Road Runner does not contact the original sender of the e-mail as part of the scanning process. Road Runner recommends that if the sender is known to you, you contact them directly and advise them of their issue. If you do not know the sender, we advise you to forward this message in its entirety (including full headers) to the Road Runner Abuse Department, at [EMAIL PROTECTED] The original message was received at Mon, 11 Jul 2005 15:58:15 -0700 from 31.15.245.218 - The following addresses had permanent fatal errors - misc@openbsd.org file attachment: transcript.zip This e-mail in its original form contained one or more attached files that were infected with the [EMAIL PROTECTED] virus or worm. They have been removed. For more information on Road Runner's virus filtering initiative, visit our Help Member Services pages at http://help.rr.com, or the virus filtering information page directly at http://help.rr.com/faqs/e_mgsp.html.
Re: Improving routing performance
Artur Grabowski wrote: Fredrik Roubert [EMAIL PROTECTED] writes: I have attached the output of dmesg. Any tips on what the most important things to investigate are? Is there any other information I should post? Ok. OpenBSD 3.5 (GENERIC) #34: Mon Mar 29 12:24:55 MST 2004 Your problems start here. yep, upgrading to 3.7-stable or -current would be a good step. cpu0: Intel Pentium (P54C) (GenuineIntel 586-class) 133 MHz cpu0: FPU,V86,DE,PSE,TSC,MSR,MCE,CX8 cpu0: F00F bug workaround installed This is a problem. Naw. P133s will pump plenty of data with simple rules, at least if the next bit is actually working for him: real mem = 16363520 (15980K) avail mem = 9117696 (8904K) And this. Ouch. Well...that's less than I'd use, but the way PF uses RAM, it either works or it doesn't. If the kernel runs out of RAM, it goes boom, not slow. On the other hand, if you call up vi while running, the system will start swapping, and that would suck. REALLY suck. 32M would be nice. That's four 8M sticks, anyone who has 'em will probably give them to you. Even 24M would be a non-trivial improvement for you (your available RAM would probably go from something like 2M to 8M...that's a large increase). HOWEVER, since you are complaining about performance, not crash-and-burn, I suspect this is not your problem, but I also suspect you will not be wondering what the extra RAM did for you once you install it. apm0 at bios0: Power Management spec V1.1 apm0: APM engage (device 1): power management disabled (1) apm0: AC on, battery charge unknown Probably this too. wouldn't be my first guess, but Art knows this area MUCH better than I do, so I'm not saying a thing here. ep1 at isapnp0 3Com 3C509B EtherLink III, TCM5095, PNP80F7, port 0x210/16 irq 9: address 00:60:97:39:50:2d, utp (default utp) Dear god. This too. ep2 at isapnp0 3Com 3C509B EtherLink III, TCM5095, PNP80F7, port 0x220/16 irq 10: address 00:60:97:12:1d:a6, utp (default utp) And this. //art Yes, I'd be starting with the NICs. Actually, I'm surprised by your OpenBSD attached directly to cable modem performance numbers. Having data flow through two of those cards, yes, will really hurt your ISA bus, but I'd expect one to take a good chunk of your available wire bandwidth. On the other hand...last time I performance checked a 3c509 card was back in the 2.7 or 2.8 days... HOWEVER, you are expecting 8Mbps performance on an 10Mbps NIC. Baaad idea. You need some newer NICs -- Intel Pro/100s, or even realtek rl(4) cards if you must (yes, they suck, but they are better than even the best ISA cards). If buying new, try gigabit cards, they are cheap, they'll make better use of limited processor. Also carefully watch things like packet size -- based on your performance numbers, I'm really thinking something is going wrong. It probably isn't duplex -- when that goes wrong, it normally goes much worse than what you are seeing, but an MTU error might be biting you, that could explain the performance you are seeing. I haven't seen MTU problems on cable modems, but there could be a first time... Nick.
NX support in VIA C7 ?
currently, there are no plans to advance pae support. -- And thats's why you need color management.
USB2 status?
I'm considering implementing a disk based backup system using USB2 hot-swap bays. I'm wondering about the stability and overall hardware support of the current USB2 drivers (on an x86 box). I'm asking because the man pages are somewhat slim and a bit scary in talking about USB2. For example ehci(4) says in the BUGS section The driver is not finished and is quite buggy. Some basic questions I'd love to have an answer to... Of course if the answer to the first one below is no real support i.e. alpha then the rest are somewhat mute :-) * Is USB2 support considered experimental, alpha, beta, rc, or release? * Do others have such a system in use? And how is it working out? * Has anyone done throughput measurements? How close to the 480Mbds theory is practice? * Are there specific hardware choices that I should make? Specifically for PCI-USB adapters as I'll be purchasing a dedicated card. * Are hot-swap bays supported in any form? Of course with the usual unmount caveat ;-) From the archives I gather there is some support for USB2 and external HDDs. And I know to stay away from Prolific based USB, re: http://thread.gmane.org/gmane.os.openbsd.misc/84162 -- I'm just looking for some more specifics about reliability and effectiveness. Thanks in advance for any info. -- -- Grafik - Don't Assume Anything -- Redshift Software, Inc. - http://redshift-software.com -- rrivera/acm.org - grafik/redshift-software.com -- 102708583/icq - grafikrobot/aim - Grafik/jabber.org
Silly patch to allow alt + f[1-4] to switch consoles.
This has only been used slightly without any real testing, so if you find any crashes due to it let me know. There is absolutely no guarantee that this is usable for any purpose. I use it without any problems to allow for easier console switching. But ymmv. For those more accustomed to the FreeBSD/Linux behavior. --- sys/dev/wscons/wskbd.c Fri Jul 8 01:40:08 2005 +++ sys.mine/dev/wscons/wskbd.c Mon Jul 11 22:20:16 2005 @@ -1370,6 +1370,7 @@ case KS_Cmd2: update_modifier(sc-id, *type, 0, MOD_COMMAND2); + update_modifier(sc-id, *type, 0, MOD_COMMAND1); break; }
Re: USB2 status?
I'm considering implementing a disk based backup system using USB2 hot-swap bays. I'm wondering about the stability and overall hardware support of the current USB2 drivers (on an x86 box). I'm asking because the man pages are somewhat slim and a bit scary in talking about USB2. For example ehci(4) says in the BUGS section The driver is not finished and is quite buggy. Apparently the man page was not updated after much development. I have removed those bogus comments. Some basic questions I'd love to have an answer to... Of course if the answer to the first one below is no real support i.e. alpha then the rest are somewhat mute :-) * Is USB2 support considered experimental, alpha, beta, rc, or release? It works totally fine for us. * Do others have such a system in use? And how is it working out? Using it fine. * Has anyone done throughput measurements? How close to the 480Mbds theory is practice? Most devices don't get to there, but the driver tries. * Are there specific hardware choices that I should make? Specifically for PCI-USB adapters as I'll be purchasing a dedicated card. They are all basically the same. * Are hot-swap bays supported in any form? Of course with the usual unmount caveat ;-) It's even better than that. You can kind of get away with disconnects somewhat, as vfs attempts to recover. Pedro has more work to do in this area, but the basics work. From the archives I gather there is some support for USB2 and external HDDs. And I know to stay away from Prolific based USB, re: http://thread.gmane.org/gmane.os.openbsd.misc/84162 -- I'm just looking for some more specifics about reliability and effectiveness. All stuff should work fine.
Re: undeadly dead
On 7/11/05, Bob Beck [EMAIL PROTECTED] wrote: Problem was a dead box late on friday, and then issues with the replacement. Sorry guys, it's back now. Thanks a lot Bob :-) good luck kind regards Siju
Re: USB2 status?
Theo de Raadt wrote: * Is USB2 support considered experimental, alpha, beta, rc, or release? It works totally fine for us. * Do others have such a system in use? And how is it working out? Using it fine. All good to hear :-) * Has anyone done throughput measurements? How close to the 480Mbds theory is practice? Most devices don't get to there, but the driver tries. So if speeds aren't better than USB1 I should blame the hardware and not the driver ;-) * Are hot-swap bays supported in any form? Of course with the usual unmount caveat ;-) It's even better than that. You can kind of get away with disconnects somewhat, as vfs attempts to recover. Pedro has more work to do in this area, but the basics work. Well that's good to know for emergency situations. I'll still play it safe and unmount before ejecting. Can't be too careful when it comes to possible write delays. All stuff should work fine. Thanks Theo... When it comes from you it certainly inspires considerable confidence. -- -- Grafik - Don't Assume Anything -- Redshift Software, Inc. - http://redshift-software.com -- rrivera/acm.org - grafik/redshift-software.com -- 102708583/icq - grafikrobot/aim - Grafik/jabber.org
Re: Silly patch to allow alt + f[1-4] to switch consoles.
On Mon, 2005-07-11 at 22:31 -0500, Jaime Fournier wrote:
This has only been used slightly without any real testing, so if you
find
any crashes due to it let me know.
There is absolutely no guarantee that this is usable for any purpose.
I use it without any problems to allow for easier console switching.
But ymmv.
For those more accustomed to the FreeBSD/Linux behavior.
Which leads me to ask... why is OpenBSD the only odd one out that
requires Ctrl+Alt+F{1,2,3,4,5} when switching between text consoles? Is
there really a good reason for leaving it the way it is?
--
Shawn K. Quinn [EMAIL PROTECTED]
