You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Apr 16, 2021. It is now read-only.
PLEASE NOTE! This Issue Tracker is NOT intended for normal support
requests! Support requests should go to the mailing list first. Once
we've confirmed your issue on the mailing list, we may ask you to create a
ticket here.
If you have contacted the mailing list first and we've asked you to create
a ticket here, please answer the following questions:
What steps will reproduce the problem?
1. Run first part of SOSetup
2. Complete network setup
3. Forced to reboot
What is the expected output? What do you see instead?
Would like to be able to make some changes before rebooting. In my case, edit
/etc/network/interfaces to handle bonding (802.3ad)
Are you using the new Security Onion 12.04?
12.04.03 20130904
Did you install from the ISO image or did you install your own version of
Ubuntu and then add our PPA and packages?
ISO
Please provide any additional information below.
Apologies if this is something already supported, and I just missed it.
Original issue reported on code.google.com by rfifa...@gmail.com on 14 Nov 2013 at 4:52
The text was updated successfully, but these errors were encountered:
sosetup-network now does the following:
- ask the user if they want to make changes to /etc/network/interfaces
- if user clicks yes, changes are made
- tells user changes have been made, recommends reboot, asks if they want to
reboot now
- if no, exit
- if yes, reboot
This will be included in the upcoming Bro 2.2 and ELSA updates.
Original comment by doug.bu...@gmail.com on 16 Nov 2013 at 4:07
Changed title: Setup should write out changes to /etc/network/interfaces and then prompt for reboot
Original issue reported on code.google.com by
rfifa...@gmail.com
on 14 Nov 2013 at 4:52The text was updated successfully, but these errors were encountered: