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
Hi again,
Thanks for your responses.
I found a setup that satisfies me:
* SRV: trunk in failover mode
* O1, O2: trunk in broadcast mode
As only one link at a time is active on SRV, I don't get duplicates. And as it
is the only one being in failover mode, no need of ifstated.
Best Regards
On Wed, Jun 19, 2013 at 11:38 PM, Bernd be...@kroenchenstadt.de wrote:
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
On Thu, Jun 20, 2013 at 08:38:11AM +0200, Bernd wrote:
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 Ierrs
On 20 June 2013 08:38, Bernd be...@kroenchenstadt.de wrote:
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 Ierrs
* Chris Smith obsd_m...@chrissmith.org [2013-06-19 16:20]:
On Wed, Jun 19, 2013 at 6:43 AM, Henning Brauer lists-open...@bsws.de wrote:
no
Thanks.
Any plans to implement this?
no.
--
Henning Brauer, h...@bsws.de, henn...@openbsd.org
BS Web Services, http://bsws.de, Full-Service ISP
Secure
On 2013-06-19, Lars Nooden lars.noo...@gmail.com wrote:
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
On 2013-06-19, rafaello konfekte peleekaiskardina...@gmail.com wrote:
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:
On 2013-06-19, Ryan Slack r...@evine.ca wrote:
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.
You will probably need to reload pf.conf, I believe openvpn
On Thu, 20 Jun 2013, Stuart Henderson wrote:
On 2013-06-19, Lars Nooden lars.noo...@gmail.com wrote:
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
Thanks Okan,
I use the selfont config, Just removed it, and worked! I will wait the
next snapshot.
Att,
2013/6/19 Okan Demirmen o...@demirmen.com
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
Followup #2.
I tried booting the older kernels available to me to see if I could
narrow down the range of the time this problem began.
The kernel from June 9 boots as expected and carp moves to master status
as it should.
The kernel from June 13 boots but carp stays stuck in INIT.
The
help me. What i'm doing wrong?
pkg_add xl2tpd (OK)
pf - disabled
vi /etc/xl2tpd/xl2tpd.conf
[lac beeline]
lns = vpn.dzer.b2b.local
redial = yes
autodial = yes
vi /etc/ppp/options
name user
vi /etc/ppp/chap-secrets
user * password
vi /etc/ppp/pap-secrets
user * password
vi
On 2013-06-18, Wiesław Herr hers...@makhleb.net wrote:
Hi misc@!
After deploying a new OpenBSD 5.3 firewall today I ran into a strange
problem. The first rule in my ruleset is one NAT-ing ICMP packets from my
host to Google's DNS IP (8.8.8.8):
fw1a-spt # pfctl -sr -R0
pass out log quick
On 06/20/2013 09:03 AM, Stuart Henderson wrote:
On 2013-06-19, Ryan Slack r...@evine.ca wrote:
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.
You will
Hi William,
I would suggest trying these things first:
- have you checked smtpd main page to Modify the current mailwrapper(8)
settings?
- stop smtpd and run it in foreground smtpd -d -v, so all the info will go
to stderr
- try to exclude dovecot and check that smtpd can deliver messages to
On 20 June 2013 16:53, Stuart Henderson s...@spacehopper.org wrote:
On 2013-06-18, WiesÅaw Herr hers...@makhleb.net wrote:
I suspect you may have an issue where state is not being created where
you expect it.
It's now recommended (and we've changed the sample pf.conf to match)
to start
and in /var/log/messages
Jun 20 10:26:33 main pppd[19445]: Protocol-Reject for unsupported protocol
0xbe6b
Jun 20 10:26:42 main last message repeated 2 times
Jun 20 11:01:33 main pppd[19445]: Protocol-Reject for unsupported protocol
0xd0d2
Jun 20 11:27:51 main pppd[19445]: Protocol-Reject for
18 matches
Mail list logo
