Re: [SLE] DHCP vs Static IP - SUSE 10.0
Sorry Donald, You must have gotten two same email. On Sun, 2005-10-16 at 09:10 -0600, Donald D Henson wrote:
See above. It looks like my gateway settings are being ignored. Here's what route -n shows on linux (V9.3):
Kernel IP routing table Destination Gateway Genmask Flags Metric Ref Use Iface 192.168.100.0 0.0.0.0 255.255.255.0 U 0 0 0 eth0 192.168.1.0 0.0.0.0 255.255.255.0 U 0 0 0 eth0 169.254.0.0 0.0.0.0 255.255.0.0 U 0 0 0 eth0 127.0.0.0 0.0.0.0 255.0.0.0 U 0 0 0 lo 0.0.0.0 192.168.1.1 0.0.0.0 UG 0 0 0 eth0 <snip> -- Donald D. Henson, Managing Director West El Paso Information Network The "Non-Initiation of Force Principle" Rules
Is there any particular reason you want to have two subnets on your LAN, behind the Linksys router? As you showed us, you have: 192.168.1.x/24 (from DHCP) 192.168.100.x/24 (static) So far in your email, I don't see any reason you just use DHCP subnet:192.168.1.x for all your PCs. And that's the way You can let all PC talk each other and let them access to the Internet at the same time. If you still want to use static IP instead of DHCP, you can assign ones outside of DHCP range on the Linksys, but still within the 192.168.1.x/24 subnet, as I wrote in my last email. In your original email, you wrote.... "..., at the same time, use DHCP provided by my ISP to go outside my local network to the Internet." The DHCP range from your ISP is different/separated from the Linksys's DHCP range. If you can get in the Linksys, you should be able to see the public IP address (in my Cable internet case, it's 24.x.y.z; I don't want to reveal my public IP to the world) DHCPed by your cable company. My case, I have a PIX FW as a router, like your Linksys, that keeps the 24.x.y.z and provide NAT(Network Address Translation) to bridge the Internet and my LAN 198.162.254.x/24. All my PCs are in this subnet. And SuSEx.xs and WinXP can talk each other at the same time all are connected to the Internet. If you know about this very well and have some reasons to have two subnets, please forgive me and ignore my comments above and just let us know about it. Toshi
I haven't been following this thread enough to know if someone mentioned this, but in order for your XP machine to communicate with anything else on the network (besides the Internet) all of the machines must belong to the same workgroup. The default for XP is usually MSHOME or WORKGROUP. You can set a workgroup in Samba that matches your XP workgroup, or change your workgroup in XP. I think the default in Samba is WORKGROUP. To check (and change) your workgroup in XP, right click 'My Computer' and select properties from the context menu that pops up. Click the tab titled 'Computer Name'. You will see the workgroup that XP belongs to in the information on this tab. If you need to change the workgroup click the 'Change' button, also on this tab. In the workgroup filed change the text to match what your Samba configuration says is the workgroup. If XP's workgroup matches Samba's already, it is sometimes worth renaming your computer, clicking 'Ok', and going through the XP Network Wizard that starts up as soo as you click 'Ok'. Windows can be flakey at times, and repeating previous work can sometimes fix a problem. Good luck, and I am sorry if this was covered. James W
James Wright wrote:
I haven't been following this thread enough to know if someone mentioned this, but in order for your XP machine to communicate with anything else on the network (besides the Internet) all of the machines must belong to the same workgroup.
I'm not using XP. All machines are running Linux. -- Donald D. Henson, Managing Director West El Paso Information Network The "Non-Initiation of Force Principle" Rules
Toshi Esumi wrote:
Is there any particular reason you want to have two subnets on your LAN, behind the Linksys router? As you showed us, you have: 192.168.1.x/24 (from DHCP) 192.168.100.x/24 (static)
Quite honestly, I don't know. Having two subnets just sort of happened when I was trying to switch from Samba to NFS. After some troubleshooting and advice from this list, NFS started working. NFS was able to use the static addresses and I was still able to access the Internet. The current problem occurred when I installed 10.0 (boxed set) on my laptop. I just want NFS and Internet access to work. If you see a way to get me there, I'll work with you as long as you're interested.
So far in your email, I don't see any reason you just use DHCP subnet:192.168.1.x for all your PCs.
Question. It appears that the router is also a DHCP server. That means that I do not need to activate DHCP on any of my machines. Right? I've set the router to start IP addresses at 192.168.1.2 and to issue a maximum of 50. Now if I configure all my network cards to use DHCP, NFS should work on all machines and all machines should be able to access the Internet. Right? And that's the way You can let all
PC talk each other and let them access to the Internet at the same time. If you still want to use static IP instead of DHCP, you can assign ones outside of DHCP range on the Linksys, but still within the 192.168.1.x/24 subnet, as I wrote in my last email.
Given my objectives, is there any reason to have a subnet with static IPs?
In your original email, you wrote.... "..., at the same time, use DHCP provided by my ISP to go outside my local network to the Internet."
The DHCP range from your ISP is different/separated from the Linksys's DHCP range. If you can get in the Linksys, you should be able to see the public IP address
Okay. I see that. (in my Cable internet case, it's 24.x.y.z; I don't
want to reveal my public IP to the world) DHCPed by your cable company. My case, I have a PIX FW as a router, like your Linksys, that keeps the 24.x.y.z and provide NAT(Network Address Translation) to bridge the Internet and my LAN 198.162.254.x/24. All my PCs are in this subnet. And SuSEx.xs and WinXP can talk each other at the same time all are connected to the Internet.
If you know about this very well and have some reasons to have two subnets, please forgive me and ignore my comments above and just let us know about it.
Thus far, your comments have been the most help. Please bear with me.
Toshi
-- Donald D. Henson, Managing Director West El Paso Information Network The "Non-Initiation of Force Principle" Rules
On Sunday 16 October 2005 01:15 pm, Donald D Henson wrote:
Question. It appears that the router is also a DHCP server. That means that I do not need to activate DHCP on any of my machines. Right?
Nope.... just go into YAST and set up your nics so they USE dchp. That's all that is needed.
I've set the router to start IP addresses at 192.168.1.2 and to issue a maximum of 50. Now if I configure all my network cards to use DHCP, NFS should work on all machines and all machines should be able to access the Internet. Right?
And that's the way You can let all
PC talk each other and let them access to the Internet at the same time. If you still want to use static IP instead of DHCP, you can assign ones outside of DHCP range on the Linksys, but still within the 192.168.1.x/24 subnet, as I wrote in my last email.
Given my objectives, is there any reason to have a subnet with static IPs?
Well maybe... (once you understand how things work :-) I use static IP addresses and place the names of all the machines into /etc/hosts If you use DHCP, you're not always going to know what IP address a particular machine has. With static IP's you would.
Bruce Marshall wrote:
If you use DHCP, you're not always going to know what IP address a particular machine has. With static IP's you would.
Slightly beside the point here, but we allocate fixed addresses over DHCP. Much easier to have all machines be DHCP clients, whether they need a dynamic or a static address. If we need a static address, we just update the /etc/dhcp.conf to have it dished out. /Per Jessen, Zürich
On Sunday 16 October 2005 01:55 pm, Per Jessen wrote:
Bruce Marshall wrote:
If you use DHCP, you're not always going to know what IP address a particular machine has. With static IP's you would.
Slightly beside the point here, but we allocate fixed addresses over DHCP. Much easier to have all machines be DHCP clients, whether they need a dynamic or a static address. If we need a static address, we just update the /etc/dhcp.conf to have it dished out.
That too..... but hopefully he can get started first. He could also have the router assign IP's based on MAC address.
Bruce Marshall wrote:
Well maybe... (once you understand how things work :-) I use static IP addresses and place the names of all the machines into /etc/hosts
If you use DHCP, you're not always going to know what IP address a particular machine has. With static IP's you would.
At this point, my problem seems to have been an address conflict between DHCP and static IPs. Now that they are in separate ranges, everything seems to be working much better. (I still can't get my wireless lan card to work but that appears to be a whole other problem.) -- Donald D. Henson, Managing Director West El Paso Information Network The "Non-Initiation of Force Principle" Rules
participants (5)
-
Bruce Marshall -
Donald D Henson -
James Wright -
Per Jessen -
Toshi Esumi