of jumbo frames per host
(as far as I know; such a thing would certainly be useful, though).
Mostly, I'd still go with "be conservative in what you send, liberal
in what you accept."
Mike
___
freebsd-net@freebsd.org maili
settable with ifconfig. It expands the "accept
what is convenient" to "and also accept whatever is reasonable
for jumbo" (for this NIC).
Mike
___
freebsd-net@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-net
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
> Mike Karels wrote:
> >>> Secure Computing (my employer) has a modification that seems reasonable
> >>> to me (well, I guess I wouldn't have done it otherwise). We adopted the
> >>> existing but unused JUMBO_MTU capability flag, and, if enabled, instru
At 07:03 PM 10/9/2007, Jack Vogel wrote:
Mike,
This is a patch against my 6.6.6 driver that adds a new value to the
debug sysctl, you would give the command 'sysctl dev.em.0.debug=2'
and it will dump out the first 32 16-bit words of the prom.
Hi,
Yes, I think thi
r gigabit
switch, a 10mbps hub, or directly cabled together?
-Mike
___
freebsd-net@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-net
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
far
> as i know.
The last NICs that I remember with control over retries were some
of the original 3Com NICs. They supported only 10Base5, the original
thick coax Ethernet (remember vampire taps?). They plugged into a
Unibus on a VAX, or a PDP-11
On Fri, 19 Oct 2007, Garrett Cooper wrote:
Just to clarify, how are the two hooked together? Is it over gigabit
switch, a 10mbps hub, or directly cabled together?
-Mike
Sure. They're both connected over a gigabit switch, but the Windows
driver's kind of sketchy because i
ENG_7 tcp to Solaris work fine with unmodified
kernel:
Is there a firewall in one path, but not the other?
-Mike
___
freebsd-net@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-net
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
value to 3, that should allow things to work even through firewalls
that do not interpret the scaling value properly.
-Mike
___
freebsd-net@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-net
To unsubscribe, send any mail
At 12:33 PM 11/2/2007, Jack Vogel wrote:
So at this point I'm unclear, with my reposting of if_em.c last
night has everyone seen both parts or do I have to try something
else?
Seems to work. I grabbed it from the mailing list archive off www.freebsd.org
http://lists.freebsd.org/pipermail/free
_route_
dhclient_program => ipv4_dhclient_program
dhclient_flags => ipv4_dhclient_flags
dhclient_flags_ => ipv4_dhclient_flags_
background_dhclient_ => ipv4_background_dhclient_
Please try it and let me know what you think.
Cheers.
--
Mike Makon
So, that's a first thing
to test before we poke at the upper layers.
If that doesn't help, can you post more details about how you are
stressing the system?
Thanks,
-Mike
___
freebsd-net@freebsd.org mailing list
http://lists.freebsd.org/m
n queue overflow condition, leading to total
collapse. I'll have to cobble together a test program to see what happens
in the listen queue overflow case.
Thanks for the quick feedback,
-Mike
___
freebsd-net@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-net
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
On Sat, 10 Nov 2007, Mike Silbersack wrote:
FWIW, my crazy theory of the moment is this: We have some bug that happens
when the listen queues overflow in 7.0, and your test is strenuous enough to
hit the listen queue overflow condition, leading to total collapse. I'll
have to c
s ok to me... but like I
said, I need to retest that too.
When I use ab I'm telling it to use a max of 100 simultaneous
connections (ab -c 100 -n 5 http://66.230.193.105/). Wouldn't that
be well under the limit?
Yep, should be. Hmph.
-Mike
___
.
> > And this would be a good time to change defaultrouter to default_router!
>
> Or we could make it shorter and call it gateway.
Changing it at this late date is probably just gratuitous.
FYI, there's a slightly updated patch back up at:
http://people.freebsd.org/~mtm/src-etc.ipv6.d
work!
I'll get this change commited in the next day or two.
-Mike
___
freebsd-net@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-net
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
be a more flexible version for-current.
Here's the question..
I need a word to use to describe the network view one is currently on..
e.g. if you are usinghe second routing table, you could say I've set xxx to 1
(0 based)..
In the spirit of your subject, why not call
e card is still supported under FreeBSD. Do you
really need T1 connectivity ?
>bgp routing software and how much RAM do folks think I can get away with?
Quagga and 1G of RAM is plenty. 512 will work just fine, but splurge
on the extra $50 to give you a bit more room :
connection.
Then send that to me and I'll get to it as soon as I can, which may be a
week from now.
-Mike
___
freebsd-net@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-net
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
default, that would be ok with me.
I'm not generally opposed to security improvements that only affect edge
cases... but being unable to connect is not an edge case!
-Mike
___
freebsd-net@freebsd.org mailing list
http://lists.freebsd.org/m
MAIL PROTECTED]>
In-Reply-To: <[EMAIL PROTECTED]>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: Mike Silbersack <[EMAIL PROTECTED]>, [EMAIL PROTECTED],
[EMAIL PROTECTED], [EMAIL PROTECTED], [EMAIL PROTECTED],
freebsd-n
fine too.
No anomalies seen.
Er, I think we may be getting the two timestamp issues crossed, wasn't
Maxim the one running into the problem where the large window scale sizes
were causing trouble?
-Mike
___
freebsd-net@freebsd.org mailing list
smaller.
(http://www.ietf.org/internet-drafts/draft-ietf-tsvwg-port-randomization-01.txt)
There are a number of commonly used ports above 1000, such as nfs and x11.
I think OpenBSD uses 1-65535, maybe that's a safer choice to go with.
g that I
can't apply it. I think all the whitespace got stomped, either by your
mail program or my mail program. Can you please resent this as an
attachment?
-Mike
___
freebsd-net@freebsd.org mailing list
http://lists.freebsd.org/mailman/lis
ure" in the BSD TCP stack that all local ports are
considered equal; even for applications that do a connect() call and
specify a remote IP/port, we do not let them use the same local port to
two different remote IPs at the same time. This puts a limit on the total
number of outgoing c
ry
additions to the local port hash time would be nice to remove if you're
investigating the related issues.
One thing you may or may not have noticed is that FreeBSD keeps TIME_WAIT
sockets in a seperate zone which has a limit size, so you will not have to
worry too much about them
On Mon, 3 Mar 2008, Fernando Gont wrote:
At 04:11 a.m. 03/03/2008, Mike Silbersack wrote:
Here's the same patch, but with the first ephemeral port changed from 1024
to 1.
Now that I've actually gone to try to apply the patch (so I can view the
two codepaths side by side, r
did get a chance to run it at the freebsd end:
Try this change; it was too late to be put in 7.0, but it will be merged
to 7-stable in a few days:
http://www.freebsd.org/cgi/cvsweb.cgi/src/sys/netinet/tcp_var.h.diff?r1=1.160;r2=1.161
-Mike
___
free
tice it being disabled at
all. In fact. FreeBSD 4.x didn't have any SACK support whatsoever.
-Mike
___
freebsd-net@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-net
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
who had more than on OS to try it out).
This sounds like the issue Jake Rizzo has been describing. The tcp_var.h
change I put in a few days ago only seems to help when timestamps are
enabled. I'll try to sit down and read through this e-mail tonight.
4 05 64 04 02 00 01 <- ends with a NOP after the EOL
I think we will need to fix tcpdump before trying to finish diagnosing
this problem. We were missing key information before.
-Mike
___
freebsd-net@freebsd.org mailing list
http://lists.freebs
On Wed, 12 Mar 2008, Mike Silbersack wrote:
I think we will need to fix tcpdump before trying to finish diagnosing this
problem. We were missing key information before.
-Mike
Hm, that was far easier than expected. Patch attached.
Here's what the two tcpdumps show now:
6.3:
IP A &g
, nop> so that we can detect such errors more easily
in the future.
I wish I had paid more attention to that part of the previous thread on
this topic!
-Mike
___
freebsd-net@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freeb
On Thu, 13 Mar 2008, Bjoern A. Zeeb wrote:
It should give you output like this:
19549200,sackOK,eol,0x01[bad padding]>
I like the [bad padding].
But I think the "good" case should look like it did before, per POLA.
-Mike
__
tcp-option-padding.diff
--
Bjoern A. Zeeb bzeeb at Zabbadoz dot NeT
I still think the non-bad case should look exactly as it did before, no
matter what set of options was selected. :)
I have not heard back from the tcpdump person that I contacted.
options=9b
ether 00:10:18:14:15:43
inet 192.168.0.12 netmask 0xff00 broadcast 192.168.0.255
media: Ethernet autoselect (100baseTX )
status: active
0[cage]#
The MTU should be 1500 after the route change no ?
---Mike
could get
around to making those fixes for you. If not, I think it's safe to
commit.
-Mike
___
freebsd-net@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-net
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
ver author for insight / help
---Mike
___
freebsd-net@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-net
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
On Sun, 18 May 2008 23:31:33 -0700 Jeremy Chadwick <[EMAIL PROTECTED]> wrote:
> On Sun, May 18, 2008 at 09:40:37PM -0700, John Timony wrote:
> > Hi,all
> >
> > I have installed Freebsd 7.0 on my Acer TravelMate 220,my router ip is
> > 192.168.0.1,the ip of my Freebsd is 192.168.1.4,Net Mask is
l, Bill can be grumpy at times, you might consider being happy that he
didn't reply. :)
First off, is this 5.2.1, or 5.2-current? If it's older, perhaps bugs in
the NDISulator have been fixed since.
Second, have you tried various versions of the windows drivers for the
card? May
em you tested the card in?
Mike "Silby" Silbersack
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-net
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
le
poking around there... if the driver is also broken there, maybe there's
hope that a new driver will fix the problem.
That's the end of my knowledge of the NDISulator, good luck! :)
Mike "Silby" Silbersack
___
[EMAIL PROTECTED] mailing
the server's end. Some
of the changes we've made in 5.x might fix the problem, but I don't think
anyone has looked into that specific case.
A simpler solution might be to use passive mode. I think that you can set
that somewhere in the install options.
Mike "Silby" Si
On Tue, 1 Jun 2004, Kris Kennaway wrote:
> On Tue, Jun 01, 2004 at 12:05:35PM -0500, Mike Silbersack wrote:
> > Sounds like something that should be dealt with on the server's end. Some
> > of the changes we've made in 5.x might fix the problem, but I don't think
&
re certainly possible.
Something fishy must be going on here, because sysinstall doesn't make too
many ftp connections, does it? Port recycling issues should only be
showing up in applications which make thousands of connections per minute.
Mike "Silby" Silbersack
___
e suited to this purpose than arc4random
(I'll have to check out Don's code in BIND.)
2. General port recycling issues.
It sounds like sequential port allocation was masking problems of type #2
in the past.
Mike "Silby" Silbersack
ll tickle the exact same port recycling problem, so reverting our
client behavior isn't a long-term solution.
I'm still too swamped to poke at the problem.
Mike "Silby" Silbersack
___
[EMAIL PROTECTED] mailing list
http://lists.freebs
NOBUFS.
I believe this message is reporting the same problem I'm seeing:
http://groups.google.com/groups?q=racoon+%22No+buffer+space+available%22&hl=en&lr=&ie=UTF-8&selm=20040606025301.GB41345%40mehnert.org&rnum=1
Does anybody k
oev.ru/en/
I would prefer that sfbufs statistics either be kept in netstat -m, OR
added to an entirely different program (perhaps vmstat). Making yet
another netstat flag just because we're scared of confusing users is a
noble compromise, but will in the end just make things more confu
th network and general memory usage.
4.x: MFC the vmstat implementation.
This would preserve 4.x's behavior, but allow 5.x users (who have a new
netstat -m output format anyway) to see sfbuf information without invocing
multiple utilities.
Mike &qu
oid collisions.
Remember: An IP ID collision is equivalent to a packet being lost; this
is not a big deal.
Mike "Silby" Silbersack
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-net
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
ts of it not getting along with the
FreeBSD driver, for whatever reason.
If you successfully flashed up to 1.7.4, I believe that you should be able
to flash back to 1.5.6 without issue.
Mike "Silby" Silbersack
___
[EMAIL PROTECTED] ma
On Wednesday 09 June 2004 02:23 pm, Mike Durian wrote:
> Sometime between Feb 9 and June 9 something changed in the kernel
> that causes racoon to fail. I'm afraid I don't have a verbatim
> error message handy, but my notes (from running racoon with debugging
> enabled, in t
set pptp disable originate
---
Here is mpd.secrets:
---
mike"secret"
---
And here is the log from an unsucessful attempt:
---
Jul 14 12:04:37 fbsd mpd: mpd: pid 59486, version 3.18
([EMAIL PROTECTED] 16:17 13-Jul-2004)
Jul 14 12:04:37 fbsd mpd: [pptp0] ppp node is "mpd
Motonori Shindo said:
> Mike,
>
> This seems like a DSL router's problem. Because PPTP encapsulates PPP
> using GRE, which is neither TCP nor UDP, routers sometimes can not NAT
> PPTP traffic. Some router conqurs this problem by simply "passing
> through" GRE p
Motonori Shindo said:
>> > This seems like a DSL router's problem. Because PPTP encapsulates PPP
>> > using GRE, which is neither TCP nor UDP, routers sometimes can not NAT
>> > PPTP traffic. Some router conqurs this problem by simply "passing
>> > through" GRE packets (and hence this feature is s
Hello,
I have recently discovered, after long periods of trying to debug a VPN
server, that i can not establish PPTP VPN connections any more. The
culprit seems to be natd not forwarding GRE properly. I have tried adding
a 'redirect_proto gre' option to natd, but same behaviour occurs. I could
swe
On Sat, 24 Jul 2004 12:47:26 +1000, in sentex.lists.freebsd.net you
wrote:
>
>I found Mike Tancsa's patch but didn't like it. I rolled my own, which
>seems to be working so far. It works by switching from LQR to simple
>echo requests when LQR times out.
I feel so unliked
ives when I first figured out
what was broken. If you need another copy I am happy to post again.
---Mike
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-net
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
On Mon, 26 Jul 2004 21:14:33 -0700, in sentex.lists.freebsd.net you
wrote:
>Mike Tancsa wrote:
>
>>On Sat, 24 Jul 2004 20:42:01 -0700, in sentex.lists.freebsd.net you
>>wrote:
>>
>>
>>>>>Seriously though, mine was a very ugly hack to
>>&g
. If you are still seeing errors check the cables. There are
occasionally incompatibilities between certain NICs and switches, but thats
pretty rare see /usr/src/sys/dev/em/README
---Mike
___
[EMAIL PROTECTED] mailing list
http://lists.freebs
s assigned that time.
Mike "Silby" Silbersack
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-net
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
> > > On Mon, Jul 12, 2004 at 03:32:18PM -0600, Mike Durian wrote:
> > > > This is just a follow-up to say the problem still exists in a
> > > > -current system I built from source yesterday (7/11/04). Does anyone
> > > > know what's going on?
>
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-net
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
table. Also, they are now
terminated prematurely when there is a shortage of ephemeral ports. As a
result, time_wait sockets are no longer the problem they were in certain
situations under 4.x.
Mike "Silby" Silbersack
___
[EMAIL PROTECT
rom the networking folks as to the
correctness of the cleanups.
Cheers.
--
Mike Makonnen | GPG-KEY: http://www.identd.net/~mtm/mtm.asc
[EMAIL PROTECTED] | Fingerprint: AC7B 5672 2D11 F4D0 EBF8 5279 5359 2B82 7CD4 1F55
[EMAIL PROTECTED]| FreeBSD - Unleash the Daemon
On Thu, 30 Sep 2004, Andrew Wenlang Zhu wrote:
Does any one know how to use Dummynet to fragment packet? Or any other open
source software can achieve this?
Thanks,
Andrew
I don't think that dummynet can fragment packets.
The program you're looking for is fragrouter, I think it's
stood the link above or TCP/IP Illustrated
Volume 3 then please refrain from participating in this discussion!
Hey, I just looked in section 24.7 in Vol. 1, and it says nothing but good
things about T/TCP - you must be the one misunderstanding things here! :)
Mik
file; you could just extend it so that if two sockets
are passed to it instead of a socket and file, it would do what you've
described above.
Tell us how it works out. :)
Mike "Silby" Silbersack
___
[EMAIL PROTECTED] mailing list
http://l
of XORP immediately after the
>next point release.
Are there advantages to XORP over say Quaaga ?
---Mike
>
>BMS
>___
>[EMAIL PROTECTED] mailing list
>http://lists.freebsd.org/mailman/listinfo/freebsd-net
>To
Neat! What about the underlying OS ? Is it optimized for a particular OS
such as
http://www.pdos.lcs.mit.edu/click/ or FreeBSD or Linux ?
---Mike
At 09:58 AM 16/11/2004, Bruce M Simpson wrote:
On Sat, Nov 13, 2004 at 09:45:26PM -0500, Mike Tancsa wrote:
> Are there advantages
the moment, and won't be back for a few weeks. Once he
returns and catches up on his e-mail, I'm sure he'll add something. If he
doesn't... e-mail him directly!
Mike "Silby" Silbersack
___
[EMAIL PROTECTED] mailing list
h
I love that it comes with a regression test,
btw. We'll have to include that in the new regression testbench that was
recently added.
This should be committed within the next few days, sorry again for the
delay.
Mike "Silby" Silbersack
_
Synopsis: [patch] TCP should honour incoming RSTs even if the receive window is
closed
Responsible-Changed-From-To: freebsd-net->silby
Responsible-Changed-By: silby
Responsible-Changed-When: Fri Nov 26 08:09:32 GMT 2004
Responsible-Changed-Why:
Patch committed, hook into the regression test fram
atively, with
timestamps, you never have to worry about such timing problems.
You are correct that the non-TS code must remain in the TCP stack.
However, I don't think complexity of the old code is what he was referring
to.
Mike "Silby" Silbersack
_
he lists and found:
http://marc.theaimsgroup.com/?l=freebsd-net&m=110172867801777&w=2
I am not sure if this is related but suspect it is - if so will adding a
differnet card from a different vendor fix this?
Below are dmesgs, pf.conf and rc.conf,
Any help would
hertype 802.1Q
(0x8100), length 64: vlan 253, p 0, ethertype ARP, arp who-has 10.2.253.2
(6f:6c:3d:49:4d:41) tell 10.2.253.50
21:00:37.204123 00:0c:f1:9d:af:04 > 00:c0:9f:31:82:f1, ethertype ARP (0x0806),
length 42: arp reply 10.2.253.2 is-at 00:0c:f1:9d:af:04
Below are dmesgs, pf.conf
see how to disable the hardware vlan tagging - does anybody know of is
this possible?
Mike.
On Wed, 1 Dec 2004, Max Laier wrote:
On Tuesday 30 November 2004 22:17, Mike Wolman wrote:
Hi,
I am having a problem with 5.3 release with pf, vlans and the em device.
<...>
I have had a hunt on t
Mitch (Bitblock) said:
> Short answer is "Yes".
>
> For basic failover, I've used a script which monitors link status and
> function (by pinging or connecting to a remote host). Failover is
> accomplished by switching the default route.
>
> Using ipfw fwd statements, you can make both links functi
lans are supported on one parent device?
>
> I don't know what happens with double tagged vlan packets.
I think what he's asking about is whether FreeBSD prevents any of the
nasty hacks that can be accomplished by double-tagging frames, or if there
is s
ion
which were attempts to fix it.)
Comments appreciated,
Mike "Silby" Silbersack--- /usr/src/sys.old/netinet/in_pcb.c Thu Dec 16 03:26:11 2004
+++ in_pcb.cThu Dec 16 03:27:29 2004
@@ -95,8 +95,10 @@
intipport_hifirstauto = IPPORT_HIFIRSTAUTO;/* 49152 */
intipport_hilastau
On Sat, 18 Dec 2004, Mike Silbersack wrote:
There have been a few reports by users of front end web proxies and other
systems under FreeBSD that port randomization causes them problems under
load. This seems to be due to a combination of port randomization and rapid
connections to the same
On Wed, 29 Dec 2004, Maxim Konovalov wrote:
On Wed, 29 Dec 2004, 03:02-0600, Mike Silbersack wrote:
This appears to work for Igor, and it seems safe enough to commit before
4.11-RC2. But, if possible, I'd like a few more sets of eyes to doublecheck
the concept and code; please take a look
firewalls like IPF or PF would handle such a situation. How do
they respond to unexpected SYN packets?
Mike "Silby" Silbersackdiff -u -r /usr/src/sys.old/netinet/tcp_input.c /usr/src/sys/netinet/tcp_input.c
--- /usr/src/sys.old/netinet/tcp_input.cMon Jan 3 01:11:40 2005
+++ /usr/
pcoming reply to Don...
Mike "Silby" Silbersack
___
freebsd-net@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-net
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
t_template->tt_ipgen,
&t_template->tt_t, (struct mbuf *)NULL,
tp->rcv_nxt, tp->snd_una - 1, 0);
(void) m_free(dtom(t_template));
, tcp_respond does look like a good candidate...
BTW, that tcp template code should probably have been removed years ago,
it's only used by keepalives now. I just haven't gotten around to
replacing it.
Mike "Silby" Silbersack
___
freebs
andall's response, it provided some useful insight into the
situation.
Mike "Silby" Silbersack
___
freebsd-net@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-net
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
n clean up that along with the dropafterack
case in tcp_input, but that would make this patch far too complex.
Please take a look at the patch and the abbreviated tcpdump from my test
and see if it looks correct.
Thanks,
Mike "Silby" Silbersackdiff -u -r /usr/src/sys.old/netinet/icm
th->th_urp--;
else
thflags &= ~TH_URG;
todrop--;
}
And then we could tear out all the two places TH_SYN is mentioned below,
the place I copied from, and the place where there the tcp_drop() is.
If we made that change, then we'd still be doing only one check for
TH_SYN, but the code wou
On Mon, 10 Jan 2005, Mike Silbersack wrote:
We could do something there like
if (th->th_seq != tp->irs) {
goto dropafterack; /* Or however we handle these bad syns */
} else {
thflags &= ~TH_SYN;
th->th_seq++;
if (th->th_urp > 1)
th->th_urp--;
else
x27;s probably
timing related, I don't know if it's really something that can be "fixed".
Anyway, it might still help if Len used tcpdump to capture a server-side
TIME_WAIT from 4.7 and a client-side TIME_WAIT from 4.10 so that we can
compare the difference. A dump from the
e not
found a solution. If anyone has any suggestions, they would be very much
appreciated (Aside from using jails, which I suspect would work but would be
cumbersome). Thanks!
Mike
___
freebsd-net@freebsd.org mailing list
http://lists.freebsd.org/ma
few
days.
Something which has occured to me in the interim is that all three issues
outlined in the tcpsecure draft should be easy to fix in pf (or ipfw?) the
same way, so we should probably patch those as well.
Mike "Silby" Silbersack
___
options.
Mike.
On Wed, 19 Jan 2005, Charlie Schluting wrote:
Did something change from 5.2.1 to 5.3?
In 5.2.1 I used to have a config where the parent device, em(4), didn't have
an IP, and the vlan dev had the IP address. (yes, the parent device was "UP")
I then configured the trunk
be quite useful.
Doesn't TCPDEBUG do something like that already, though? I haven't taken
a look into it, perhaps I should.
Mike "Silby" Silbersack
___
freebsd-net@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-n
On Sun, 20 Feb 2005, Kris Kennaway wrote:
On Sun, Feb 20, 2005 at 07:40:35PM -0600, Mike Silbersack wrote:
Yes, I think that'd be very useful; when a user has a repeatable network
problem, we could have them turn this on and create a detailed log file
for us. In cases of reset connections
Hi,
I have recently cvsuped to a new snapshot of -current, the existing system
was about 1-2 months old. I am now seeing a lot of link state messages in
dmesg.
em0: link state changed to DOWN
em0: link state changed to UP
em0: link state changed to DOWN
em0: link state changed to UP
em0: link sta
machine, I think it has
options to scramble such things, no matter what OS the clients behind it
are running.
Mike "Silby" Silbersack
___
freebsd-net@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-net
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
301 - 400 of 1032 matches
Mail list logo
