--- Original message ---
From: "Eugene Grosbein" <eu...@grosbein.net>
Date: 3 July 2019, 10:48:51

03.07.2019 14:28, wishmaster пишет:
> 
>   
> 
> --- Original message ---
> From: "Eugene Grosbein" <eu...@grosbein.net>
> Date: 3 July 2019, 10:16:31
> 
> 03.07.2019 14:08, wishmaster wrote:
> 
>>
>> Hi,
>>
>> the office's server has 6 jails and 2 bhyve virtual servers.
>> The problem is when I restart server, jails start for a long time (about 6 
>> minutes). All this time the server does not acts as router, that is no 
>> packets between interfaces. From within the server packets are transmitted 
>> and received (ping works correctly), but from LAN - no.
>>
>> I do not remember either this issue has appeared after upgrading to 12.0 or 
>> switching from STABLE to RELEASE branch, but this issue has been appearing 
>> for about half of year or little more.
>>
>> Toggle sysctl net.inet.ip.forwarding while jails are starting don't help.
>>
>> root@e-server: uname -a
>> FreeBSD e-server 12.0-RELEASE-p3 FreeBSD 12.0-RELEASE-p3 GENERIC  amd64
>>
>> jail_enable="YES"
>> jail_parallel_start="NO"
>> jail_list="basejail jdb jphp jwww jmail jdns"
>> jail_reverse_stop="YES"
>> Any advices?
> 
> Does your LAN use NAT service of the router and/or its DNS resolver?
> You should uncomment /var/log/console.log in the /etc/syslog.conf,
> create this file and reboot then read the file carefully and check whether
> you NAT/DNS services start before jails.
> 
> Logging to the console log file is already enabled.
> I check Internet connection w/o DNS services.
> 
> Some logs...

[skip] 

> Jul  3 07:57:04 e-server kernel: Jul  3 07:57:04 e-server kernel: 
> ng_ether_ifnet_arrival_event: can't re-name node epair8b
> Jul  3 07:57:27 e-server kernel:  jphp

If you use ethernet bridging for jails and real NIC, make sure you do NOT 
assign any IP addresses
to bridge members. Instead, assign all IP addresses to the bridge itself as 
aliases
and make sure you bring the bridge and real nic UP before start of jails.


I do not use any bridging on this server, just 192.168.254 subnet for jails. 
Again, all worked fine until I had upgraded or switched to RELEASE. Upgrading 
and switching was almost in one time, therefore I don't know what was the 
reason.




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

Reply via email to