Hello Wieslaw, hello misc@!
I run into a similar problem with my 'litle border' gateway here at my ISP.
We was experimenting with a regular ADSL connection to put what we call low
traffic priority, but our ADSL provider is diferent from our 2x fibber. All
of our IPs are from the fibber
Hi,
I've got problems with increasing Ierrs on several machines with several
em(4) interfaces. Is there a way to get *detailed* information on these?
# netstat -I em3 -d
NameMtu Network Address Ipkts IerrsOpkts
Oerrs Colls Drop
em3 1500 Link de:ad:be:ef
On Tue, Jun 18, 2013 at 12:33:51PM -0700, William Orr wrote:
Thanks Gilles, first for the help and second for the fantastic software.
One last question - is there a way I can resend the mail stuck in
the queue? I've tried smtpctl schedule all, but it doesn't seem to
resolve the aliases,
* Chris Smith obsd_m...@chrissmith.org [2013-04-23 16:21]:
Seems that pf can enforce a min-ttl but can it explicitly set the ttl
on packets leaving an interface?
no.
--
Henning Brauer, h...@bsws.de, henn...@openbsd.org
BS Web Services, http://bsws.de, Full-Service ISP
Secure Hosting, Mail and
Hi misc,
I have the following setup:
* O1 and O2: two openbsd firewall/routers with:
* carp-ed client side interface
* trunked server side interfaces + carp-ed trunk device
* SRV: server with trunked interfaces (for testing I'm using one server, but
there will be 2 servers cross connected
I'm running into some difficulty with access denied in squid3 when I
switch it to act as an intercepting proxy. It works as normal when I use
it as a regular proxy but when turning on intercepting (formerly
transparent proxying) the web browser shows this error:
...Access Denied.
On 06/19/13 15:08, Lars Noodén wrote:
I'm running into some difficulty with access denied in squid3 when I
switch it to act as an intercepting proxy. It works as normal when I use
it as a regular proxy but when turning on intercepting (formerly
transparent proxying) the web browser shows this
Hi,
I think this is a little bit off-topic on this list, or should we
start discussing all problems of all ports here? ...
Anyway, you should make sure to use divert-to instead of rdr-to in
your pf.conf. rdr-to is considered to be obsolete for userland
proxies (except for spamd).
Reyk
On Wed,
On Wed, Jun 19, 2013 at 6:43 AM, Henning Brauer lists-open...@bsws.de wrote:
no
Thanks.
Any plans to implement this?
Has anyone done a successful upgrade from Loongson 5.2 to 5.3? I've done
upgrades on numerous platforms and this is the only one I've ever had
problems with. The upgrade seemed to go fine and finish normally. After the
reboot it goes from the Lemote Dragon screen to a black screen and stops
there.
On Wed, 19 Jun 2013, Reyk Floeter wrote:
Anyway, you should make sure to use divert-to instead of rdr-to in
your pf.conf. rdr-to is considered to be obsolete for userland
proxies (except for spamd).
That solved it exactly. I had not seen the change and had been trying
rdr-to instead of
A fresh install also doesn't boot and using PMON to boot into it fails the
same way as on the old install. Well crap. That was unexpected.
PMON boot -k /dev/fs/ext2@wd0/boot/boot
Loading file: /dev/fs/ext2@wd0/boot/boot (elf)
(elf)
0x81e2/44368 + 0x81e2ad50/4400(z) +
OpenBSD/loongson BOOT
Sorry if this is duplicated. Been a few hours since I sent it and did not
see it hit the list. Also did not find it on marc or gmane.
Has anyone done a successful upgrade from Loongson 5.2 to 5.3? I've done
upgrades on numerous platforms and this is the only one I've ever had
problems with. The
Hello,
Thanks Barry, this was exactly what I was looking for. Been using it now
for a couple of days with TEMPer sensor on both 5.3 stable and current by
using this patch written by SASANO Takayoshi:
http://www2192ue.sakura.ne.jp/~uaa/gomitext/2013/20130331/20130331.diff
Any ideas when this
In pf.conf I've got skip on {lo,tun0}, however after openvpn starts,
skip is removed from tun0. Is there a way to avoid this?
In the mean time I've added pass quick on tun0 to pf.conf.
# pfctl -f /etc/pf.conf
# ls -l /dev/tun0
crw--- 1 root wheel 40, 0 Jun 19 09:32 /dev/tun0
# pfctl -v
but it booted and ran the installer?
On Wed, Jun 19, 2013 at 8:00 AM, John Long codeb...@inbox.lv wrote:
A fresh install also doesn't boot and using PMON to boot into it fails the
same way as on the old install. Well crap. That was unexpected.
PMON boot -k /dev/fs/ext2@wd0/boot/boot
Did not upgrade mine yet.
Wait for Miod's answer. He's the best person for knowledge on this platform.
Message du 19/06/13 17:09
De : John Long
A : misc@openbsd.org
Copie à :
Objet : Can't boot Loongson after upgrade from 5.2 - 5.3
Sorry if this is duplicated. Been a few hours since
An update...the bsd.rd kernel boots from / but not bsd. bsd from snapshots
also boots. Looks like there is some problem with bsd in loongson 5.3
release.
/jl
--
ASCII ribbon campaign ( ) Powered by Lemote Fuloong
against HTML e-mail X Loongson MIPS and OpenBSD
and proprietary/ \
Has anyone done a successful upgrade from Loongson 5.2 to 5.3? I've done
upgrades on numerous platforms and this is the only one I've ever had
problems with. The upgrade seemed to go fine and finish normally. After the
reboot it goes from the Lemote Dragon screen to a black screen and stops
A fresh install also doesn't boot and using PMON to boot into it fails the
same way as on the old install. Well crap. That was unexpected.
If a new install fails, now that's something unexpected. Will installing
5.2 (which used to work) boot again?
Miod
On Wed, Jun 19, 2013 at 07:53:30PM +, Miod Vallat wrote:
A fresh install also doesn't boot and using PMON to boot into it fails the
same way as on the old install. Well crap. That was unexpected.
If a new install fails, now that's something unexpected. Will installing
5.2 (which used
An update...the bsd.rd kernel boots from / but not bsd. bsd from snapshots
also boots. Looks like there is some problem with bsd in loongson 5.3
release.
Where did you get your 5.3 release from? Did you check its md5?
Miod
On Wed, Jun 19, 2013 at 08:10:17PM +, Miod Vallat wrote:
An update...the bsd.rd kernel boots from / but not bsd. bsd from snapshots
also boots. Looks like there is some problem with bsd in loongson 5.3
release.
Where did you get your 5.3 release from? Did you check its md5?
That's
On Wed, Jun 19, 2013 at 11:17:57AM -0700, Bryan Irvine wrote:
but it booted and ran the installer?
Yes. There appears to be a problem with the kernel.
I just tried something interesting. I booted the installer and used the
shell to save bsd as obsd on the installed system and then ln -s bsd.rd
Where did you get your 5.3 release from? Did you check its md5?
That's it! Thank you.
I got release from ftp.openbsd.org. But the sha256 for bsd doesn't match
what's in SHA256. I'm used to ignoring those messages from snapshots so I
didn't catch it.
Cluebatting myself...apparently it was
Hello Misc,
The Jun18/19 snapshot have a break version of CWM
It`s always crash when I try to resize a window (just click M-M1, and then
its segfaults).
Follow dmesg and GDB
Thanks
tales:mosconi {102} gdb cwm
GNU gdb 6.3
Copyright 2004 Free Software Foundation, Inc.
GDB is free software,
On Wed 2013.06.19 at 22:34 -0300, Rodrigo Mosconi wrote:
Hello Misc,
The Jun18/19 snapshot have a break version of CWM
It`s always crash when I try to resize a window (just click M-M1, and then
its segfaults).
Follow dmesg and GDB
Thanks
tales:mosconi {102} gdb cwm
GNU gdb 6.3
On Wed 2013.06.19 at 22:04 -0400, Okan Demirmen wrote:
On Wed 2013.06.19 at 22:34 -0300, Rodrigo Mosconi wrote:
Hello Misc,
The Jun18/19 snapshot have a break version of CWM
It`s always crash when I try to resize a window (just click M-M1, and then
its segfaults).
Follow dmesg
28 matches
Mail list logo
