1
German - Deutsch / Re: Proxy Qnap Nas - Keine Verbindung
« on: May 11, 2020, 05:31:23 pm »
Ja ist an.
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.
2
German - Deutsch / Re: Proxy Qnap Nas - Keine Verbindung
« on: May 10, 2020, 09:58:38 am »
Ich kann auf IP-Adressen (8.8.8.
pingen. Auf namen (google.de) nicht. Die Namensauflösung geht nicht.
pingen. Auf namen (google.de) nicht. Die Namensauflösung geht nicht.
3
German - Deutsch / Re: Proxy Qnap Nas - Keine Verbindung
« on: May 09, 2020, 08:09:13 pm »
Der Proxy ist es nicht.
Die Namensauflösung funktioniert leider auf der LAN Schnittstelle seit dem Update auf 20.1.3 nicht mehr.
Interessanterweise funktionier die Namensauflösung auf den VLAN's einwandfrei.
Ich erkenne keinen Unterschied in der Konfiguration...
Die Namensauflösung funktioniert leider auf der LAN Schnittstelle seit dem Update auf 20.1.3 nicht mehr.
Interessanterweise funktionier die Namensauflösung auf den VLAN's einwandfrei.
Ich erkenne keinen Unterschied in der Konfiguration...
4
German - Deutsch / Re: Proxy Qnap Nas - Keine Verbindung
« on: May 07, 2020, 11:12:13 pm »
Hast Du es gelöst?
5
20.1 Legacy Series / Re: OPNsense 20.1 - problems with DNS
« on: April 02, 2020, 07:48:26 am »
Has anyone figured out, why clients (based on linux) has issues to resolve names since last update of opnsense, and windows machines not?
My NAS and Ubiquity Controler are not able to resolve adresses anymore, using opnsense as DNS and Gateway.
My NAS and Ubiquity Controler are not able to resolve adresses anymore, using opnsense as DNS and Gateway.
6
20.1 Legacy Series / Re: OPNsense 20.1 - problems with DNS
« on: March 23, 2020, 06:33:13 pm »
Same issue here... since update.. Some Clients (e.g. NAS) is not longer able to resolve via unbound dns running on OPNSense...
7
19.1 Legacy Series / Not usual.... :)
« on: February 13, 2019, 07:04:30 am »
Not sure, if this is the right place to do.. to say... and i did not see to much of it.. but..
Yesterday i upgraded my system from 18.7 to 19.1. Prepared everything for a worst case of failure.
It was absolutely seamless and smooth. It can't run better.
I want to send a big thank you for all the effort and motivation to the project team. I cam from ipfire a year ago... and yes it was the right decision to do so... from a technical perspective... and from the feeling of beeing a part of a wider community.
Frank
Yesterday i upgraded my system from 18.7 to 19.1. Prepared everything for a worst case of failure.
It was absolutely seamless and smooth. It can't run better.
I want to send a big thank you for all the effort and motivation to the project team. I cam from ipfire a year ago... and yes it was the right decision to do so... from a technical perspective... and from the feeling of beeing a part of a wider community.
Frank
8
18.7 Legacy Series / Re: Fresh install on new box
« on: December 27, 2018, 06:48:35 am »
Hi,
i expected same behaviour since i have VLAN's configured.
When i push the login-button after, lets say 5 secs again, the initial page appears immediately.
I am using chrome.
i expected same behaviour since i have VLAN's configured.
When i push the login-button after, lets say 5 secs again, the initial page appears immediately.
I am using chrome.
9
18.7 Legacy Series / Re: [SOLVED] not boot after update to 18.7.9
« on: December 15, 2018, 07:54:46 am »
THANK YOU marjohn56, THANK YOU franco,
i installed from new media and adviced to use an old configuration via installation.
That works brilliant.
- two remarks
1.) During installation the normal warning messages that all data on the selected disk will be erased. even when i have upfront to this message the old installation from disk selected and imported. That was confusing
2.) It took me a while to figure out, why i do not have access to the GUI and no Internet access. Reason was, i have seperated my LAN into VLAN's, and also descripted in the alias section. AND... the reason for the issue was, that alias are not included into the backup, or at leased they were not installed from the former installation.
I saw a post here, that you guys have it at your plate, because of inconsistency of old backup to new fw-version.
having this said... again... thanks a lot...
best
Frank
i installed from new media and adviced to use an old configuration via installation.
That works brilliant.
- two remarks
1.) During installation the normal warning messages that all data on the selected disk will be erased. even when i have upfront to this message the old installation from disk selected and imported. That was confusing
2.) It took me a while to figure out, why i do not have access to the GUI and no Internet access. Reason was, i have seperated my LAN into VLAN's, and also descripted in the alias section. AND... the reason for the issue was, that alias are not included into the backup, or at leased they were not installed from the former installation.
I saw a post here, that you guys have it at your plate, because of inconsistency of old backup to new fw-version.
having this said... again... thanks a lot...
best
Frank
10
18.7 Legacy Series / Re: not boot after update to 18.7.9
« on: December 14, 2018, 10:51:31 am »
A complete new installation... puuh...
is there no other possible solution.....?
is there no other possible solution.....?
11
18.7 Legacy Series / [SOLVED] no boot after update to 18.7.9
« on: December 14, 2018, 09:18:10 am »
Hi,
i've updated to 18.7.9.
During boot (first time when filesystems are mounted) message
/usr/lib/liblzma.so.5 Unsupported version 0 of Elf_Verdef entry
appears.
System is skipping this message and discovers USB ports.
After "configuring PHP: OK" same message appears three time during executing php scripts.
Finally system hangs with "Enter full pathname of shell or Teturn for /bin/sh" after Launching the inin system...
Not sure what went wrong.... can you guys support me please ?
regards
Frank
i've updated to 18.7.9.
During boot (first time when filesystems are mounted) message
/usr/lib/liblzma.so.5 Unsupported version 0 of Elf_Verdef entry
appears.
System is skipping this message and discovers USB ports.
After "configuring PHP: OK" same message appears three time during executing php scripts.
Finally system hangs with "Enter full pathname of shell or Teturn for /bin/sh" after Launching the inin system...
Not sure what went wrong.... can you guys support me please ?
regards
Frank
12
18.1 Legacy Series / Re: IGMPProxy1.3 is not starting
« on: September 18, 2018, 05:52:08 am »
I found an different solution, outside the opnsense box. Means... i am out... sorry.
13
18.1 Legacy Series / Re: igmpproxy won't start after upgrade
« on: September 02, 2018, 08:56:55 pm »
you can find discussions here within the forum.
14
18.1 Legacy Series / Re: IGMPProxy1.3 is not starting
« on: July 28, 2018, 03:51:53 pm »
Hej great news !
i am waiting to one of my friends to connect the MR401 with his speedport. (I have no, since i am using a draytec 132 as endpoint for my VDSL line.
I think i can come back mid of August with results. As far as i have it, i will post it here.
Thanks Giddie,
Best regards
Frank
i am waiting to one of my friends to connect the MR401 with his speedport. (I have no, since i am using a draytec 132 as endpoint for my VDSL line.
I think i can come back mid of August with results. As far as i have it, i will post it here.
Thanks Giddie,
Best regards
Frank
15
18.1 Legacy Series / Re: IGMPProxy1.3 is not starting
« on: July 14, 2018, 07:30:06 am »
Hi Giddie,
wow.... this is fabuoulus.
I will give it a try....weekend next week..
thank you very much to figure it out.
how do you have set up the TFTP proxy on opnsense?
thanks again.
I will let you know next week, the outcome of my results.
Frank
wow.... this is fabuoulus.
I will give it a try....weekend next week..
thank you very much to figure it out.
how do you have set up the TFTP proxy on opnsense?
thanks again.
I will let you know next week, the outcome of my results.
Frank