On Mon, May 22, 2017 at 03:50:27PM +1000, Jonathan Gray wrote:
>
> On Mon, May 22, 2017 at 01:13:34PM +0800, Kevin Lo wrote:
> > Hi,
> >
> > The diff below adds D-Link DWA-525 rev A2 to ral(4) which works fine on
> > amd64
> > and update ral(4) manpage.
>
> This could also add other missing ids
Hello again,
Tim Stewart writes:
> Tim Stewart writes:
>
>> This patch teaches iked to reject a KE with a Notify payload of type
>> INVALID_KE_PAYLOAD when the KE uses a different Diffie-Hellman group
>> than is configured locally. The rejection indicates the desired
>> group.
>>
>> In my envi
On Mon, May 22, 2017 at 01:13:34PM +0800, Kevin Lo wrote:
> Hi,
>
> The diff below adds D-Link DWA-525 rev A2 to ral(4) which works fine on amd64
> and update ral(4) manpage.
This could also add other missing ids.
RALINK
0x3390 (RT33XX)
0x359f (RT35XX)
0x5362 (RT53XX)
EDIMAX
0x7711 (RT35XX)
0x7
Tim Stewart writes:
> This patch teaches iked to reject a KE with a Notify payload of type
> INVALID_KE_PAYLOAD when the KE uses a different Diffie-Hellman group
> than is configured locally. The rejection indicates the desired
> group.
>
> In my environment, this patch allows stock strongSwan
Hi,
The diff below adds D-Link DWA-525 rev A2 to ral(4) which works fine on amd64
and update ral(4) manpage.
# dmesg |grep ral0
ral0 at pci3 dev 1 function 0 "Ralink RT5360" rev 0x00: apic 2 int 16, address
f8:e9:03:ae:08:c4
ral0: MAC/BBP RT5392 (rev 0x0223), RF RT5360 (MIMO 1T1R)
# ifconfig ra
On 05/21/17 15:12, Edgar Pettijohn wrote:
On 05/21/17 14:53, Edgar Pettijohn wrote:
This may not be the best way to handle this, but it was the first fix
to come to mind. Not sure where to put this in the manual or if its
even worth documenting. Thoughts?
Thanks,
Edgar
Well it worked w
On 05/21/17 14:53, Edgar Pettijohn wrote:
This may not be the best way to handle this, but it was the first fix
to come to mind. Not sure where to put this in the manual or if its
even worth documenting. Thoughts?
Thanks,
Edgar
Well it worked when invoked as /usr/src/usr.sbin/bind/bin/dig
This may not be the best way to handle this, but it was the first fix to
come to mind. Not sure where to put this in the manual or if its even
worth documenting. Thoughts?
Thanks,
Edgar
Index: dig.c
===
RCS file: /cvs/src/usr.sb
Hi,
bgpd.conf manual has an example with :
good="{ 192.168.0.0/16, 172.16.0.0/12, 10.0.0.0/8 }"
bad="{ 224.0.0.0/4 prefixlen >= 4, 240.0.0.0/4 prefixlen >= 4 }"
ugly="{ 127.0.0.1/8, 169.254.0.0/16 }"
deny from any prefix { $good $bad $ugly }
This syntax is not valid with current parse.y.
Here
On Mon, May 15, 2017 at 20:13 +0200, Mike Belopuhov wrote:
> Here are some bits to display flow queues alongside H-FSC ones.
> It's a bit hackish in a way I switch the "bandwidth" field to
> the "bandwidth or flows" and then use node->qstats.data.period
> because I'm too lazy to change the pfctl_qu
While switching init and reboot to CPU_LIDACTION, I forgot about the
#ifdef's. Ok?
natano
Index: init/init.c
===
RCS file: /cvs/src/sbin/init/init.c,v
retrieving revision 1.64
diff -u -p -r1.64 init.c
--- init/init.c 3 May 2017 09:5
On Thu, May 11, 2017 at 01:11:16PM +0200, David Coppa wrote:
>
> I think this comment was copy-pasted as is from the comment some
> lines below, but this is about hibernation, not sleep.
sleep != suspend
Suspend and hibernate both are sleep states.
>
> Ok?
>
> Index: acpibtn.c
>
12 matches
Mail list logo