On Mon, 18 Dec 2000, Wes Peters wrote:
> I need a tiny DNS server I can hack up. When our router/firewall/gateway is
> in "first birthday" mode, it doesn't yet have a connection to the internet.
> We'd like to run a DNS server on the box that resolves ALL DNS A requests
> from the internal LAN t
On Sun, Dec 17, 2000 at 04:12:19PM -0500, Robert Watson wrote:
> On Sun, 17 Dec 2000, Jesper Skriver wrote:
>
> > - ip source and destination addresses
> > - tcp source and destination ports
> > - tcp sequence number
> >
> > Can we make it zap the sessions regardless of the current state ?
> >
Hi, everybody
I am using freebsd 4.2 to test vlan. I find if running ng_ether, you can not configure
the vlan. If you configure vlan, the system will display :
Fatal trap 12 : page fault while in kernel mode, ..
then system is rebooted auto.
How to solve this problem?
Yian
To
Hi,
I'm trying to find out what to to now regarding this.
To summarize.
PHK committed my original patch, this patch have the following
functionality
- When a ICMP administrative prohibited is recieved, it zap's
all TCP sessions in SYN-SENT state matching the source and destination
IP addr
Hello everyone,
I have a problem, in the morning someone hacked into my computer at home. It
is ADSL Gateway running FreeBSD 3.4 , root password is changed by hacker.
Can anyone tell where on the system I can find some tracks of a hacker?
What should I check first?
Which log files?
Anyone? Please
Title: RE: Hacked computer
I would do a find / -name g
g is a well known rootkit, im not sure if it works with freebsd but I am sure it can be modified, that is what most of the script kiddies are using these days, it changes a bunch of things like ps, and last and who... If you find a direc
If you've been rooted, then the logs are probably no good. But check you wtmp
for logons, and messages, and well if you don't see anything unusual there then
the've prabaly been wiped. Have regained root yet? personally I would pull the
box off net and backup theimportant config stuff, then blast
At Mon, 18 Dec 2000, [EMAIL PROTECTED] wrote:
>Hello everyone,
>I have a problem, in the morning someone hacked into my computer at home. It
>is ADSL Gateway running FreeBSD 3.4 , root password is changed by hacker.
>Can anyone tell where on the system I can find some tracks of a hacker?
>What sh
On Mon, 18 Dec 2000, Jesper Skriver wrote:
> - Check for SYN-SENT state removed
I was thinking about this point, and I think there are two compelling
reasons to keep it enabled only for the SYN_SENT state.
First, the cases in which connections are in progress to a port which is
in the process
On Mon, Dec 18, 2000 at 01:20:51PM -0600, Mike Silbersack wrote:
>
> On Mon, 18 Dec 2000, Jesper Skriver wrote:
>
> > - Check for SYN-SENT state removed
>
> I was thinking about this point, and I think there are two compelling
> reasons to keep it enabled only for the SYN_SENT state.
>
> First
I suggest that the ICMP unreachable affect connections only in
SYN-SENT and only if the seq number matches, and that it not
affect IPSEC'd connections at all.
FYI, IPSEC does not run over GRE, but uses two protocol numbers
of its own, 50 for ESP and 51 for AH. IKE uses UDP port 500,
not TCP.
With
On Mon, Dec 18, 2000 at 05:12:48PM -0500, Barney Wolff wrote:
> I suggest that the ICMP unreachable affect connections only in
> SYN-SENT and only if the seq number matches, and that it not
> affect IPSEC'd connections at all.
When you say IPsec doesn't use TCP at all, it will not be affected in
Ok, the new version of the diff is here, and it's a mere 35K (compared to
the last one which was 162k):
http://people.freebsd.org/~bmilekic/m_flag_rnm.diff
Big bloat reduction compared to last time.
It renames M_WAIT to M_TRYWAIT, M_DONTWAIT stays M_DONTWAIT, and also
fixes a few r
13 matches
Mail list logo
