Skip site navigation (1)Skip section navigation (2)
Date:      Fri, 19 Jan 1996 00:33:36 -0800 (PST)
From:      John-Mark Gurney <gurney_j@nike.efn.org>
To:        Chael Hall <nowhere@chaos.taylored.com>
Cc:        questions@freebsd.org
Subject:   Re: Gateway/gated questions
Message-ID:  <Pine.NEB.3.91.960119002747.202L-100000@nike.efn.org>
In-Reply-To: <Pine.BSF.3.91.960118185250.2913B-100000@chaos.taylored.com>

next in thread | previous in thread | raw e-mail | index | archive | help
On Thu, 18 Jan 1996, Chael Hall wrote:

> 
> I have decided to separate the Internet traffic from the NetWare traffic 
> on our network.  So, I took the FreeBSD machines and the router and 
> created a small thin Ethernet network for just them.  I added a second 
> SMC Ultra to one of the machines (running 2.1.0) and configured it.  I'm 
> running bootpd on the "gateway" machine and the clients can find it and 
> configure off of it.  They can telnet to it, etc. and I can do anything I 
> want from the gateway machine itself, but nobody can get across the 
> gateway to the other side.  I.e., a client on our internal network can't 
> access a server somewhere on the Internet.

[...]

> I compiled the kernel with "options GATEWAY" and it also has the IPFW 
> stuff in it, but I'm not using it at the moment.  I hard-coded some stuff 
> in /etc/sysconfig:
> 
> network_interfaces="ed0 ed1 lo0"
> ifconfig_ed0="inet 206.53.224.28  netmask 255.255.255.0"

you need to make sure that ALL the machines see the 206.53.224 net with 
the same subnetmask... so you should change the above to match the below....

> ifconfig_ed1="inet 206.53.224.58  netmask 255.255.255.224"
> ifconfig_lo0="inet localhost"

[...]

> 
>      In this situation, 206.53.224.28 (ed0) is on the Internet and 
> 206.53.224.58 (ed1) is on the internal network.  206.53.224.[33-62] are 
> internal IP addresses, 206.53.224.1 is our router.

what is most likely happening is that your other machines don't see the 
206.53.224 the same...  your gateway says that all the machines are on 
the gateway/freebsd network and that no routing is neccessary...  because 
of the netmask...  if you change the netmask for your internet network 
(one with your gateway) to match the internal, and add a route to your 
freebsd machine like "route add 206.53.224.32 206.53.224.28"... and that 
should help... it will tell the gateway to get to the machine 
206.53.224.[33-62] that it needs to go through 206.53.224.28 because of 
your routed -s... hope this helps... TTYL..

John-Mark

gurney_j@efn.org
Modem/FAX: (503) 683-6954   (FreeBSD Box)

Live in Peace, destroy Micro$oft, support free software, run FreeBSD (unix)

GCS/M/Sd#h+s+!gau-a--w++++vC+++++UF++++P---E---N++W---M--V--Y+t+5++G+b+D++
B----eu+h++!f++n----

CD5OUF++++.L-------2W.DM----N.9---NET2SP3s.2,4s.,4d.2,6---




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.NEB.3.91.960119002747.202L-100000>