Autosnort
Autosnort copied to clipboard
da667
LuaJIT library not found
Hello,
I receive the error attached when trying to install Snort via the Building VM's book. I tried downloading and installing the LuaJIT library, but receive the same error each time. Any help would be greatly appreciated.
Thank you!
I just fixed this issue today. Can you download autosnort again to ensure you are running the latest release then try this again?
On Sat, Dec 29, 2018, 6:21 PM Shootace <[email protected] wrote:
Hello, I receive the error attached when trying to install Snort via the Building VM's book. I tried downloading and installing the LuaJIT library, but receive the same error each time. Any help would be greatly appreciated. Thank you! [image: img_6793] https://user-images.githubusercontent.com/46234434/50542925-82dc8200-0b96-11e9-9f94-4d81a61b6234.jpg
— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/da667/Autosnort/issues/61, or mute the thread https://github.com/notifications/unsubscribe-auth/ACFvf94FupaT11d3HZGP3ovjuYEZeZynks5u9_j4gaJpZM4Zkvzo .
So the new Autosnort completed successfully and rebooted. The testing of the bridge still failed. So I saw your comment on my Suricata issue. So I went into /etc/network/interfaces and it had a message that netplan(5) replaced this file. So I had to modify 50-cloud-init.yaml instead under /etc/netplan. I commented out s8 and s9 in this file. Rebooted and now s8 does not show an IP address any longer and the s8 and s9 show UP, NOARP, and PROMISC. I powered up Kali and Metasploitable 2 and the ping command does not work. Network unreachable. ifconfig on M2 shows no ip address on eth0 (only interface, besides the loopback). I have attached ifconfig from the IPS VM
Okay, so we're on the right track. Can you verify that you have configured promiscuous mode on the virtual network interfaces (presumably interface 2 and 3) advanced settings and set promiscuous mode to allow all or allow vms on those interfaces?
On Sat, Dec 29, 2018, 8:49 PM Shootace <[email protected] wrote:
So the new Autosnort completed successfully and rebooted. The testing of the bridge still failed. So I saw your comment on my Suricata issue. So I went into /etc/network/interfaces and it had a message that netplan(5) replaced this file. So I had to modify 50-cloud-init.yaml instead under /etc/netplan. I commented out s8 and s9 in this file. Rebooted and now s8 does not show an IP address any longer and the s8 and s9 show UP, NOARP, and PROMISC. I powered up Kali and Metasploitable 2 and the ping command does not work. Network unreachable. ifconfig on M2 shows no ip address on eth0 (only interface, besides the loopback). I have attached ifconfig from the IPS VM [image: img_7047] https://user-images.githubusercontent.com/46234434/50543612-28015580-0bab-11e9-8361-1d84ae244ef2.jpg
— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/da667/Autosnort/issues/61#issuecomment-450533662, or mute the thread https://github.com/notifications/unsubscribe-auth/ACFvf6oupWM1tRPP2xSMH4xerZ4K4ug_ks5u-BusgaJpZM4Zkvzo .
Can you show me what network the metasploitable 2 vm and Kali Linux vms are connected to, as well as their network adapter advanced settings in virtual box please?
On Sat, Dec 29, 2018, 9:29 PM Shootace <[email protected] wrote:
ps -ef|grep snort output looks correct as well... [image: img_7050] https://user-images.githubusercontent.com/46234434/50543858-ca700780-0bb0-11e9-900a-199ebf65891e.jpg
— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/da667/Autosnort/issues/61#issuecomment-450534934, or mute the thread https://github.com/notifications/unsubscribe-auth/ACFvf6KzRBsfkCrzBB8CFgdvgR8-UwFEks5u-CT-gaJpZM4Zkvzo .
Sure...I also have noticed that when Metasploitable 2 is booting up, that the "Configuring network interfaces..." fails. It stays on this screen for a few mins before getting to prompt. I have attached image of this error as well. Not sure if it is related or not.
Okay so based on everything I can see here, there are two recommendations I can make that may help.
-
navigate to advanced settings on the ips vm in virtual box. For network adapter 2 and 3, change the adapter type to Intel pro/1000 my server. Reboot the ips vm, reboot the metasploitable 2 vm. If that doesn't work try setting this drop-down to "paravirtualized network" instead. It's rare, but I've seen a few cases where switching virtual network adapter types fixed the issue you're seeing.
-
download the metasploitable 2 vm again, and set it up from scratch. I've seen cases where the vm itself somehow got corrupted. I have no idea how but a fresh vm fixed the issue
On Sat, Dec 29, 2018, 10:37 PM Shootace <[email protected] wrote:
And my DHCP Static Mappings in pfsense under OPT1... [image: pfsense dhcp static mapping] https://user-images.githubusercontent.com/46234434/50544146-415dce00-0bba-11e9-8ca0-e7e334e2741b.jpg
— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/da667/Autosnort/issues/61#issuecomment-450536962, or mute the thread https://github.com/notifications/unsubscribe-auth/ACFvf8Tt9TUozkp2FqmJiU5-_DrqWpjjks5u-DTngaJpZM4Zkvzo .
Recreating the Metasploitable 2 VM did the trick! When I first tried to create it, I pointed to the Metasploitable vmdk file on my E:\vbox, but received an inaccessible error. So I moved the file to my C:\vbox location and it worked. Upon bootup I immediately noticed that the "Configuring network interfaces..." was no longer failing and booted up quickly. Think you were right. it was corrupted for some reason. I changed the network adapters 2 and 3 on the IPS VM back to Intel pro/1000 MT Desktop. Booted up everything and ping commands work all the way around. Thank you so much for helping me through this and for such a quick response!
I'm glad to hear things worked out! Have a happy New year, and lemme know if you run into anymore issues
On Sun, Dec 30, 2018, 1:14 AM Shootace <[email protected] wrote:
Recreating the Metasploitable 2 VM did the trick! When I first tried to create it, I pointed to the Metasploitable vmdk file on my E:\vbox, but received an inaccessible error. So I moved the file to my C:\vbox location and it worked. Upon bootup I immediately noticed that the "Configuring network interfaces..." was no longer failing and booted up quickly. Think you were right. it was corrupted for some reason. I changed the network adapters 2 and 3 on the IPS VM back to Intel pro/1000 MT Desktop. Booted up everything and ping commands work all the way around. Thank you so much for helping me through this and for such a quick response!
— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/da667/Autosnort/issues/61#issuecomment-450541613, or mute the thread https://github.com/notifications/unsubscribe-auth/ACFvf0YxCzWeAIniW4Ps685PHOoPPbWMks5u-FnWgaJpZM4Zkvzo .
@da667
I am having LuaJIT library not found as well on Ubuntu 14.04 LTS. I have already installed using sudo apt-get install luajit.
EDIT: I got it to work.
@da667 Hi, How can i fix the same error??? I installed LuaJIT and still the error mesage ;(
