Re: [Dnsmasq-discuss] Issues with multiple subnets on dnsmasq

2012-09-03 Thread subhranshu dwivedi
Thanks Ryan for replying,

I seriously need your help here,

We have dhcp ranges:-

dhcp-range=eth1,172.16.49.101,172.16.49.254,14400
dhcp-range=eth1,172.16.50.1,172.16.50.254,14400
dhcp-range=eth1,172.16.51.101,172.16.51.254,14400
dhcp-range=eth4,172.16.56.20,172.16.56.254,14400
dhcp-range=eth3,172.16.52.21,172.16.53.254,14400

So none of the machines pull the 172.16.48.x ip addresses, however they do
pull other ones like 49/50/51/52/56,apart from 49 series pulled from dhcp
and 48 series if forced manualy, all other can ping 172.16.48.4.

For all the series which we have setup on eth1, i.e

dhcp-range=eth1,172.16.49.101,172.16.49.254,14400
dhcp-range=eth1,172.16.50.1,172.16.50.254,14400
dhcp-range=eth1,172.16.51.101,172.16.51.254,14400

We are trying to setup *172.16.48.4* as gateway, it works fine for 50/51
ips pulled by hosts but, dont work for 49 series,
and subnet which its lying under in vlan is 255.255.252.0

on Untangle
route
-n
[root @ untangle]
Kernel IP routing table
Destination Gateway Genmask Flags Metric RefUse
Iface
192.0.2.0   0.0.0.0 255.255.255.0   U 0  00
dummy0
192.0.2.0   0.0.0.0 255.255.255.0   U 0  00 utun
172.16.57.0 0.0.0.0 255.255.255.0   U 0  00 eth0
172.16.56.0 0.0.0.0 255.255.255.0   U 0  00 eth4
172.16.52.0 0.0.0.0 255.255.254.0   U 0  00 eth3
172.16.48.0 0.0.0.0 255.255.254.0   U 0  00 eth2
172.16.48.0 0.0.0.0 255.255.252.0   U 0  00 eth1

ifconfig on host with 50

eth0  Link encap:Ethernet  HWaddr 00:18:8b:c3:f2:10
  inet addr:172.16.50.235  Bcast:172.16.51.255  Mask:255.255.252.0
  inet6 addr: fe80::218:8bff:fec3:f210/64 Scope:Link
  UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
  RX packets:123102 errors:0 dropped:10 overruns:0 frame:0
  TX packets:70439 errors:0 dropped:0 overruns:0 carrier:0
  collisions:0 txqueuelen:1000
  RX bytes:115719183 (115.7 MB)  TX bytes:7541314 (7.5 MB)
  Interrupt:17

loLink encap:Local Loopback
  inet addr:127.0.0.1  Mask:255.0.0.0
  inet6 addr: ::1/128 Scope:Host
  UP LOOPBACK RUNNING  MTU:16436  Metric:1
  RX packets:3477 errors:0 dropped:0 overruns:0 frame:0
  TX packets:3477 errors:0 dropped:0 overruns:0 carrier:0
  collisions:0 txqueuelen:0
  RX bytes:331477 (331.4 KB)  TX bytes:331477 (331.4 KB)

arp -a
? (172.16.48.147) at 00:0c:29:ce:46:7c [ether] on eth0
? (172.16.48.146) at 00:04:23:b0:92:d8 [ether] on eth0
? (172.16.48.4) at 00:04:23:c7:52:62 [ether] on eth0
? (172.16.48.1) at 00:1a:a2:24:73:c1 [ether] on eth0

Please suggest.


On Mon, Sep 3, 2012 at 10:28 PM, Ryan Chapman  wrote:

