Hi there,

The hostapd.conf says that this might not be needed anymore.

Thought about some quirks. Did not touch the reset button yet but had in mind to use it as some ACPI power button to enable cold boot by pressing a button, not unplugging and replugging odd wires. Resetting the config by that button would be a waste of that button. You would have to hook up to the APU board by serial again in order to revive it. If you did so, you might as well just have moved away the bad config and reboot :-) Once I get a hang of how that reset button works (gotta look into the GPIO stuff), I'll open a new ticket. Maybe we can add some generic config wizzardry to set up LEDs and GPIOs once we get a good grasp on it.

Pull request: https://github.com/vyos/vyos-build-kernel/pull/6

Pull request: https://github.com/vyos/vyos-1x/pull/353

thanks for explaining the backgrounds! I wonder if a removal of the hostfile-update option should be suggested.

Found the culprit.

Uh, that's nice easter eggs folks :-) Thank you both for your valuable hints! They'll be very handy!

Pull request: https://github.com/vyos/vyos-1x/pull/330

Pull request: https://github.com/vyos/vyos-1x/pull/306

Pull request: https://github.com/vyos/vyos-1x/pull/305

These are the VyOS 1.2 configuration commands for a mixed-mode 5GHz AP:

Found it. My bad.

Pull request: https://github.com/vyos/vyos-1x/pull/303

Pull request: https://github.com/vyos/vyos-1x/pull/301

This is the logic from my old wireless-hostapd.pl file:

This is the logic from my old wireless-hostapd.pl file:

Here is the logic from my old wireless-hostapd.pl file:

Aye, from what I see in my old wireless-hostap.pl, logic should go like this. Every "print" is output to the wlanX.cfg which serves as config input for hostapd.

Thanks for fixing! Took me half a day today to figure this out :)

In "broken" mode, no, as clients will refuse to sync to an unsynchrinized server. That's how I stumbled across this in first place.
In "fixed" mode, once NTPd is synced again, clients will fetch time from VyOS. On my testbed, I have this (now working) config:

Hi there,

I seem to be wrong with my initial statement where to set the version. The file debian/vyatta-wireless/DEBIAN/control is not even in version control and I can't seem to find a hint on where this version string 0.3.41+vyos2+current1 really comes from.

Pull request sent. Please consider for merge.

Cheers @c-po! Unfortunately, the build failed with reference to "clearfog". Do you know what this is or if I could fix this somehow in vyatta-wireless?
Right now, I have no idea...

In T452#11673, @dmbaturin wrote:

Merged.

It will have to be refactored for the new vyos-1x approach, but then the entire package will, so we'll better have the .ac support now, and refactor later.

As pointed out in T529#11515, I rewrote this command to now do the following:

I'd like to prompt for a decision:

• break backward compatibility to implement the above scheme (I'd suggest that) or
• stick with this pull request (T452) and work around the regdom-setting by using the existing pull request in T529.

In T529#11515, @alainlamar wrote:

I had a chat with @syncer yesterday, where we also discussed the approach of setting WiFi regulatory domains. We agreed upon two issues prompting for an Architect's decision (@dmbaturin):

• Code that does persistent changes should go to the configure section. This would mean three things:
  • The part writing to files would be moved from T529 to T452.
  • Backward compatibility in T452 would be broken as the set interfaces wireless wlanX country DE node would be moved in front of the interface name tag config node: set interfaces wireless regulatory-domain DE which would allow for a complete and easy to understand way of making all persistent changes in one go. [...]

Hi folks,

I'll be available this Monday and Thursday after 21:30 until 23:30 CET.

I agree with your approach on handing in bug reports and feature requests. What I try to figure out is how folks trying to solve these bugs and implement feature requests would best approach maintainers. Since there is very few maintainers and they spend their spare time on VyOS project maintainance, I think there should be guidelines for folks (like me) on how to hand in code for review - and maybe how not to. This, I hope, would allow maintainers to accept more pull requests with less use of their valuable spare time.

Thanks mate,

Cheers mate!