The setup is ISP -> DSL -> Linksys Router -> LAN LAN igor: SuSE9.1 and W2000Pro abnormal: SuSE9.1 inga: SuSE9.1 and W2000Pro Igor and AbNormal are always on the LAN, Inga, a laptop, is on and off the LAN. I think, at least I hope, that I finally have got the router figured out. At least, all three machines can access the internet and each on the LAN can ping the others. If I understood the tech support person at Linksys correctly the router is assigning ip's to each machine as it comes up on the LAN. The CHCP network address server settings has the local DHCP server enabled with a start address of 192.168.1.100 and 50 addresses. When everything is down I always bring up igor first which should assign the ip 192.168.1.100, and, in fact, does. Next is the part that has me totally confused. Once igor is up I bring abnormal on the LAN and he should be assigned the ip 192.168.1.101. However, if I do ifconfig on igor I get: eth0 Link encap:Ethernet HWaddr 00:A0:CC:78:C9:1F inet addr:192.168.1.102 Bcast:192.168.1.255 Mask:255.255.255.0 inet6 addr: fe80::2a0:ccff:fe78:c91f/64 Scope:Link UP BROADCAST NOTRAILERS RUNNING MULTICAST MTU:1500 Metric:1 RX packets:8175 errors:0 dropped:0 overruns:0 frame:0 TX packets:5014 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:100 RX bytes:9015344 (8.5 Mb) TX bytes:486525 (475.1 Kb) Interrupt:11 Base address:0x6000 lo Link encap:Local Loopback inet addr:127.0.0.1 Mask:255.0.0.0 inet6 addr: ::1/128 Scope:Host UP LOOPBACK RUNNING MTU:16436 Metric:1 RX packets:453 errors:0 dropped:0 overruns:0 frame:0 TX packets:453 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:31789 (31.0 Kb) TX bytes:31789 (31.0 Kb) So I wondering where in this business is the Router's local DHCP setting being overwritten by what which results in abnormal being assigned the ip 192.168.1.102? This problem, and its' predecessors, have been driving me up the wall for several weeks now. Of course, it would help if only I knew what I was doing. My ultimate goal is to get the LAN machines talking to each other so that I can transfer files and use the printer which is currently connected to igor. I used to be able to do this before I had the DSL line and the Router. Hopefully, with assistance I'll be able to get there again. One final question, my printer is a HP DeskJet 612C. Is there any way that I can access this as a networked printer? That is, not directly attached to igor? Thanks in advance.
On Thursday 15 January 2004 13:22, Stephen P. Molnar, Ph.D. wrote:
So I wondering where in this business is the Router's local DHCP setting being overwritten by what which results in abnormal being assigned the ip 192.168.1.102?
First of all there is no reason to assume that a dhcp server will always assign addresses sequentially. As long as it doesn't assign the same address to two machines, a server is free to hand out addresses in any order it likes. Secondly, dhcp servers hand out addresses with a lease time, the length of which depends on how you configured it. If you start up machine foo on the nmetwork and it was assigned 192.168.1.101, the router won't assign that address to another machine *at least* until the lease time expires.
This problem, and its' predecessors, have been driving me up the wall for several weeks now. Of course, it would help if only I knew what I was doing.
My ultimate goal is to get the LAN machines talking to each other so that I can transfer files and use the printer which is currently connected to igor. I used to be able to do this before I had the DSL line and the Router. Hopefully, with assistance I'll be able to get there again.
Two options that I can see: either get the dhcp server to dynamically update a dns server, so that you always use one name for one machine, even if the IP changes, or assign static IP addresses to the machines, outside the dhcp address space and only use dhcp for machines that are only on the LAN temporarily
On Thursday 15 January 2004 12:22 pm, Stephen P. Molnar, Ph.D. wrote:
The setup is ISP -> DSL -> Linksys Router -> LAN
LAN
igor: SuSE9.1 and W2000Pro abnormal: SuSE9.1 inga: SuSE9.1 and W2000Pro
Igor and AbNormal are always on the LAN, Inga, a laptop, is on and off the LAN.
I think, at least I hope, that I finally have got the router figured out. At least, all three machines can access the internet and each on the LAN can ping the others. If I understood the tech support person at Linksys correctly the router is assigning ip's to each machine as it comes up on the LAN. The CHCP network address server settings has the local DHCP server enabled with a start address of 192.168.1.100 and 50 addresses.
When everything is down I always bring up igor first which should assign the ip 192.168.1.100, and, in fact, does.
You cannot rely on DHCP assigning the same address to a machine just by booting order. DHCP can assign any address within its range. You can (depending on the features of the DHCP server) associate a MAC address with an IP address, which will garuntee the same assignment each time.
Next is the part that has me totally confused. Once igor is up I bring abnormal on the LAN and he should be assigned the ip 192.168.1.101. However, if I do ifconfig on igor I get:
eth0 Link encap:Ethernet HWaddr 00:A0:CC:78:C9:1F inet addr:192.168.1.102 Bcast:192.168.1.255 Mask:255.255.255.0 inet6 addr: fe80::2a0:ccff:fe78:c91f/64 Scope:Link UP BROADCAST NOTRAILERS RUNNING MULTICAST MTU:1500 Metric:1 RX packets:8175 errors:0 dropped:0 overruns:0 frame:0 TX packets:5014 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:100 RX bytes:9015344 (8.5 Mb) TX bytes:486525 (475.1 Kb) Interrupt:11 Base address:0x6000
lo Link encap:Local Loopback inet addr:127.0.0.1 Mask:255.0.0.0 inet6 addr: ::1/128 Scope:Host UP LOOPBACK RUNNING MTU:16436 Metric:1 RX packets:453 errors:0 dropped:0 overruns:0 frame:0 TX packets:453 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:31789 (31.0 Kb) TX bytes:31789 (31.0 Kb)
So I wondering where in this business is the Router's local DHCP setting being overwritten by what which results in abnormal being assigned the ip 192.168.1.102?
Like I said above...
This problem, and its' predecessors, have been driving me up the wall for several weeks now.
This is only a problem because you expect the system to function differently to how it does.
Of course, it would help if only I knew what I was doing.
We all have to learn that one!
My ultimate goal is to get the LAN machines talking to each other so that I can transfer files and use the printer which is currently connected to igor. I used to be able to do this before I had the DSL line and the Router. Hopefully, with assistance I'll be able to get there again.
Is there a reason why you are not using static IP assignments. With so few machines DHCP is not really necessary and complicates the other things you are trying to achieve. Having said that, my ADSL modem/ router will only talk to boxes which it has assigned an IP to (for security reasons, I assume.) Dylan -- "They that can give up essential liberty to obtain a little temporary safety, deserve neither liberty nor safety." -Benjamin Franklin
participants (3)
-
Anders Johansson -
Dylan -
Stephen P. Molnar, Ph.D.