> On the host that pulls a 172.16.48 address, try a ping of 172.16.48.4 and
> then check the arp table to make sure it resolved to a hardware address.
>  If not, tcpdump arp traffic.
>
> It might be interesting to see what an ifconfig, "route -n" and "arp -a"
> look like on the 172.16.48 host...
>
>
> On Sep 3, 2012, at 7:29 AM, subhranshu dwivedi <
> subhranshu.dwiv...@erminsystems.com> wrote:
>
> Hi All,
>
> I have Untangle with DNS masq setup at my end,
>
> With interface:
>
> External
> eth0  Link encap:Ethernet  HWaddr 00:04:23:c7:52:63
>   inet addr:172.16.57.10  Bcast:172.16.57.255  Mask:255.255.255.0
>
> INTERNAL
> eth1  Link encap:Ethernet  HWaddr 00:04:23:c7:52:62
>   inet addr:172.16.48.4  Bcast:172.16.51.255  Mask:255.255.252.0
> DMZ
> eth2  Link encap:Ethernet  HWaddr 00:1b:21:0e:1f:46
>   inet addr:172.16.48.110  Bcast:172.16.49.255  Mask:255.255.254.0
>
> Extra ones:
> eth3  Link encap:Ethernet  HWaddr fc:75:16:8e:57:2b
>   inet addr:172.16.52.20  Bcast:172.16.53.255  Mask:255.255.254.0
>
> eth4  Link encap:Ethernet  HWaddr fc:75:16:8e:57:42
>   inet addr:172.16.56.2  Bcast:172.16.56.255  Mask:255.255.255.0
>
> Now my dnsmasq.conf,
>
> localise-queries
> server=202.56.224.135 # uplink.1
> server=59.144.127.16 # uplink.1
> expand-hosts
> addn-hosts=/etc/untangle-net-alpaca/dnsmasq-hosts
> no-hosts
> domain=bpl.netlink.com
> interface=eth1
> interface=eth3
> interface=eth4
> dhcp-range=eth1,172.16.49.101,172.16.49.254,14400
> dhcp-range=eth1,172.16.50.1,172.16.50.254,14400
> dhcp-range=eth1,172.16.51.101,172.16.51.254,14400
> dhcp-range=eth4,172.16.56.20,172.16.56.254,14400
> dhcp-range=eth3,172.16.52.21,172.16.53.254,14400
> dhcp-option=eth1,3,172.16.48.1
> dhcp-option=eth4,3,172.16.56.1
> dhcp-option=eth3,3,172.16.52.1
> dhcp-option=eth1,1,255.255.252.0
> dhcp-option=eth4,1,255.255.255.0
> dhcp-option=eth3,1,255.255.254.0
> dhcp-option=eth1,6,172.16.48.146,172.16.48.147
> dhcp-option=eth4,6,172.16.48.146,172.16.48.147
> dhcp-option=eth3,6,172.16.52.3,172.16.48.146
> dhcp-lease-max=500
> dhcp-host=00:13:02:a9:8b:57,172.16.48.106,2

[Dnsmasq-discuss] Problem getting dnsmasq to send a different default gateway to a host

2012-09-03 Thread Fadi

Hello,

Please be kind this is my first posting to this list.

I have spent hours trying to get this to work, but I seem to be missing
something.

I'm using the latest shibby build of TomatoUSB, and I want dnsmasq to send
the default gateway and dns server address of 192.168.0.55 to the host whose
MAC address is xx:xx:xx:xx:xx.

So I added this to the DNSmasq custom config:


dhcp-mac=red,xx:xx:xx:xx:xx:xx
dhcp-option=red,3,192.168.0.55
dhcp-option=red,6,192.168.0.55


This almost works. When I look at the DHCP OFFER packet in Wireshark,
dnsmasq is sending TWO default gateway (option 3) addresses, the
192.168.0.55 I specified above PLUS the router's 192.168.0.1 address.

How can I prevent it from sending the router's IP as well? Some hosts on the
network (tagged red) are using the 192.168.0.1 address as their default
gateway and some are using the 192.168.0.55.

I have tried different permutations of using "tag:" and "set:" and "net:"
always with the same result.

What am I doing wrong?

Thanks in advance.


___
Dnsmasq-discuss mailing list
Dnsmasq-discuss@lists.thekelleys.org.uk
http://lists.thekelleys.org.uk/mailman/listinfo/dnsmasq-discuss


Re: [Dnsmasq-discuss] dhcp logging and dhcp-range static configuration

