I have just tried pinging my laptop from the desktop, and it worked. I got 0% packet loss. However the browser on my desktop is unable to visit the server on my laptop. When I enter the laptop's IP address in the URL bar, it is unable to connect.
I ran nmap and it stated that port 80 is open for http.
I do not have a file or directory in /var/log called messages. I have checked the other log files and haven't found any evidence of the pings.
This is the result of
:
Code:
alternatives.log apport.log.3.gz auth.log.1 cups fsck kern.log.2.gz ntpstats syslog.1 tallylog
alternatives.log.1 apport.log.4.gz auth.log.2.gz dmesg gpu-manager.log lastlog php7.0-fpm.log syslog.2.gz upstart
apache2 apport.log.5.gz boot.log dpkg.log gufw.log libvirt php7.0-fpm.log.1 syslog.3.gz wtmp
apparmor apt bootstrap.log dpkg.log.1 hp lightdm php7.0-fpm.log.2.gz syslog.4.gz wtmp.1
apport.log aptitude btmp faillog installer mintsystem.log samba syslog.5.gz Xorg.0.log
apport.log.1 aptitude.1.gz btmp.1 firewalld kern.log mintsystem.timestamps speech-dispatcher syslog.6.gz Xorg.0.log.old
apport.log.2.gz auth.log ConsoleKit fontconfig.log kern.log.1 mysql syslog syslog.7.gz
Is one of these relevant?
I did find the following entry in syslog after disabling apparmor:
Code:
Feb 12 11:14:12 dylanuszwei-Satellite-P750 systemd[1]: Stopping LSB: AppArmor initialization...
Feb 12 11:14:12 dylanuszwei-Satellite-P750 apparmor[10500]: * Clearing AppArmor profiles cache
Feb 12 11:14:12 dylanuszwei-Satellite-P750 apparmor[10500]: ...done.
Feb 12 11:14:12 dylanuszwei-Satellite-P750 apparmor[10500]: All profile caches have been cleared, but no profiles have been unloaded.
Feb 12 11:14:12 dylanuszwei-Satellite-P750 apparmor[10500]: Unloading profiles will leave already running processes permanently
Feb 12 11:14:12 dylanuszwei-Satellite-P750 apparmor[10500]: unconfined, which can lead to unexpected situations.
Feb 12 11:14:12 dylanuszwei-Satellite-P750 apparmor[10500]: To set a process to complain mode, use the command line tool
Feb 12 11:14:12 dylanuszwei-Satellite-P750 apparmor[10500]: 'aa-complain'. To really tear down all profiles, run the init script
Feb 12 11:14:12 dylanuszwei-Satellite-P750 apparmor[10500]: with the 'teardown' option."
Feb 12 11:14:12 dylanuszwei-Satellite-P750 systemd[1]: Stopped LSB: AppArmor initialization.
Since it is leaving the profiles in place, is it possible that apparmor is still blocking access? From what I understand apparmor functions similarly to SELinux. I would think disabling it would be all I need to do, but perhaps it is still doing something in the background.
Let me know if you need me to post any more information up here.