Page 2 of 4 FirstFirst 1234 LastLast
Results 11 to 20 of 36
  1. #11
    Untangle Ninja Jim.Alles's Avatar
    Join Date
    Jul 2008
    Location
    Central PA
    Posts
    1,513

    Default

    And do you have anything in Custom dnsmasq options, at Network / [Advanced] [DNS & DHCP]?

  2. #12
    Untangle Junkie dmorris's Avatar
    Join Date
    Nov 2006
    Location
    San Carlos, CA
    Posts
    17,746

    Default

    Quote Originally Posted by tucansam View Post
    tcpdump: verbose output suppressed, use -v or -vv for full protocol decode
    listening on eth1, link-type EN10MB (Ethernet), capture size 262144 bytes
    17:01:47.819122 cc:c0:79:61:ae:fd > ff:ff:ff:ff:ff:ff, ethertype IPv4 (0x0800), length 332: 0.0.0.0.68 > 255.255.255.255.67: BOOTP/DHCP, Request from cc:c0:79:61:ae:fd, length 290
    17:01:47.819464 1c:1b:0d:62:cc:cf > cc:c0:79:61:ae:fd, ethertype IPv4 (0x0800), length 343: 192.168.0.1.67 > 192.168.0.24.68: BOOTP/DHCP, Reply, length 301
    17:01:47.876018 cc:c0:79:61:ae:fd > ff:ff:ff:ff:ff:ff, ethertype IPv4 (0x0800), length 344: 0.0.0.0.68 > 255.255.255.255.67: BOOTP/DHCP, Request from cc:c0:79:61:ae:fd, length 302
    17:01:47.880091 1c:1b:0d:62:cc:cf > cc:c0:79:61:ae:fd, ethertype IPv4 (0x0800), length 343: 192.168.0.1.67 > 192.168.0.24.68: BOOTP/DHCP, Reply, length 301
    17:02:59.088241 7c:5c:f8:69:17:ca > ff:ff:ff:ff:ff:ff, ethertype IPv4 (0x0800), length 342: 192.168.0.53.68 > 255.255.255.255.67: BOOTP/DHCP, Request from 7c:5c:f8:69:17:ca, length 300
    17:02:59.088988 1c:1b:0d:62:cc:cf > 7c:5c:f8:69:17:ca, ethertype IPv4 (0x0800), length 342: 192.168.0.1.67 > 192.168.0.53.68: BOOTP/DHCP, Reply, length 300
    17:03:24.896766 88:19:08:23:95:8c > ff:ff:ff:ff:ff:ff, ethertype IPv4 (0x0800), length 342: 0.0.0.0.68 > 255.255.255.255.67: BOOTP/DHCP, Request from 88:19:08:23:95:8c, length 300
    17:03:24.903176 1c:1b:0d:62:cc:cf > 88:19:08:23:95:8c, ethertype IPv4 (0x0800), length 343: 192.168.0.1.67 > 192.168.0.70.68: BOOTP/DHCP, Reply, length 301
    17:04:07.764555 88:19:08:23:95:8c > ff:ff:ff:ff:ff:ff, ethertype IPv4 (0x0800), length 342: 0.0.0.0.68 > 255.255.255.255.67: BOOTP/DHCP, Request from 88:19:08:23:95:8c, length 300
    17:04:07.767682 1c:1b:0d:62:cc:cf > 88:19:08:23:95:8c, ethertype IPv4 (0x0800), length 343: 192.168.0.1.67 > 192.168.0.70.68: BOOTP/DHCP, Reply, length 301


    standby for screen shot
    Of these, which is incorrect?
    They all look correct based on your reservations screenshot I think.
    Attention: Support and help on the Untangle Forums is provided by volunteers and community members like yourself.
    If you need Untangle support please call or email support@untangle.com

  3. #13
    Untangle Ninja Jim.Alles's Avatar
    Join Date
    Jul 2008
    Location
    Central PA
    Posts
    1,513

    Default

    Quote Originally Posted by tucansam View Post
    under untangle, very few static assignments "stuck." usually (almost always) all clients would grab an address from the public pool (ie 192.168.1.100-110), ignoring the assignment the dhcp server was supposed to hand out (is 00:00:00:00:00:01 gets 192.168.1.1 etc)

    any ideas?
    Yeah, it is a logical thing, I thought:
    dnsmasq expects the entire DHCP range to be defined for it, and the DHCP reservations {Static DHCP Entries} must be within that range.
    But the dnsmasq documentation states there is no such restriction.

    Static IP addresses, defined at the host, do not require DHCP, and must be outside of that range.

    As a convention, or landmark in my head, I reserve the first 99 IP's to static assignment on the hosts, and give .100 to .199 (at least) to DHCP. .250 would be good, too at the top end.
    Last edited by Jim.Alles; 08-05-2019 at 07:26 AM. Reason: clarification
    theoak likes this.

  4. #14
    Untangle Junkie dmorris's Avatar
    Join Date
    Nov 2006
    Location
    San Carlos, CA
    Posts
    17,746

    Default

    Quote Originally Posted by Jim.Alles View Post
    Yeah, it is a logical thing, dnsmasq expects the entire DHCP range to be defined for it, and the static DHCP assignments must be within that range. Static IP addresses, defined at the host, do not require DHCP, and must be outside of that range.
    thats not true according to the docs though
    http://www.thekelleys.org.uk/dnsmasq...smasq-man.html
    Jim.Alles and f1assistance like this.
    Attention: Support and help on the Untangle Forums is provided by volunteers and community members like yourself.
    If you need Untangle support please call or email support@untangle.com

  5. #15
    Untangle Ninja Jim.Alles's Avatar
    Join Date
    Jul 2008
    Location
    Central PA
    Posts
    1,513

    Default

    yes, I see.
    the hosts must be within the subnet, however. It becomes less certain when dnsmasq had to guess at the subnet, and decides it is a class C, for instance.

    HUH SMH

  6. #16
    Untangler
    Join Date
    Aug 2011
    Posts
    95

    Default

    The bold lines look like formerly reserved addresses turning into addresses from the pool. There are more lines to highlight but I am trying to get out the door and the forum freaked out about message length. I'll post screenshots of the other config screens later.

    Overnight:

    17:33:07.004867 1c:1b:0d:62:cc:cf > 08:05:81:68:5c:60, ethertype IPv4 (0x0800), length 343: 192.168.0.1.67 > 192.168.0.157.68: BOOTP/DHCP, Reply, length 301
    17:33:07.047776 08:05:81:68:5c:60 > ff:ff:ff:ff:ff:ff, ethertype IPv4 (0x0800), length 590: 0.0.0.0.68 > 255.255.255.255.67: BOOTP/DHCP, Request from 08:05:81:68:5c:60, length 548
    17:33:07.051791 1c:1b:0d:62:cc:cf > 08:05:81:68:5c:60, ethertype IPv4 (0x0800), length 343: 192.168.0.1.67 > 192.168.0.157.68: BOOTP/DHCP, Reply, length 301

    17:35:47.552958 94:e3:6d:76:31:29 > ff:ff:ff:ff:ff:ff, ethertype IPv4 (0x0800), length 342: 192.168.0.201.68 > 255.255.255.255.67: BOOTP/DHCP, Request from 94:e3:6d:76:31:29, length 300
    17:35:47.557921 1c:1b:0d:62:cc:cf > 94:e3:6d:76:31:29, ethertype IPv4 (0x0800), length 342: 192.168.0.1.67 > 192.168.0.201.68: BOOTP/DHCP, Reply, length 300
    17:44:42.188460 94:53:30:b3:be:c1 > 1c:1b:0d:62:cc:cf, ethertype IPv4 (0x0800), length 352: 192.168.0.77.68 > 192.168.0.1.67: BOOTP/DHCP, Request from 94:53:30:b3:be:c1, length 310
    17:49:49.403113 cc:c0:79:61:ae:fd > 1c:1b:0d:62:cc:cf, ethertype IPv4 (0x0800), length 332: 192.168.0.24.68 > 192.168.0.1.67: BOOTP/DHCP, Request from cc:c0:79:61:ae:fd, length 290
    17:49:49.407987 1c:1b:0d:62:cc:cf > cc:c0:79:61:ae:fd, ethertype IPv4 (0x0800), length 343: 192.168.0.1.67 > 192.168.0.24.68: BOOTP/DHCP, Reply, length 301
    17:52:24.782907 3c:a3:08:8b:d1:00 > 1c:1b:0d:62:cc:cf, ethertype IPv4 (0x0800), length 342: 192.168.0.204.68 > 192.168.0.1.67: BOOTP/DHCP, Request from 3c:a3:08:8b:d1:00, length 300
    17:52:24.788265 1c:1b:0d:62:cc:cf > 3c:a3:08:8b:d1:00, ethertype IPv4 (0x0800), length 342: 192.168.0.1.67 > 192.168.0.204.68: BOOTP/DHCP, Reply, length 300
    17:54:25.765330 88:19:08:d0:32:2c > ff:ff:ff:ff:ff:ff, ethertype IPv4 (0x0800), length 342: 192.168.0.80.68 > 255.255.255.255.67: BOOTP/DHCP, Request from 88:19:08:d0:32:2c, length 300
    17:54:25.765938 1c:1b:0d:62:cc:cf > ff:ff:ff:ff:ff:ff, ethertype IPv4 (0x0800), length 342: 192.168.0.1.67 > 255.255.255.255.68: BOOTP/DHCP, Reply, length 300
    17:54:25.778631 88:19:08:d0:32:2c > ff:ff:ff:ff:ff:ff, ethertype IPv4 (0x0800), length 342: 0.0.0.0.68 > 255.255.255.255.67: BOOTP/DHCP, Request from 88:19:08:d0:32:2c, length 300
    17:54:27.569513 88:19:08:d0:32:2c > ff:ff:ff:ff:ff:ff, ethertype IPv4 (0x0800), length 342: 0.0.0.0.68 > 255.255.255.255.67: BOOTP/DHCP, Request from 88:19:08:d0:32:2c, length 300
    17:54:28.032583 1c:1b:0d:62:cc:cf > 88:19:08:d0:32:2c, ethertype IPv4 (0x0800), length 343: 192.168.0.1.67 > 192.168.0.156.68: BOOTP/DHCP, Reply, length 301
    17:54:28.032853 1c:1b:0d:62:cc:cf > 88:19:08:d0:32:2c, ethertype IPv4 (0x0800), length 343: 192.168.0.1.67 > 192.168.0.156.68: BOOTP/DHCP, Reply, length 301
    17:54:29.154292 88:19:08:d0:32:2c > ff:ff:ff:ff:ff:ff, ethertype IPv4 (0x0800), length 342: 0.0.0.0.68 > 255.255.255.255.67: BOOTP/DHCP, Request from 88:19:08:d0:32:2c, length 300
    17:54:29.161079 1c:1b:0d:62:cc:cf > 88:19:08:d0:32:2c, ethertype IPv4 (0x0800), length 343: 192.168.0.1.67 > 192.168.0.156.68: BOOTP/DHCP, Reply, length 301
    17:55:26.725943 88:19:08:d0:32:2c > ff:ff:ff:ff:ff:ff, ethertype IPv4 (0x0800), length 342: 0.0.0.0.68 > 255.255.255.255.67: BOOTP/DHCP, Request from 88:19:08:d0:32:2c, length 300
    17:55:26.726446 1c:1b:0d:62:cc:cf > 88:19:08:d0:32:2c, ethertype IPv4 (0x0800), length 343: 192.168.0.1.67 > 192.168.0.156.68: BOOTP/DHCP, Reply, length 301
    17:55:28.608477 88:19:08:d0:32:2c > ff:ff:ff:ff:ff:ff, ethertype IPv4 (0x0800), length 342: 0.0.0.0.68 > 255.255.255.255.67: BOOTP/DHCP, Request from 88:19:08:d0:32:2c, length 300
    17:56:28.163453 88:19:08:d0:32:2c > ff:ff:ff:ff:ff:ff, ethertype IPv4 (0x0800), length 342: 0.0.0.0.68 > 255.255.255.255.67: BOOTP/DHCP, Request from 88:19:08:d0:32:2c, length 300
    17:56:28.167433 1c:1b:0d:62:cc:cf > 88:19:08:d0:32:2c, ethertype IPv4 (0x0800), length 343: 192.168.0.1.67 > 192.168.0.156.68: BOOTP/DHCP, Reply, length 301
    17:58:07.146756 08:05:81:68:5c:60 > ff:ff:ff:ff:ff:ff, ethertype IPv4 (0x0800), length 590: 0.0.0.0.68 > 255.255.255.255.67: BOOTP/DHCP, Request from 08:05:81:68:5c:60, length 548
    17:58:07.151817 1c:1b:0d:62:cc:cf > 08:05:81:68:5c:60, ethertype IPv4 (0x0800), length 343: 192.168.0.1.67 > 192.168.0.157.68: BOOTP/DHCP, Reply, length 301

    17:58:20.681767 94:e3:6d:76:31:29 > 1c:1b:0d:62:cc:cf, ethertype IPv4 (0x0800), length 342: 192.168.0.201.68 > 192.168.0.1.67: BOOTP/DHCP, Request from 94:e3:6d:76:31:29, length 300
    17:58:20.687661 1c:1b:0d:62:cc:cf > 94:e3:6d:76:31:29, ethertype IPv4 (0x0800), length 342: 192.168.0.1.67 > 192.168.0.201.68: BOOTP/DHCP, Reply, length 300
    18:07:37.202664 94:53:30:b3:be:c1 > 1c:1b:0d:62:cc:cf, ethertype IPv4 (0x0800), length 352: 192.168.0.77.68 > 192.168.0.1.67: BOOTP/DHCP, Request from 94:53:30:b3:be:c1, length 310
    18:07:37.208641 1c:1b:0d:62:cc:cf > 94:53:30:b3:be:c1, ethertype IPv4 (0x0800), length 368: 192.168.0.1.67 > 192.168.0.77.68: BOOTP/DHCP, Reply, length 326
    18:10:11.584551 7c:5c:f8:69:17:ca > 1c:1b:0d:62:cc:cf, ethertype IPv4 (0x0800), length 348: 192.168.0.53.68 > 192.168.0.1.67: BOOTP/DHCP, Request from 7c:5c:f8:69:17:ca, length 306
    18:10:11.589499 1c:1b:0d:62:cc:cf > 7c:5c:f8:69:17:ca, ethertype IPv4 (0x0800), length 367: 192.168.0.1.67 > 192.168.0.53.68: BOOTP/DHCP, Reply, length 325
    18:12:00.482807 4c:b1:99:48:7e:56 > ff:ff:ff:ff:ff:ff, ethertype IPv4 (0x0800), length 342: 192.168.0.78.68 > 255.255.255.255.67: BOOTP/DHCP, Request from 4c:b1:99:48:7e:56, length 300
    18:12:00.483567 1c:1b:0d:62:cc:cf > ff:ff:ff:ff:ff:ff, ethertype IPv4 (0x0800), length 342: 192.168.0.1.67 > 255.255.255.255.68: BOOTP/DHCP, Reply, length 300
    18:12:00.652169 4c:b1:99:48:7e:56 > ff:ff:ff:ff:ff:ff, ethertype IPv4 (0x0800), length 342: 0.0.0.0.68 > 255.255.255.255.67: BOOTP/DHCP, Request from 4c:b1:99:48:7e:56, length 300
    18:12:02.450124 4c:b1:99:48:7e:56 > ff:ff:ff:ff:ff:ff, ethertype IPv4 (0x0800), length 342: 0.0.0.0.68 > 255.255.255.255.67: BOOTP/DHCP, Request from 4c:b1:99:48:7e:56, length 300
    18:12:03.174843 1c:1b:0d:62:cc:cf > 4c:b1:99:48:7e:56, ethertype IPv4 (0x0800), length 343: 192.168.0.1.67 > 192.168.0.154.68: BOOTP/DHCP, Reply, length 301
    18:12:03.175305 1c:1b:0d:62:cc:cf > 4c:b1:99:48:7e:56, ethertype IPv4 (0x0800), length 343: 192.168.0.1.67 > 192.168.0.154.68: BOOTP/DHCP, Reply, length 301
    18:12:04.261026 4c:b1:99:48:7e:56 > ff:ff:ff:ff:ff:ff, ethertype IPv4 (0x0800), length 342: 0.0.0.0.68 > 255.255.255.255.67: BOOTP/DHCP, Request from 4c:b1:99:48:7e:56, length 300
    18:12:04.266938 1c:1b:0d:62:cc:cf > 4c:b1:99:48:7e:56, ethertype IPv4 (0x0800), length 343: 192.168.0.1.67 > 192.168.0.154.68: BOOTP/DHCP, Reply, length 301

    18:12:40.010551 00:00:ec:68:91:4d > 1c:1b:0d:62:cc:cf, ethertype IPv4 (0x0800), length 342: 192.168.0.22.68 > 192.168.0.1.67: BOOTP/DHCP, Request from 00:00:ec:68:91:4d, length 300
    18:12:40.014324 1c:1b:0d:62:cc:cf > 00:00:ec:68:91:4d, ethertype IPv4 (0x0800), length 343: 192.168.0.1.67 > 192.168.0.22.68: BOOTP/DHCP, Reply, length 301
    18:13:49.793201 cc:c0:79:61:ae:fd > 1c:1b:0d:62:cc:cf, ethertype IPv4 (0x0800), length 332: 192.168.0.24.68 > 192.168.0.1.67: BOOTP/DHCP, Request from cc:c0:79:61:ae:fd, length 290
    18:13:49.797917 1c:1b:0d:62:cc:cf > cc:c0:79:61:ae:fd, ethertype IPv4 (0x0800), length 343: 192.168.0.1.67 > 192.168.0.24.68: BOOTP/DHCP, Reply, length 301
    18:14:43.817531 3c:a3:08:8b:d1:00 > 1c:1b:0d:62:cc:cf, ethertype IPv4 (0x0800), length 342: 192.168.0.204.68 > 192.168.0.1.67: BOOTP/DHCP, Request from 3c:a3:08:8b:d1:00, length 300
    18:14:43.823708 1c:1b:0d:62:cc:cf > 3c:a3:08:8b:d1:00, ethertype IPv4 (0x0800), length 342: 192.168.0.1.67 > 192.168.0.204.68: BOOTP/DHCP, Reply, length 300
    18:21:20.876158 94:e3:6d:76:31:29 > 1c:1b:0d:62:cc:cf, ethertype IPv4 (0x0800), length 342: 192.168.0.201.68 > 192.168.0.1.67: BOOTP/DHCP, Request from 94:e3:6d:76:31:29, length 300
    18:21:20.880231 1c:1b:0d:62:cc:cf > 94:e3:6d:76:31:29, ethertype IPv4 (0x0800), length 342: 192.168.0.1.67 > 192.168.0.201.68: BOOTP/DHCP, Reply, length 300
    18:21:43.823532 88:19:08:d0:32:2c > 1c:1b:0d:62:cc:cf, ethertype IPv4 (0x0800), length 342: 192.168.0.156.68 > 192.168.0.1.67: BOOTP/DHCP, Request from 88:19:08:d0:32:2c, length 300
    18:21:43.829401 1c:1b:0d:62:cc:cf > 88:19:08:d0:32:2c, ethertype IPv4 (0x0800), length 343: 192.168.0.1.67 > 192.168.0.156.68: BOOTP/DHCP, Reply, length 301
    18:23:07.323707 08:05:81:68:5c:60 > ff:ff:ff:ff:ff:ff, ethertype IPv4 (0x0800), length 590: 0.0.0.0.68 > 255.255.255.255.67: BOOTP/DHCP, Request from 08:05:81:68:5c:60, length 548
    18:23:07.328982 1c:1b:0d:62:cc:cf > 08:05:81:68:5c:60, ethertype IPv4 (0x0800), length 343: 192.168.0.1.67 > 192.168.0.157.68: BOOTP/DHCP, Reply, length 301
    18:30:36.243273 94:53:30:b3:be:c1 > 1c:1b:0d:62:cc:cf, ethertype IPv4 (0x0800), length 352: 192.168.0.77.68 > 192.168.0.1.67: BOOTP/DHCP, Request from 94:53:30:b3:be:c1, length 310

    rom 3c:a3:08:8b:d1:00, length 300

  7. #17
    Untangler
    Join Date
    Aug 2011
    Posts
    95

    Default

    Can confirm that, overnight, three hosts -- two Apple and one Roku -- didn't care for their reserved addresses and picked up addresses from the pool.

  8. #18
    Untangler
    Join Date
    Aug 2011
    Posts
    95

  9. #19
    Untangler jcoffin's Avatar
    Join Date
    Aug 2008
    Location
    Sunnyvale, CA
    Posts
    7,991

    Default

    NAT should not be checked for the Internal interface unless you have a specific reason. Only use that on WANs



    Do you have any settings in /admin/index.do#config/network/advanced/dns_and_dhcp ? Is the Untangle hardware or a VM? What is the MAC address of the Internal NIC?

    192.168.0.1.67 > 192.168.0.204.68 Is this an IP listed in the static list?
    Jim.Alles likes this.
    Attention: Support and help on the Untangle Forums is provided by
    volunteers and community members like yourself.
    If you need Untangle support please call or email support@untangle.com

  10. #20
    Master Untangler
    Join Date
    Aug 2016
    Posts
    193

    Default

    Quote Originally Posted by Jim.Alles View Post
    ...
    As a convention, or landmark in my head, I reserve the first 99 IP's to static, and give .100 to .199 (at least) to DHCP. .250 would be good, too at the top end.
    My range the first 150 for static ... and then .151 to .250 for DHCP.

    Never had a problem when I define static outside of DHCP range.
    Untangle 14.2.1 (Build: 14.2.1.20190814) (Kernel: 4.9.0-9-untangle-amd64)
    QOTOM-Q355G4
    1.6-2.7 GHz Intel I5 5250U, 128GB SSD mSATA, 8GB RAM DDR3L, 4xRJ-45 Intel I211AT 10/100/1000 Controller

Page 2 of 4 FirstFirst 1234 LastLast

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •  

SEO by vBSEO 3.6.0 PL2