2012-09-03 Thread Simon Kelley

On 03/09/12 18:06, Jean-Baptiste Denis wrote:

Hello everybody,

I'm running the provided centos dnsmasq version 2.48, and I've got a
question regarding logging of dhcp requests.

I've configured a static dhcp-range to assign ip addresses to well know
system using their hardware address.

Something like the following :

dhcp-range=192.168.0.1,static,255.255.255.0
dhcp-host=net:x86_64,00:30:99:99:99:1C,node1,192.168.0.2
...

The problem I've got is that my log file are full of unhonored dhcp
requests (which is normal, since they don't have any dhcp-host entry in
dnsmasq.conf) :

DHCPDISCOVER(eth0) 00:30:98:87:65:f0 no address available
...
...

Is there a way to prevent logging the DHCPDISCOVER request for
unconfigured hardware address in dhcp-range static mode ?



Try

dhcp-ignore=!known

or possibly the old syntax

dhcp-ignore=#known

I can't remember if 2.48 is new enough for the first one.


Cheers,

Simon.



___
Dnsmasq-discuss mailing list
Dnsmasq-discuss@lists.thekelleys.org.uk
http://lists.thekelleys.org.uk/mailman/listinfo/dnsmasq-discuss


[Dnsmasq-discuss] dhcp logging and dhcp-range static configuration

2012-09-03 Thread Jean-Baptiste Denis
Hello everybody,

I'm running the provided centos dnsmasq version 2.48, and I've got a
question regarding logging of dhcp requests.

I've configured a static dhcp-range to assign ip addresses to well know
system using their hardware address.

Something like the following :

dhcp-range=192.168.0.1,static,255.255.255.0
dhcp-host=net:x86_64,00:30:99:99:99:1C,node1,192.168.0.2
...

The problem I've got is that my log file are full of unhonored dhcp
requests (which is normal, since they don't have any dhcp-host entry in
dnsmasq.conf) :

DHCPDISCOVER(eth0) 00:30:98:87:65:f0 no address available
...
...

Is there a way to prevent logging the DHCPDISCOVER request for
unconfigured hardware address in dhcp-range static mode ?

Regards,

Jean-Baptiste



___
Dnsmasq-discuss mailing list
Dnsmasq-discuss@lists.thekelleys.org.uk
http://lists.thekelleys.org.uk/mailman/listinfo/dnsmasq-discuss


Re: [Dnsmasq-discuss] Issues with multiple subnets on dnsmasq

2012-09-03 Thread Ryan Chapman
On the host that pulls a 172.16.48 address, try a ping of 172.16.48.4 and then 
check the arp table to make sure it resolved to a hardware address.  If not, 
tcpdump arp traffic.

It might be interesting to see what an ifconfig, "route -n" and "arp -a" look 
like on the 172.16.48 host…


On Sep 3, 2012, at 7:29 AM, subhranshu dwivedi 
 wrote:

