BGPd uses 100% CPU

7;s a 5.1 GENERIC.MP#207 amd64 install Any Idea where to begin debugging ? Regards Matthias -- Matthias Cramer, Erachfeldstrasse 1b, CH-8180 Bülach http://www.freestone.net GnuPG 1024D/2D208250 = DBC6 65B6 7083 1029 781E 3959 B62F DF1C 2D20 8250 [demime 1.01d removed an attachment of

Re: BGPd uses 100% CPU

and all is looking perfect. So the bug was me and not bgpd ... Regards Matthias On 12/06/12 21:05, Claudio Jeker wrote: > On Tue, Jun 12, 2012 at 09:43:55AM +0200, Matthias Cramer wrote: >> Hi All >> >> I have a newly set up OpenBSD VM which mainly runs bgpd. I have 2 fu

PF: clock upd packets that allready have a state

-F states the connection is blocked. Is there a way to: - clear a single state? - to block a packet even with a established state ? Regards Matthias -- Matthias Cramer, Erachfeldstrasse 1b, CH-8180 Bülach http://www.freestone.net GnuPG 1024D/2D208250 = DBC6 65B6 7083 1029 781E 3959 B62F

Re: PF: block upd packets that allready have a state

Hi Marios On 25/06/12 15:58, Marios Makassikis wrote: > On 25 June 2012 15:36, Matthias Cramer wrote: >> Hi >> > > Hi, > >> From time to time I have some attacks to my SIP PBX. I like to block them on >> my OpenBSD >> box which stands in front of it. Th

Re: PF: block upd packets that allready have a state

ething > like ALTQ to throttle traffic. The problem remains though, since you > may end up throttling all > connections to your PBX, including legitimate clients. I considered ALTQ, but that is in my opinion not a very nice way to solve this problem. Regards Mattthias -- Matthias C

Re: PF: block upd packets that allready have a state

here are no connections to close ... It's SIP --> UDP .. The attacker can always use the same packet header. Think there is no way to solve that at Layer 3 or 4, You have to look at the content. Regards Matthias -- Matthias Cramer, Erachfeldstrasse 1b, CH-8180 Bülach, Switzerland http://ww

OpebBSD 4.9 and Intel 82579LM support

Hi I've setup a new SuperMicro Server with a Intel 82574L and a Intel 82579LM Gigabit NIC. The 82574L get's recognised with no problems as em0. The 82579LM does not show up anywhere. As I found out this is a fairly new chipset. Is there already support for this chipset or will there be soon ? Re

Re: OpebBSD 4.9 and Intel 82579LM support

Hi Claudio and Jonathan Compiling a current kernel solved my problem. Had some time to find out that I first need to recompile config !!! Thanks for your tip Matthias On 07/06/11 16:13, Claudio Jeker wrote: > On Tue, Jun 07, 2011 at 02:31:25PM +0200, Matthias Cramer wrote: >> Hi &

Problem with Broadcom Ethernet in IBM Server under 4.6

e1 phy 1: BCM5703 10/100/1000baseT PHY, rev. 2 With the snapshot release it worked like a charm. I remember that I tried installing 4.5 and it did not work then too. Any hints on how to fix ? Should I probably use a kernel from snapshot again ? Regards Matthias -- Matthias Cramer, Erachfel

Re: VLANs, OpenBSD, Cisco HP

rather then skipping directly to a higher number? From the FAQ, > section 6.2.1, they show the vlan0 interface being associated with vlan > 2 so the file number does not need to match the vlan number: > >$ cat /etc/hostname.vlan0 >inet 172.21.0.31 255.255.255.0 NONE vlan 2 vlan