Re: 11.1-RELEASE from SVN

[Sydney Meyer via freebsd-stable]

Hi Glen, 

thanks for the update..

Your work (and the work of others of course) is one of the main reasons why i 
use and promote the use of FreeBSD. One of the last truly engineered Operating 
Systems.

Thank you for your work, you probably can guess it already, i truly appreciate 
it.

I'll store the fireworks till wednesday then..

Sydney

> On 23. Jul 2017, at 22:38, Glen Barber <g...@freebsd.org> wrote:
> 
> Hi Sydney,
> 
> The release date in UPDATING actually was a mistake.  (I looked at the
> wrong month...)
> 
> Glen
> 
> On Sun, Jul 23, 2017 at 10:23:43PM +0200, Sydney Meyer via freebsd-stable 
> wrote:
>> Hi Dimitry,
>> 
>> thank you for your reply.
>> 
>> Please excuse me if i came across impatiently, that was not my intention.
>> 
>> It's just that i find the way the project handles events like these, new 
>> releases, security incidents, etc. very interesting and just generally love 
>> to hear about it.
>> 
>> Glen, e.g., sent a revised RC-Announcement Mail because of a omitted PGP 
>> signature. Gotta love this attention to detail.
>> 
>> So i saw the commit with the anticipated 11.1-RELEASE date in the UPDATING 
>> file and the updated schedule on the website and thought, i just ask..
>> 
>> The (seamingly) disappeared 11.1.0-RELEASE was my mistake (old pathrev in 
>> the url on svnweb).
>> 
>> Anyhow, i am sure everybody hard at work and i'm looking forward to 
>> (another) really awesome dot-release.
>> 
>> Have a nice rest-weekend..
>> 
>> Sydney
>> 
>>> On 23. Jul 2017, at 14:53, Dimitry Andric <d...@freebsd.org> wrote:
>>> 
>>> On 23 Jul 2017, at 14:36, Sydney Meyer via freebsd-stable 
>>> <freebsd-stable@freebsd.org> wrote:
>>>> 
>>>> are there any "last-minute" issues/changes with the 11.1-RELEASE build?
>>>> 
>>>> The 11.1-RELEASE appears to be gone from SVN after the switch from 
>>>> releng/11.1 to -RELEASE and the Press Release Schedule seems to have 
>>>> changed without notice.
>>>> 
>>>> Not that this is an issue to me, as the releases aren't officially 
>>>> released until @re sends the announcment email, i'm just curious..
>>> 
>>> Don't worry, the release engineers are furiously working behind the
>>> scenes to get all the correct bits built, verified and uploaded.  This
>>> will just take a few days.  The schedule is here:
>>> 
>>> https://www.freebsd.org/releases/11.1R/schedule.html
>>> 
>>> It is also perfectly normal for stable/11 to be renamed -STABLE again,
>>> this is the usual procedure after tagging releases in releng.
>>> 
>>> -Dimitry
>>> 
>> 
>> ___
>> freebsd-stable@freebsd.org mailing list
>> https://lists.freebsd.org/mailman/listinfo/freebsd-stable
>> To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Re: 11.1-RELEASE from SVN

[Sydney Meyer via freebsd-stable]

Hi Dimitry,

thank you for your reply.

Please excuse me if i came across impatiently, that was not my intention.

It's just that i find the way the project handles events like these, new 
releases, security incidents, etc. very interesting and just generally love to 
hear about it.

Glen, e.g., sent a revised RC-Announcement Mail because of a omitted PGP 
signature. Gotta love this attention to detail.

So i saw the commit with the anticipated 11.1-RELEASE date in the UPDATING file 
and the updated schedule on the website and thought, i just ask..

The (seamingly) disappeared 11.1.0-RELEASE was my mistake (old pathrev in the 
url on svnweb).

Anyhow, i am sure everybody hard at work and i'm looking forward to (another) 
really awesome dot-release.

Have a nice rest-weekend..

Sydney

> On 23. Jul 2017, at 14:53, Dimitry Andric <d...@freebsd.org> wrote:
> 
> On 23 Jul 2017, at 14:36, Sydney Meyer via freebsd-stable 
> <freebsd-stable@freebsd.org> wrote:
>> 
>> are there any "last-minute" issues/changes with the 11.1-RELEASE build?
>> 
>> The 11.1-RELEASE appears to be gone from SVN after the switch from 
>> releng/11.1 to -RELEASE and the Press Release Schedule seems to have changed 
>> without notice.
>> 
>> Not that this is an issue to me, as the releases aren't officially released 
>> until @re sends the announcment email, i'm just curious..
> 
> Don't worry, the release engineers are furiously working behind the
> scenes to get all the correct bits built, verified and uploaded.  This
> will just take a few days.  The schedule is here:
> 
> https://www.freebsd.org/releases/11.1R/schedule.html
> 
> It is also perfectly normal for stable/11 to be renamed -STABLE again,
> this is the usual procedure after tagging releases in releng.
> 
> -Dimitry
> 

___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

11.1-RELEASE from SVN

[Sydney Meyer via freebsd-stable]

Hello @re,

are there any "last-minute" issues/changes with the 11.1-RELEASE build?

The 11.1-RELEASE appears to be gone from SVN after the switch from releng/11.1 
to -RELEASE and the Press Release Schedule seems to have changed without notice.

