http://dev.packages.vyos.net/repositories/current/vyos/pool/main/v/vyatta-wanloadbalance/vyatta-wanloadbalance_0.13.70+vyos2+current1_amd64.deb
solving the issue
it may be closed
- Queries
- All Stories
- Search
- Advanced Search
- Transactions
- Transaction Logs
Feed Advanced Search
Advanced Search
Advanced Search
Feb 19 2019
Feb 19 2019
hagbard triaged T1255: /usr/libexec/vyos/conf_mode/host_name.py needs to add an additional newline char as Normal priority.
hagbard closed T1254: wireguard generate wireguard keypair fails when executed on the iso as Resolved.
hagbard changed the status of T1254: wireguard generate wireguard keypair fails when executed on the iso from Open to In progress.
hagbard triaged T1254: wireguard generate wireguard keypair fails when executed on the iso as Wishlist priority.
oleksandr.ovsiannikov added a comment to T1247: WAN load-balancing fail when !<x.x.x.x/x> configured in rules.
oleksandr.ovsiannikov added a comment to T1247: WAN load-balancing fail when !<x.x.x.x/x> configured in rules.
@hagbardIt fixes the issue with WANLOADBALANCE_PRE chain, but we still observe unexpected behavior.
I will write a little bit more letter.
Feb 17 2019
Feb 17 2019
Feb 15 2019
Feb 15 2019
hagbard moved T1247: WAN load-balancing fail when !<x.x.x.x/x> configured in rules from Need Triage to In Progress on the VyOS 1.2 Crux board.
@zsdc Is it working for you with the package above?
Feb 14 2019
Feb 14 2019
hagbard changed the status of T1247: WAN load-balancing fail when !<x.x.x.x/x> configured in rules from Confirmed to Needs testing.
@zsdc All right, http://dev.packages.vyos.net/repositories/current/vyos/pool/main/v/vyatta-wanloadbalance/vyatta-wanloadbalance_0.13.70+vyos2+current1_amd64.deb should solve the issue you are seeing. The code of the binary is good for another dozen bug tickets =)
Pls let me know if it works as expected, since I only tested your particular use case.
LBDecision::execute(): applying command to system: iptables -t mangle -A WANLOADBALANCE_PRE -i eth1 --proto all --destination ! 192.168.0.0/16 -m state --state NEW -j ISP_eth1
Bad argument `192.168.0.0/16'
Try `iptables -h' or 'iptables --help' for more information.
LBDecision::execute(): applying command to system: iptables -t mangle -A WANLOADBALANCE_PRE -i eth1 --proto all --destination ! 192.168.0.0/16 -j CONNMARK --restore-mark
Bad argument `192.168.0.0/16'
Try `iptables -h' or 'iptables --help' for more information.
hagbard changed the status of T1247: WAN load-balancing fail when !<x.x.x.x/x> configured in rules from Open to Confirmed.
Happens in /opt/vyatta/sbin/wan_lb.
gmurphy42 added a comment to T1246: VyOS 1.2.0 "openvpn-options" configuration does not allow quotes in values.
I checked the 'server' options for 'push-route' and 'name-server' and even with these configured as opposed to the openvpn-option configuration entry, it still gives the "Options error" complaint about the push command.
Feb 13 2019
Feb 13 2019
I checked and $ show system kernel-messages | grep pppoe0 did not return any output.
Feb 12 2019
Feb 12 2019
Feb 10 2019
Feb 10 2019
I will have to re-test tonight (when nobody else is using the Internet) and get some log output.
Interface name is ppp0 but will later be renamed to pppoe0
c-po changed the status of T1242: Error when setting 'pppoe 0 ipv6 address autoconf' from Open to Confirmed.
cpo@BR1# set interfaces ethernet eth1 pppoe 0 ipv6 address autoconf
[edit]
cpo@BR1# commit
[ interfaces ethernet eth1 pppoe 0 ipv6 address autoconf ]
cp: cannot create regular file ‘/etc/ppp/ipv6-up.d/50-vyos-pppoe0-autoconf’: No such file or directory
sed: can't read /etc/ppp/ipv6-up.d/50-vyos-pppoe0-autoconf: No such file or dire ctory
chmod: cannot access ‘/etc/ppp/ipv6-up.d/50-vyos-pppoe0-autoconf’: No such file or directory
Warning: IPv6 forwarding is currently enabled.
IPv6 address auto-configuration will not be performed
unless IPv6 forwarding is disabled.Feb 9 2019
Feb 9 2019
hagbard closed T1238: Wireguard allows invalid IP's as Resolved by committing Restricted Diffusion Commit.
Feb 8 2019
Feb 8 2019
Feb 6 2019
Feb 6 2019
I’ll add that I think this is happening because of the .252 and .254 addresses. The 254 address connects, but the 252 address is marked in a constant state of connecting.
Feb 5 2019
Feb 5 2019
In T1226#32102, @hagbard wrote:@Maltahl Let me know if you still need help, please. I put the task meanwhile on-hold.
Feb 4 2019
Feb 4 2019
hagbard changed the status of T1226: Wireguard not working between vyos routers 1.2.0 from In progress to On hold.
@Maltahl Let me know if you still need help, please. I put the task meanwhile on-hold.
EwaldvanGeffen added a comment to T1212: IPSec Tunnel to Cisco ASA drops reliably after 4.2GB transferred.
Configured protocols does not match Proposed protocols. Try without pfs configuration on the VyOS side.
hagbard closed T1225: wireguard implement 'set int wireguard wg0 peer name disable' to disable single peers as Resolved.
http://dev.packages.vyos.net/repositories/current/vyos/pool/main/v/vyos-1x/vyos-1x_1.2.0-12_all.deb next rolling release has it.
hagbard changed the status of T1226: Wireguard not working between vyos routers 1.2.0 from Open to In progress.
Feb 3 2019
Feb 3 2019
Feb 2 2019
Feb 2 2019
In T1226#32033, @hagbard wrote:@Maltahl Did you try the same with the rolling release? I don't see any issue with your config in particular, did you check that the wg traffic is actually getting to your router02?
@Maltahl Did you try the same with the rolling release? I don't see any issue with your config in particular, did you check that the wg traffic is actually getting to your router02?
That is not how wireguard works ? that is how ipsec and openvpn works.
This is how ipv4 works :) and have nothing to do with wireguard, ipsec etc. Actually the config you have applied eill in some situations work, but that relies on the handling of the packets inside the kernel and is not following the tcp/ip principles... If you take a look on the quick start guide on the wireguard webpage you se it there aswell... https://www.wireguard.com/quickstart/.
In T1226#32008, @runar wrote:Hi! I see that your tunnels does not resides inside the same subnet, one devise is '10.0.90.1/24' and the other one '10.0.100.1/24'.. please move one of then to ip .2 in the subnet belonging to the other router.
Hi! I see that your tunnels does not resides inside the same subnet, one devise is '10.0.90.1/24' and the other one '10.0.100.1/24'.. please move one of then to ip .2 in the subnet belonging to the other router.
Feb 1 2019
Feb 1 2019
Forgot to add version for both routers, sorry.
hagbard triaged T1225: wireguard implement 'set int wireguard wg0 peer name disable' to disable single peers as Normal priority.
Jan 31 2019
Jan 31 2019
Jan 30 2019
Jan 30 2019
Fix: https://github.com/vyos/vyos-1x/commit/2f70340179a64d5936c32cc3c0d6d7f6f04054d0 applied, pkg build currently running.
Too add, routes are present in FRR
hagbard changed the status of T1217: 1.2.0 LTS cant delete wireguard wg0 interface from Confirmed to In progress.
Bug confirmed.
hagbard changed the status of T1217: 1.2.0 LTS cant delete wireguard wg0 interface from Open to Confirmed.
fma@glos1ce1dk:~$ sh ver Version: VyOS 1.2.0 Built by: Sentrium S.L. Built on: Sun 27 Jan 2019 19:08 UTC Build ID: 795d6338-c1ce-4ebb-992f-d064f5af9309
I can't replicate it, but I'm using also the rolling release.
Can you please provide the output of:
njh renamed T1214: Add `ipaddrcheck` to the packages directory from Add `ipaddrcheck ` to the packages directory to Add `ipaddrcheck` to the packages directory.
mdsmds edited projects for T1213: ddclient not functional, added: VyOS 1.2 Crux; removed VyOS 1.2 Crux ( VyOS 1.2.0-rc11).
Jan 29 2019
Jan 29 2019
kroy renamed T1212: IPSec Tunnel to Cisco ASA drops reliably after 4.2GB transferred from IPSec Tunnel to Cisco ASA drops after exactly 4.2GB transferred to IPSec Tunnel to Cisco ASA drops reliably after 4.2GB transferred.
kroy updated the task description for T1212: IPSec Tunnel to Cisco ASA drops reliably after 4.2GB transferred.
kroy updated the task description for T1212: IPSec Tunnel to Cisco ASA drops reliably after 4.2GB transferred.
Jan 28 2019
Jan 28 2019
thinkl33t updated the task description for T1211: Blank hostnames from dhcpd are able to bring down DNS.
thinkl33t created T1211: Blank hostnames from dhcpd are able to bring down DNS in the S1 VyOS Public space.
Jan 27 2019
Jan 27 2019
@UnicronNL Thank you very much, that is really useful to know.
If you manually partition you need to keep in mind 2 things.
the filesystem label needs to be "persistence" (mkfs.ext4 < device > -L persistence)
and in the root of the filesystem you must create a persistence.conf file containing "/ union"
(echo "/ union" > /persistence.conf) on your partition meat for vyos.
syncer renamed T1194: cronjob is being setup even if not saved from conjob is being setup even if not saved to cronjob is being setup even if not saved.
Jan 26 2019
Jan 26 2019