On 22 April 2011 19:37, Rick Sewill <rsew...@gmail.com> wrote:
> On Friday, April 22, 2011 12:11:38 PM Aaron Gray wrote:
> > I am trying to set up a network and gateway on 192.168.1.x that I am
> using
> > for BOOTP'ing servers.
> >
> > dhcpd.conf
> > ~~~~~~~~~~~
> > allow booting;
> > allow bootp;
> > ddns-update-style interim;
> > ignore client-updates;
> > subnet 192.168.1.0 netmask 255.255.255.0 {
> > option subnet-mask 255.255.255.0;
> > option broadcast-address 192.168.1.255;
> > option routers 192.168.1.1;
> > option router-discovery true;
> > option domain-name-servers 8.8.8.8;
> > range dynamic-bootp 192.168.1.200 192.168.1.240;
> > next-server 192.168.0.140;
> > filename "pxelinux.0";
> > }
> > subnet 192.168.0.0 netmask 255.255.255.0 {
> > }
> > ~~~~~~~~~~
> >
> > But I cannot seem to get HTTP or other services to work on 192.168.1.x
> >
> > I have the existing 192.168.0.x network and was wondering how gateway
> > requests should get from 192.168.1.x to 192.168.0.1 ?
> >
> > Many thanks in advance,
> >
> > Aaron
>
> If I were a dhcp client, with no other routing configuration information,
> I will arp for the router at 192.168.1.1 to find the router's mac address.
> I would send the packet not destined to my local subnet to the router.
>
> I will not arp for 192.168.0.140 because it is not on my local subnet.
>
> The question becomes, how is the router at 192.168.1.1 configured?
> The router needs to forward the packets to the 192.168.0.x network.
How do I do that ?
>
To see the path, on the 192.168.1.x machine, try traceroute -n 192.168.0.x
>
traceroute works that way round but not the other.
Thanks,
Aaron
--
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
