Re: Routing stops working when we create a new vlan
On 07.08.2015 01:57, Marcelo Gondim wrote: For all work again I need to restart the router. I don't know if I could correctly explain the problem. Do you have gateway_enable=YES in your /etc/rc.conf? -- WBR, Andrey V. Elsukov signature.asc Description: OpenPGP digital signature
Re: Routing stops working when we create a new vlan
On 08/06/2015 22:09, Marcelo Gondim wrote: PR: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=202144 The output of ifconfig and netstat -nr -f inet, before and after you create the new vlan, would be most helpful. Eric Hi Eric, I put the information you requested in PR. Wow, the only difference in the output is the new vlan interface. This is odd. I'm afraid I have no ideas off-hand, and I don't have enough spare cycles to dive in. Best of luck. Eric ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
FreeBSD 10.2-RC3 Now Available
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 The third RC build of the 10.2-RELEASE release cycle is now available. This is expected to be the final RC build of this release cycle. Installation images are available for: o amd64 GENERIC o i386 GENERIC o ia64 GENERIC o powerpc GENERIC o powerpc64 GENERIC64 o sparc64 GENERIC The image checksums follow at the end of this email. FreeBSD/arm SD card images are available for: o BEAGLEBONE o CUBOX-HUMMINGBOARD o GUMSTIX o RPI-B o PANDABOARD o WANDBOARD Note: For convenience for those without console access to supported arm devices, a default 'freebsd' user exists for ssh(1) login. The password is 'freebsd', which it is strongly recommended to change after gaining access to the system. Additionally, the 'root' user password is 'root', which is also recommended to change. All images can be downloaded from: ftp://ftp.freebsd.org/pub/FreeBSD/releases/ISO-IMAGES/10.2/ If you notice problems, please report them through the Bugzilla PR system. If you would like to use SVN to do a source based update of an existing system, use the releng/10.2 branch. A list of changes since 10.1-RELEASE are available in the release notes: https://www.freebsd.org/releases/10.2R/relnotes.html === Changes Since 10.2-RC2 === o An issue with mlock(2) and truncation of file backing the wired regions was fixed. o An error that would cause bsdinstall(8) to improperly validate the checksums of remote distribution sets has been corrected. o The pms(4) driver has been updated to prevent attaching to invalid devices, which would lead to a system panic on boot. o An error resulting in the kern.racct.enable tunable not taking effect has been corrected. o A patch(1) shell vulnerability has been fixed. [FreeBSD-SA-15:18] o A routed(8) remote denial of service vulnerability has been fixed. [FreeBSD-SA-15:19] o A segmentation fault in pw(8) when changing the UID of a user has been fixed. === Virtual Machine Disk Images === VM disk images are available for the amd64 and i386 architectures. Disk images may be downloaded from the following URL (or any of the FreeBSD FTP mirrors): ftp://ftp.freebsd.org/pub/FreeBSD/releases/VM-IMAGES/10.2-RC3/ The partition layout is: ~ 512k - freebsd-boot GPT partition type (bootfs GPT label) ~ 1GB - freebsd-swap GPT partition type (swapfs GPT label) ~ ~17GB - freebsd-ufs GPT partition type (rootfs GPT label) The disk images are available in QCOW2, VHD, VMDK, and raw disk image formats. The image download size is approximately 135 MB, which decompress to a 20GB sparse image. Note to consumers of the dvd1.iso image: The bsdconfig(8) utility cannot install the packages included on the DVD, however they can be installed manually. To install packages from the dvd1.iso image, create and mount the /dist directory: # mkdir -p /dist # mount -t cd9660 /dev/cd0 /dist Replace '/dev/cd0' with the appropriate cd(4) device as necessary. Next, bootstrap pkg(8) from the DVD: # env REPOS_DIR=/dist/packages/repos \ pkg bootstrap At this point, pkg-install(8) can be used to install additional packages from the DVD. Please note, the REPOS_DIR environment variable should be used each time using the DVD as the package repository, otherwise conflicts with packages from the upstream mirrors may occur when they are fetched. For example, to install Gnome and Xorg, run: # env REPOS_DIR=/dist/packages/repos \ pkg install xorg-server xorg gnome3 [...] === Amazon EC2 AMI Images === FreeBSD/amd64 EC2 AMIs are available in the following regions: us-east-1 region: ami-63aa0608 us-west-1 region: ami-4f1ce30b us-west-2 region: ami-5d58536d sa-east-1 region: ami-8d4cc590 eu-west-1 region: ami-2ebaea59 eu-central-1 region: ami-baa5a1a7 ap-northeast-1 region: ami-ca50eeca ap-southeast-1 region: ami-c2606f90 ap-southeast-2 region: ami-810546bb === Azure / VM Depot Images === FreeBSD/amd64 images are available for use within the Microsoft Azure hosting platform through VM Depot. For deployment instructions, see: https://vmdepot.msopentech.com/Vhd/Show?vhdId=56718version=60115 === Google Compute Engine Images === FreeBSD/amd64 images are available on Google Compute Engine, and can be deployed with the gcloud utility by running: % gcloud compute instances create INSTANCE_NAME --image \ freebsd-10-2-rc3-amd64 --image-project=freebsd-org-cloud-dev % gcloud compute ssh INSTANCE_NAME === Vagrant Images === FreeBSD/amd64 images are available on the Hashicorp Atlas site for the VMWare Desktop and VirtualBox providers, and can be deployed by running: % vagrant init freebsd/FreeBSD-10.2-RC3 % vagrant up === Upgrading === The freebsd-update(8) utility supports binary upgrades of amd64 and i386 systems running earlier FreeBSD releases. Systems running earlier FreeBSD releases can upgrade as follows: # freebsd-update upgrade -r
FreeBSD_STABLE_9-i386 - Build #125 - Fixed
FreeBSD_STABLE_9-i386 - Build #125 - Fixed: Build information: https://jenkins.FreeBSD.org/job/FreeBSD_STABLE_9-i386/125/ Full change log: https://jenkins.FreeBSD.org/job/FreeBSD_STABLE_9-i386/125/changes Full build log: https://jenkins.FreeBSD.org/job/FreeBSD_STABLE_9-i386/125/console Change summaries: No changes ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: Routing stops working when we create a new vlan
On Fri, Aug 7, 2015 at 4:29 PM, Marcelo Gondim gon...@bsdinfo.com.br wrote: On 07-08-2015 10:16, Andrey V. Elsukov wrote: On 07.08.2015 01:57, Marcelo Gondim wrote: For all work again I need to restart the router. I don't know if I could correctly explain the problem. Do you have gateway_enable=YES in your /etc/rc.conf? I have net.inet.ip.forwarding=1 but when I create a new vlan, the system is changing to: net.inet.ip.forwarding=0. Why? I try to go back to the value 1 and the system does not return to work. Only back to work if I restart the system. []'s Gondim The change to 0 is probably due to not having gateway_enable=YES in rc.conf Best regards Andreas ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: Routing stops working when we create a new vlan
On Fri, Aug 07, 2015 at 05:33:51PM +0300, Andrey V. Elsukov wrote: On 07.08.2015 17:29, Marcelo Gondim wrote: On 07-08-2015 10:16, Andrey V. Elsukov wrote: On 07.08.2015 01:57, Marcelo Gondim wrote: For all work again I need to restart the router. I don't know if I could correctly explain the problem. Do you have gateway_enable=YES in your /etc/rc.conf? I have net.inet.ip.forwarding=1 but when I create a new vlan, the system is changing to: net.inet.ip.forwarding=0. Why? AFAIR, devd starts some scripts and if you don't have gateway_enable=YES net.inet.ip.forwarding will be reset to zero. And since devd doesn't restart sysctl.conf you lose your gateway. I think this is incorrect behavior. The right way to configure router - use gateway_enable=YES in rc.conf. Changing gateway_enable in rc.conf don't have immediatly effect. Changing gateway_enable and plug interface do unexpectedly effect. Why forwarding controlling not only by /etc/rc.d/routing but also by /etc/rc.d/netif? ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: Routing stops working when we create a new vlan
On 07-08-2015 11:33, Andrey V. Elsukov wrote: On 07.08.2015 17:29, Marcelo Gondim wrote: On 07-08-2015 10:16, Andrey V. Elsukov wrote: On 07.08.2015 01:57, Marcelo Gondim wrote: For all work again I need to restart the router. I don't know if I could correctly explain the problem. Do you have gateway_enable=YES in your /etc/rc.conf? I have net.inet.ip.forwarding=1 but when I create a new vlan, the system is changing to: net.inet.ip.forwarding=0. Why? AFAIR, devd starts some scripts and if you don't have gateway_enable=YES net.inet.ip.forwarding will be reset to zero. And since devd doesn't restart sysctl.conf you lose your gateway. The right way to configure router - use gateway_enable=YES in rc.conf. I try to go back to the value 1 and the system does not return to work. Only back to work if I restart the system. This seems strange, are you sure? Problem solved using gateway_enable = YES in /etc/rc.conf. But I still think it does wrong. Why to create a vlan I need to have this parameter configured in rc.conf? Or why it needs to change net.inet.ip.forwarding? []'s Gondim ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: Routing stops working when we create a new vlan
On 07-08-2015 10:16, Andrey V. Elsukov wrote: On 07.08.2015 01:57, Marcelo Gondim wrote: For all work again I need to restart the router. I don't know if I could correctly explain the problem. Do you have gateway_enable=YES in your /etc/rc.conf? I have net.inet.ip.forwarding=1 but when I create a new vlan, the system is changing to: net.inet.ip.forwarding=0. Why? I try to go back to the value 1 and the system does not return to work. Only back to work if I restart the system. []'s Gondim ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: Routing stops working when we create a new vlan
On 07.08.2015 17:29, Marcelo Gondim wrote: On 07-08-2015 10:16, Andrey V. Elsukov wrote: On 07.08.2015 01:57, Marcelo Gondim wrote: For all work again I need to restart the router. I don't know if I could correctly explain the problem. Do you have gateway_enable=YES in your /etc/rc.conf? I have net.inet.ip.forwarding=1 but when I create a new vlan, the system is changing to: net.inet.ip.forwarding=0. Why? AFAIR, devd starts some scripts and if you don't have gateway_enable=YES net.inet.ip.forwarding will be reset to zero. And since devd doesn't restart sysctl.conf you lose your gateway. The right way to configure router - use gateway_enable=YES in rc.conf. I try to go back to the value 1 and the system does not return to work. Only back to work if I restart the system. This seems strange, are you sure? -- WBR, Andrey V. Elsukov signature.asc Description: OpenPGP digital signature
Re: Routing stops working when we create a new vlan
On Fri, Aug 7, 2015 at 9:54 AM, Marcelo Gondim gon...@bsdinfo.com.br
wrote:
But I still think it does wrong. Why to create a vlan I need to have this
parameter configured in rc.conf? Or why it needs to change
net.inet.ip.forwarding?
Because that is what the directions for configuring a default gateway
state, and the directions are based off of code behavior.
/etc/rc.d/routing:
if checkyesno gateway_enable; then
ropts_init inet
echo -n ' gateway=YES'
${SYSCTL} net.inet.ip.forwarding=1 /dev/null
else
${SYSCTL} net.inet.ip.forwarding=0 /dev/null
fi
--
Adam
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: Routing stops working when we create a new vlan
On 8/7/2015 10:29 AM, Marcelo Gondim wrote: On 07-08-2015 10:16, Andrey V. Elsukov wrote: On 07.08.2015 01:57, Marcelo Gondim wrote: For all work again I need to restart the router. I don't know if I could correctly explain the problem. Do you have gateway_enable=YES in your /etc/rc.conf? I have net.inet.ip.forwarding=1 but when I create a new vlan, the system is changing to: net.inet.ip.forwarding=0. Why? I try to go back to the value 1 and the system does not return to work. Only back to work if I restart the system. devd. As suggested, have gateway_enable=YES in rc.conf so interface creations dont mess that up. I am not sure why devd wants/needs to do this, but it does. ---Mike -- --- Mike Tancsa, tel +1 519 651 3400 Sentex Communications, m...@sentex.net Providing Internet services since 1994 www.sentex.net Cambridge, Ontario Canada http://www.tancsa.com/ ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Cannot build kernel with qlxgbe on 10.2 RC2 (and probably 11-current)
Hi all, I have a problem with build kernel. You cannot use device qlxgbe in kernel config. I don't check but 11-current have same problem. It is caused by r284982 and r284741. New files were added but static files were not added. http://svnweb.freebsd.org/base?view=revisionrevision=284982 http://svnweb.freebsd.org/base?view=revisionrevision=284741 The patch is attached. Please check it. Thanks, -- Daisuke Aoyama qlxgbe-20150808.patch Description: Binary data ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: Cannot build kernel with qlxgbe on 10.2 RC2 (and probably 11-current)
On Sat, Aug 08, 2015 at 10:47:09AM +0900, Daisuke Aoyama wrote: Hi all, I have a problem with build kernel. You cannot use device qlxgbe in kernel config. I don't check but 11-current have same problem. It is caused by r284982 and r284741. New files were added but static files were not added. http://svnweb.freebsd.org/base?view=revisionrevision=284982 http://svnweb.freebsd.org/base?view=revisionrevision=284741 The patch is attached. Please check it. Please open a PR in Bugzilla. Glen Index: sys/conf/files.amd64 === --- sys/conf/files.amd64 (revision 286400) +++ sys/conf/files.amd64 (working copy) @@ -292,10 +292,13 @@ dev/qlxgb/qla_isr.c optionalqlxgb pci dev/qlxgb/qla_misc.c optionalqlxgb pci dev/qlxgb/qla_os.c optionalqlxgb pci +dev/qlxgbe/ql_boot.c optionalqlxgbe pci dev/qlxgbe/ql_dbg.c optionalqlxgbe pci +dev/qlxgbe/ql_fw.c optionalqlxgbe pci dev/qlxgbe/ql_hw.c optionalqlxgbe pci dev/qlxgbe/ql_ioctl.coptionalqlxgbe pci dev/qlxgbe/ql_isr.c optionalqlxgbe pci +dev/qlxgbe/ql_minidump.c optionalqlxgbe pci dev/qlxgbe/ql_misc.c optionalqlxgbe pci dev/qlxgbe/ql_os.c optionalqlxgbe pci dev/qlxgbe/ql_reset.coptionalqlxgbe pci pgpBcblEep2mV.pgp Description: PGP signature