> Hi All,
> 
> I have Untangle with DNS masq setup at my end,
> 
> With interface:
> 
> External
> eth0  Link encap:Ethernet  HWaddr 00:04:23:c7:52:63  
>   inet addr:172.16.57.10  Bcast:172.16.57.255  Mask:255.255.255.0
> 
> INTERNAL
> eth1  Link encap:Ethernet  HWaddr 00:04:23:c7:52:62  
>   inet addr:172.16.48.4  Bcast:172.16.51.255  Mask:255.255.252.0
> DMZ
> eth2  Link encap:Ethernet  HWaddr 00:1b:21:0e:1f:46  
>   inet addr:172.16.48.110  Bcast:172.16.49.255  Mask:255.255.254.0
> 
> Extra ones: 
> eth3  Link encap:Ethernet  HWaddr fc:75:16:8e:57:2b  
>   inet addr:172.16.52.20  Bcast:172.16.53.255  Mask:255.255.254.0
> 
> eth4  Link encap:Ethernet  HWaddr fc:75:16:8e:57:42  
>   inet addr:172.16.56.2  Bcast:172.16.56.255  Mask:255.255.255.0
> 
> Now my dnsmasq.conf,
> 
> localise-queries
> server=202.56.224.135 # uplink.1
> server=59.144.127.16 # uplink.1
> expand-hosts
> addn-hosts=/etc/untangle-net-alpaca/dnsmasq-hosts
> no-hosts
> domain=bpl.netlink.com
> interface=eth1
> interface=eth3
> interface=eth4
> dhcp-range=eth1,172.16.49.101,172.16.49.254,14400
> dhcp-range=eth1,172.16.50.1,172.16.50.254,14400
> dhcp-range=eth1,172.16.51.101,172.16.51.254,14400
> dhcp-range=eth4,172.16.56.20,172.16.56.254,14400
> dhcp-range=eth3,172.16.52.21,172.16.53.254,14400
> dhcp-option=eth1,3,172.16.48.1
> dhcp-option=eth4,3,172.16.56.1
> dhcp-option=eth3,3,172.16.52.1
> dhcp-option=eth1,1,255.255.252.0
> dhcp-option=eth4,1,255.255.255.0
> dhcp-option=eth3,1,255.255.254.0
> dhcp-option=eth1,6,172.16.48.146,172.16.48.147
> dhcp-option=eth4,6,172.16.48.146,172.16.48.147
> dhcp-option=eth3,6,172.16.52.3,172.16.48.146
> dhcp-lease-max=500
> dhcp-host=00:13:02:a9:8b:57,172.16.48.106,24h
> dhcp-host=94:39:e5:e6:a7:cf,172.16.48.208,24h
> 
> 
> Now the issue is that i when we assign the ips with dnsmasq running with 
> multiple subnets as mentioned we face issues with range 49:
> dhcp-range=eth1,172.16.49.101,172.16.49.254,14400
> dhcp-range=eth1,172.16.50.1,172.16.50.254,14400
> dhcp-range=eth1,172.16.51.101,172.16.51.254,14400
> 
> it assigns the 50 and 51 series fine with internet access but when assigns 49 
> series ip cant ping the untangles internal ip:172.16.48.4
> and hence no internet for 49 series 
> 
> Please suggest what can we do to resolve this.
> 
> -- 
> Best Regards,
>  
> Subhranshu Dwivedi
> Technology Support
> Ermin Systems
> 0120.437.6161 (Main)
> 741.581.0583(direct)
> subhranshu.dwiv...@erminsystems.com
>  
> Our Expertise: Consulting Services | Data Centre Solutions | Storage 
> Solutions | Network Integration | IT Infrastructure Optimization | Managed 
> Services | Software Licensing | Audio-Visual Integration| Database Migration 
> | ERP Solutions| IVR Services | Virtualization |
> This email and any attachments are sent in confidence, subject to applicable 
> legal privilege and upon the basis that the recipient will conduct 
> appropriate virus checks. If you receive this email in error, please 
> telephone us upon receipt: you are strictly prohibited from using, copying or 
> disseminating it or any information contained in it, save to the intended 
> recipient. Internet communications are not secure and Ermin Systems Pvt. Ltd. 
> is not responsible for their abuse by third parties, nor for any alteration 
> or corruption in transmission, nor for any damage or loss caused by any virus 
> or other defects.
> P Please consider the environment before printing this e-mail.
> 
> ___
> Dnsmasq-discuss mailing list
> Dnsmasq-discuss@lists.thekelleys.org.uk
> http://lists.thekelleys.org.uk/mailman/listinfo/dnsmasq-discuss

___
Dnsmasq-discuss mailing list
Dnsmasq-discuss@lists.thekelleys.org.uk
http://lists.thekelleys.org.uk/mailman/listinfo/dnsmasq-discuss


[Dnsmasq-discuss] Issues with multiple subnets on dnsmasq

2012-09-03 Thread subhranshu dwivedi
Hi All,

I have Untangle with DNS masq setup at my end,

With interface:

External
eth0  Link encap:Ethernet  HWaddr 00:04:23:c7:52:63
  inet addr:172.16.57.10  Bcast:172.16.57.255  Mask:255.255.255.0

