On Sat, Dec 10, 2016 at 12:32:56AM +0100, Patrick Wildt wrote:
> Hi,
>
> I have an IPsec setup that uses IPv6 with IPsec udpencap. In udpencap
> the "next protocol" field is set to UDP. After decapsulation that
> field is set to "IPIP". Unfortunately the udp decapsulation always
> uses the
On Sat, Dec 10, 2016 at 12:32:56AM +0100, Patrick Wildt wrote:
> Hi,
>
> I have an IPsec setup that uses IPv6 with IPsec udpencap. In udpencap
> the "next protocol" field is set to UDP. After decapsulation that
> field is set to "IPIP". Unfortunately the udp decapsulation always
> uses the
Hi,
I have an IPsec setup that uses IPv6 with IPsec udpencap. In udpencap
the "next protocol" field is set to UDP. After decapsulation that
field is set to "IPIP". Unfortunately the udp decapsulation always
uses the IPv4 offset of "next protocol". This means the other layers
will write "IPIP"
On Fri, Dec 09, 2016 at 10:08:09AM +0100, Rafael Zalamena wrote:
> On Thu, Dec 08, 2016 at 08:43:20PM +0100, Rafael Zalamena wrote:
> > This diff implements layer 2 relaying support for dhcrelay with further
> > support for Relay Agent Info (RFC 3046). This feature is mostly used by
> > switched
On Fri, Dec 09, 2016 at 09:10:42AM -0800, Chris Cappuccio wrote:
> So would you be able to share your framework for automating the
> testing and/or creating the web page ?
The framework for the regression tests is on github. For most tests
you need one machine to control everything and one
> From owner-tech+M54722=martin=martinbrandenburg@openbsd.org Fri Dec 9
> 13:42:59 2016
> From: Erik Lax
> Subject: Proxy ARP and npppd (tun)
> To: tech@openbsd.org
> Date: Fri, 9 Dec 2016 19:42:46 +0100
>
> Hi,
>
> In previous OpenBSD versions (5.9 and eariler) it was
Hi,
In previous OpenBSD versions (5.9 and eariler) it was possible to do
proxy-arp with the npppd server if the proxy-arp was setup before the
npppd connection was made. As of 6.0 (and todays snapshots) proxy arp
and npppd (tun interfaces) seems to be broken.
The behavior is now as such;
- if
I have noticed that mira will choose rates which result in a substantial
number of Tx retries, almost 50% or so even for normal 64 byte ping packets.
The diff below makes retry-heavy rates less attractive which makes the
number of retried frames shrink significantly.
The highest rate shown by
Setting the HT_PROT flag in the MAC context command forces all data frames
to be preceded by an RTS frame. There's not much wrong with RTS expect that
it slows our transmit speed down, so we should not enable it unnecessarily.
Because we do not support 40 MHz channels yet we do not need to enable
On Fri, Dec 09, 2016 at 09:53:39AM +0100, Michal Mazurek wrote:
> It might be worth explaining how to load firmware during a fresh
> install, and warn about the dangers of mounting over /mnt. This
> functionality was introduced in 4.4.
>
> While getting online for an install is not really
On Thu, Dec 08, 2016 at 08:43:20PM +0100, Rafael Zalamena wrote:
> This diff implements layer 2 relaying support for dhcrelay with further
> support for Relay Agent Info (RFC 3046). This feature is mostly used by
> switched networks that might not be using IP addresses when in the edge
> with the
It might be worth explaining how to load firmware during a fresh
install, and warn about the dangers of mounting over /mnt. This
functionality was introduced in 4.4.
While getting online for an install is not really necessary, I like to
download my sets from the internet.
Index: faq/faq4.html
12 matches
Mail list logo