<div dir="ltr">Hi Glenn,<div>It did not show the default route of <a href="http://0.0.0.0/0">0.0.0.0/0</a> with route -n. One thing I noticed is, I can ping to another Address only with -I interface_name. For example I can send and receive packets with <b>ping -I eth0 8.8.8.8.</b> </div><div>If I use <b>ping 8.8.8.8 </b>it is not working. Am I missing anything here?</div><div><br></div><div>Regards</div><div>Simon</div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Thu, Mar 18, 2021 at 8:15 PM <<a href="mailto:glenn.satchell@uniq.com.au">glenn.satchell@uniq.com.au</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">Hi Simon,<br>
<br>
The default route will show up with a destination of <a href="http://0.0.0.0/0" rel="noreferrer" target="_blank">0.0.0.0/0</a> if you <br>
use route -n.<br>
<br>
If you use "ip route" it will show up with a destination of "default" in <br>
the first column.<br>
<br>
regards,<br>
Glenn<br>
<br>
On 2021-03-19 13:54, SIMON BABY wrote:<br>
> Hi Peter,<br>
> Thank you so much for helping.<br>
> <br>
> Yes, I am using ISC dhcpd. My query is with ISC DHCPd I can ping to<br>
> any network, but I did not see the ISC gateway in the kernel route<br>
> table. Will it be stored somewhere else so that when packet goes out,<br>
> the hardware (NIC) gets this information?<br>
> <br>
> Regards<br>
> Simon<br>
> <br>
> On Thu, Mar 18, 2021 at 5:07 PM Peter Yardley<br>
> <<a href="mailto:peter.martin.yardley@gmail.com" target="_blank">peter.martin.yardley@gmail.com</a>> wrote:<br>
> <br>
>> Hi,<br>
>> <br>
>> This is prolly a problem with your configuration. Are you using ISC<br>
>> DHCPd? If so could provide a relevant snippet of your configuration,<br>
>> anonymised if necessary.<br>
>> <br>
>> I used to configure subnets like this …<br>
>> <br>
>> subnet 10.20.50.0 netmask 255.255.254.0 {<br>
>> option subnet-mask 255.255.254.0;<br>
>> option broadcast-address 10.20.51.255;<br>
>> option routers 10.20.50.1;<br>
>> <br>
>> pool {<br>
>> # A device for Blah<br>
>> host HMTXYZ { hardware ethernet 00:40:9d:54:4c:c7;<br>
>> fixed-address 10.20.50.32; }<br>
>> …<br>
>> <br>
>> range 10.20.51.0 138.25.51.254;<br>
>> }<br>
>> <br>
>> Of course there are many other correct possiblities<br>
>> <br>
>>> On 19 Mar 2021, at 10:03 am, SIMON BABY <<a href="mailto:simonkbaby@gmail.com" target="_blank">simonkbaby@gmail.com</a>><br>
>> wrote:<br>
>>> <br>
>>> Hi,<br>
>>> I have a query about the DHCP provided IP address vs Static IP<br>
>> address configured manually. When i get the IP address from DHCP, I<br>
>> can ping to 8.8.8.8 (google public server) where as<br>
>>> with a statically configured IP address, I could not. When I<br>
>> looked into the route table (route -n ), I did not see any default<br>
>> gateway with DHCP or Statically configured IP. (I am testing with<br>
>> Linux).<br>
>>> <br>
>>> 1. Can I know when the packet goes out , how did the hardware<br>
>> (NIC) find the default gateway in the case of the DHCP provided IP<br>
>> address since I did not see any default gw IP in the routing table?<br>
>>> 2. With statically configured IP, if I explicitly configure a<br>
>> default GW, I can see packets are going out and receiving. I can see<br>
>> the default GW in the routing table. Do I need a default GW to send<br>
>> packets from a statically configured IP address ?<br>
>>> <br>
>>> Thank you for your time<br>
>>> <br>
>>> Regards<br>
>>> Simon<br>
>>> <br>
>>> _______________________________________________<br>
>>> ISC funds the development of this software with paid support<br>
>> subscriptions. Contact us at <a href="https://www.isc.org/contact/" rel="noreferrer" target="_blank">https://www.isc.org/contact/</a> for more<br>
>> information.<br>
>>> <br>
>>> dhcp-users mailing list<br>
>>> <a href="mailto:dhcp-users@lists.isc.org" target="_blank">dhcp-users@lists.isc.org</a><br>
>>> <a href="https://lists.isc.org/mailman/listinfo/dhcp-users" rel="noreferrer" target="_blank">https://lists.isc.org/mailman/listinfo/dhcp-users</a><br>
>> <br>
>> Peter Yardley<br>
>> <a href="mailto:peter.martin.yardley@gmail.com" target="_blank">peter.martin.yardley@gmail.com</a><br>
>> <br>
>> _______________________________________________<br>
>> ISC funds the development of this software with paid support<br>
>> subscriptions. Contact us at <a href="https://www.isc.org/contact/" rel="noreferrer" target="_blank">https://www.isc.org/contact/</a> for more<br>
>> information.<br>
>> <br>
>> dhcp-users mailing list<br>
>> <a href="mailto:dhcp-users@lists.isc.org" target="_blank">dhcp-users@lists.isc.org</a><br>
>> <a href="https://lists.isc.org/mailman/listinfo/dhcp-users" rel="noreferrer" target="_blank">https://lists.isc.org/mailman/listinfo/dhcp-users</a><br>
> _______________________________________________<br>
> ISC funds the development of this software with paid support<br>
> subscriptions. Contact us at <a href="https://www.isc.org/contact/" rel="noreferrer" target="_blank">https://www.isc.org/contact/</a> for more<br>
> information.<br>
> <br>
> dhcp-users mailing list<br>
> <a href="mailto:dhcp-users@lists.isc.org" target="_blank">dhcp-users@lists.isc.org</a><br>
> <a href="https://lists.isc.org/mailman/listinfo/dhcp-users" rel="noreferrer" target="_blank">https://lists.isc.org/mailman/listinfo/dhcp-users</a><br>
_______________________________________________<br>
ISC funds the development of this software with paid support subscriptions. Contact us at <a href="https://www.isc.org/contact/" rel="noreferrer" target="_blank">https://www.isc.org/contact/</a> for more information.<br>
<br>
dhcp-users mailing list<br>
<a href="mailto:dhcp-users@lists.isc.org" target="_blank">dhcp-users@lists.isc.org</a><br>
<a href="https://lists.isc.org/mailman/listinfo/dhcp-users" rel="noreferrer" target="_blank">https://lists.isc.org/mailman/listinfo/dhcp-users</a><br>
</blockquote></div>