summaryrefslogtreecommitdiff
path: root/etc
AgeCommit message (Collapse)Author
2014-12-03Adding initial support for loading a config from AWS EC2 user-datajrb
2014-10-08Bug #335, run the EC2 key fetching script as vyattacfg.Daniil Baturin
2014-10-08If not running on AWS (system UUID and serial do not start with EC2), don't ↵Daniil Baturin
do AWS-specific things.
2014-07-25Set vyos-intfwatchd to start at boot by default.Daniil Baturin
2014-07-25Add vyod-intfwatchd for restoring IPv6 addresses after link flaps.Daniil Baturin
As bad as it can be, it seems to sort of work.
2014-04-28Add support for installing a new image on the Amazon AMIhydrajump
- Check if installing on AWS EC2 platform via instance metadata. - Configure GRUB correctly, so that boot messages are available via instance's console. - Add init.d script to fetch user's EC2 public key during boot.
2012-12-12revert 918bd40d3e3f238a800b1486f70e2d5ee1d71a72John Southworth
2012-09-04Bugfix 8290John Southworth
Don't allow default password to persist after first boot. Due to the numerous ways a user can get a vyatta system this required a lot of changes. 1. Don't allow a user to set a password to 'vyatta' after first login, but allow it on the initial boot otherwise the system will have no user. 2. Don't allow the password to be set to vyatta in installer. 3. Force password change on first login. under the following conditions: 3.a. User is an admin level user. Operators do not have the abillity to change the config so they can't change passwords. Allow 'vyatta' to be the password until an admin logs in. 3.b. This is not the livecd, its silly to force a password change before install.
2011-12-13Bug 7672: Don't execute check-params-on-reboot.d if config fileDaniil Baturin
does not exist.
2011-08-19Cleanup vyatta-config-reboot-paramsStephen Hemminger
Split comments out of Description: text which is part of LSB info into later parts of the file.
2011-04-18* run start-up script vyatta-config-reboot-params very early in boot processMohit Mehta
This script executes scripts lying in the following directory: /opt/vyatta/bin/sudo-users/check-params-on-reboot.d Scripts in check-params-on-reboot.d are intended for parameters that require a reboot to take effect after they are set/changed. Because of the reboot requirement, underlying value and related config paramter value can become out-of-sync in couple of cases: 1. change parameter value, don't save config, reboot. Underlying value is different than the value in config file. 2. install new image; when new image boots, underlying value is the default Vyatta shipped value not the value in config file. More info: http://bugzilla.vyatta.com/show_bug.cgi?id=6915#c1 This check-in also adds ipv6_disable_blacklist script in check-params-on-reboot.d to fix the above mentioned problem for 'system ipv6 disable' and 'system ipv6 blacklist'
2011-03-22Update copybreak module param listStephen Hemminger
Update list of network drivers copybreak parameters to match current kernel version. This is harmless with out of date kernels. Fixes warning about unknown module parameter with r8169
2010-02-03Move modprobe.d/no-copybreak from vyatta-cfgStephen Hemminger
All interface related files are in vyatta-cfg-system package.
2007-12-19Revert "add init script to force udev settle before itf configured"Tom Grennan
This is unnecessary if the config.boot file is available before udevd starts. This reverts commit a9cd192305b779cb62aecd858ad9a4e5a1fbcad4.
2007-12-17add init script to force udev settle before itf configuredTom Grennan