On Tue, Oct 19, 2010 Bernhard Schmidt wrote:
> Alexey Dokuchaev wrote:
> > Not sure if this is a driver or ifconfig(8) problem, but after I -mediaopt
> > monitor, ifconfig(8) still reports it in media line:
> >
> > media: IEEE 802.11 Wireless Ethernet autoselect
> >
> > However, as I said, sc
I got 2 servers with CARP enabled. One is MASTER, second - BACKUP.
CARP is for HA of running some service on that servers.
All works fine, but today I've got interesting case:
Service was not responding for 5 minutes. Can't tell more details
because it was said by not IT guy.
Okay, I went to chec
Hi,
On 19/10/2010 22:06, Julian Elischer wrote:
> Wireshark understands all the protocols in question so get packet
> captures of good and
> bad sessions (as similar as you can) and see what is different.
> (wireshark reads
> tcpdump files so it's easy to capture).
As is often the case, the packe
On 10/20/10 7:23 AM, Paul Thornton wrote:
Hi,
On 19/10/2010 22:06, Julian Elischer wrote:
Wireshark understands all the protocols in question so get packet
captures of good and
bad sessions (as similar as you can) and see what is different.
(wireshark reads
tcpdump files so it's easy to capture
On Wed, 20 Oct 2010, Paul Thornton wrote:
[..]
> With a Windows XP client (I know, it was nearby though) the following
> things happen:
>
> Server -> Client PPP CHAP Success (Welcome!! message).
> Server -> Client PPP CCP config request
> Server -> Client IPCP Config request (setting IP
have you tried pap instead of chap on Cisco dialer?
On 10/20/10, Ian Smith wrote:
> On Wed, 20 Oct 2010, Paul Thornton wrote:
>
> [..]
>
> > With a Windows XP client (I know, it was nearby though) the following
> > things happen:
> >
> > Server -> Client PPP CHAP Success (Welcome!! message).
2010/10/20 Alexey Dokuchaev :
> On Tue, Oct 19, 2010 Bernhard Schmidt wrote:
>> Alexey Dokuchaev wrote:
>> > Not sure if this is a driver or ifconfig(8) problem, but after I -mediaopt
>> > monitor, ifconfig(8) still reports it in media line:
>> >
>> > media: IEEE 802.11 Wireless Ethernet autos
9, 2010 at 23:53, Paul B Mahol wrote:
> Hi,
>
> First: we should pin curthread on CPU before we check on which CPU is
> curthread.
>
> Second: instead of sti & cli use critical sections when saving %fs register.
>
> Third: I do not know what happens if we get preempted while windows
> code were r
On 10/20/10, Bernhard Schmidt wrote:
> 9, 2010 at 23:53, Paul B Mahol wrote:
>> Hi,
>>
>> First: we should pin curthread on CPU before we check on which CPU is
>> curthread.
>>
>> Second: instead of sti & cli use critical sections when saving %fs
>> register.
>>
>> Third: I do not know what happe
I had occasion to think about this, and I was wondering if someone is
working to add
either or both of these features, Intel's hardware supports it, it does not
seem that
hard to add, or am I missing something?
Cheers,
Jack
___
freebsd-net@freebsd.org m
On Wed, 20 Oct 2010, Jack Vogel wrote:
Hi,
I had occasion to think about this, and I was wondering if someone is
working to add
either or both of these features, Intel's hardware supports it, it does not
seem that
hard to add, or am I missing something?
Strange that I had been thinking of tha
Looked to me like Michael already has the SCTP stuff in the inet6 code.
Not sure if it needs further enabling or what??
I'm not positive about what cards are in the netperf cluster. Any card
that em, igb, and ixgbe supports can do the TCP/UDP checksum
offloads whether in IPv4 or 6 if handed to it.
12 matches
Mail list logo