Netgate Discussion Forum
    • Categories
    • Recent
    • Tags
    • Popular
    • Users
    • Search
    • Register
    • Login

    Dhcrelay problem - tun0: not found

    Scheduled Pinned Locked Moved DHCP and DNS
    1 Posts 1 Posters 1.3k Views
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • O
      Oroboros
      last edited by

      I've assigned my OpenVPN tun0 interface as Opt2 and setup firewall rules on it. I even have openospfd running over tun0 now (which required hand-editing config, but that is another story).

      But, dhcrelay refuses to start and listen on tun0 - requests go out over it just fine but replies are ignored.

      If I start it by hand I get the cryptic 'tun0: not found' which is also what gets logged in the system logs when started automatically:

      /usr/local/sbin/dhcrelay -i tun0 -i rl2 172.16.4.1

      Internet Systems Consortium DHCP Relay Agent V3.0.7
      Copyright 2004-2008 Internet Systems Consortium.
      All rights reserved.
      For info, please visit http://www.isc.org/sw/dhcp/
      Listening on BPF/rl2/00:40:48:b2:97:1f
      Sending on  BPF/rl2/00:40:48:b2:97:1f
      tun0: not found

      The tun0 is there, and is functional:

      ifconfig tun0

      tun0: flags=8051 <up,pointopoint,running,multicast>metric 0 mtu 1500
              inet6 fe80::240:48ff:feb2:9721%tun0 prefixlen 64 scopeid 0x8
              inet 10.40.41.2 –> 10.40.41.1 netmask 0xffffffff
              Opened by PID 406

      ping 10.40.41.1

      PING 10.40.41.1 (10.40.41.1): 56 data bytes
      64 bytes from 10.40.41.1: icmp_seq=0 ttl=64 time=68.303 ms
      64 bytes from 10.40.41.1: icmp_seq=1 ttl=64 time=68.945 ms
      ^C
      --- 10.40.41.1 ping statistics ---
      2 packets transmitted, 2 packets received, 0.0% packet loss
      round-trip min/avg/max/stddev = 68.303/68.624/68.945/0.321 ms

      I do have 4 total bpf devices on the system (1.2.3-RELEASE on the regular pfsense platform):

      ls -l /var/dhcpd/dev/bpf*

      crw–-----  1 dhcpd  _dhcp    0,  96 Feb  6 14:18 /var/dhcpd/dev/bpf0
      crw-------  1 dhcpd  _dhcp    0, 104 Feb  6 14:18 /var/dhcpd/dev/bpf1
      crw-------  1 dhcpd  _dhcp    0, 105 Feb  6 14:18 /var/dhcpd/dev/bpf2
      crw-------  1 dhcpd  _dhcp    0, 106 Feb  8 15:52 /var/dhcpd/dev/bpf3

      ls -l /dev/bpf*

      crw-------  1 root  wheel    0,  96 Feb  6 14:18 /dev/bpf0
      crw-------  1 root  wheel    0, 104 Feb  6 14:18 /dev/bpf1
      crw-------  1 root  wheel    0, 105 Feb  6 14:18 /dev/bpf2
      crw-------  1 root  wheel    0, 106 Feb  8 15:52 /dev/bpf3

      I'm guessing that bpf3 is the one that corresponds to tun0, given the difference in dates?

      date

      Mon Feb  8 16:25:03 MST 2010

      But my OpenVPN tunnel has been up for two days? I'm certain of that fact, so that date on bpf3 makes no sense in relation to anything on the system.</up,pointopoint,running,multicast>

      1 Reply Last reply Reply Quote 0
      • First post
        Last post
      Copyright 2025 Rubicon Communications LLC (Netgate). All rights reserved.