from L3Switch1 and L3Switch2 from/to My Box (192.168.1.254) can ping/traceroute without problems..
the previous configuration was, i use L3Switch1's DHCP server, but it's quite annoying (sometimes does not work, so i must restart the switch).. ok so these are the logical topology client (10.10.x./24) -- (10.10.x.1) L3Switch1 (192.168.200.21) -- (192.168.200.20) L3Switch2 (192.168.1.1) -- (192.168.1.254) My Box DNSmasq (real ip) if i use static IP on the client, it works just fine, i can ping/traceroute from/to any node without problems.. On Wed, Feb 3, 2010 at 12:24 PM, Santiago Zarate <[email protected]> wrote: > Have you checked the routing tables?... also... any of the client has > ever got a ip from the dhcp server, and can you ping back other > clients + server? > 2010/2/3 Kiswono Prayogo <[email protected]>: >> hi, i have tried it.. but how do i debug it? what i mean is how can i >> know if there are any DHCP request packet sent to my box or from my >> box to the client.. >> >> *** >> i run dnsmasq with this command instead of running it as service: >> >> sudo dnsmasq -d --log-dhcp >> >> and got these message: >> >> dnsmasq: started, version 2.47 cachesize 8192 >> dnsmasq: compile time options: IPv6 GNU-getopt DBus I18N TFTP >> dnsmasq: DHCP, IP range 10.10.6.10 -- 10.10.6.254, lease time 12h >> dnsmasq: DHCP, IP range 10.10.5.10 -- 10.10.5.254, lease time 12h >> dnsmasq: DHCP, IP range 10.10.3.10 -- 10.10.3.254, lease time 12h >> dnsmasq: DHCP, IP range 10.10.2.10 -- 10.10.2.254, lease time 12h >> dnsmasq: DHCP, IP range 10.10.1.10 -- 10.10.1.254, lease time 12h >> dnsmasq: reading /etc/resolv.conf >> dnsmasq: using nameserver 208.67.220.220#53 >> dnsmasq: using nameserver 208.67.222.222#53 >> dnsmasq: read /etc/hosts - 14966 addresses >> [no more message, even if the client send DHCP requests] >> >> *** >> these are my configuration (my box (dhcp, gateway and dns server) ip >> address is 192.168.1.254): >> >> dhcp-range=WAP1,10.10.1.10,10.10.1.254,255.255.255.0,12h >> dhcp-option=WAP1,3,10.10.1.1 >> dhcp-range=WAP2,10.10.2.10,10.10.2.254,255.255.255.0,12h >> dhcp-option=WAP2,3,10.10.2.1 >> dhcp-range=WAP3,10.10.3.10,10.10.3.254,255.255.255.0,12h >> dhcp-option=WAP3,3,10.10.3.1 >> dhcp-range=WAP5,10.10.5.10,10.10.5.254,255.255.255.0,12h >> dhcp-option=WAP5,3,10.10.5.1 >> dhcp-range=WAP6,10.10.6.10,10.10.6.254,255.255.255.0,12h >> dhcp-option=WAP6,3,10.10.6.1 >> dhcp-option=6,192.168.1.254 >> >> *** >> the logical topology: >> >> client -- L3switch1 (forwarding bootp/dhcp to 192.168.1.254) -- my box >> (192.168.1.254) >> >> L3switch1: set forwarding-options helpers bootp server 192.168.1.254 >> i.e. if the client got IP 10.10.2.33 then, the gateway is 10.10.2.1, >> and the dns server is 192.168.1.254 >> >> *** >> the physical topology: >> >> client -- access point -- L3switch1 -- L3switch2 -- my box >> (192.168.1.254) -- internet >> >> -- >> Regards, >> Kiswono P >> GB >> >> _______________________________________________ >> Dnsmasq-discuss mailing list >> [email protected] >> http://lists.thekelleys.org.uk/mailman/listinfo/dnsmasq-discuss >> > -- Regards, Kiswono P GB
