@Dataforce @fetzerms
ip rule "from" already in CLI T439
- Feed Queries
- All Stories
- Search
- Feed Search
- Transactions
- Transaction Logs
All Stories
Nov 22 2020
Okay, then I can merge this service into NAT66
That we can deal with later on when it‘s needed
@pasik Can you check if it solves your expectation?
I can consider migrating to the implementation of nat66, but I'm not sure if there is a case where the nat66 feature does not need to be enabled, but NDP proxy needs to be enabled
I still have the opinion that NDP proxy should be automatically configured when configuring nat66 as by then all interfaces and directions of the translation are known and the user must not configure any additional daemon.
Nov 21 2020
Thanks, works now.
@danielpo thanks foe the config. A new rolling containig a fix for this issue was just published. A smoketest will be added today to ensure this wont happen again.
Nov 20 2020
authentication {
password xxxx
username xxxxx
}
device-type tun
encryption {
cipher aes256
}
firewall {
in {
ipv6-name DENYv6_IN
name DENY_IN
}
local {
ipv6-name DENYv6_IN
name DENY_IN
}
}
hash sha256
mode client
openvpn-option "key-direction 1"
openvpn-option route-nopull
persistent-tunnel
protocol tcp-active
remote-host 1.2.3.4
remote-host 1.2.3.5
remote-port 1195
tls {
ca-cert-file /config/auth/cert.ca
auth-file /config/auth/tls-auth
tls-version-min 1.2
}Please show us your config
Now this error appear when trying the latest image:
@dmbaturin @artooro Come on, remember not to forget NAT46
@c-po I am thinking, although it is not possible to incorporate NAT66, whether we can prioritize how to improve and incorporate NDP Proxy
DNS domain name servers are always requested from the server but must be explicitly "allowed" by set systems name-servers-dhcp
Running Docker on 1.3 rolling works, but there is no integration with the docker bridge interfaces and docker iptables rules obviously.
My goal was to run Traefik and Pihole and it works so far.
https://gist.github.com/Cremator/183c1a4d24e7812f94ec4bd41f7718b3
https://marc.info/?l=dhcp-hackers&m=128755776831463 describes the solution.
Setting ClientName, ClientIp, ClientMac, ClientDomain on release and expire fails, and there's no need for that since they are already known.
Simply removing all "set" commands in the release and expire section fixes this bug and restores the desired behaviour that i.e. the leases are removed from /etc/hosts.
I just saw the patch above for how to fix this and yes, with that line changed to sudo it now works correctly.
Thanks!
Nov 19 2020
I have adjust the logic which now sets the interface MAC address before any other parameter. Using the OSI model this makes sense as the MAC layer is below IP.