Menu

Show posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.

Show posts Menu

Messages - Solaris17

#31
My machine cant find the repository. This happened after I did the git pull several posts ago. I have just continued to do them since I cannot update normally.

EDIT:: was able to back up to 17.1.b from 17.1.b_9 by

# opnsense-update -sn "17.1\/latest"
# opnsense-update -fp

#32
Same issue here on Intel hardware (coretemp)

like above work around is

# kldload coretemp
#33
17.1 Legacy Series / Local DNS server failure
December 10, 2016, 08:02:54 AM
When attempting to use a DNS server on my LAN as the primary DNS server the whole network loses connection. A reboot does not fix the issue.

However if the DNS server is set on the client. Than the network works fine. Not sure where I should start looking?

I already have DNS rebind set to off.

I have seen this in the error logs. This is the IP of my DNS server.


opnsense: /system_general.php: The command '/sbin/route delete -host 10.0.0.19' returned exit code '1', the output was 'route: route has not been found delete host 10.0.0.19 fib 0: not in table'


Basically. I have an adnetwork filter based off of DNS.

On the remote DNS server (which is on my LAN)
I have the IP statically set.
I have the default gateway the IP of the router.
I have the DNS server IP set to Google & Level3 Communications.

If I set the DNS server under Settings>General in opnsense I lose ALL network connectivity.

However; If I manually take a PC and set it to use the DNS server everything works correctly and ads are filtered.

I wanted the router to simply use this local DNS server because its a pain to set DNS on all members of the network. I initially thought this might be a drop because of a detected DNS rebind attack, however I ran my own DNS server previously and that was still disabled.

I dont really know where to begin debugging this.

OPNsense 17.1.a_878-amd64
FreeBSD 11.0-RELEASE-p2
OpenSSL 1.0.2j 26 Sep 2016
#34
Exciting! Hopefully we will have an upgrade path?  :-X
#35
Quote from: franco on November 24, 2016, 05:34:15 PM
It must have been an early time in 17.1-ALPHA when you set up this machine.

Are the packages fine now? If you have connectivity back, run this:

# cd /usr/core
# git pull
# make upgrade


Cheers,
Franco

Very early, I have been running the betas and upgrading into them steadily since early 16.x. The packages were fine and I was able to correct SSH with your help from before. The above commands worked with no issue. I did have to git reset --hard for my modification to Makefile in removing the dependency, wouldnt have worked anyway because I was also missing p7zip.
#36
Has anyone else reported this? I figured the other two made sense, but I was unable to run any of that initially because it failed at ngattach from the very beginning even when the other two stages completed fine initially.
#37
To add to this from my thread I forgot to update here (Sorry I got married that month!)

https://forum.opnsense.org/index.php?topic=3778.0

I updated to the newer 17 Alpha and My NAT type on the PS4 has switched back to 2 without the need of any configuration.

Current build number is

OPNsense 17.1.a_539-amd64
FreeBSD 11.0-RELEASE-p2
OpenSSL 1.0.2j 26 Sep 2016
#38
hm, here ya go. Maybe its a misinterpretation on my part on what they are supposed to do. However I was under the impression it would allow updates to the _7xx builds


root@TDE-Core-Router:~ # opnsense-code core
fatal: destination path '/usr/core' already exists and is not an empty directory.
root@TDE-Core-Router:~ # cd /usr/core
root@TDE-Core-Router:/usr/core # opnsense-update -t opnsense-devel
The package type 'opnsense-devel' is already installed.
root@TDE-Core-Router:/usr/core # make upgrade
/usr/core/+POST_INSTALL -> /usr/core/work/src/+POST_INSTALL
/usr/core/+PRE_DEINSTALL -> /usr/core/work/src/+PRE_DEINSTALL
>>> Missing dependency: ngattach
*** Error code 1

Stop.
make[1]: stopped in /usr/core
*** Error code 1

Stop.
make: stopped in /usr/core
root@TDE-Core-Router:/usr/core # pkg install ngattach
Updating OPNsense repository catalogue...
OPNsense repository is up-to-date.
All repositories are up-to-date.
pkg: No packages available to install matching 'ngattach' have been found in the repositories
root@TDE-Core-Router:/usr/core #

#39
On that topic Were the commands at the end of the OP supposed to bring people upto the GIT version? Because the base install only currently goes upto 539. After the mishap with upgrading those commands don't really work, stating that the directory already exists etc. I would remove it to attempt it again but i'm uncertain what was touched in the process originally.
#40
Quote from: franco on November 24, 2016, 12:36:10 PM
Neat, pkg 1.9.x has a bug that prevents installation of packages because it tries to drop privileges and thus can't read the directory owned by root.

EDIT: OTOH, I'm relieved that the upgrades do work and we can explain the missing packages transition reported recently.

Wow thats odd. Does BSD know about this yet?
#41
17.1 Legacy Series / Re: Atheros AR9280 support
November 22, 2016, 04:33:09 AM
Awesome! really like work on the wireless. Glad to see you in colors Lattera! was always a huge fan of the hardenedBSD builds!
#42
ran the updates via console and everything is fine now on the following.

OPNsense 17.1.a_539-amd64
FreeBSD 11.0-RELEASE-p2
OpenSSL 1.0.2j 26 Sep 2016
#43
Hey thanks for taking the time out of your day to give me the commands. I dont know the repos well enough to be able to guess. Im at work ATM but till give it a try tonight.
#44
Hey Franco, Sorry its taken so long to respond.

I was running the alpha 17.x on BSD 10.3. I dont remember exact versioning. sorry.

It was an openSSL build. Though funny you should mention I could have sworn I had libreSSL installed at one point and I have not formatted.

I used the update command sequence in the OP of this thread.

You wouldnt have any idea how to maybe get this patched up would you? Any way I might be able to just pkg install the missing dependencies? I will format if needed but if there is a chance I can pull up the plane ill do it.

Thanks a bunch let me know if I can be of any assistance Franco!
#45
Finally took the plunge and did the upgrade.

Only issues iv ran into thus far are now I cant SSH and UPnP is broken.

Those 2 services

miniupnpd
sshd

refuse to start. Even after reboots. Changing the gui has no effect.

I also wasnt able to run the commands to allow updates by isntalling GIT, because I cant SSH into the unit. I will need to wait until I can console in.