Date: Fri, 27 Apr 2001 08:36:05 -0700 (PDT) From: Rick Duvall <maillist@coastsight.com> To: Mike Vierow <mvierow@e-agency.com> Cc: freebsd-questions@FreeBSD.ORG Subject: RE: Networking information source Message-ID: <Pine.BSF.4.21.0104270819190.42944-100000@ns1.coastsight.com> In-Reply-To: <NDBBKOMGPMLAELJLFGLBCEGHDJAA.mvierow@e-agency.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Let's say, for example, the IP address for the WAN side of your router is 209.181.51.10 with a netmask of 255.255.255.252, and the ISP's router is on 209.181.51.9 with the same netmask. Your router and the ISP's router should be able to talk with each other. That's step 1: The next step is to know what your IP block from your ISP is. Say your assigned block is a full class C of 65.149.2.0. Your netmask will be 255.255.255.0. Well, you have to give the ethernet interface of your router 1 IP address in that segment. By assigning the ethernet interface the subnet mask of 255.255.255.0, the router will assume that everything else on your LAN is a node, meaning that it's the only router. FreeBSD won't be set up as a router then. If it's a cisco (which I am assuming since you said priv exec to the router), and your router and the ISP's router are talking to each other, and your router can ping a machine in the outside world, and your ISP has already routed you your block of IP's, then set up your ethernet interface like this, substituting the example with your IP address. interface ethernet0 description make sure you do a no shutdown on this interface ip address 65.149.2.1 255.255.255.0 ! Then, on FreeBSD, do: ifconfig fxp0 inet 65.149.2.2 netmask 255.255.255.0 route add 0.0.0.0 65.149.2.1 If you are wanting FreeBSD to do the routing (2 NIC interfaces on your FreeBSD box), set Cisco to the following: interface ethernet0 description this is private IP between the cisco and freebsd ip address 192.168.0.1 255.255.255.252 ! ip route 65.149.2.0 255.255.255.0 192.168.0.2 Then on FreeBSD: ifconfig fxp0 inet 192.168.0.2 netmask 255.255.255.252 ifconfig fxp1 inet 65.149.2.1 netmask 255.255.255.0 route add 0.0.0.0 192.168.0.1 (make sure gateway_enable=yes is set in /etc/rc.conf) I think that the second example would be stupid, but in both examples, you would give your workstations an IP address of 65.149.2.whatever with a netmask of 255.255.255.0. The second example would route to the freebsd box, then to the router then out, the first example would just go to the router and never touch the freebsd box. I prefer to keep it simple myself. Why do you need to route it through the FreeBSD box? What is it you are trying to set up? On Thu, 26 Apr 2001, Mike Vierow wrote: > Thanks for the quick reply Rick, > > The FreeBSD box is connected to the router via ethernet. What is required in > setting up nodes? I do have priv. exec mode access to > the routers, both at the ISP and here in the office, should something need > modification. Do you remember how you first learned how to do this, and where > you got the info from? I am really interested in picking this up with a full > understanding of what is going on, and not just the 'scape-goat 'give me the > commands' approach so your input is very much appreciated. > > Mike V. > > > -----Original Message----- > > From: owner-freebsd-questions@FreeBSD.ORG > > [mailto:owner-freebsd-questions@FreeBSD.ORG]On Behalf Of Rick Duvall > > Sent: Thursday, April 26, 2001 5:01 PM > > To: Mike Vierow > > Cc: freebsd-questions@FreeBSD.ORG > > Subject: Re: Networking information source > > > > > > Is your FreeBSD box hooked directly to the frame-relay or point to point > > connection to your ISP, or do you have a router and the FreeBSD box is > > hooked to the router over ethernet? > > > > It could be that your router (the one hooked to the upstream provider) has > > the entire class c routed to it's ethernet interface, in which you can > > only put nodes on it. If you set up that router to do private IP on a > > crossover cable to your freebsd box (multihomed freebsd), then on do > > gateway_enable in /etc/rc.conf, and from the other router hooked to your > > ISP you set a static route to the private ip address of your freebsd > > box. Then, on the other Freebsd nic, set an IP address and netmask for > > the NIC, then that will work. > > > > Have I thoroughly confused you yet? > > > > If your freebsd box is hooked directly to your ISP, then you just need to > > set your IP address and netmask for your NIC on the ethernet > > network. 255.255.255.0 will be your netmask. That's 24 bits for network > > and 8 bits for host. > > > > Sincerely, > > > > Rick Duvall > > > > On Thu, 26 Apr 2001, Mike Vierow wrote: > > > > > I have a class c that I am attempting to route through a FreeBSD > > box, but with > > > little success. The class c is provided by my service provider and > > is available > > > on my local network. Would all I need is a static route, or do I need to run > > > routed to alert my Cisco router that that class c needs to go one > > hop further? > > > If this class c was xxx.yyy.zzz.0, and my interfaces were xl0 and xl1, what > > > would may config look like? > > > > > > I have searched for info regarding this, but all I have found is > > the man page of > > > routed, and several unhelpful mailing list posts. Can someone direct me to a > > > source where I can learn more information about this? TIA > > > > > > Mike > > > > > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > > > with "unsubscribe freebsd-questions" in the body of the message > > > > > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > > with "unsubscribe freebsd-questions" in the body of the message > > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.BSF.4.21.0104270819190.42944-100000>