User Details
- User Since
- Aug 3 2017, 1:55 PM (54 w, 2 d)
- Availability
- Available
Today
If we'd use
range {
start 172.16.0.1
stop 172.16.0.250
}this would be transparent for IPv4 and IPv6
Yesterday
Wed, Aug 15
Tue, Aug 14
Now using the following config, unfortunately my routers don't have that much traffic:
Mon, Aug 13
Could you please provide e.g. links to SRX docu/whitepapers?
Sat, Aug 11
Required packages should be added to this file: https://github.com/vyos/vyos-1x/blob/current/debian/control
Fri, Aug 10
Please put key geberation as usual under run generate vpn (openvpn key generationnuses the same subtree)
Wed, Aug 8
@begetan could you please retest?
# We need to generate an "interfaces=..." entry in the setup section # only if the underlying IPsec kernel code we are using is KLIPS. # If we are using NETKEY, the "interfaces=..." entry is essentially # not used, though we do need to include the line and the keyword # "%none" to keep the IPsec setup code from defaulting the entry.
Duplicate of T495
Sun, Jul 29
+1 for Constellations
Sat, Jul 21
Fri, Jul 20
Removing LKM support requires reweiting some scripts which do a modprobe upon configuring stuff, but I line the idea in general.
Jul 15 2018
Also user creation is handled in https://github.com/vyos/vyatta-cfg-system/blob/current/lib/Vyatta/Login/User.pm
Jul 12 2018
I'd go for /etc/logrotate.d
Jul 10 2018
Hi @panachoi thanks for the info and sharing your config. I was always interested in Netflow (what is it, what can I do with it). I'm happy to look into this but could you tell me any software which I can use to display (graphically would be the best) the flow result?
Jul 9 2018
Encrypted passwords depend on the engineID, or lets say it in other words - encrypted passwords are hashed/salted with the engine ID. Migrating the encrypted string to a different machine with a different engine ID will fail.
Jul 6 2018
Jul 5 2018
Jul 4 2018
My guess it that something is wrong with your terminal or you have some weird unprintable characters in it.
Please re-open if issue should occur again
cpo@LR1:~$ configure [edit] cpo@LR1# set system host-name foo [edit] cpo@LR1# run show version Version: VyOS 1.2.0-rolling+201807022212 cpo@LR1# show system host-name >host-name foo [edit] cpo@LR1# commit [edit]
Jul 1 2018
@Line2 thanks for retesting.
Jun 30 2018
Please retest with latest ISO
Just spawn a VyOS 1.1.8 VM and the ifAlias appears
Jun 29 2018
In general I like the idea.
Jun 28 2018
cpo@LR1:~$ show snmp mib ifmib ifAlias eth0 eth0: ifAlias = NET-MYBLL-MUCI-BACKBONE
Jun 27 2018
@Asteroza usually htop only gives you a snapshot about the current system behavior/missbehavior. For this kind of thing I use SNMP monitoring with libreNMS so I get a detailed graph + backlog about the routers utilisation.
Jun 26 2018
The "problem" is inherited from the old SNMP CLI definition which was re-generated in XML by me and is now generated here: https://github.com/vyos/vyos-1x/blob/current/interface-definitions/snmp.xml#L230-L237.
@begetan thanks for this detialed description.
Jun 24 2018
maybe you could assist us by trying the following steps on your system:
Jun 22 2018
cpo@LR1:~$ show version Version: VyOS 1.2.0-rolling+201806220337 Built by: autobuild@vyos.net Built on: Fri 22 Jun 2018 03:37 UTC Build ID: 02d18d8e-5aa4-4d62-b424-10092ea446de
There was a bug in show version some rolling releases back. Please update.
Jun 21 2018
Fix applied to current and helium branch (if there will be a 1.1.9 release)
cpo@LR1# set system flow-accounting netflow source-ip 192.168.253.13
[edit]
cpo@LR1# show system flow-accounting
+netflow {
+ source-ip 192.168.253.13
+}