Hi!

Broken since: relay_udp.c,v 1.43. Worked before. I tried to fix it but quickly 
ran out of time and changed it from dns relay to redirect.

Rivo

On 22/02/2017, 00:17, "[email protected] on behalf of Michael W. Lucas" 
<[email protected] on behalf of [email protected]> wrote:

    Hi,
    
    Running 6.0 snapshot from 5 Feb on amd64, and experimenting with
    relayd.
    
    I set up a DNS cluster using redirects, as per relayd.conf(5). Worked
    fine, so I'm pretty sure the DNS servers behind my relayd box work.
    
    The man page says that relayd has a relay protocol for DNS, that
    randomizes query IDs. Cool idea, let's try it. My relayd.conf now
    looks like so:
    
    --
    table <dns> { 192.0.2.101 192.0.2.102 }
    dns protocol dnsfix
    relay dns {
            listen on 203.0.113.213 port 53
            forward to <dns> port 53 check tcp
            protocol dnsfix
    }
    --
    
    
    With "protocol dnsfix" present, relayd listens on UDP only. I'm
    guessing using relayd's DNS protocol makes this happen. Which would
    make sense, you don't need it for TCP queries.
    
    So let's try to run this critter.
    
    # relayd -dvvvv
    startup
    socket_rlimit: max open files 1024
    socket_rlimit: max open files 1024
    pfe: filter init done
    socket_rlimit: max open files 1024
    socket_rlimit: max open files 1024
    relayd_tls_ticket_rekey: rekeying tickets
    relay_privinit: adding relay dns
    protocol 1: name dnsfix
            flags: used, relay flags:
            tls session tickets: enabled
            type: dns
    hce_notify_done: 192.0.2.101 (tcp connect ok)
    host 192.0.2.101, check tcp (4ms,tcp connect ok), state unknown -> up, 
availability 100.00%
    hce_notify_done: 192.0.2.102 (tcp connect ok)
    host 192.0.2.102, check tcp (6ms,tcp connect ok), state unknown -> up, 
availability 100.00%
    pfe_dispatch_hce: state 1 for host 1 192.0.2.101
    pfe_dispatch_hce: state 1 for host 2 192.0.2.102
    adding 2 hosts from table dns:53
    adding 2 hosts from table dns:53
    relay_launch: running relay dns
    relay_launch: running relay dns
    adding 2 hosts from table dns:53
    relay_launch: running relay dns
    
    I make a DNS query from a client, say to google.com or my site or
    whatever, and get:
    
    lost child: pid 779 terminated; signal 11
    hce exiting, pid 61465
    pfe exiting, pid 93428
    ca exiting, pid 1166
    ca exiting, pid 11360
    ca exiting, pid 57827
    lost child: pid 38872 terminated; signal 11
    lost child: pid 57998 terminated; signal 11
    parent terminating, pid 76339
    
    Am I abusing this program? Or is this a real crash?
    
    Thanks,
    ==ml
    
    
    -- 
    Michael W. Lucas    Twitter @mwlauthor 
    nonfiction: https://www.michaelwlucas.com/
    fiction: https://www.michaelwarrenlucas.com/
    blog: http://blather.michaelwlucas.com/
    
    

Reply via email to