I have a LinkSys WRT54GL router, which I would like to attach to my CentOS-5.6 server, to set up a LAN 192.168.2.* . The server is attached to the internet through a Billion modem/router which has a single ethernet outlet.
The instructions for the LinkSys router assume that it is being attached directly to an ADSL modem. But for various reasons I want everything to go through my server.
I wonder if anyone has set up a system like this? If so, I'd be grateful for advice on how to do it.
2011/4/24 Timothy Murphy gayleard@eircom.net:
I have a LinkSys WRT54GL router, which I would like to attach to my CentOS-5.6 server, to set up a LAN 192.168.2.* . The server is attached to the internet through a Billion modem/router which has a single ethernet outlet.
The instructions for the LinkSys router assume that it is being attached directly to an ADSL modem. But for various reasons I want everything to go through my server.
Without any information on what the purpose of such a setup would be, it's close to impossible to give you any recommendations. Is it because you want to use your CentOS system as a firewall? a router? a HTTP proxy? a network sniffer?
Or is it because you only have one external ethernet outlet and you want to access the internet on your other systems, while the services on your server still can be accessed from the outside? In the last case, you would normally just put your server on the LAN and do port-forwarding on your router. If it's because you want your server to be "outside" of your LAN, a more correct approach would be to setup a DMZ zone on your router, dedicate one of the LAN ports as DMZ port and connect your server there.
I wonder if anyone has set up a system like this?
Perhaps, perhaps not, depends on what the purpose of the system is.
Best regards Kenni
At Sun, 24 Apr 2011 17:08:50 +0200 CentOS mailing list centos@centos.org wrote:
2011/4/24 Timothy Murphy gayleard@eircom.net:
I have a LinkSys WRT54GL router, which I would like to attach to my CentOS-5.6 server, to set up a LAN 192.168.2.* . The server is attached to the internet through a Billion modem/router which has a single ethernet outlet.
The instructions for the LinkSys router assume that it is being attached directly to an ADSL modem. But for various reasons I want everything to go through my server.
Without any information on what the purpose of such a setup would be, it's close to impossible to give you any recommendations. Is it because you want to use your CentOS system as a firewall? a router? a HTTP proxy? a network sniffer?
Or is it because you only have one external ethernet outlet and you want to access the internet on your other systems, while the services on your server still can be accessed from the outside? In the last case, you would normally just put your server on the LAN and do port-forwarding on your router. If it's because you want your server to be "outside" of your LAN, a more correct approach would be to setup a DMZ zone on your router, dedicate one of the LAN ports as DMZ port and connect your server there.
I wonder if anyone has set up a system like this?
Perhaps, perhaps not, depends on what the purpose of the system is.
I would guess that the OP just wants a Wireless Access Point. It is hard (impossible at retail outlets) to get 'just an Access Point', although I think Linksys, et. al. still make just plain Access Points these are no longer commonly available at the retail level.
I am using a Netgear 'Wireless Router' as an Access Point. *I* don't even have broadband Internet at all (I use dialup). Just leave the WAN jack unconnected. Use a machine with a wired network (RJ45) that gets its IP address via DHCP and connect this with an Cat5 cable to any of the LAN ports on the Router, let it get an address automagically from the router and connect to the router via the router's default IP address with a web browser. You should then be able to 'login' to the admin pages using the default username and password. If you can, you can disable the WAN (in the case of the cheap Netgear box, you can't and it will bitch and moan about not having internet access to check for firmware updates -- I just ignore it). I just disable the router's DHCP server, set its IP address to something consistent with my LAN (a static IP address in the same subnet, with the proper netmask, etc.), tell it to use *my* DHCP server, default route, etc. Oh, and set up its SSID and security. I run DHCP on my desktop for my LAN. Once the router is set up to work with your LAN, just jack a Cat5 from any of its LAN ports to your switch.
Best regards Kenni _______________________________________________ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Robert Heller wrote:
I would guess that the OP just wants a Wireless Access Point. It is hard (impossible at retail outlets) to get 'just an Access Point', although I think Linksys, et. al. still make just plain Access Points these are no longer commonly available at the retail level.
I am using a Netgear 'Wireless Router' as an Access Point. *I* don't even have broadband Internet at all (I use dialup). Just leave the WAN jack unconnected. Use a machine with a wired network (RJ45) that gets its IP address via DHCP and connect this with an Cat5 cable to any of the LAN ports on the Router, let it get an address automagically from the router and connect to the router via the router's default IP address with a web browser. You should then be able to 'login' to the admin pages using the default username and password. If you can, you can disable the WAN (in the case of the cheap Netgear box, you can't and it will bitch and moan about not having internet access to check for firmware updates -- I just ignore it). I just disable the router's DHCP server, set its IP address to something consistent with my LAN (a static IP address in the same subnet, with the proper netmask, etc.), tell it to use *my* DHCP server, default route, etc. Oh, and set up its SSID and security. I run DHCP on my desktop for my LAN. Once the router is set up to work with your LAN, just jack a Cat5 from any of its LAN ports to your switch.
That is more or less exactly what I'm hoping to achieve - except that I would like my server also to be my DHCP server. But I'll start off with you method, and see how I get on.
At Sun, 24 Apr 2011 21:11:31 +0200 CentOS mailing list centos@centos.org wrote:
Robert Heller wrote:
I would guess that the OP just wants a Wireless Access Point. It is hard (impossible at retail outlets) to get 'just an Access Point', although I think Linksys, et. al. still make just plain Access Points these are no longer commonly available at the retail level.
I am using a Netgear 'Wireless Router' as an Access Point. *I* don't even have broadband Internet at all (I use dialup). Just leave the WAN jack unconnected. Use a machine with a wired network (RJ45) that gets its IP address via DHCP and connect this with an Cat5 cable to any of the LAN ports on the Router, let it get an address automagically from the router and connect to the router via the router's default IP address with a web browser. You should then be able to 'login' to the admin pages using the default username and password. If you can, you can disable the WAN (in the case of the cheap Netgear box, you can't and it will bitch and moan about not having internet access to check for firmware updates -- I just ignore it). I just disable the router's DHCP server, set its IP address to something consistent with my LAN (a static IP address in the same subnet, with the proper netmask, etc.), tell it to use *my* DHCP server, default route, etc. Oh, and set up its SSID and security. I run DHCP on my desktop for my LAN. Once the router is set up to work with your LAN, just jack a Cat5 from any of its LAN ports to your switch.
That is more or less exactly what I'm hoping to achieve - except that I would like my server also to be my DHCP server. But I'll start off with you method, and see how I get on.
I use my 'desktop' as a DHCP server (amoungst other things) in addition to being my desktop.
Robert Heller wrote:
That is more or less exactly what I'm hoping to achieve - except that I would like my server also to be my DHCP server. But I'll start off with you method, and see how I get on.
I use my 'desktop' as a DHCP server (amoungst other things) in addition to being my desktop.
Sorry, I didn't read carefully enough what you said - I see now that what you did is _exactly_ what I'd like to achieve!
Kenni Lund wrote:
I have a LinkSys WRT54GL router, which I would like to attach to my CentOS-5.6 server, to set up a LAN 192.168.2.* . The server is attached to the internet through a Billion modem/router which has a single ethernet outlet.
Without any information on what the purpose of such a setup would be, it's close to impossible to give you any recommendations. Is it because you want to use your CentOS system as a firewall? a router? a HTTP proxy? a network sniffer?
I don't actually think my motives are relevant. In case I didn't described the situation clearly, my CentOS server is connected to an ADSL modem by ethernet (eth0). The modem's IP address is 192.168.1.254 .
I have a second NIC on my server (eth1) and I want to attach my LinkSys router to this by ethernet, to work effectively as an access point (perhaps that answers your question?) on a LAN 192.168.2.* .
I'd like to connect my laptop to the system with WiFi, with an address perhaps of 192.168.2.3 . The router might have the address 192.168.2.12 .
Or is it because you only have one external ethernet outlet and you want to access the internet on your other systems, while the services on your server still can be accessed from the outside? In the last case, you would normally just put your server on the LAN and do port-forwarding on your router. If it's because you want your server to be "outside" of your LAN, a more correct approach would be to setup a DMZ zone on your router, dedicate one of the LAN ports as DMZ port and connect your server there.
Neither of the above, if I understand you correctly. I want to connect the router as described above.
The reason, roughly speaking, is that I want all data that comes into or out of my system to go through the server, where the traffic can be followed and monitored if necessary.
I wonder if anyone has set up a system like this?
Perhaps, perhaps not, depends on what the purpose of the system is.
Do you have a LinkSys router with an IP address other than 192.168.1.1 , or even better with an address other than 192.168.1.* ? If you have, could you tell me _how_ you did it, please. I don't really care _why_ you did it.
The instructions on the router only explain how to set it up (with address 192.168.1.1) attached directly to an ADSL modem. I could do that, but I don't want to ...
On 04/24/2011 01:15 PM, Timothy Murphy wrote:
Kenni Lund wrote:
I have a LinkSys WRT54GL router, which I would like to attach to my CentOS-5.6 server, to set up a LAN 192.168.2.* . The server is attached to the internet through a Billion modem/router which has a single ethernet outlet.
Without any information on what the purpose of such a setup would be, it's close to impossible to give you any recommendations. Is it because you want to use your CentOS system as a firewall? a router? a HTTP proxy? a network sniffer?
I don't actually think my motives are relevant. In case I didn't described the situation clearly, my CentOS server is connected to an ADSL modem by ethernet (eth0). The modem's IP address is 192.168.1.254 .
I have a second NIC on my server (eth1) and I want to attach my LinkSys router to this by ethernet, to work effectively as an access point (perhaps that answers your question?) on a LAN 192.168.2.* .
I'd like to connect my laptop to the system with WiFi, with an address perhaps of 192.168.2.3 . The router might have the address 192.168.2.12 .
Or is it because you only have one external ethernet outlet and you want to access the internet on your other systems, while the services on your server still can be accessed from the outside? In the last case, you would normally just put your server on the LAN and do port-forwarding on your router. If it's because you want your server to be "outside" of your LAN, a more correct approach would be to setup a DMZ zone on your router, dedicate one of the LAN ports as DMZ port and connect your server there.
Neither of the above, if I understand you correctly. I want to connect the router as described above.
The reason, roughly speaking, is that I want all data that comes into or out of my system to go through the server, where the traffic can be followed and monitored if necessary.
I wonder if anyone has set up a system like this?
Perhaps, perhaps not, depends on what the purpose of the system is.
Do you have a LinkSys router with an IP address other than 192.168.1.1 , or even better with an address other than 192.168.1.* ? If you have, could you tell me _how_ you did it, please. I don't really care _why_ you did it.
The instructions on the router only explain how to set it up (with address 192.168.1.1) attached directly to an ADSL modem. I could do that, but I don't want to ...
You basically have 2 choices.
If you connect the router's External port (with IP 192.168.2.x) directly to eth1 then on the INSIDE of that router you will need to use a 3rd IP subnet (ie, 192.168.3.x).
The second choice is to connect eth1 of your CentOS machine to an INTERNAL port on the router (if it has more than one). You can configure the inside of the router to 192.168.2.x and the external port of the router would not be connected to anything and the other devices would connect to the wireless of the router or the other internal ports.
On 04/24/2011 01:15 PM, Timothy Murphy wrote:
I don't actually think my motives are relevant. In case I didn't described the situation clearly, my CentOS server is connected to an ADSL modem by ethernet (eth0). The modem's IP address is 192.168.1.254 .
I have a second NIC on my server (eth1) and I want to attach my LinkSys router to this by ethernet, to work effectively as an access point (perhaps that answers your question?) on a LAN 192.168.2.* .
I'd like to connect my laptop to the system with WiFi, with an address perhaps of 192.168.2.3 . The router might have the address 192.168.2.12 .
[SNIP]
Do you have a LinkSys router with an IP address other than 192.168.1.1 , or even better with an address other than 192.168.1.* ? If you have, could you tell me _how_ you did it, please. I don't really care _why_ you did it.
I'm doing pretty much exactly what you propose, but I'm using DD-WRT in place of the standard WRT54GL firmware. That allows me to configure the WRT54GL as a wireless access point and 6-port switch, with all routing and server functions performed by the Linux box that serves as a gateway between my internal network and my cable modem. The router lives at address 192.168.43.1. Yes, it would probably make more sense to put the gateway box at the ".1" address and the non-routing "router" at ".2" or elsewhere, but that's not how my network evolved.
Problem is that I don't have a WRT54 with standard firmware, so it's hard to give instructions. As others have said, you would need to use only the LAN ports on the router. Configure the router not to use DHCP for its WAN connection and then you should be able to set up its local IP address, subnet mask, and other network parameters manually. It's hard to imagine a router that wouldn't let you do that. Yes, when the router boots with its factory default settings it will be using 192.168.1.1, but you can temporarily configure your network interface to talk on that subnet, log into the router, and configure it to your liking.
On 25/04/11 04:15, Timothy Murphy wrote:
Do you have a LinkSys router with an IP address other than 192.168.1.1 , or even better with an address other than 192.168.1.* ? If you have, could you tell me _how_ you did it, please. I don't really care _why_ you did it.
The instructions on the router only explain how to set it up (with address 192.168.1.1) attached directly to an ADSL modem. I could do that, but I don't want to ...
The reason you might want to stick with the 192.168.1.* IP address is because when you have a need to reset to factory defaults, you'll find it takes some extra steps to reconnect to it (can be done by adding a slave IP address to the NIC attached to your AP; ip addr add 192.168.1.x/24 dev ethx) to reconfigure. In my case, I simply changed my internal network to suit the Linksys and never looked back.
I have my set up as follows:
(Pardon my ASCII art if it fails to render properly once I hit send)
------------ ----------------- ---------------- ----------------- | Internet |----| 5-port switch |----| CentOS 5 Box |----| 8-port switch | ------------ ----------------- ---------------- ----------------- | V <<<----------------------------------------------------<<< | V ----------------
--|Linksys WRT54G|
----------------
My internal devices (192.168.1.x/24) are attached to the 8-port switch. I use only 2-ports on the 5 port switch to connect the ADSL modem to the server. All DHCP, DNS, Firewalling, is done on the CentOS box. I know most will cringe on the next few words, but I happen to like the way it is setup. On the ADSL modem, I've set the CentOS box as the DMZ so that I can control all Nating on the server. It has not failed me for the last 6 years I've been doing this. The key is to have a deny,allow firewall policy - meaning the policy on all chains is DROP, then I puunch the holes I need.
Hopefully not too much verbiage.
Cheers, Ak.
Anthony wrote:
On 25/04/11 04:15, Timothy Murphy wrote:
Do you have a LinkSys router with an IP address other than 192.168.1.1 , or even better with an address other than 192.168.1.* ? If you have, could you tell me _how_ you did it, please. I don't really care _why_ you did it.
The instructions on the router only explain how to set it up (with address 192.168.1.1) attached directly to an ADSL modem. I could do that, but I don't want to ...
The reason you might want to stick with the 192.168.1.* IP address is because when you have a need to reset to factory defaults, you'll find it takes some extra steps to reconnect to it (can be done by adding a slave IP address to the NIC attached to your AP; ip addr add 192.168.1.x/24 dev ethx) to reconfigure. In my case, I simply changed my internal network to suit the Linksys and never looked back.
I have my set up as follows:
(Pardon my ASCII art if it fails to render properly once I hit send)
| Internet |----| 5-port switch |----| CentOS 5 Box |----| 8-port switch |
| V<<<----------------------------------------------------<<< | V ----------------
--|Linksys WRT54G|
----------------My internal devices (192.168.1.x/24) are attached to the 8-port switch. I use only 2-ports on the 5 port switch to connect the ADSL modem to the server. All DHCP, DNS, Firewalling, is done on the CentOS box. I know most will cringe on the next few words, but I happen to like the way it is setup. On the ADSL modem, I've set the CentOS box as the DMZ so that I can control all Nating on the server. It has not failed me for the last 6 years I've been doing this. The key is to have a deny,allow firewall policy - meaning the policy on all chains is DROP, then I puunch the holes I need.
Hopefully not too much verbiage.
Cheers, Ak.
His ADSL modem is already on 192.168.1.x subnet, so CentOS WAN NIC already uses it. And I do not expect resetting router to defaults every week. Maybe never.
Ljubomir
On 25/04/11 09:34, Ljubomir Ljubojevic wrote:
His ADSL modem is already on 192.168.1.x subnet, so CentOS WAN NIC already uses it. And I do not expect resetting router to defaults every week. Maybe never.
Ljubomir
Ah yes - forgot that titbit of information - :(.
In that case, what you need do is connect the Linksys to the same switch as the one which hosts your eth1 and ADSL modem. Go to the configuration pages on the Linksys, change the IP and subnet, then when you commit and reboot, disconnect the ethernet cable from that switch and onto the switch your LAN is connected to. Then on your browser, reconnect to the new IP and continue to configure whatever else you need.
Remember to disable DHCP on the Linksys. However, if you want to identify users using the AP, then you can create an exclusion range in your CentOS DHCP and dish out that excluded range from your Linksys DHCP.
Cheers, Ak.
Anthony wrote:
what you need do is connect the Linksys to the same switch as the one which hosts your eth1 and ADSL modem. Go to the configuration pages on the Linksys, change the IP and subnet, then when you commit and reboot, disconnect the ethernet cable from that switch and onto the switch your LAN is connected to. Then on your browser, reconnect to the new IP and continue to configure whatever else you need.
I tried that, with several variations, and none of them seemed to work. I'm wondering if it is possible with the default operating system on the LinkSys54GL, as I see most people who have done something like what I am trying to do have installed dd-wrt on the router.
In any case, I've given up for the time being; I'm only here (in Italy) for 10 days, and have spent 3 of them getting on the internet! The Telecomitalia modem I was given never worked for more than 10 minutes, then it had to be switched off and on again. (Telecomitalia seems to drive a significant part of the population into homicidal rage.) The Billion modem (or modem/router) I brought with me works perfectly.
At Mon, 25 Apr 2011 09:10:36 +1000 CentOS mailing list centos@centos.org wrote:
On 25/04/11 04:15, Timothy Murphy wrote:
Do you have a LinkSys router with an IP address other than 192.168.1.1 , or even better with an address other than 192.168.1.* ? If you have, could you tell me _how_ you did it, please. I don't really care _why_ you did it.
The instructions on the router only explain how to set it up (with address 192.168.1.1) attached directly to an ADSL modem. I could do that, but I don't want to ...
The reason you might want to stick with the 192.168.1.* IP address is because when you have a need to reset to factory defaults, you'll find it takes some extra steps to reconnect to it (can be done by adding a slave IP address to the NIC attached to your AP; ip addr add 192.168.1.x/24 dev ethx) to reconfigure. In my case, I simply changed my internal network to suit the Linksys and never looked back.
My laptop is setup to use DHCP on either its hard Ethernet or wireless. Jacking in a spare Cat5 cable would work for me if/when I need to reconfigure a factory reset router.
I have my set up as follows:
(Pardon my ASCII art if it fails to render properly once I hit send)
| Internet |----| 5-port switch |----| CentOS 5 Box |----| 8-port switch |
| V<<<----------------------------------------------------<<< | V ----------------
--|Linksys WRT54G|
----------------My internal devices (192.168.1.x/24) are attached to the 8-port switch. I use only 2-ports on the 5 port switch to connect the ADSL modem to the server. All DHCP, DNS, Firewalling, is done on the CentOS box. I know most will cringe on the next few words, but I happen to like the way it is setup. On the ADSL modem, I've set the CentOS box as the DMZ so that I can control all Nating on the server. It has not failed me for the last 6 years I've been doing this. The key is to have a deny,allow firewall policy - meaning the policy on all chains is DROP, then I puunch the holes I need.
Hopefully not too much verbiage.
Cheers, Ak.
CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
On 04/24/11 11:15 AM, Timothy Murphy wrote:
Without any information on what the purpose of such a setup would be, it's close to impossible to give you any recommendations. Is it because you want to use your CentOS system as a firewall? a router? a HTTP proxy? a network sniffer?
I don't actually think my motives are relevant. In case I didn't described the situation clearly, my CentOS server is connected to an ADSL modem by ethernet (eth0). The modem's IP address is 192.168.1.254 .
your goal is very relevant if youj are expecting us to suggest a workable solution.
but ouch, sounds like your modem is ALSO a NAT router, and is probably running DHCP already. what IP is eth0 of this linux PC ?
you want to avoid 'double nat' where there's multiple layers of address translation as its just ugly as heck to troubleshoot, and adds complexity without any additional value..
assuming I'm right, and your modem is in fact doing NAT routing too, then I'd put DD-WRT or Tomato opensource firmware on the WRT54GL, configure it for LAN only use, so all 5 ports are LAN, plug it into the modem, plug your computer(s) into the WRT's switch also, and configure the WRT"s wireless. now all your systems will be on that 192.168.1.xxx subnet.
John R Pierce wrote:
On 04/24/11 11:15 AM, Timothy Murphy wrote:
Without any information on what the purpose of such a setup would be, it's close to impossible to give you any recommendations. Is it because you want to use your CentOS system as a firewall? a router? a HTTP proxy? a network sniffer?
I don't actually think my motives are relevant. In case I didn't described the situation clearly, my CentOS server is connected to an ADSL modem by ethernet (eth0). The modem's IP address is 192.168.1.254 .
your goal is very relevant if youj are expecting us to suggest a workable solution.
but ouch, sounds like your modem is ALSO a NAT router, and is probably running DHCP already. what IP is eth0 of this linux PC ?
you want to avoid 'double nat' where there's multiple layers of address translation as its just ugly as heck to troubleshoot, and adds complexity without any additional value..
assuming I'm right, and your modem is in fact doing NAT routing too, then I'd put DD-WRT or Tomato opensource firmware on the WRT54GL, configure it for LAN only use, so all 5 ports are LAN, plug it into the modem, plug your computer(s) into the WRT's switch also, and configure the WRT"s wireless. now all your systems will be on that 192.168.1.xxx subnet.
He wants to pass all traffic through CentOS box so he can monitor traffic, run bandwidth shaping, etc..
As for double-NAT, it's not so horrible. I now people using even triple-NAT without issues. Not recommended, but much easier for noob's then learning how to route properly. 7 years of experience speaking.
Ljubomir
John R Pierce wrote:
I don't actually think my motives are relevant.
In case I didn't described the situation clearly, my CentOS server is connected to an ADSL modem by ethernet (eth0). The modem's IP address is 192.168.1.254 .
your goal is very relevant if youj are expecting us to suggest a workable solution.
My point was that you suggested various alternatives to what I was aiming at. There is a perfectly simple "solution", which is actually what I am doing now, namely to attach the router to the modem. But as I said, I am hoping for a solution where all data will pass through my server.
but ouch, sounds like your modem is ALSO a NAT router, and is probably running DHCP already. what IP is eth0 of this linux PC ?
The server currently has IP address 192.168.1.2, and the modem has IP address 192.168.1.254.
assuming I'm right, and your modem is in fact doing NAT routing too, then I'd put DD-WRT or Tomato opensource firmware on the WRT54GL, configure it for LAN only use, so all 5 ports are LAN, plug it into the modem, plug your computer(s) into the WRT's switch also, and configure the WRT"s wireless. now all your systems will be on that 192.168.1.xxx subnet.
Can one actually have two NICs on a computer in the same LAN? I would have thought that would cause problems?
On 04/24/11 6:05 PM, Timothy Murphy wrote:
Can one actually have two NICs on a computer in the same LAN? I would have thought that would cause problems?
you can setup a bridge to do that, but the firewall rules are a little trickier (at least, most of the linux firewall packages assume you're doing NAT).
can you disable the NAT function in the modem so your eth0 gets the 'real' internet IP, and talks to your ISP's router as the gateway, then MASQ's the 192.168.1.x subnet?
Timothy Murphy wrote:
I don't actually think my motives are relevant. In case I didn't described the situation clearly, my CentOS server is connected to an ADSL modem by ethernet (eth0). The modem's IP address is 192.168.1.254 .
It is very much relevant. I am in WISP business for last 7 years and there are several options.
Since you want your CentOS box to act as Router/Firewall/NAT(Otherwise you need to route inside your network)/DHCP server, first setup Linksys router (look below).
Then connect CentOS box Internal NIC to one of the Internal/Local/LAN ports on Linksys and configure that CentOS internal NIC on the same subnet.
Once that is finished, connect via other LAN ports on Linksys or via wireless (IP must be on the same subnet as Linksys new IP and CentOS internal NIC) and try pinging CentOS Internal IP.
When successful, run "echo 1 > /proc/sys/net/ipv4/ip_forward" to enable port forwarding and setup NAT/Masquerade to avoid seting up routing between subnets. You should be able to ping to outside from entire internal network.
Setup DHCP server on CentOS box and caching DNS server if you need it, or use 8.8.8.8 and 8.8.4.4 as DNSservers.
I recommend webmin and shorewall for easier setup (both exist as rpm's), and even maybe ClearOS instead of CentOS. Google it, you will find it.
The reason, roughly speaking, is that I want all data that comes into or out of my system to go through the server, where the traffic can be followed and monitored if necessary.
Do you have a LinkSys router with an IP address other than 192.168.1.1 , or even better with an address other than 192.168.1.* ? If you have, could you tell me _how_ you did it, please. I don't really care _why_ you did it.
setup Linksys by going to http://192.168.1.1 in your browser (set IP on the PC you are accessing from to 192.168.1.2 fro example) and find "LAN settings" or "TCP/IP" or similar, and change "192.168.1.1" to desired IP. Since It will act as simple AP/Bridge, default gateway is irrelevant.
Ljubomir
That's exactly how I have my home network configured. Had it for many years actually.
There's a Linux box that is the central point of the network. It has several network cards: one for the cable modem, another for the WiFi access point, another for the local LAN.
On the cable modem, I just get an IP address via DHCP from the provider.
The WiFi access point is connected to the server via a loopback Ethernet cable actually. There's no need to use a switch when there are only 2 devices connected. Also, in this setup, there's no point to use a WiFi router - a simple WiFi access point is much better. The Linux server becomes the router.
The third network card goes into a switch that connects all the local LAN.
The Linux box does NAT for all the networks behind it. Also runs a local DNS cache and stuff like that.
On 04/25/11 12:28 PM, Florin Andrei wrote:
The WiFi access point is connected to the server via a loopback Ethernet cable actually. There's no need to use a switch when there are only 2 devices connected. Also, in this setup, there's no point to use a WiFi router - a simple WiFi access point is much better.
the catch is, routers are both cheaper and easier to find.
you can use a typical router as a access point if you...
* disable DHCP server on the router * set the WAN (internet) address to something static and 'safe' like 10.255.255.254 mask 255.255.255.0 * set the LAN (local) IP address to a unused static IP on your subnet so you can access it for management * use only the LAN ports on the router (it can be used as a 4-port switch)
if the router is compatible with Tomato or DD-Wrt firmware, there's a setting that does the equivalent of this, AND lets you use the WAN port as another switch port.
At Mon, 25 Apr 2011 13:20:58 -0700 CentOS mailing list centos@centos.org wrote:
On 04/25/11 12:28 PM, Florin Andrei wrote:
The WiFi access point is connected to the server via a loopback Ethernet cable actually. There's no need to use a switch when there are only 2 devices connected. Also, in this setup, there's no point to use a WiFi router - a simple WiFi access point is much better.
the catch is, routers are both cheaper and easier to find.
you can use a typical router as a access point if you...
* disable DHCP server on the router * set the WAN (internet) address to something static and 'safe' like 10.255.255.254 mask 255.255.255.0
You don't really need to do anything with the WAN port, so long as it is unconnected.
* set the LAN (local) IP address to a unused static IP on your subnet so you can access it for management * use only the LAN ports on the router (it can be used as a 4-port switch)if the router is compatible with Tomato or DD-Wrt firmware, there's a setting that does the equivalent of this, AND lets you use the WAN port as another switch port.
CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
-
Anthony -
Florin Andrei -
John R Pierce -
Johnny Hughes -
Kenni Lund -
Ljubomir Ljubojevic -
Robert Heller -
Robert Nichols -
Timothy Murphy