-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Patrick Shanahan wrote: > > My Netgear wireless router, WGT624 v3, crashed. The wired section no > longer provides DHCP. In order to provide service (wireless) for my > wife (and maintain a generally pleasant environment) I replaced with > wireless with an old Netgear RP114, long out of service. > > I now have modem to RP114 to base computer and using another port on > the RP114 to input on the WGT624 provide wireless to my wife's computer. > > Addressing on the RP114 is 192.168.0.1 and my box becomes 192.168.0.2 > Netstat shows connections also from 192.168.1.2 to 192.168.1.1 (which > *was* the WGT624 addr). > > udp 0 0 192.168.1.2:30724 192.168.1.1:domain ESTABLISHED > udp 0 0 192.168.1.2:51408 192.168.1.1:domain ESTABLISHED > > > I have changed /etc/resolv.conf to use 192.168.0.1 as nameserver. > > Ipconfig on my wife's computer indicates it is 192.168.1.3 with a > gateway of 192.168.1.1. > > I cannot ping 192.168.1.[1-3] > > What changes do I need to make to connect with samba via my home > network, or is my only choice spending $$$s. > > > 192.168.0.1 192.168.0.2 > Modem --> RP114 ---> MyComputer > \ > \ > WGT624 --> (Wireless) ==> Wife Computer > 192.168.1.1 192.168.1.3 > > I can access the WGT624 from my wife's computer, but not the RP114. > I can access the RP114 from my computer, but not the WGT624 > > at least not at my knowledge level :^) > > tks,
a) For an environment involving 2 or 3 machines DHCP is more likely to give grief than any benefit, static addressing is probably easier to maintain. I know DHCP seems easy but there are some hidden pitfalls in DHCP which the naive can fall into. If you wish to continue using DHCP make damn certain that only one device is supplying addresses, otherwise you will playing network address lotto. b) Are you maintaining a local DNS? If not it it has just possibly become a good idea :-). c) 192.168.XXX.XXX (and 10.XXX.XXX.XXX) addresses are nominally non routeable, I have run into problems where some routing stuff has been a little too strict about interpreting this. But this usually can be worked round by tweaking routing tables and creating appropriate static routes. d) If you cannot configure things so that all the machines are are on the same subnet (i.e all on 192.168.0.x or 192.168.1.x) I would have a look at the routing tables to ensure that the route between 192.168.0.1, 192.168.1.3, and 192.168.1.3 and the rest of the world are defined, and for samba purposes part of the same DNS domain (this can be done either with Bind or the /etc/hosts file). I would spend a little time with LNAG (Linux Network Administrators Guide) which is usually somewhere in the SuSE documentation, and IMHO a must read for anyone who wants to play with networking... - -- ============================================================================== I have always wished that my computer would be as easy to use as my telephone. My wish has come true. I no longer know how to use my telephone. Bjarne Stroustrup ============================================================================== -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.5 (GNU/Linux) Comment: Using GnuPG with SUSE - http://enigmail.mozdev.org iD8DBQFHGc9fasN0sSnLmgIRAmDGAJ9z+L36A4sa7SNg0Kj/rocXbxODYACfRe04 CgOZAahSSRSArtzchVGVfkM= =kG3H -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
