On Sat, 24 Nov 2007, Aryeh Friedman wrote:
Where do I find the main() [and/or other entery point] for the kernel I
tend to understand stuff better if I follow the flow of exec from the start
Everyone else is suggesting very earlier in the boot, but I think the point
where the kernel
On Sat, Nov 24, 2007 at 03:33:24AM +, Aryeh Friedman wrote:
Where do I find the main() [and/or other entery point] for the
kernel I tend to understand stuff better if I follow the flow of
exec from the start
note that kernel as such does not exist. its threads/processes running
code in
Dear all,
I have come to understand that postgresql needs sys v ipc. I haven't
tried to figure out why exactly, but I'm sure they have good reasons.
As I came to understand, if you enable jail_sysvipc_allow in rc.conf I
am defeating the purpose of a jail.
So basically I if you want pgsql in
As a lot of people recommended using tcpdump, here it is. The only thing
that stands out, are hundreds and thousands of lines like this:
13:45:49.991592 IP 82.165.252.222.36887 ns1.galandrex.ee.43077: UDP,
length 9216
13:45:49.996482 IP 82.165.252.222.36887 ns1.galandrex.ee.33803: UDP,
length
Joel V. [EMAIL PROTECTED] wrote:
Hello all,
I'm not experiencing this problem, my friend is. He's simply too pissed off
to write here and I'm afraid he's going to set his office on fire if he
doesn't solve the problem soon, so without further ado, here's the problem:
He has two fbsd
I've noticed that in the kernel configuration IPSEC_ESP disappeared
from the options. It says that you just need device crypto and IPSEC.
Does this mean that with crypto and IPSEC I have all I need to treat
ESP like the old IPSEC_ESP option?
I'm having some problems right now setting up a vpn
As a lot of people recommended using tcpdump, here it is. The only
thing that stands out, are hundreds and thousands of lines like this:
13:45:49.991592 IP 82.165.252.222.36887 ns1.galandrex.ee.43077: UDP,
length 9216
13:45:49.996482 IP 82.165.252.222.36887 ns1.galandrex.ee.33803: UDP,
On Sat, 2007-11-24 at 08:51 -0500, Bill Moran wrote:
Joel V. [EMAIL PROTECTED] wrote:
Hello all,
I'm not experiencing this problem, my friend is. He's simply too pissed off
to write here and I'm afraid he's going to set his office on fire if he
doesn't solve the problem soon, so
On Nov 24, 2007 10:11 PM, Giulio Ferro [EMAIL PROTECTED] wrote:
I've noticed that in the kernel configuration IPSEC_ESP disappeared
from the options. It says that you just need device crypto and IPSEC.
Does this mean that with crypto and IPSEC I have all I need to treat
ESP like the old
Hi.
On Sat, Nov 24, 2007 at 03:11:05PM +0100, Giulio Ferro wrote:
I've noticed that in the kernel configuration IPSEC_ESP disappeared
from the options. It says that you just need device crypto and IPSEC.
Does this mean that with crypto and IPSEC I have all I need to treat
ESP like the old
VANHULLEBUS Yvan wrote:
I'm having some problems right now setting up a vpn to complete phase 2,
(the error is no proposal chosen).
Since ipsec-tools uses the facilities in the kernel, I want to make sure
that the
kernel provides everything racoon needs...
That really sounds
Why not to try another NIC?
Att.
Ronald Gonzalez
--- Joel V. [EMAIL PROTECTED] escribió:
Hello all,
I'm not experiencing this problem, my friend is.
He's simply too pissed off
to write here and I'm afraid he's going to set his
office on fire if he
doesn't solve the problem soon, so
Joel V. wrote:
As a lot of people recommended using tcpdump, here it is. The only thing
that stands out, are hundreds and thousands of lines like this:
13:45:49.991592 IP 82.165.252.222.36887 ns1.galandrex.ee.43077: UDP,
length 9216
13:45:49.996482 IP 82.165.252.222.36887
On Sat, Nov 24, 2007 at 12:11:18PM +0100, Gabor Tjong A Hung wrote:
As I came to understand, if you enable jail_sysvipc_allow in rc.conf I am
defeating the purpose of a jail.
Not totally defeating the purpose but SysV IPC is not jail-aware so
any jailed process can see and affect the global SysV
Hello.
A big thanks to everyone who contacted me. FreeBSD really has the best
community one could help for.
Now, it has been confirmed by the backbone manager that we're dealing with a
DDOS attack. However, the ISP seems to be as clueless as a headless sheep,
and we haven't been able to contact
Joel V. wrote:
Hello.
A big thanks to everyone who contacted me. FreeBSD really has the best
community one could help for.
Now, it has been confirmed by the backbone manager that we're dealing with a
DDOS attack. However, the ISP seems to be as clueless as a headless sheep,
and we
Joel V. wrote:
Hello.
A big thanks to everyone who contacted me. FreeBSD really has the best
community one could help for.
Now, it has been confirmed by the backbone manager that we're dealing with a
DDOS attack. However, the ISP seems to be as clueless as a headless sheep,
and we haven't been
Jeff Mohler wrote:
On Nov 24, 2007 2:08 PM, Julian Elischer [EMAIL PROTECTED]
mailto:[EMAIL PROTECTED] wrote:
Joel V. wrote:
Hello.
A big thanks to everyone who contacted me. FreeBSD really has the
best
community one could help for.
Now, it has been
Remko Lodder wrote:
Joel V. wrote:
Hopefully the situation will be fixed soon. One final question though: are
there any quick steps one can take to protect their server from DDOS attacks
like these?
If someone wants to flood your network connection with packets there is
nothing you can do
On Nov 24, 2007 2:08 PM, Julian Elischer [EMAIL PROTECTED] wrote:
Joel V. wrote:
Hello.
A big thanks to everyone who contacted me. FreeBSD really has the best
community one could help for.
Now, it has been confirmed by the backbone manager that we're dealing
with a
DDOS attack.
Hi,
From what I read in The Design and Implementation of the FreeBSD
Operating System,said:
'However, most of the heavily used parts of the kernel have been moved out
from under the giant lock, including much of the virtual memory system,
the networking stack, and the filesystem.'
What the
21 matches
Mail list logo
