Dear FreeBSD Guys,
It is FreeBSD Release 9.0 x64 and i see this log very frequent almost
every second, And i want to block this IP from reaching my server. i
configured the PF as following but still see the same logs, it is like
it did not work.
block in log quick from 41.211.2.239/32 to any
On 11 Sep 2012, at 10:15, "Shiv. Nath" wrote:
> Dear FreeBSD Guys,
>
> It is FreeBSD Release 9.0 x64 and i see this log very frequent almost every
> second, And i want to block this IP from reaching my server. i configured the
> PF as following but still see the same logs, it is like it did n
On Tue, Sep 11, 2012 at 10:15 AM, Shiv. Nath
wrote:
> Dear FreeBSD Guys,
>
> It is FreeBSD Release 9.0 x64 and i see this log very frequent almost every
> second, And i want to block this IP from reaching my server. i configured
> the PF as following but still see the same logs, it is like it did
Sep 11 07:49:56 titan avahi-daemon[1567]: Received response from host
41.211.2.239 with invalid source port 4331 on interface 'em0.0'
Sep 11 07:50:25 titan avahi-daemon[1567]: Received response from host
41.211.2.239 with invalid source port 38627 on interface 'em0.0'
Sep 11 07:51:29 titan avahi-
Hi,
I'm under the illusion that I've found a bug in the FreeBSD kernel, but
since I'm new to FreeBSD, a quiet voice tells me it's probably a case of
"you're doing it wrong".
Also, I'm not sure if this is the right place to complain. So feel free
to redirect me.
I'll start with some context:
* F
On Tue, Sep 11, 2012 at 4:26 AM, Damien Fleuriot wrote:
> On 11 Sep 2012, at 10:15, "Shiv. Nath"
> wrote:
> > It is FreeBSD Release 9.0 x64 and i see this log very frequent almost
> every second, And i want to block this IP from reaching my server. i
> configured the PF as following but still se
On Tue, Sep 11, 2012 at 6:05 PM, Brandon Allbery wrote:
> On Tue, Sep 11, 2012 at 4:26 AM, Damien Fleuriot wrote:
>
>> On 11 Sep 2012, at 10:15, "Shiv. Nath"
>> wrote:
>> > It is FreeBSD Release 9.0 x64 and i see this log very frequent almost
>> every second, And i want to block this IP from rea
On Tue, Sep 11, 2012 at 11:12 AM, Kimmo Paasiala wrote:
> On Tue, Sep 11, 2012 at 6:05 PM, Brandon Allbery
> wrote:
> > On Tue, Sep 11, 2012 at 4:26 AM, Damien Fleuriot wrote:
> >> On 11 Sep 2012, at 10:15, "Shiv. Nath"
> >> wrote:
> >> It says it received a *response* so my understanding is *
I would actually question why avahi is even enabled on a server; perhaps
the correct answer is simply to disable it in rc.conf.
You do know that avahi-daemon's main use is to advertise _services_running on a
host?
Yes, but zeroconf-style services are often more of a peer-to-peer nature
instead
Mikolaj Golub wrote:
On Mon, Sep 10, 2012 at 04:46:15PM +0200, Miroslav Lachman wrote:
Mikolaj Golub wrote:
On Sun, Sep 09, 2012 at 11:56:55PM +0200, Miroslav Lachman wrote:
I am running bsnmpd with basic snmpd.config (only community and location
changed).
When there is a problem with HDD and
Well, there definitely seems to be a problem with igb and lagg.
igb alone works as it should, but doesn't seem to work properly in lagg.
To be sure I started from scratch from a 9.0 release with nothing but:
/etc/rc.conf
---
ifconfig_igb0="inet ..
On Sep 11, 2012 2:12 PM, "Giulio Ferro" wrote:
>
> Well, there definitely seems to be a problem with igb and lagg.
>
> igb alone works as it should, but doesn't seem to work properly in lagg.
>
> To be sure I started from scratch from a 9.0 release with nothing but:
>
> /etc/rc.conf
>
Today I decided to take the plunge and make clang the default compiler, ie
I set
WITH_CLANG=yes
WITH_CLANG_IS_CC=yes
WITH_CLANG_EXTRAS=yes
in src.conf. No problem so far. However I wanted to avoid building base gcc
( the whole collection ). Is WITHOUT_GCC what I'm looking for?
On another clang
On Tue, 11 Sep 2012, Giulio Ferro wrote:
Well, there definitely seems to be a problem with igb and lagg.
igb alone works as it should, but doesn't seem to work properly in lagg.
To be sure I started from scratch from a 9.0 release with nothing but:
/etc/rc.conf
---
On Tue, 11 Sep 2012, Freddie Cash wrote:
On Sep 11, 2012 2:12 PM, "Giulio Ferro" wrote:
cloned_interfaces="lagg0"
ifconfig_lagg0="laggproto lacp laggport igb1 laggport igb2 laggport igb3
192.168.x.x/24"
sshd_enable="YES"
---
This doesn't eve
In article <504f4049.9080...@dest-unreach.be>, nio...@dest-unreach.be
writes:
>
>I'm under the illusion that I've found a bug in the FreeBSD kernel, but
>since I'm new to FreeBSD, a quiet voice tells me it's probably a case of
>"you're doing it wrong".
Nope. It's a known bug in the version of geo
On 2012-09-11 (Tuesday) 23:49:24 Andreas Nilsson wrote:
> Today I decided to take the plunge and make clang the default compiler, ie
> I set
>
> WITH_CLANG=yes
> WITH_CLANG_IS_CC=yes
> WITH_CLANG_EXTRAS=yes
>
> in src.conf. No problem so far. However I wanted to avoid building base gcc
> ( the wh
On Tue, Sep 11, 2012 at 10:16:57PM +0200, Miroslav Lachman wrote:
> (gdb) bt
> #0 0x000801046cba in refresh_disk_storage_tbl () from
> /usr/lib/snmp_hostres.so
> #1 0x0008010478bd in refresh_device_tbl () from
> /usr/lib/snmp_hostres.so
> #2 0x000801047be6 in start_device_tbl () f
On Tue, Sep 11, 2012 at 11:49:24PM +0200, Andreas Nilsson wrote:
> Is there a specif PR to use for ports that fails with clang and does
> not specify to use gcc ( > devel/cdecl and deskutils/calibre so were
> the culprits so far)
There is no specific PR. We have not yet placed the requirement on
TB --- 2012-09-12 06:10:00 - tinderbox 2.9 running on freebsd-stable.sentex.ca
TB --- 2012-09-12 06:10:00 - FreeBSD freebsd-stable.sentex.ca 8.2-STABLE
FreeBSD 8.2-STABLE #4: Wed Sep 28 13:48:49 UTC 2011
mdtan...@freebsd-stable.sentex.ca:/usr/obj/usr/src/sys/server amd64
TB --- 2012-09-12 06
TB --- 2012-09-12 06:10:00 - tinderbox 2.9 running on freebsd-stable.sentex.ca
TB --- 2012-09-12 06:10:00 - FreeBSD freebsd-stable.sentex.ca 8.2-STABLE
FreeBSD 8.2-STABLE #4: Wed Sep 28 13:48:49 UTC 2011
mdtan...@freebsd-stable.sentex.ca:/usr/obj/usr/src/sys/server amd64
TB --- 2012-09-12 06
On Wed, Sep 12, 2012 at 8:04 AM, Mark Linimon wrote:
> For most of the failures, we are already aware of them, as a result of
> our periodic runs. So, just filing a PR to say "broken on clang" doesn't
> really help us all that much.
>
I disagree. Just a tiny bit ;-)
If the PR says that USE_GCC=
22 matches
Mail list logo
