Ok. I will try to use containers, this good idea.
Containers will be more predictable and stable I suppose.
- Queries
- All Stories
- Search
- Advanced Search
- Transactions
- Transaction Logs
Advanced Search
Dec 16 2020
Yes I know that I must install printer driver. I successfully solved this problem long time ago by using additional partition. And YES I KNOW that VyOS is not a general server operating system. But some time convenient use ONE universal host instead two or more.
I prefer build images with some additional packages, such as cups. For example in order to administer printer I should add user to group lpadmin. In releases 1.2.x it was easy, but now I necessary after each update do it manually.
Dec 11 2020
I checked.
In version 1.3-rolling-202012110217 issue fixed.
Dec 10 2020
Jan 4 2019
Today I maked new ISOs. Now FTP and PPTP conntrack modules work as expected!
Problem resolved for me.
Dec 28 2018
I suppose problem in conntrack modules. Not only PPTP doesn't work. Publishing of FTP server after upgrade to version 1.2.0 from 1.1.8 also stop working. Disabling/Enabling ftp conntrack do not solve problem too.
Dec 27 2018
Oct 8 2018
I checked issue with and without IPSEC/vti.
Without vti arp worked fine. Then I applied config with vti router began to respond for all arp requests with all own MACs.
Oct 7 2018
I checked image vyos-1.2.0-rolling+201810071039-amd64.iso kernel 4.14.65 work fine. Router respond only for own requests.
Oct 6 2018
I prepared config and pcap file. I removed e100 NIC from bridge, however problem present. Windows can't get address nor static neither dynamic. Windows determined it as address conflict.
Oct 4 2018
I have same issue with bridge, wich consist of Intel NICs (drivers igb and e100). Router responding for all arp requests.
My NICs are: Intel Corporation 82575GB Gigabit Network Connection (rev 02) and Intel Corporation 82557/8/9/0/1 Ethernet Pro 100 (rev 08)