INTERNAL
eth1  Link encap:Ethernet  HWaddr 00:04:23:c7:52:62
  inet addr:172.16.48.4  Bcast:172.16.51.255  Mask:255.255.252.0
DMZ
eth2  Link encap:Ethernet  HWaddr 00:1b:21:0e:1f:46
  inet addr:172.16.48.110  Bcast:172.16.49.255  Mask:255.255.254.0

Extra ones:
eth3  Link encap:Ethernet  HWaddr fc:75:16:8e:57:2b
  inet addr:172.16.52.20  Bcast:172.16.53.255  Mask:255.255.254.0

eth4  Link encap:Ethernet  HWaddr fc:75:16:8e:57:42
  inet addr:172.16.56.2  Bcast:172.16.56.255  Mask:255.255.255.0

Now my dnsmasq.conf,

localise-queries
server=202.56.224.135 # uplink.1
server=59.144.127.16 # uplink.1
expand-hosts
addn-hosts=/etc/untangle-net-alpaca/dnsmasq-hosts
no-hosts
domain=bpl.netlink.com
interface=eth1
interface=eth3
interface=eth4
dhcp-range=eth1,172.16.49.101,172.16.49.254,14400
dhcp-range=eth1,172.16.50.1,172.16.50.254,14400
dhcp-range=eth1,172.16.51.101,172.16.51.254,14400
dhcp-range=eth4,172.16.56.20,172.16.56.254,14400
dhcp-range=eth3,172.16.52.21,172.16.53.254,14400
dhcp-option=eth1,3,172.16.48.1
dhcp-option=eth4,3,172.16.56.1
dhcp-option=eth3,3,172.16.52.1
dhcp-option=eth1,1,255.255.252.0
dhcp-option=eth4,1,255.255.255.0
dhcp-option=eth3,1,255.255.254.0
dhcp-option=eth1,6,172.16.48.146,172.16.48.147
dhcp-option=eth4,6,172.16.48.146,172.16.48.147
dhcp-option=eth3,6,172.16.52.3,172.16.48.146
dhcp-lease-max=500
dhcp-host=00:13:02:a9:8b:57,172.16.48.106,24h
dhcp-host=94:39:e5:e6:a7:cf,172.16.48.208,24h


Now the issue is that i when we assign the ips with dnsmasq running with
multiple subnets as mentioned we face issues with range 49:
dhcp-range=eth1,172.16.49.101,172.16.49.254,14400
dhcp-range=eth1,172.16.50.1,172.16.50.254,14400
dhcp-range=eth1,172.16.51.101,172.16.51.254,14400

it assigns the 50 and 51 series fine with internet access but when assigns
49 series ip cant ping the untangles internal ip:172.16.48.4
and hence no internet for 49 series

Please suggest what can we do to resolve this.

-- 
Best Regards,

* *

*Subhranshu Dwivedi***

Technology Support

*Ermin Systems*

0120.437.6161 (Main)

741.581.0583(direct)

subhranshu.dwivedi@**erminsystems.com 



--

*Our Expertise: **Consulting Services | Data Centre Solutions | Storage
Solutions | Network Integration | IT Infrastructure Optimization | Managed
Services | Software Licensing | Audio-Visual Integration| Database
Migration | ERP Solutions| IVR Services | Virtualization |***

This email and any attachments are sent in confidence, subject to
applicable legal privilege and upon the basis that the recipient will
conduct appropriate virus checks. If you receive this email in error,
please telephone us upon receipt: you are strictly prohibited from using,
copying or disseminating it or any information contained in it, save to the
intended recipient. Internet communications are not secure and Ermin
Systems Pvt. Ltd. is not responsible for their abuse by third parties, nor
for any alteration or corruption in transmission, nor for any damage or
loss caused by any virus or other defects.

*P** **Please consider the environment before printing this e-mail.*
___
Dnsmasq-discuss mailing list
Dnsmasq-discuss@lists.thekelleys.org.uk
http://lists.thekelleys.org.uk/mailman/listinfo/dnsmasq-discuss