Thank you, Alan. That explains so much! I'll let y'all know what happens.
Hopefully I'll be able to work on it today or tomorrow...
Siri Amrit
On Sunday 26 December 2004 09:40 pm, Alan Dayley kindly wrote:
> > On Sunday 26 December 2004 10:22 am, Siri Amrit Kaur wrote:
> > I'm reviving an old thread because I _finally_ got to use IPCop at work,
> > and immediately ran into a problem. I know more about Linux than I do
> > about networking...
> > Background: We have Cox cable and a static IP address. We have a Linksys
> > router. Got an 8-port switch for the 5 boxes in the LAN running
> > WinXP-Home. I have enabled Static and disabled DHCP in IPCop. That's
> > correct, right? Following the diagram below, we lose internet access for
> > the five boxes on the LAN. IPCop has internet access (it wants to update
> > itself), but the boxes in the LAN don't.
> >
> > I ran ifconfig and it seems to detect both NICs for Red and Green.
> >
> > > ISP<---->cable modem<--[dynamic IP]-->Linksys router
> > > <--[192.168.1.1]---[192.168.1.2]-->IPCop Red<-->
> > > IPCop Green<--[192.168.0.1]-->switch<--Other computers...
>
> Siri,
>
> I'll do some comments and descriptions about your network, as I understand
> them.
>
> Each of the two IPCop network cards must be on their own sub-net. That
> means that the "third and fourth bytes" of their IP addresses must be
> different. For exampe: If Red is 192.168.1.x then Green should be
> 192.168.[something other than 1].x.
>
> I am assuming your network to be like this:
>
> Cox<---->cable modem<--[static IP from Cox]-->Linksys router
> <--[192.168.1.1]---[192.168.1.2]-->IPCop Red<-->
> IPCop Green<--[192.168.0.1]-->switch<--Other computers...
>
> Is that correct?
>
> In the above, there are three network segments: (1) Cox to Linksys router,
> (2) router to IPCop Red and (3) IPCop Green to switch with other computers.
> Each segment has it's own subnet. Let's talk about each so that we are
> clear on what is happening.
>
> (1) Not much to say here. The cable modem provides a static IP to the
> "outside" port on the Linksys router. You description shows that his part
> is working so we will leave it at that.
>
> (2) There are two IPs in this subnet; the router "inside" port and the
> IPCop Red. They must have the same first three address numbers. In my
> example I called them 192.168.1.1 and 192.168.1.2, respectively.
>
> Digression: Each IP of a subnet must get it's IP either by static
> assignment or DHCP. Static assignment means that a person must configure
> the computer to have that IP address and must be aware of what the IPs are
> so as to not assign the same IP to more than one computer. DHCP means that
> one of the computers on the subnet is the server and it hands out IP
> numbers to the other computers on the subnet when they ask for them.
>
> Back to (2): In the connection between the router and IPCop Red, Red cannot
> be the DHCP server. IPCop won't do that and should not do that. It
> expects to either be assigned a static IP or it will look for a DHCP server
> to give it one. The Linksys router would be the DHCP server if it is
> enabled for this subnet.
>
> Now, you state that "IPCop has internet access (it wants to update
> itself)." Does that mean it has successfully accessed the internet? If so,
> we don't need to worry about this subnet except to know the first three IP
> address numbers of it so that the (3) subnet will get something different.
>
> (3) IPCop Green and all the comptuers connected to Green via the switch
> are on the same subnet. The address rules apply here in that either each
> computer must be assigned a static address or a computer on the subnet is
> the DHCP server to provide addresses to the others. IPCop provides an
> adminitration screen to enable it to be a DHCP server and the range of
> addresses that it will hand out to the other computers. I would suggest
> this as the easiest way to handle the internal subnet. Make sure you
> assign a range with the third and fourth bytes of the address different
> than the address on the Red interface.
>
> Following my possible example above, setting the IPCop to be the DHCP
> server, You could set IPCop Green to be 192.168.0.1 and to hand out the
> address range 192.168.0.2-50. The online documentation is pretty clear on
> how this should work. Try the install manual here:
> http://www.ipcop.org/1.4.0/en/install/html/ and in particular the Appendix
> A on networking http://www.ipcop.org/1.4.0/en/install/html/home-nets.html.
>
> I just noted that in all the dicussion above I failed to mention the need
> for specifying a gateway and DNS server. The gateway is the IP address of
> the computer that allows communication from your computer to get out on the
> net: ie. the gate out. If you statically assign the IP address of the
> computers on the switch, you must also assign them the IP address of the
> IPCop Green as the gateway so the packets know how to get out. You will
> also need to give the computers an address to a DNS server. This is why
> DHCP is so nice. As long as IPCop is getting to the net fine via Red, you
> can set IPCop to be the DHCP server and each of the workstations on Green
> will then get their IP address, gateway address and DNS address
> automatically.
>
> Maybe that is alot to take in at once but once you set it up, it is not too
> hard to "get," I think. Just post again to get more help if you need it.
> I'll be unavailable for most of the morning but there are other here, like
> Chris, who can and will help.
>
> Alan
> > ---------------------------------------------------
> PLUG-discuss mailing list - PLUG-discuss@lists.plug.phoenix.az.us
> To subscribe, unsubscribe, or to change you mail settings:
> http://lists.PLUG.phoenix.az.us/mailman/listinfo/plug-discuss
---------------------------------------------------
PLUG-discuss mailing list -
PLUG-discuss@lists.plug.phoenix.az.us
To subscribe, unsubscribe, or to change you mail settings:
http://lists.PLUG.phoenix.az.us/mailman/listinfo/plug-discuss
(text/plain)