On 2018-08-10, Henry Bonath wrote:
> Also could it be that you are using IPv6, not IPv4? (and your IPv6 is
> missing its gateway)
> If the IPv6 gateway is bad/missing you'll get that "no route to host"
> message.
This is for fastly.cdn.openbsd.org which is cnamed to
osff.map.fastly.net - the DNS
On 2018-08-11, Walt wrote:
> On August 10, 2018 3:57 PM, Henry Bonath he...@thebonaths.com wrote:
>
>> Also could it be that you are using IPv6, not IPv4? (and your IPv6 is
>> missing its gateway)
>> If the IPv6 gateway is bad/missing you'll get that "no route to host"
>> message.
>
> I've
On 2018-08-11, Daniel Ouellet wrote:
> Hi,
>
> I am not sure you got that right.
>
> If you are an ISP the minimum assignment is /32 and you assigned /48 to
> end company and /56 to users.
>
> If you asked me that's a wasted, but that's what they suggest.
>
> For end users, a /64 would be plenty
Sorry for the double posting.
But Just to add to the info, the RFC 3177 did specify assignment to
remote site even house being /48 and big site like /47
https://tools.ietf.org/html/rfc3177
Crazy.
The revise version of it RFC 6177 correct that crazy assignment and
specif that you should do /56.
Hi,
I am not sure you got that right.
If you are an ISP the minimum assignment is /32 and you assigned /48 to
end company and /56 to users.
If you asked me that's a wasted, but that's what they suggest.
For end users, a /64 would be plenty if you asked me and /56 for company
would be plenty as
On 8/10/18 10:38 PM, Daniel Ouellet wrote:
> Hi,
>
> I am not sure you got that right.
>
> If you are an ISP the minimum assignment is /32 and you assigned /48 to
> end company and /56 to users.
>
> If you asked me that's a wasted, but that's what they suggest.
>
> For end users, a /64
On August 10, 2018 3:57 PM, Henry Bonath he...@thebonaths.com wrote:
> Also could it be that you are using IPv6, not IPv4? (and your IPv6 is
> missing its gateway)
> If the IPv6 gateway is bad/missing you'll get that "no route to host"
> message.
I've encountered that issue before, but it isn't
Also could it be that you are using IPv6, not IPv4? (and your IPv6 is
missing its gateway)
If the IPv6 gateway is bad/missing you'll get that "no route to host"
message.
On Fri, Aug 10, 2018 at 4:31 PM, Stuart Henderson
wrote:
> On 2018-08-07, traveller wrote:
> > After OpenBSD, one too many
On 2018-08-07, traveller wrote:
> After OpenBSD, one too many “/“
That won't cause this.
> On Aug 7, 2018, 11:16 AM -0700, Benjamin Walkenhorst
> , wrote:
>> Hello everyone,
>>
>> I recently installed OpenBSD 6.3 in a VPS.
>>
>> In the last few days, I get an error message when running
On 08/07/18 13:18, traveller wrote:
After OpenBSD, one too many “/“
I concur.
cat /etc/installurl
https://fastly.cdn.openbsd.org/pub/OpenBSD
You probably did the ole copy/paste from somewhere and got a trailing '/'.
On Aug 7, 2018, 11:16 AM -0700, Benjamin Walkenhorst
, wrote:
Hello
After OpenBSD, one too many “/“
On Aug 7, 2018, 11:16 AM -0700, Benjamin Walkenhorst
, wrote:
> Hello everyone,
>
> I recently installed OpenBSD 6.3 in a VPS.
>
> In the last few days, I get an error message when running pkg_add, "no route
> to host".
> I have tried setting various hosts in
вт, 7 авг. 2018 г., 21:16 Benjamin Walkenhorst <
walkenhorst.benja...@gmail.com>:
> Hello everyone,
>
> I recently installed OpenBSD 6.3 in a VPS.
>
> In the last few days, I get an error message when running pkg_add, "no
> route to host".
> I have tried setting various hosts in /etc/installurl,
12 matches
Mail list logo
