Messages

181

Development and Code Review / Re: Let's improve the docs (and build a new plugin)

« on: February 02, 2018, 10:04:59 am »

I agree. If that autobackup is a feature that sooner or later will be on the roadmap for the core, we should refrain from implementing it as a plugin.

182

German - Deutsch / Re: PPP0E Verbindung oder direkte Verbindung zu FritzBox? welche Methode ist besser?

« on: February 01, 2018, 10:18:18 pm »

https://github.com/opnsense/core/issues/2155

183

German - Deutsch / Re: PPP0E Verbindung oder direkte Verbindung zu FritzBox? welche Methode ist besser?

« on: February 01, 2018, 09:47:01 pm »

Ich habe bei Github ein Bugreport eingestellt. Hier würde das vermutlich untergehen.

184

German - Deutsch / Re: PPP0E Verbindung oder direkte Verbindung zu FritzBox? welche Methode ist besser?

« on: February 01, 2018, 08:24:18 pm »

Interessant. Ich habe momentan ebenfalls Probleme mit IPv6 nach der Zwangstrennung.
Meine Clients wollen einfach nicht über IPv6 ins Internet. Adressen bekommen sie problemlos zugewiesen.

Eine Analyse ergab, dass Pings von einem Client an einen Testserver ankamen, vom Testserver replied wurden, aber dann an der sense auf pppoe0 kommt nichts mehr an. Nach einem Restart der Box funktioniert wieder alles.

185

Development and Code Review / Re: Let's improve the docs (and build a new plugin)

« on: February 01, 2018, 08:14:54 pm »

Okay, so collect is install's anti-target 
That's really helpful. I will test this setup tomorrow. Thank you!

186

German - Deutsch / Re: Problem mit Web Proxy

« on: February 01, 2018, 03:52:26 pm »

OPNsense macht Probleme, wenn auf der Blacklist Seiten stehen, die auch bei Nicht abzufangende SSL Seiten eingetragen sind.

Hast du die kompletten ACLs übernommen oder hast du schon Kategorien aussortiert?

187

German - Deutsch / Re: OpenVPN Zugriff-Problem auf LAN

« on: February 01, 2018, 01:32:03 pm »

Problem gelöst bekommen

Danke

Und woran hat es gelegen? Wenn du den Thread hier schon erstellst, dann erleuchte uns bitte auch mit der Lösung 

188

Development and Code Review / Re: Let's improve the docs (and build a new plugin)

« on: February 01, 2018, 12:02:09 pm »

Yes, it is just a little bit uncomfortable.

Either I clone opnsense/plugins and define path mappings inside my IDE, then I can work directly with the repository but I have no real code completion.

Or I work directly on the vm, have full code completion inside the IDE but cannot use the plugins repo. Then I would have to remember which of the files belong to the plugin and copy them over to the repo

189

Development and Code Review / Re: Let's improve the docs (and build a new plugin)

« on: February 01, 2018, 09:53:09 am »

Hi,

I wrote some guides for beginners, perhaps they'll help you a bit:
http://www.routerperformance.net/opnsense/

There's already a plugin for SCP backup in the devel-tree, perhaps you want to extend it?

A good start e.g. would a plugin for bandwidthd or vnstat, they are easy daemons and should be easy to set up.

Happy to follow your journey here 

Thanks, I will have a look at your guides.

so you want to try something like this?
https://github.com/opnsense/plugins/tree/master/sysutils/scp-backup

Yes. But this plugin will have options on which protocol to use. In a version 2.0 you could also specify multiple backup targets using multiple strategies.

----------

Here some first questions:

How can I install a PLUGIN_DEVEL=yes plugin ?
What is the development lifecycle of a new plugin? What steps it takes from devel=yes to no?

As of starting out:

My computer is a mac, so to get the toolchain up I will probably need a fresh FreeBSD VM. Then cloning opnsense/tools and follow the instructions in the opnsense/tools readme. This leads me to a machine I can use for building.
After make update step is done, I will have cloned all relevant git repositories on my - let me call it BuildServer.