Not that this is an issue to me, as the releases aren't officially released 
until @re sends the announcment email, i'm just curious..

Thanks..

Sydney
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Re: VirtualBox outbound networking

[Sydney Meyer via freebsd-stable]

Yes, same here. Bridging is working as it should, including ICMP of course.

On Windows, i wouldn't even be able to manually add a route, so that one is out 
for me too:)

I found several posts about NAT-related problems with VirtualBox. I read vb is 
using "slirp" for it's NAT implementation, because of portability, which 
appears to do crazy things to ICMP messages, but, obviously, i dont know this 
for sure.

But it doesn't appear to be a problem with FreeBSD or the RC's itself, so i 
will ask around some VirtualBox users or @freebsd-virtualization..

> On 9. Jul 2017, at 02:12, Mike Karels  wrote:
> 
>> Mea Cupla, i guess.. I can confirm that both, NAT and bridged networking, 
>> are indeed working fine on 11.1-RC1 too. The "problem" appears to be "only" 
>> with ICMP and the way VirtualBox implements NAT, i.e. TCP and UDP work fine. 
>> A post from last month stated bridged networking on 11.1 BETA1 onwards 
>> wouldn't work either, that i can confirm is working fine, at least here and 
>> as far as i can see.
> 
>> Mike, can your vbox guests send ICMP messages beyond their gateway on 10.3 
>> or is this known behaviour?
> 
> Yes, I can ping beyond the default gateway.  But I realized after I set
> the last response, I am using bridging and not NAT.  Don't want to use
> Windows routing :-)!
> 
>   Mike

___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Re: VirtualBox outbound networking

[Sydney Meyer via freebsd-stable]

Mea Cupla, i guess.. I can confirm that both, NAT and bridged networking, are 
indeed working fine on 11.1-RC1 too. The "problem" appears to be "only" with 
ICMP and the way VirtualBox implements NAT, i.e. TCP and UDP work fine. A post 
from last month stated bridged networking on 11.1 BETA1 onwards wouldn't work 
either, that i can confirm is working fine, at least here and as far as i can 
see.

Mike, can your vbox guests send ICMP messages beyond their gateway on 10.3 or 
is this known behaviour?

Thanks again..

Sydney

> On 9. Jul 2017, at 00:57, Sydney Meyer  wrote:
> 
> Hi Mike,
> 
> yes, a (correct) default route is added and the guest can reach the 
> VirtualBox nat-gateway.. oddly enough, the VirtualBox DHCP server seems to 
> have passed the hosts resolv.conf and is able to dig dns responses with my 
> local-lan dns resolver, but can't ping it.
> 
> When a guest digs to my routers dns service, i can see the packets on the 
> router coming from hosts IP address, i.e. nat working, but when i try to ping 
> it the router, i can't see any packets, neither on the host nor on the remote 
> site.

___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Re: VirtualBox outbound networking

[Sydney Meyer via freebsd-stable]

Hi Mike,

yes, a (correct) default route is added and the guest can reach the VirtualBox 
nat-gateway.. oddly enough, the VirtualBox DHCP server seems to have passed the 
hosts resolv.conf and is able to dig dns responses with my local-lan dns 
resolver, but can't ping it.

When a guest digs to my routers dns service, i can see the packets on the 
router coming from hosts IP address, i.e. nat working, but when i try to ping 
it the router, i can't see any packets, neither on the host nor on the remote 
site.
   
   
> On 9. Jul 2017, at 00:33, Mike Karels  wrote:
> 
>> That is, e.g. in "NAT" mode VirtualBox' own DHCP server hands out addresses 
>> to guest, which are in turn able to ping the host but can't get outside 
>> their own networks.
> 
>> I'm sorry for not mentioning this in the first post.
> 
> Are you getting a default route from the (virtual) DHCP server?  If not,
> can you add one manually?  I can attest that the route is working with
> 10.3, but probably you have even more recent experience.
> 
>   Mike

___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Re: VirtualBox outbound networking

[Sydney Meyer via freebsd-stable]

That is, e.g. in "NAT" mode VirtualBox' own DHCP server hands out addresses to 
guest, which are in turn able to ping the host but can't get outside their own 
networks.

I'm sorry for not mentioning this in the first post.

> On 8. Jul 2017, at 20:46, Sydney Meyer  wrote:
> 
> Hello List,
> 
> i have trouble getting any form of outbound networking, i.e. "nat" or 
> "bridged" with the e1000 guest interfaces, to work with VirtualBox on 11.1 
> BETAs and RCs. I have recompiled the virtualbox-ose port from head with its 
> virtualbox-ose-kmod dependency from hand but without any luck.
> 
> Am i missing something here in context of port-provided kernel modules not 
> being compatible with the non-release kernels or something?
> 
> Sydney

___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

VirtualBox outbound networking

[Sydney Meyer via freebsd-stable]

Hello List,

i have trouble getting any form of outbound networking, i.e. "nat" or "bridged" 
with the e1000 guest interfaces, to work with VirtualBox on 11.1 BETAs and RCs. 
I have recompiled the virtualbox-ose port from head with its 
virtualbox-ose-kmod dependency from hand but without any luck.

Am i missing something here in context of port-provided kernel modules not 
being compatible with the non-release kernels or something?

Sydney
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"