Hi Michael,
On Sun, Apr 11, 2021 at 2:27 PM Michael Sierchio wrote:
>
> On Sun, Apr 11, 2021 at 2:20 PM Matt Joras wrote:
>
> > Hi Michael,
> >
> > On Sun, Apr 11, 2021, 1:25 PM Michael Sierchio wrote:
> >
> >> Hi, all. I noticed my firewall was dropp
bhārata
> ___
> freebsd-net@freebsd.org mailing list
> https://lists.freebsd.org/mailman/listinfo/freebsd-net
> To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org"
>
Matt Joras
>
_
er, actually finding out what capability 0x400 refers to seems to be
neigh on impossible.
Regards,
Matt Churchyard
___
freebsd-net@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-net
To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org"
)
Let me know any addition information you need.
Thank you,
Matt Allanson
System Engineer I
[TriMedx]
7144 Lakeview Pkwy W Drive
Indianapolis, IN 46268
(317) 275-5515 office/fax
(317) 939-3313 mobile
matt.allan...@trimedx.com<mailto:matt.allan...@trimedx.com>
trimedx.com<http://www.tr
It has been brought to my attention that I didn't link to the bug, my
apologies. https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=227720 If anyone
could take a look and see what could be the problem I would greatly appreciate
it. Please let me know if you need anything else.
Thank you,
Hey guys,
Wondering if anyone has had a chance to look into this bug.
Thank you,
Matt Allanson
System Engineer I
[TriMedx]
7144 Lakeview Pkwy W Drive
Indianapolis, IN 46268
(317) 275-5515 office/fax
(317) 939-3313 mobile
matt.allan...@trimedx.com<mailto:matt.allan...@trimedx.com>
trime
t;
Saying "Not for FreeBSD" is needlessly confusing and not accurate. In
the common parlance "raw sockets" does not refer to libdnet, which is
not a part of the FreeBSD base system. You cannot use traditional raw
sockets on FreeBSD to receive traditional protocol packets. The only
way to do that in the base system is to use a BPF handle directly.
Matt
___
freebsd-net@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-net
To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org"
ernally.
Good luck.
Matt Joras
___
freebsd-net@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-net
To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org"
s to be OACTIVE, (though I'm not sure why all your A's are
swapped with R's). When it's OACTIVE it will drop packets and generally
behave as if the link is down. Does igb0 stay in OACTIVE indefinitely,
or does it go back to a normal state at any point?
Matt
.com - here)" [1]
That doesn't mention their newer NICs, however, though I don't see a
mention of the feature on their product sheets.
Matt
[1] https://community.mellanox.com/docs/DOC-1450
___
freebsd-net@freebsd.org mailing list
https://lists
On 08/07/2017 09:11, Hans Petter Selasky wrote:
> Hi,
>
> Try to enter "kgdb" and run:
>
> thread apply all bt
>
> Look for the callout function in question.
>
> --HPS
>
If you don't have a way to attach kgdb handy you could also break into
ddb(4) and run "alltrace". Though gdb would be more useful
estions of alternative
approaches. An approach I did think about, but discarded, was to add a
protocol function to struct protosw, something like int
pr_getsockdescr(struct socket *, char *, size_t) which would fill in a
"human-readable" description of the socket based on whatever is appropr
are never called from swi context or one serving as an ithread. Eventually
these constructs should be replaced by sx locks and the DELAYs replaced
with sleeps.
--
[image: Limelight Networks] <http://www.limelight.com/>
Matt Macy - *Consultant*
+1 650 440 8947
www.limelight.com Del
based on flow
information (e.g. RSS hashing), but as far as I know that is generally
limited within a single port, so it doesn't really help in the general
case of a lagg.
Matt
___
freebsd-net@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-net
To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org"
Out of curiosity, what sort of lagg setup are you using that's causing
the TCP packets to be split across the two lagg interfaces?
Matt
On Mon, Jun 26, 2017 at 1:35 PM, Navdeep Parhar wrote:
> On Thu, Jun 22, 2017 at 3:57 PM, Youssef GHORBAL
> wrote:
>> Hello,
>>
&
e has an interest in this work please review the revision:
https://reviews.freebsd.org/D11370
Thanks,
Matt Joras
___
freebsd-net@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-net
To unsubscribe, send any mail to &
On Mon, Jun 26, 2017 at 6:36 AM, Andrey V. Elsukov wrote:
> On 26.06.2017 16:29, Ben RUBSON wrote:
>>
>>> On 26 Jun 2017, at 15:25, Andrey V. Elsukov wrote:
>>>
>>> On 26.06.2017 16:27, Ben RUBSON wrote:
> On 26 Jun 2017, at 15:13, Andrey V. Elsukov wrote:
>
> I think it is not
incorrect
information displayed by ifconfig(8).
Matt
___
freebsd-net@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-net
To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org"
es drivers sleeping in the vlan_*config event handlers (which
involves having a global rmlock _and_ sx in if_vlan).
I was planning on doing a similar audit/fixing of if_lagg soon when I
get the chance.
Matt Joras
___
freebsd-net@freebsd.org mailing list
htt
top of bxe and then you
downed bxe you could very easily hit a use-after-free since bxe free'd
its rings while if_lagg is trying to transmit a packet.
Matt Joras
On Mon, Apr 11, 2016 at 2:03 PM, K. Macy wrote:
> You do understand that init needs to be run every time interface
> sett
c(dmat, dmamap, op); \
^~
/usr/src/sys/dev/netmap/if_em_netmap.h:151:11: note: forward declaration of
'struct em_buffer'
struct em_buffer *txbuf = &txr->tx_buffers[nic_i];
Any ideas or am I trying to
> On Mon, Apr 04, 2016 at 10:37:48PM +, Brooks Davis wrote:
> > On Mon, Apr 04, 2016 at 11:29:31AM +0000, Matt Churchyard via freebsd-net
> > wrote:
> > > From the little information I can find on the net it seems that valeX:Y
> > > is the format for a
yone would like to review them.
https://reviews.freebsd.org/D5825
The essence of the changes is to make the global vlan lock an
rmlock(9) and expand its scope to synchronize reading/using ifvlans
with destruction events as well as ensure exlusivity in certain
configuration paths.
Thanks,
hether that applies to just the first part of the whole thing.
Can anyone clarify the valid format for a vale switch/port?
Is there any length or character restriction on X & Y?
Regards
Matt Churchyard
___
freebsd-net@freebsd.org mai
ode to RGMII mode."
It seems that some additional driver development will likely be required.
Thanks,
Matt
On 9 March 2015 at 06:19, Yonghyeon PYUN wrote:
> On Fri, Mar 06, 2015 at 12:45:22PM +, Matt Dooner wrote:
>> Hello,
>>
>> I am having some trouble config
ig is forked at
https://github.com/MattDooner/crochet-freebsd/ and u-boot changes
against 2014.04 at https://github.com/MattDooner/u-boot
Cheers,
Matt
___
freebsd-net@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-net
To unsubs
> On Wed, Feb 11, 2015 at 05:49:35PM + I heard the voice of Matt
> Churchyard, and lo! it spake thus:
> > > On 11 Feb 2015, at 17:38, Warren Block wrote:
> > > ifconfig em0 inet 192.168.1.1/24
> >
> > Yeah I've been using that format in rc.conf for y
> On 11 Feb 2015, at 17:38, Warren Block wrote:
>
>> On Wed, 11 Feb 2015, Matt Churchyard wrote:
>>
>> Just been helping someone on the forums who appears to have configured their
>> network interface incorrectly. It looks like they've assigned 250.250.250.
On 2015-2-11, at 09:59, Matt Churchyard wrote:
>> Just been helping someone on the forums who appears to have configured their
>> network interface incorrectly. It looks like they've assigned 250.250.250.0
>> as the netmask.
> that's not invalid. The netmask is
hy FreeBSD accepts this value as a netmask? I'm fairly
well versed in IPv4, although not a real expert, but I see no reason why such a
mask would be used.
Testing on my Win8.1 workstation, it gets rejected telling me the mask must be
contiguous (i.e. all 1's then 0's), as I wou
x if it
works for you (and I guess numerous other users). It just seems strange that if
I force the interface up, it’s absolutely perfect. Chances are, if I ever use
carp in production on real machines, it may just work but what I’m seeing in
Virtualbox doesn’t seem right.
Regards,
Matt
From
m at the moment. I actually have no
current requirement for carp, I was just doing some testing to see how it
worked.
As I said I'll try again with 10.1 and if it's still the same I may get more
involved with trying to find out exactly what's going on and whether it's a bu
is possible in earlier versions that use the old carp system. (And
configuration of the old carp is quite different)
Regards,
Matt Churchyard
--
Hi Matt,
I think I'm the user you try to help in the forum ;-).
I had the same problem like you when doing the first tests with carp. The alias
and a few 10.0-RELEASE vm's I've had kicking
around for a while. I might replace them with 10.1-RC2 tomorrow and see if I
get the same thing.
Matt
On 15 Oct 2014, at 16:58, Freddie Cash
mailto:fjwc...@gmail.com>> wrote:
You don't need the "up" keyword, and it defin
address, I'd expect it to work with a single /30 carp address)
Regards,
Matt Churchyard
___
freebsd-net@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-net
To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org"
go a lot
of changes as I understand it between 9 and 10.
On 4/14/2014 9:14 PM, Eugene M. Zheganin wrote:
Hi.
On 10.04.2014 02:15, Matt Lager wrote:
I have used IPSEC tunnels w/ racoon to establish point to point VPN
connections for a long time, with great success. I recently decided to
upgrade
king sure interfaces were all named properly and whatnot.
Any advice would be appreciated. Thanks!
Matt
--
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.
___
freebsd-net@freebsd.org mailing li
On Aug 9, 2013, at 1:44 PM, Thor Lancelot Simon wrote:
> On Fri, Aug 09, 2013 at 09:34:25PM +0100, Mindaugas Rasiukevicius wrote:
>> Steven,
>>
>> Steven Bellovin wrote:
>>> There's a one-word summary: *assurance*. With the current design,
>>> it's easy to *know* what can happen. With a Turi
1 at the same time and
sending FIN/ACKs repeatedly (though our connections are a bizarre case
of this where both ends of the connection are actually the same
connection).
Thanks,
Matt
___
freebsd-net@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-net
To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org"
receiver's advertised window allows, the total
FlightSize would remain less than or equal to cwnd plus 2*SMSS,
and that new data is available for transmission.
So, this is a detailed way of asking: do we need a check here to make s
e you know already know what else needs to
be done for that).
Just let us know if you want us to prepare the rest of the patch for that
new stat or not.
Thanks,
Matt
On Mon, Apr 8, 2013 at 8:13 AM, Andre Oppermann wrote:
> On 05.04.2013 13:09, Matt Miller wrote:
>
>> Hey Rick,
>
tate) {
+ TCPSTAT_INC(tcps_rcvwhileclosing);
+ goto drop;
+ }
KASSERT(tp->t_state > TCPS_LISTEN, ("%s: TCPS_LISTEN",
__func__));
Or, if there's someone more familiar with the locking in these paths, they
may be able to come up with a wa
On Wed, Mar 13, 2013 at 3:35 PM, Chuck Swiger wrote:
> Hi--
>
> On Mar 13, 2013, at 8:21 AM, Matt Miller wrote:
>> If we have a connection that has received a SYN and ip_output()
>> returns, say, EHOSTUNREACH, is there anything that guarantees the
>> connection would a
e ENETDOWN:
case ENETUNREACH:
if (TCPS_HAVERCVDSYN(tp->t_state)) {
tp->t_softerror = error;
return (0);
}
Thanks,
Matt
___
ith the problem. Once an interface sees a packet with
anything else at 0x47f, it's no longer affected, so there's a narrow
window of vulnerability in affected NICs.
Matt
___
freebsd-net@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-net
To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org"
well.
I'll try to test it this weekend on my rt3090.
Matt
___
freebsd-net@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-net
To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org"
FD_SET(sock, &svc_fdset);
svc_maxfd = max(svc_maxfd, sock);
}
rwlock_unlock(&svc_fd_lock);
}
Thanks,
Matt
___
freebsd-net@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-net
To unsubscr
On 03/20/12 14:54, Gustau Perez Querol wrote:
> VBoxManage modifyvm "FreeBSD virtual machine" --nic1 bridge --nictype
> bridge virtio --bridgeadapter vlan10
On my machines running virtualbox-ose-4.0.14, VBoxManage won't accept vlan
interfaces either - I need to kill the GUI then edit the conf
You're welcome. For what it's worth, the Linux driver uses the second set of
values referenced below. I think one of the two drivers likely has a bug, but
I'm not currently in a position to test it on hardware, so you don't need to fix
it on my account :)
Thanks and regards,
ke-on-lan.
Thanks and regards,
Matt
___
freebsd-net@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-net
To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org"
production code examples if you
require them, but this link should be more than enough to get you
started:
http://www.benzedrine.cx/ackpri.html
-Matt
___
freebsd-net@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-net
To un
On 4 October 2011 19:17, Li, Qing wrote:
> Hi,
>
> Please download the newer patch from
>
> http://people.freebsd.org/~qingli/in6.c.diff
>
> This patch ought to fix both problems.
Just applied this patch. Yes, this fixes both problems. As far as I
can see now everything is working. So the
On 4 October 2011 10:48, Matt Smith wrote:
> I have just applied the patch, recompiled the kernel, and rebooted
> with my original configuration in rc.conf and all interfaces have come
> up as expected now. The routes are there, I can ping everything, and I
> can connect to everything
rc.conf and all interfaces have come
up as expected now. The routes are there, I can ping everything, and I
can connect to everything as expected.
I don't know if this is going to affect 9.0? But if it does could it
get committed into that tree to make it into t
you if you come up with a patch.
I'm still really confused though why it worked before my power failure
and failed afterwards when as far as I'm aware nothing has changed on
the system.
I'll await the patch and test it out when you post it.
Regards, Matt.
__
On 26 September 2011 21:00, Mark Atkinson wrote:
> Depending on your release you might need to add
>
> ifconfig gif0 inet6 -ifdisabled
Thanks for the suggestion but this also made no difference. The
problem isn't that the interface is down or disabled, from other
suggestions yesterday it's become
On 26 September 2011 17:05, Gary Palmer wrote:
>
> Not sure, however an experiment may be in order
>
> # ifconfig gif0
> ifconfig: interface gif0 does not exist
> # ifconfig gif0 create
> # ifconfig gif0 tunnel 1.2.3.4
> # ifconfig gif0 inet6 2abc::2 2abc::1 prefixlen 128
> # netstat -nr -f inet
On 26 September 2011 15:21, Gary Palmer wrote:
> Smells like a routing table problem or similar configuration problem.
> On my tunnel endpoint, admitedly running 7.4 not 8.x or head, pings
> to the LOCAL endpoint of the gif0 tunnel go over lo0, not the external
> interface (gif0). I believe that
On 26 September 2011 14:29, Gary Palmer wrote:
> On Mon, Sep 26, 2011 at 10:27:53AM +0100, Matt Smith wrote:
> Do you have access to any other IPv6 hosts on a separate link? If so,
> I would suggest trying a ping or traceroute back to your IP or
> IPs across the tunnel and see if the
On 26 September 2011 12:46, Bjoern A. Zeeb
wrote:
> Given you are using NAT make sure that works as expected for the gif
> from the remote end. It might be worth, if you can, do tcpdump on
> the external interface of your router.
>
> Also make sure you can reach the IPv4 tunnel destination.
I a
f0
ff02::%gif0/32fe80::240:63ff:fee8:793e%gif0 U gif0
And here are my firewall rules to prove it's flushed:
root@tao[~]# ipfw list
65535 allow ip from any to any
Thanks for any help or suggestions, Regards Matt.
___
On 07/22/11 18:42, Adrian Chadd wrote:
When do we just give in and commit this merged code for now?
Adrian
On 19 July 2011 01:25, Matt wrote:
On 07/14/11 00:02, a...@freebsd.org wrote:
Synopsis: [ral] ral(4) needs to be resynced with OpenBSD's to gain
RT2860/2870 support.
Respon
ches (rt2860 merged with ral):
https://docs.google.com/leaf?id=0B6YlMzJxarGbMWFmZDUxMTgtOTU4ZC00MjRlLThhMTctZTE1MDcwNDJiZDIx&hl=en_US
If you have build errors, please provide output of uname -a, and copying
exact error messages if any.
Thanks,
Matt
___
x27;s appending your domain).
Did you set your local DNS server to use forwarders? Also, are all your
DNS records properly appended with a period (for instance 1.1.1.1 A
bitblocks.com.)?
Can you provide the output (on a UNIX machine) of: dig @192.168.125.9
On Thu, 28 Apr 2011 03:29:46 -0400, Adam Stylinski wrote:
Hello,
I have an intel gigabit network adapter (the 1000 GT w/chipset
82541PI) which performs poorly in Freebsd compared to the same card
in
Linux. I've tried this card in two different freebsd boxes and for
whatever reason I get poor
ess now. Thank you for this. I was about to try and apply
the patch that you posted but this does the trick.
Regards, Matt.
___
freebsd-net@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-net
To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org"
On 22 March 2011 03:00, J. Hellenthal wrote:
>
> Hi Matt,
>
> Unofficially not sure if you have already checked into this so I am not sure
> if it is really a solution to your problem but may be a step forward. Check
> out the man page for ip6addrctl(8) that allows you to se
On 15 March 2011 11:39, Matt Smith wrote:
>
> Hi, I have a question about source routing I hope you can help me with.
I have been doing some more research into this and it appears the
proper way to accomplish what I want is to set
net.inet6.ip6.use_deprecated to 0 and then deprecate th
rence.
Do you know of any simple way of doing this that works? I use ipfw as my
firewall and I'm running FreeBSD 8.2-RELEASE at the moment.
Regards, Matt.
___
freebsd-net@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-net
The following reply was made to PR kern/143939; it has been noted by GNATS.
From: Matt Reimer
To: bug-follo...@freebsd.org,
dima_...@inbox.lv
Cc:
Subject: Re: kern/143939: [ipfw] [em] ipfw nat and em interface rxcsum problem
Date: Wed, 17 Feb 2010 15:30:47 -0800
Same thing happens for me on
Box is running 8.0-RELEASE-p2 cvsupped two days ago.
NICs are em bonded with lagg failover and running a few vlan interfaces.
net.my_fibnum: 0
net.add_addr_allfibs: 1
net.fibs: 4
This is reproducible, but with the lack of (accessible?) documentation on
multiple routing tables, I don't know if th
Jeff Blank wrote:
> I wrote:
>> I've just upgraded a 7.1-REL server to 8.0-REL and have lost my
>> ability to use vlan(4) on top of lagg(4) on top of em(4).
A workaround for this is to disable hardware vlan tagging:
# ifconfig em0 -vlanhwtag
(don't forget to do all em interfaces and put it in rc
> I think I found a bug in the SCTP authentication code, in
> sctp_load_addresses_from_init() in sctp_pcb.c
I noticed the same calculation appears in
sctp_auth.c:sctp_auth_get_cookie_params(). Does this fix also need to be
applied there?
Cheers,
Matt.
-Original Message-
From: M
iated.
-Matt
___
freebsd-net@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-net
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
> Linksys WAG354G
> Ambit U10C019
> Netgear CG814GCMR
I've seen this on a Netgear CG814WG.
Matt
___
freebsd-net@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-net
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
t the problem only occurred on
> Windows (at least, the ones who had more than on OS to try it out).
...
Me too: I saw this exact problem with RELENG_7 a month or so ago, and
worked around it by disabling SACK.
Matt
___
freebsd-net@freebsd.
On Nov 10, 2007 12:13 AM, Mike Silbersack <[EMAIL PROTECTED]> wrote:
>
> On Fri, 9 Nov 2007, Matt Reimer wrote:
>
> > I first noticed this problem running ab; then to simplify I used
> > netrate/http[d]. What's strange is that it seems fine over the local
> >
On Nov 9, 2007 7:46 PM, Mike Silbersack <[EMAIL PROTECTED]> wrote:
>
> On Fri, 9 Nov 2007, Matt Reimer wrote:
>
> > On a eight core machine running RELENG_7 I'm seeing TCP stalls,
> > sometimes lasting up to 60 seconds or so. While trying to tr
er is wrongly being decremented twice?
Matt
# sysctl net.inet.tcp.syncache
net.inet.tcp.syncache.rst_on_sock_fail: 1
net.inet.tcp.syncache.rexmtlimit: 3
net.inet.tcp.syncache.hashsize: 512
net.inet.tcp.syncache.count: -97
net.inet.tcp.syncache.cachelimit: 15360
net.inet.tcp.syncache.bucketlimi
Can someone take a look at PR 89061
(http://www.freebsd.org/cgi/query-pr.cgi?pr=89061). It contains a
patch adding an /etc/rc.conf knob to autoconfigure an RFC 3068 6to4
address.
Matt
___
freebsd-net@freebsd.org mailing list
http://lists.freebsd.org
newer versions more
robust in the face of allocation failures? I thought I read once that
they were, but I would like to make sure.
Thanks in advance.
Matt
___
freebsd-net@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-net
To
ase - if the device driver
isn't loaded, then IPMI should still work ;)
- Matt
-Original Message-
From: Matt [mailto:[EMAIL PROTECTED]
Sent: Thursday, March 16, 2006 7:24 AM
To: 'Jack Vogel'; 'freebsd-net@freebsd.org'
Subject: RE: IPMI During Boot
Hello,
The hel
work (until
I reboot).
Matt Houston
Systems Administrator
Successful Hosting
[EMAIL PROTECTED]
http://www.SuccessfulHosting.com
Toll-Free: +1.866.494.5096
=
The Success behind your web site!
=
-Original Message-
From: [EMAIL PROT
s storage
subclass = SCSI
[EMAIL PROTECTED]:4:1: class=0x01 card=0x688015d9 chip=0x801d9005 rev=0x10
hdr=0x00
vendor = 'Adaptec Inc'
device = 'AIC-7902B Ultra320 SCSI Controller'
class= mass storage
subclass = SCSI
[EMAIL PROTECTED]:1:0:
rporate networks (using commercial IPSec solutions) --
or for those who don't need the double-encapsulation.
--
Matt Emmerton
___
freebsd-net@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-net
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
y searches.
I'm looking for a basic PCI 1-port card with jumbo frame support if
possible--I can live without it. Either way, stability is much more
important than performance.
Thanks in advance for your recommendations.
--
Matt Staroscik
[EMAIL PROTECTED] | http:/
IP option processing and ipfirewall(4) checking.
It is not guaranteed that every packet will be
fast-forwarded.
--
Matt Emmerton
___
freebsd-net@freebsd.org mailing list
http://lists.freebsd.org/mailma
>
> Matt,
>
> --- Matt Emmerton <[EMAIL PROTECTED]> wrote:
>
> > I'm working on it :) It's a bit hairy because of
> > the changes between 4.x
> > and 5.x, but I should have something by next week.
>
> Wow - this is really great of you. Just
can not be found anywhere on the
> Internet ? If so, it would be worth if you could submit a
> port of the older release of ntop.
I'm working on it :) It's a bit hairy because of the changes between 4.x
and 5.x, but I should have something by next week.
--
Matt Emmerton
___
> --- Matt Emmerton <[EMAIL PROTECTED]> wrote:
>
> > I'm not sure where you're looking, but
> > http://www.ntop.org definitely
> > describes a network monitoring application.
> >
> > It's stil in the ports -- you can install it like
>
ng it successfully under FreeBSD 5.x ?
I'm not sure where you're looking, but http://www.ntop.org definitely
describes a network monitoring application.
It's stil in the ports -- you can install it like this: cd
/usr/ports/net/ntop && make install
--
Matt Emmerton
Great, thank you very much for the advice and attention on this issue. I
very much appreciate it.
The short term results on these seem very good.
Thanks again.
Matthew Ruzicka - Systems Administrator
Front Range Internet, Inc.
[EMAIL PROTECTED] - (970) 212-0728
Got SPAM? Take back your email
Konovalov wrote:
> On Fri, 13 May 2005, 12:58-0600, Matt Ruzicka wrote:
>
> > Yes, it still does. And actually the script Maxim attached to his last
> > email (using our IP's) has an interesting side effect of causing the
> > connections to fail.
> >
&
2:47:35 2005 failed
Matthew Ruzicka - Systems Administrator
Front Range Internet, Inc.
[EMAIL PROTECTED] - (970) 212-0728
Got SPAM? Take back your email with MailArmory. http://www.MailArmory.com
On Fri, 13 May 2005, Mike Silbersack wrote:
>
> On Fri, 13 May 2005, Matt Ruzicka wrote:
>
Thank you both very much for all the help.
Incidentally those systems are now running 4.11 (patched today for htt).
They are primarily web servers running apache 1.3.33 with customer as well
as company cgi's running on them, but are also running proftpd.
Let me know if I can get you any system r
Hmm.. doesn't seem to have helped.
-->uptime
9:59AM up 29 mins, 2 users, load averages: 0.96, 0.92, 1.24
-->sysctl -a | grep net.inet.ip.portrange.
net.inet.ip.portrange.lowfirst: 1023
net.inet.ip.portrange.lowlast: 600
net.inet.ip.portrange.first: 1024
net.inet.ip.portrange.last: 5000
net.inet
helps either way.
Thank you for the suggestion.
Matthew Ruzicka - Systems Administrator
Front Range Internet, Inc.
[EMAIL PROTECTED] - (970) 212-0728
Got SPAM? Take back your email with MailArmory. http://www.MailArmory.com
On Thu, 12 May 2005, Mike Silbersack wrote:
>
> On Thu, 12 Ma
A couple days after we patched our systems, we started to receive a number
of reports of mysql connection errors when our patched FreeBSD 4.9 web
servers were trying to connect to our mysql server, which lives on a
separate FreeBSD machine.
Initially we thought this was a networking error related
I read the first link; but when I looked in the files, there is
no field frmhdr and the code does not flow the way the article
suggest (wi_start doesn't call that function..)
The patch looks better, I will back up the source and try and
apply it. We will see..
--
Matt Sealey <[EMAIL P
this one fix
and not anything else so I am loathe to update entire swathes
of files beyond if_wi.c :)
Thanks in advance,
--
Matt Sealey <[EMAIL PROTECTED]>
Manager, Genesi, Developer Relations
___
freebsd-net@freebsd.org mailing lis
1 - 100 of 142 matches
Mail list logo
