Pull request created: https://github.com/vyos/vyatta-wireless/pull/9/files

Pull request sent. Please consider a merge.

@syncer thanks for the offer :)

@c-po thanks for pointing me to the interface definitions!

I found an example file in vyatta-lldp:

I found an example XML tag config file in vyatta-lldp:

@c-po Thank you for the quick response and especially for the workaround! This was of great value...

@c-po I re-arranged the code and the git commits and hope things are fine now so this ticket may come to its deserved end of life.

@dmbaturin Yes, as time permits. That's my worst constraint.

@c-po I did some major work on vyatta-wireless, including the introduction of nested nodes to configure card capabilities. Would you mind to take a look at it and suggest improvements for:

• using a better way than Perl smartmatch to compare strings against arbitrary lists of strings (like in Python if "bar" in ["foo", "bar", "baz"]: print("True"))
• a nicer way to getting rid of mutual exclusions without adding too much responsibility on parsing by wireless-hostapd.pl. Transforming ht and vht from multi nodes into nested directories and then implement a bool node for each capability flag would IMHO require much more parsing in wireless-hostapd.pl but would solve the issue with mutual exclusions which could be implemented as simple multi-choice nodes...

Yeah. I ignored T141 by purpose for two reasons:

• I do not know enough about what proper AAA support would exaclty mean.
• Maybe doing this one step at a time would make incorporating changes easier instead of trying to achieve it all in one run?

I propose to introduce config nodes to create AllowUsers, AllowGroups, DenyUsers and DenyGroups settings in sshd_config. Additionally, I propose to introduce a sshd-option config node.

thanks for the advice! My Git skills suck, but I'll try to catch up quickly. I cloned your repo, checked out branch z507-sshd and did a git diff c5e11462769bea9769335944f0f8a8f5411d027e > t507_c-po.patch which is the last commit prior to T507 commits. Then I ran diff on that patch file and the one I created before. No difference, which means, your commits are nicely done!

Upon add system image vyos-xxxx.iso, serial speed arguments in Kernel boot parameters are set statically to 9600 baud, no matter what /config/config.boot states.
The culprit seems to be in file /opt/vyatta/sbin/install-image-existing lines 262 to 280, where templates from /opt/vyatta/etc/grub/default-union-grub-entry is used to set up the new grub.cfg. Within the latter file, serial speed is statically set to 9600 baud.

In T452#10768, @c-po wrote:

@alainlamar Kernel Updated and Rebuild triggered on CI server.

Uhmm, I guess, we may have a hard row to hoe here:

Today, I had a look into the vyatta-wireless package to see if I could hack something up to work with the new Kernel changes via VyOS CLI.

@c-po here you go:

Hi folks,

I use squid as a caching proxy to very considerably speed up patching and non-encrypted static web content. I also use the blacklists which are updated every day. While VyOS with Squid and Wifi is a very good integrated router for home and SOHO, I also use it as building bloc for sample firewalls you encounter in corporate environments in several showcases.

Meanwhile I learned how to successfully use DFS with the ATH10K driver. It is kind of a nasty driver to use as the makers put many obstacles into firmware and the driver module code to prevent "daisy chained" accidents related to setting wrong regulatory domains. RegDomain setting was not possible without Kernel config parameters "CONFIG_ATH_REG_DYNAMIC_USER_CERT_TESTING" and "CONFIG_ATH_REG_DYNAMIC_USER_REG_HINTS". I guess that was the reason why hostapd always crashed when trying to use DFS.

@c-po Thanks for sharing your Kernel build steps. My question however was about building a custom Kernel _into_ a new ISO, so includung a successful run of "make iso".

@c-po Yes, I happily would!
BTW: How did you manage to build 1.2.x with a custom Kernel? I continuously fail on the attempt when the build process tries to build the initrd for the custom Kernel. Would you mind to share your build steps?

@c-po Hi, don't cheer up too early, I was not able to tst it all together since VyOS 1.2.x would not build due to server problems for the past week. Certain test steps on Ubuntu LTS 16.04 on a PC-Engines apu3b4 board using a Compex WLE600VX card indicated several possible pitfalls like reg domain switching. And then, as you already indicated, there are some old packages to be replaced in Debian Jessie. Major testing and some developing still needs to be done before we can celebrate a "recipe" for our cake. That is where I hope for your help and offer mine, too :-)

I'd also greatly prefer unchanged default behavior, but a config option to bring in the new hotness :)