Re: network setup
On Thu, Oct 15, 2009 at 4:42 PM, Ilych narmonov narmonov2...@gmail.comwrote: Guys, I'm new with freeBSD setup. I hope somebody here who will give some links on how I will buil my network using freeBSD. I'm planning to use it as my router and dhcp server. Thanks everyone.. Carlos Narmonov ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org Here you'll find specifics on virtually all common tasks including the ones you mentioned. http://www.freebsd.org/doc/en/books/handbook/ -- Adam Vande More ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Network setup
Hi Ruel, On 04/04/2008, Ruel Luchavez [EMAIL PROTECTED] wrote: Hi I'm a beginner on this kind of industry I hope you guys will help me because i really want to LEARN..and i cant get any support on my fellows...:D I have a Linksys wireless-g broadband router model WRT54G here and I tried to configure it..but still i could not connect to Internet. I don't know if I've configured it wrong..could some one help me how to do it step by step? I would like to set-up this in our existing network for us to have wireless connection in other building... We are using DELL Power Connect 2724 here.. if I understand you correctly you need help to generally set up your router. This can't be handled on this help, but I think we can help you to configure your FreeBSD box if you want to connect to your WLAN once its set up. If you need help with the Linksys-Router you should search for a linksys based Mailing List, or forum. The people there are Linksys Users themselves and know how to deal with this stuff. IMO there's a good forum out there with lots of helpfull people: http://www.linksysinfo.org In case I misunderstood you and you have a FreeBSD specific issue, please provide some details of where your problems are, what Hardware you're using. And what you tried. There's an entire chapter in the FreeBSD handbook dealing with this Wireless Networking, too. Please see http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/network-wireless.html You might want to read on basic networking, too. HTH Christian ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Network setup
On Fri, 4 Apr 2008 17:52:22 +0800 Ruel Luchavez [EMAIL PROTECTED] wrote: I have a Linksys wireless-g broadband router model WRT54G here and I tried to configure it..but still i could not connect to Internet. I don't know if I've configured it wrong..could some one help me how to do it step by step? I have the WRT150N myself; however, the setup is virtually the same. By the way, are you sure that you want to invest the time is using a 'G' protocol router? The 'N' version is readily available, much faster and has a greater range. Anyway, I used a Windows box to do the initial configuration/installation of the router. Visit the linksys site and get the latest installer package: http://www.linksys.com/servlet/Satellite?c=L_CASupport_C1childpagename=US%2FLayoutcid=1166859678292pagename=Linksys%2FCommon%2FVisitorWrapperlid=7829237314L06 Obviously, that should be all one line. After downloading and running the installed, download and run the updater program. It works on your router and might very well have an updated firmware for you. Now that the router is working, you can start configuring it for your network. signature.asc Description: PGP signature
Re: Network setup
On Fri, 4 Apr 2008 12:48:08 +0200 (CEST) Wojciech Puchar [EMAIL PROTECTED] wrote: I have the WRT150N myself; however, the setup is virtually the same. By the way, are you sure that you want to invest the time is using a 'G' protocol router? The 'N' version is readily available, much faster and has a greater range. even better - use cables. cheapest and fastest;) The OP stated, or at least I assumed that he meant that the network was rather extensive. Using cables, while it might provide a faster data transfer, could easily cost more to implement. If the OP can get the wireless network up and running easily enough, he might very well save a considerable amount of time. Since he did not provide a schematic of his network, that is just a guess. -- Gerard [EMAIL PROTECTED] Wasn't there something about a PASCAL programmer knowing the value of everything and the Wirth of nothing? signature.asc Description: PGP signature
Re: Network Setup Question
On Friday 10 November 2006 19:17, Doug Hardie wrote: I have a bit of an unusual network setup situation. I have a machine that is only used to store backups. It gets moved around to different locations occasionally so it has to be able to live on a 192.168.1.x or a 10.0.1.x network without reconfiguration. I also need a fixed last address byte so I can connect to it remotely. I initially set it up with DHCP and then used an alias for the .250 address on both networks. That worked, but caused problems for the local network in one location. The particular user couldn't understand why sometimes his computer got different IP addresses. So I tried to establish the 192.168.1.250 as the primary address and added an alias of 10.0.1.250. That works in both environments except that there is no default route. Is there a way to negotiate just a default route via DHCP and not an IP address? or is there a way to set the default route based on which IP address is in use? Thanks. ___ dhclient.conf can get pretty granular as to exactly what you want from your DHCP server. myself, i use it to get everything, but to ignore the domain search mine tries to provide. man dhclient.conf and you will see tons of options (and some really good examples too). cheers, jonathan ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Network Setup Question
On Nov 10, 2006, at 19:34, Jonathan Horne wrote: On Friday 10 November 2006 19:17, Doug Hardie wrote: I have a bit of an unusual network setup situation. I have a machine that is only used to store backups. It gets moved around to different locations occasionally so it has to be able to live on a 192.168.1.x or a 10.0.1.x network without reconfiguration. I also need a fixed last address byte so I can connect to it remotely. I initially set it up with DHCP and then used an alias for the .250 address on both networks. That worked, but caused problems for the local network in one location. The particular user couldn't understand why sometimes his computer got different IP addresses. So I tried to establish the 192.168.1.250 as the primary address and added an alias of 10.0.1.250. That works in both environments except that there is no default route. Is there a way to negotiate just a default route via DHCP and not an IP address? or is there a way to set the default route based on which IP address is in use? Thanks. ___ dhclient.conf can get pretty granular as to exactly what you want from your DHCP server. myself, i use it to get everything, but to ignore the domain search mine tries to provide. man dhclient.conf and you will see tons of options (and some really good examples too). There are lots of options all right, but I couldn't find anything that would cause it not to negotiate the IP address. All of the other options are configurable. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Network Setup Question
On Friday 10 November 2006 21:56, Doug Hardie wrote: On Nov 10, 2006, at 19:34, Jonathan Horne wrote: On Friday 10 November 2006 19:17, Doug Hardie wrote: I have a bit of an unusual network setup situation. I have a machine that is only used to store backups. It gets moved around to different locations occasionally so it has to be able to live on a 192.168.1.x or a 10.0.1.x network without reconfiguration. I also need a fixed last address byte so I can connect to it remotely. I initially set it up with DHCP and then used an alias for the .250 address on both networks. That worked, but caused problems for the local network in one location. The particular user couldn't understand why sometimes his computer got different IP addresses. So I tried to establish the 192.168.1.250 as the primary address and added an alias of 10.0.1.250. That works in both environments except that there is no default route. Is there a way to negotiate just a default route via DHCP and not an IP address? or is there a way to set the default route based on which IP address is in use? Thanks. ___ dhclient.conf can get pretty granular as to exactly what you want from your DHCP server. myself, i use it to get everything, but to ignore the domain search mine tries to provide. man dhclient.conf and you will see tons of options (and some really good examples too). There are lots of options all right, but I couldn't find anything that would cause it not to negotiate the IP address. All of the other options are configurable. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] Doug, I'm no expert, but it seems to me that your requirements are a little too optimistic. If I understand correctly, you want this machine to be able to connect to multiple heterogenous networks, and always get the same last byte for its ip. The only way to do that reliably, in my mind, is to have each dhcp server on each network assign a static address based upon the MAC address of your computer. If you do not have access to the DHCP server configuration on a particular network then you must manually configure the nic. Assuming that you know the universe of networks that you will connect to ... say 3 or 300 possible networks ... then you could write a script in /usr/local/etc/rc.d to test various network configs ... but you might be better off just manually configuring the nic and moving on, as you cannot guarantee that the terminal byte of the ip will be available on any given network. IP just doesn't work that way. I'd be interested in any solution you may scare up, as I am faced with a similar situation. My solution is to just use static assignment, with an identifiable NETBIOS name in Samba. Good Luck lane ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Network Setup Question
On Friday 10 November 2006 21:56, Doug Hardie wrote: On Nov 10, 2006, at 19:34, Jonathan Horne wrote: On Friday 10 November 2006 19:17, Doug Hardie wrote: I have a bit of an unusual network setup situation. I have a machine that is only used to store backups. It gets moved around to different locations occasionally so it has to be able to live on a 192.168.1.x or a 10.0.1.x network without reconfiguration. I also need a fixed last address byte so I can connect to it remotely. I initially set it up with DHCP and then used an alias for the .250 address on both networks. That worked, but caused problems for the local network in one location. The particular user couldn't understand why sometimes his computer got different IP addresses. So I tried to establish the 192.168.1.250 as the primary address and added an alias of 10.0.1.250. That works in both environments except that there is no default route. Is there a way to negotiate just a default route via DHCP and not an IP address? or is there a way to set the default route based on which IP address is in use? Thanks. ___ dhclient.conf can get pretty granular as to exactly what you want from your DHCP server. myself, i use it to get everything, but to ignore the domain search mine tries to provide. man dhclient.conf and you will see tons of options (and some really good examples too). There are lots of options all right, but I couldn't find anything that would cause it not to negotiate the IP address. All of the other options are configurable. ___ i was thinking more along the lines, that you would pre-set your 2 ip addresses, and let the dhclient file request only default gateway. or... might it not be simpler, to configure a static DHCP lease for the box at each site, thus guaranteeing that it always has the .250? in the end, thats probably the best mileage way to go. jonathan ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Network Setup Question
On Nov 10, 2006, at 20:26, Lane wrote: On Friday 10 November 2006 21:56, Doug Hardie wrote: On Nov 10, 2006, at 19:34, Jonathan Horne wrote: On Friday 10 November 2006 19:17, Doug Hardie wrote: I have a bit of an unusual network setup situation. I have a machine that is only used to store backups. It gets moved around to different locations occasionally so it has to be able to live on a 192.168.1.x or a 10.0.1.x network without reconfiguration. I also need a fixed last address byte so I can connect to it remotely. I initially set it up with DHCP and then used an alias for the .250 address on both networks. That worked, but caused problems for the local network in one location. The particular user couldn't understand why sometimes his computer got different IP addresses. So I tried to establish the 192.168.1.250 as the primary address and added an alias of 10.0.1.250. That works in both environments except that there is no default route. Is there a way to negotiate just a default route via DHCP and not an IP address? or is there a way to set the default route based on which IP address is in use? Thanks. ___ dhclient.conf can get pretty granular as to exactly what you want from your DHCP server. myself, i use it to get everything, but to ignore the domain search mine tries to provide. man dhclient.conf and you will see tons of options (and some really good examples too). There are lots of options all right, but I couldn't find anything that would cause it not to negotiate the IP address. All of the other options are configurable. ___ I'm no expert, but it seems to me that your requirements are a little too optimistic. If I understand correctly, you want this machine to be able to connect to multiple heterogenous networks, and always get the same last byte for its ip. The only way to do that reliably, in my mind, is to have each dhcp server on each network assign a static address based upon the MAC address of your computer. Thats a bit much for the particular users who are housing this computer temporarily. Its bad enough that they have to put an address translation in their router to enable me to get to the .250 address. At least I can fairly easily walk them through that. If you do not have access to the DHCP server configuration on a particular network then you must manually configure the nic. That can only be done if you can access the machine which you can't in this setup since there is no default route. Assuming that you know the universe of networks that you will connect to ... say 3 or 300 possible networks ... then you could write a script in /usr/local/etc/rc.d to test various network configs ... but you might be better off just manually configuring the nic and moving on, as you cannot guarantee that the terminal byte of the ip will be available on any given network. IP just doesn't work that way.' There are only a very small number of locations for this machine, less than 5. However, its possible that at any time a new one might be necessary. This is an off-site backup machine and there needs to be someone available if we need to retrieve it. It can't be unavailable for a couple weeks. I'd be interested in any solution you may scare up, as I am faced with a similar situation. My solution is to just use static assignment, with an identifiable NETBIOS name in Samba. I am going back to the old configuration with a regular DHCP connection and then two static aliases: one for the 192 and one for the 10 addresses. That works but causes one particular user fits. I will just have to try and teach him that IP addresses will change as his DHCP reassigns them. He will have to check his computer's address and not just presume. Thanks for all the ideas. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Network setup
On Fri, 8 Oct 2004 11:51:53 +0200 (CEST), Svein Halvor Halvorsen [EMAIL PROTECTED] wrote: At home I have in my network: - A FreeBSD server - A FreeBSD workstation - A Windows gaming box - A FreeBSD laptop - A friend's backup server All are connected to a switch witch in turn is connected to the internett. I have real ethernet comming into my house, and all my machines have public IP-addresses which are handed out by a DHCP server outside of my control. Since my ISP have started to enforce soft bandwidth limiting, with the consequence of losing my connection for 48 hours if exceeded, I need some mean to count my traffic. Only traffic outside the subnet is counted. I therefore thought I could put another FreeBSD machine between my switch and the internet, which counts traffic (and also acts as a firewall). However, I can not afford to get another box to do this. So I thought I could use the server. I also want to put a wireless card in the firewall to allow me to move around with my laptop. Something like this: Internet | | | --- |fxp0 | | | -- | FBSD Server | ) ) ) | Laptop | | | 802.11 | FreeBSD | |fxp1 | -- --- | -- | Switch | -- | --- | | | - | - | Workstation 1 | | | Workstation 2 | | FreeBSD | | |Windows| - | - | --- | Friend's server | |FreeBSD | --- I'd like the possibility to have the workstations on the public internet (with public IP-addresses handed out by my ISP's DHCP sever). I must admit I'm out of my league here, but I guess I'd like the FBSD server to be invisible for the workstations and the backup server, but still be able analyse the IP-traffic. Is this possible? Does this kind of setup have a name, for which I can google? If this is impossible, I guess I could setup NAT on the server/firewall, and forward a couple of ports to the server behind the firewall. The issue is that all the traffic needs to be counted, and at least two machines needs to be visible on the public internet. Additionally I'd like to have a wireless connection for my laptop. I guess an ad-hoc setup would do for this? SVein Halvor ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] Hi Svein, I *think* you might need to setup a network bridge. http://www.freebsd.org/doc/en_US.ISO8859-1/articles/filtering-bridges/index.html Hope this helps. David ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Network setup
[David Jenkins, 2004-10-08] : I *think* you might need to setup a network bridge. http://www.freebsd.org/doc/en_US.ISO8859-1/articles/filtering-bridges/index.html Hope this helps. This seems to be *exactly* what I'm looking for! Thanks! Svein Halvor ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Network setup
On Fri, Oct 08, 2004 at 02:31:01PM +0200, Svein Halvor Halvorsen wrote: [David Jenkins, 2004-10-08] : I *think* you might need to setup a network bridge. http://www.freebsd.org/doc/en_US.ISO8859-1/articles/filtering-bridges/index.html Hope this helps. This seems to be *exactly* what I'm looking for! Thanks! You can combine this with the port ipa if you like. Ipfw counts the traffic but loses this at reboots or commands on the console. You can setup rules for certain cases. Cut bandwith of users if they used to much and such. If you use mrtg, then you could make graphs of this. I have an example of all of this on my website. -- Alex Please copy the original recipients, otherwise I may not read your reply. WWW: http://www.kruijff.org/alex/FreeBSD/ ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
