The following reply was made to PR kern/123053; it has been noted by GNATS.
From: Eric F Crist <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
Cc: [EMAIL PROTECTED],
[EMAIL PROTECTED],
[EMAIL PROTECTED]
Subject: Re: kern/123053
Date: Fri, 25 Apr 2008 07:29:01 -0500
On Apr 24, 2008, at 7:25 PM
hanks for you replies!
-
Eric F Crist
Secure Computing Networks
___
freebsd-net@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-net
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
ny mail to "[EMAIL PROTECTED]"
-
Eric F Crist
Secure Computing Networks
___
freebsd-net@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-net
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
we could make it shorter and call it gateway.
Well there is a difference between router and gateway.
I think that gateway would be a better word since from my
understanding that is what people use today.
+1 vote for the "gateway". I always wandered why it's called
"router", si
On Nov 6, 2007, at 9:28 AM, Andrey V. Elsukov wrote:
Eric F Crist wrote:
In the your /etc/ipfw.sh script you should use "-f" flag when you
run
ipfw flush command.
I am, but that has nothing to do with my problem. My problem is
that,
during system boot, I'm asked the fol
On Nov 6, 2007, at 7:32 AM, Andrey V. Elsukov wrote:
Eric F Crist wrote:
firewall_enable="YES"
firewall_script="/etc/ipfw.sh"
FWIW, ipfw.sh ONLY has count rules it it. There isn't any NAT/etc
going on here. Also, IPFW was compiled with DEFAULT TO ACCEPT,
since I&
t sits, forever, waiting for an answer. I've tried adding
natd_enable="NO", natd_enable="YES", removing natd_enable entirely
from my rc.conf file, and having IPDIVERT compiled into the kernel,
and not. No matter what I do, I cannot get rid of this damn question!
Thanks fo
iate blocks in place ...
Is there either a command line command, or ports tool, that I can
use similar
to top, or systat -iostat, that will help identify the IP that is
being
attacked?
Thank you ...
tcpdump might be of use.
-
Eric F Crist
Secure Computing Networks
PGP.sig
Description:
On Aug 10, 2007, at 10:40 AMAug 10, 2007, David Gilbert wrote:
"Eric" == Eric F Crist writes:
Eric> FWIW, I've been using if_bridge for a short while (month or two)
Eric> and I've got all my IPs assigned to the interfaces themselves,
Eric> and not bridge0. I&#x
ut everything works great.
I'm using the fxp driver on both cards (Dell PowerEdge 1550 dual
10/100 interfaces).
Feel free to ask more about my setup, if I can help at all.
-
Eric F Crist
Secure Computing Networks
___
freebsd-net@freebsd
php/IPv6_on_FreeBSD_6.2
-
Eric F Crist
Secure Computing Networks
___
freebsd-net@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-net
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
nd
support, you'll probably have to go to a higher-end business class
solution, such as a T1 or even possibly an ISDN line.
HTH
-
Eric F Crist
Secure Computing Networks
___
freebsd-net@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-net
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
lter/UUNet? I didn't think most of
them did IPv6 yet. Are they just not accepting your providers block?
Brandon
On Fri, 29 Jun 2007 07:12:53 -0500
Eric F Crist <[EMAIL PROTECTED]> wrote:
[cut it out]
I just wanted everyone to know that my IPv6 Woes have been
resolved. As it turn
subnet in their routing tables. Third, and last, there is (still)
a routing problem on the high-level at Verizon/Alter/UUnet that has
yet to be resolved.
Thanks a lot for all your help!
-
Eric F Crist
Secure Computing Networks
___
freebsd-net
On Jun 26, 2007, at 7:08 PMJun 26, 2007, Bruce A. Mah wrote:
If memory serves me right, Eric F Crist wrote:
On Jun 26, 2007, at 4:32 PMJun 26, 2007, Bruce A. Mah wrote:
[big snip]
I wonder if the problem I've seen with bridge(4) might be related to
your IPv6 problems (since y
On Jun 26, 2007, at 4:32 PMJun 26, 2007, Bruce A. Mah wrote:
If memory serves me right, Eric F Crist wrote:
Hi Eric--
First note that I'm a different Bruce than the chap who's been helping
thus far. :-)
BTW, use "ndp -a" to see this.
Your setup is not *too* different
On Jun 25, 2007, at 7:55 PMJun 25, 2007, Bruce M. Simpson wrote:
Eric F Crist wrote:
My problem isn't getting out to 2001:4980:1::5, it's getting to my
LAN, the 2001:4980:1:111::/64 network. My gateway, the machine
from which I posted the routing and ifconfig information, is
m with the
fxp driver, or perhaps my setup with the ethernet bridging?
Thanks again.
-
Eric F Crist
Secure Computing Networks
___
freebsd-net@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-net
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
nk there may possibly be a problem with the bridging code?
Any ideas would help. For the record, I have read the FreeBSD
Handbook, amongst many, many, many other documentation sources.
TIA for the help!
-
Eric F Crist
Secure Computing Networks
_
19 matches
Mail list logo
