show-dhcp-leases.pl under vyatta-op remains the only extant deadweight Vyatta script and needs to be removed.

https://github.com/vyos/vyos-1x/pull/2323

It seems this problem is not caused by IPsec, but it was caused by GRE implementation.

PR for sagitta:
https://github.com/vyos/vyos-1x/pull/2315

Add option protocol, PR https://github.com/vyos/vyos-1x/pull/2313

set policy local-route rule 100 destination '192.0.2.12'
set policy local-route rule 100 protocol 'tcp'
set policy local-route rule 100 set table '100'

Adding use outline from PR for future reference; the dir vyos-1x-current below refers to a local copy of the vyos-1x source:

Fixed

Also added flowtable as nothing needs to be sequenced in there either:
https://github.com/JeffWDH/vyos-1x/commit/ac22cc054d9c15af010c824ac9a05f5cc71fc954

I have not contributed code to this project before so let me know if I've missed conventions...

Just to be clear, the build I'm going from is just my own build of current to my own build of current -- it says 1.4 because I only changed the version string to 1.5 after this build went through since i'm the only one using my build :)

I just noticed that this still is a problem. Excerpt below from downloading an upgrade:

PR for 1.3 https://github.com/vyos/vyos-1x/pull/2310

In T5497#160905, @JeffWDH wrote:

1.5-rolling-202309250022

Is there a reason why some global options and some address groups (not all) are included in the output? Seems unintentional to me.

Is there a reason why some global options and some address groups (not all) are included in the output? Seems unintentional to me.

Shouldnt that be default for lb then in the vyos buildscripts and how does --debug affect things other than logging during build?

What is the "system update-check url" supposed to be once its implemented?

Note that is is the "--debug" flag that one wants in order to see the full mksquashfs command that is executed.

@stingalleman As mentioned above (and confirmed in discussions earlier this week), we've had few if any reports of issues with the udev approach, so we would be very interested to hear details of your case.

When will this bug be fixed? I am having a lot of issues with this.

Verified to be working as expected.

@jestabro I havent verified it yet but then perhaps the buildscript for VyOS should be altered to include --verbose?

PR: https://github.com/vyos/vyos-1x/pull/2305

PR removing zone-policy op-mode: https://github.com/vyos/vyos-1x/pull/2304

PR: https://github.com/vyos/vyos-1x/pull/2304

Op-mode command reduce
PR https://github.com/vyos/vyos-1x/pull/2302

vyos@r4:~$ show conf com | match firew
set firewall ipv4 input filter default-action 'accept'
set firewall ipv4 input filter rule 1 action 'accept'
set firewall ipv4 input filter rule 1 description 'Allow loopback'
set firewall ipv4 input filter rule 1 inbound-interface interface-name 'lo'
set firewall ipv4 input filter rule 1 source address '127.0.0.0/8'
set firewall ipv4 input filter rule 2 action 'accept'
set firewall ipv4 input filter rule 2 description 'Allow established/related'
set firewall ipv4 input filter rule 2 state established 'enable'
set firewall ipv4 input filter rule 2 state related 'enable'
set firewall ipv4 input filter rule 60 action 'accept'
set firewall ipv4 input filter rule 60 description 'Allow SSH from trusted networks'
set firewall ipv4 input filter rule 60 destination port '22'
set firewall ipv4 input filter rule 60 protocol 'tcp'
set firewall ipv4 input filter rule 10000 action 'drop'
set firewall ipv4 input filter rule 10000 description 'Drop everything else'
vyos@r4:~$ 
vyos@r4:~$ produce firewall rule-resequence start 10 step 10

PRs:
https://github.com/vyos/vyos-1x/pull/2298
https://github.com/vyos/vyatta-op/pull/71
https://github.com/vyos/vyos-build/pull/419

Oops, sorry about that!

@Apachez It is not FQDN based

Should I ask this to you.

In T5601#160566, @vvinci00 wrote:

Hello,

I need to reverse proxy TCP traffic.
the traffic is not HTTP/HTTPS

Contact our sales or ask forum

It's possible to use VyOS as reverse proxy on TCP traffic (not HTTP)?
if yes, what configuration it's necessary?
if not, do you know any solutions that can help me?

In T5601#160566, @vvinci00 wrote:

Hello,

I need to reverse proxy TCP traffic.
the traffic is not HTTP/HTTPS

I need to reverse proxy TCP traffic.
the traffic is not HTTP/HTTPS

set netns name mgmt
set interfaces virtual-ethernet veth1 address '10.0.0.0/31'
set interfaces virtual-ethernet veth1 peer-name 'veth10'
set interfaces virtual-ethernet veth10 address '10.0.0.1/31'
set interfaces virtual-ethernet veth10 netns 'mgmt'
set interfaces virtual-ethernet veth10 peer-name 'veth1'

PR https://github.com/vyos/vyos-1x/pull/2295

set system sysctl parameter net.ipv4.tcp_syncookies value '1'
set system sysctl parameter net.ipv4.tcp_timestamps value '1'

PR https://github.com/vyos/vyos-1x/pull/2294