Hey Sebastian and Patrik,
Thanks for the replies and sorry for the vagueness. Should have been
sleeping rather than upgrading/posting. By some minor miracle, a
reboot after sysmerge was done too :)
Started using unbound from ports on 5.4-stable last winter and once it
was working really haven't m
On 2014-07-23 20:30, Gordon Turner wrote:
Hey all,
Based on the feedback from Daniel and others, I have successfully
connected to my OpenBSD instance running behind my router / firewall
from an iOS and OSX client on the Internet. (Updated instructions
below.)
The one issue that I have is that
On Saturday 26 July 2014 17:38:06 Fung wrote:
> http://www.openbsd.org/faq/faq4.html#Morefdisk
>
> uh-oh! What's our offset? Simple -- the offset of the previous partition
> plus the size of the partition, in this case, 63+10490382 = 10490445.
>
> offset: [0] 10490445
> size: [0] *
> fdisk:*1>
>
On Saturday, July 26, 2014 17:35 CEST, Sonic wrote:
> On Sat, Jul 26, 2014 at 11:21 AM, Sonic wrote:
> > If you're just using a /24 as your access-control seems to indicate
> > try replacing the above with (this works great for me):
> > local-zone: "0.0.10.in-addr.arpa." transparent
> >
> > an
On 07/26/14 07:40, Edward wrote:
> Hi,
>
> While browsing for mg editor tutorial[1] from www.openbsd.org, stumble
> on broken link to it in FAQ 8. A random check on cvsweb related target
> link, is broken as well. Below is a patch for fixing all the links in
> faq8.html.
>
> If this looks good,
On Sat, Jul 26, 2014 at 11:21 AM, Sonic wrote:
> If you're just using a /24 as your access-control seems to indicate
> try replacing the above with (this works great for me):
> local-zone: "0.0.10.in-addr.arpa." transparent
>
> and update the stub-zone name to read:
> name: "0.0.10.in-addr.arpa."
On Sat, May 17, 2014 at 2:04 PM, Sebastian Reitenbach
wrote:
> local-zone: "10.in-addr.arpa." nodefault
If you're just using a /24 as your access-control seems to indicate
try replacing the above with (this works great for me):
local-zone: "0.0.10.in-addr.arpa." transparent
and update the stub-z
On Sat, Jul 26, 2014 at 07:41:18PM +0800, Edward wrote:
> Hi,
>
> While browsing for mg editor tutorial[1] from www.openbsd.org, stumble
> on broken link to it in FAQ 8. A random check on cvsweb related target
> link, is broken as well. Below is a patch for fixing all the links in
> faq8.html.
>
hmm, on Fri, Jul 25, 2014 at 02:11:00PM -0400, Mike Burns said that
> > Anybody know of any small laptops (not necessarily chromebooks) that run
> > OpenBSD well?
>
> Thinkpad X1 Carbon. -current works well: wifi, keyboard, mouse,
> touchscreen, suspend, resume, USB, headphones. See my recent thre
Hi,
While browsing for mg editor tutorial[1] from www.openbsd.org, stumble
on broken link to it in FAQ 8. A random check on cvsweb related target
link, is broken as well. Below is a patch for fixing all the links in
faq8.html.
If this looks good, I'll send in more patch (particularly on FAQ 5,9,
Following up on this thread given the mention it got in the recent
unbound question:
On Sat, May 17, 2014 at 08:04:32PM +0200, Sebastian Reitenbach wrote:
>
> # the stub zones I want to resolve via nsd on localhost
> stub-zone:
> name: "ds9"
> stub-addr: 127.0.0.1@5353
>
> stub-z
On Sat, Jul 26, 2014 at 04:04:32AM -0400, Todd Zimmermann wrote:
> Have name resolution failure after an upgrade ( rebooting into the the
> new system) on my crusty i386 server. A # kill -9 'unbound pid' plus
> starting unbound from rc.d after and everything is fine. Might have
> been going on for
http://www.openbsd.org/faq/faq4.html#Morefdisk
uh-oh! What's our offset? Simple -- the offset of the previous partition plus
the size of the partition, in this case, 63+10490382 = 10490445.
offset: [0] 10490445
size: [0] *
fdisk:*1>
in this situation, default offset = 0 ?? may this fuction cha
On Saturday, July 26, 2014 10:04 CEST, Todd Zimmermann
wrote:
> Have name resolution failure after an upgrade ( rebooting into the the
> new system) on my crusty i386 server. A # kill -9 'unbound pid' plus
> starting unbound from rc.d after and everything is fine. Might have
> been going on fo
Have name resolution failure after an upgrade ( rebooting into the the
new system) on my crusty i386 server. A # kill -9 'unbound pid' plus
starting unbound from rc.d after and everything is fine. Might have
been going on for awhile, but usually it works itself out.
-- Z
15 matches
Mail list logo