Now, the BuildServer is no OPNsense instance itself. So to have a running system, I could launch a second vm - let's call it DevServer. I have seen a vagrant makefile in the src repository's release directory. Can I somehow use it to start up the exact built OPNsense version I cloned?

190

Development and Code Review / Let's improve the docs (and build a new plugin)

« on: January 31, 2018, 09:42:06 pm »

Hey!

To ease the learning curve for new contributors and to extend the wiki with some more details regarding development, especially focussing on how to begin, I like to start developing a new plugin for OPNsense.

My goal is to use the documentation as well as the readme files and the source code on github as the only reference. Everywhere I get stuck, because I find the docs are lacking information I want to report here, find a solution and propose improvements for the docs.

Of course, you can make hours-taking deep dive in the source code, travelling from framework A over tool B to source file C. But I want to make the plugins tutorial more streamlined and add some glue knowledge.

About the plugin:
The AutoBackup plugin that I want to write is going to take the config.xml and uploads it to a remote target. Remote targets can be one of FTP, FTPS, SCP/SFTP etc (extendable via Interfaces). A cronjob is responsible for triggering the backup action on defined times. There is already such an option for GoogleDrive but this is just one target.

What needs to be done for this plugin?
- add a cronjob item that can be selected in the cron settings
- creating a GUI (Controllers, Models, Forms, Views)
- adding PHP libraries for remote file protocols, if not already provided (maybe involving composer during build?)
- actions and API functions etc.

Information about how to achieve these things is hard to find. Sometimes some glue components are not documented. e.g how forms interact with the model and internal Phalcon stuff.

Also I like to find a good way on how to set up a complete development environment. Starting with using the tools repo for building, continuing with how to set up a development instance of OPNsense, along with an IDE. So that it is easy to change code inside the IDE and immediately see the changes in the browser.

There will be some more specific questions in the future. However, I'm not looking for the devs to do my work. It's just sometimes I feel something is missing. And I like to ask my questions and I also like the documentation benefiting from our findings.

191

18.1 Legacy Series / Re: Upgrade 17.7.12_1>18.1 failure

« on: January 30, 2018, 12:17:58 am »

In my company, we developers call this the "git monster" - eating away code 

192

18.1 Legacy Series / Re: Upgrade 17.7.12_1>18.1 failure

« on: January 30, 2018, 12:15:06 am »

So your code change will set the correct protocol ICMP or IPV6-ICMP according to the rule's selected inet protocol.
This will avoid misconfiguring. Great.

193

18.1 Legacy Series / Re: Upgrade 17.7.12_1>18.1 failure

« on: January 29, 2018, 11:30:47 pm »

The error message you quoted seems to tell that there is a rule regarding ICMP.

There were error(s) loading the rules: /tmp/rules.debug:143: proto icmp doesn't match address family inet6 - The line in question reads [143]: pass in quick on pppoe0 reply-to ( pppoe0 fe80::eab7:48ff:fed9:a00 ) inet6 proto icmp from {any} to {any} keep state label "USER_RULE: Allow IPv6 Ping" # 560108416307135435e3168fe05a398b

> None of my ICMP rules are 4+6
The error also occurs when you have a v6 only rule which uses the protocol "ICMP" instead of "IPV6-ICMP"

194

18.1 Legacy Series / Re: Upgrade 17.7.12_1 to 18.1: Lost IPv4 connectivity from configured networks

« on: January 29, 2018, 11:17:50 pm »

https://forum.opnsense.org/index.php?topic=7060.msg31267#msg31267

If using rules for ICMP:

- do NOT mix v6 and v4 rules (don't use "IPv4+IPv6" version constraint)
- use protocol "IPV6-ICMP" for any rule regarding ICMP and v6
- use protocol "ICMP" for any rule regarding ICMP and v4

195

18.1 Legacy Series / Re: Upgrade 17.7.12_1>18.1 failure

« on: January 29, 2018, 11:17:02 pm »

@Taomin:

got me an hour debugging before figuring it out.

If using rules for ICMP:

- do NOT mix v6 and v4 rules (don't use "IPv4+IPv6" version constraint)
- use protocol "IPV6-ICMP" for any rule regarding ICMP and v6
- use protocol "ICMP" for any rule regarding ICMP and v4