On Wed, Dec 07, 2016 at 05:39:22PM +0100, J?r?me FRGACIC wrote:
> Hello tech,
>
> While reading disklabel(8) man page I remark that the two possibles
> units '%' (percent of total) and '&' (percent of free) are only
> mentioned in the description of the 'p' option but not in the section
> which li
This diff makes dhcrelay(8) drop packets that were not meant for us.
This is a safety check suggested by jca@ to avoid relaying packets with
the address of other relays.
ok?
Index: dhcrelay.c
===
RCS file: /cvs/src/usr.sbin/dhcrelay/
That will add an extra newline in the proxy case where it does:
fprintf(ttyout, "Requesting %s", origline);
...
fprintf(ttyout, " (via %s)\n", proxyurl);
There is actually a newline printed for the non-proxy case but it
happens too late.
We either need to avoid printing
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 customer.
Basically this diff allows you to run dhcrelay on interfaces wi
I noticed that Jiri's ftp debug output had two instances where NULL
was printed as a string. This fixes it.
$ ftp -o /dev/null -M -d -V
http://ftp.eu.openbsd.org/pub/OpenBSD/snapshots/amd64/
Before:
host ftp.eu.openbsd.org, port (null), path pub/OpenBSD/snapshots/amd64/, save
as /dev/null, aut
Rafael Zalamena writes:
> On Thu, Dec 08, 2016 at 06:59:18PM +0100, Jeremie Courreges-Anglas wrote:
>> Rafael Zalamena writes:
>>
>> [...]
>>
>> >> Another problem: the relay->server code uses send(2) on a connected
>> >> socket and thus has no destination IP issue. But the relay->client path
On Thu, Dec 08, 2016 at 06:59:18PM +0100, Jeremie Courreges-Anglas wrote:
> Rafael Zalamena writes:
>
> [...]
>
> >> Another problem: the relay->server code uses send(2) on a connected
> >> socket and thus has no destination IP issue. But the relay->client path
> >> now uses the source address
See 'GET /url...' location in the output in the first example:
j.
$ ftp -o /dev/null -M -d http://ftp.eu.openbsd.org/pub/OpenBSD/snapshots/amd64/
host ftp.eu.openbsd.org, port (null), path pub/OpenBSD/snapshots/amd64/, save
as /dev/null, auth (null).
Trying 77.238.36.16...
Requesting http://ftp.
Rafael Zalamena writes:
[...]
>> Another problem: the relay->server code uses send(2) on a connected
>> socket and thus has no destination IP issue. But the relay->client path
>> now uses the source address from the server->relay packet. I think
>> we should keep using interfaces->primary_addr
On Thu, Dec 08, 2016 at 05:07:41PM +0100, Jeremie Courreges-Anglas wrote:
> ---sniped---
> I think you've summoned Cthulhu with this diff. :)
>
> I started noticing a wrong behavior with when testing a multi-relay
> setup, as prompted by Patrick's diff. See
>
> marc.info/?l=openbsd-tech&m=14809
On Thu, Nov 17, 2016 at 02:58:21PM +0100, Stefan Sperling wrote:
> This change allows iwm(4) users to see which rates they're sending and
> receiving packets at (kinda useful for debugging rate scaling issues).
This is a follow-up fix to the diff quoted below (since committed).
Don't strip bits w
Rafael Zalamena writes:
> On Wed, Dec 07, 2016 at 09:36:24PM +0100, Jeremie Courreges-Anglas wrote:
>> Rafael Zalamena writes:
>>
>> > I'm implementing some features for dhcrelay and to make them fit I need
>> > some clean ups in the dhcrelay(8) first. This diff changes most of the
>> > input/o
Hi,
We are doing some regression and performance testing with OpenBSD
-currrent. The daily results are published on this web site.
http://bluhm.genua.de/
bluhm
On Thu, Dec 08, 2016 at 01:16:43PM +, Stuart Henderson wrote:
> On 2016/12/08 09:42, Landry Breuil wrote:
> > Hi,
> >
> > i know this is in the examples section of syslog.conf(5), but i got
> > bitten by this again, so what do ppl thing about adding those 3 lines to
> > the default syslog.conf
Hi all,
i have this supermicro box:
https://www.supermicro.nl/products/motherboard/Xeon/D/X10SDV-TP8F.cfm
dmesg without this patch shows :
vendor "Intel", unknown product 0x6f34 (class DASP subclass Time and
Frequency, rev 0x03) at pci12 dev 16 function 1 not configured
with this patch:
"Intel
On 2016/12/08 09:42, Landry Breuil wrote:
> Hi,
>
> i know this is in the examples section of syslog.conf(5), but i got
> bitten by this again, so what do ppl thing about adding those 3 lines to
> the default syslog.conf ?
>
> wont push for this, was just taunted by someone "i would OK a diff to
On Wed, Dec 07, 2016 at 09:36:24PM +0100, Jeremie Courreges-Anglas wrote:
> Rafael Zalamena writes:
>
> > I'm implementing some features for dhcrelay and to make them fit I need
> > some clean ups in the dhcrelay(8) first. This diff changes most of the
> > input/output functions prototypes to tak
Hi,
i know this is in the examples section of syslog.conf(5), but i got
bitten by this again, so what do ppl thing about adding those 3 lines to
the default syslog.conf ?
wont push for this, was just taunted by someone "i would OK a diff to
add an example to the default syslog.conf" :)
Landry
I
18 matches
Mail list logo
