samba - Oct 1998 - samba and dhcp problem

Hello,

	Can someone please help me out with the following. I have 
installed Samba for FreeBSD. It runs and at *times* runs great. But 
here is the big problem. Well the problem involves the ISP I am 
connected to, I think. 

	I am connected to the Internet via cablemodem. The cable co. 
uses a dhcp server. From time to time the IP's change. Today I 
was lucky as all my IP's were in the 24.64.136 range. With all 3 
IP's from the cablemodem using those set of numbers, and using 
Samba to say listen to MP3's (as a test) I noticed immediately that 
the sound was no longer broken up. I looked at the hub and further 
noticed that the pc's were talking to each other without going out to 
the net as had been the way it was prior. 

	After installing corel8, and rebooting one of the windows 
machines, I had the misfortune of having one windows machine 
coming up with 24.64.138.88 and I was back to broken sounds, not 
being able to re-connect to shared drives (via samba on FreeBSD 
box..which IP had not changed). I then edited smb.conf in the allow 
hosts section to have it as:
hosts allow = 24.64.136. 24.64.138. 127.
but this did not help. So, I entered in networking, in Win98 control 
panel, in the section "specify IP address" my old IP and rebooted. 
When the system came back up, I had my old number. I enabled 
(prior) wins server in SMB.CONF and in WINS, in network, I put the 
address of the FreeBSD box. Now after rebooting with the above, 
forcing my old ip to be used, I am again able to listen to those 
MP3's unbroken.

	Is there some sort or work around to all this. There will come a 
time shortly when I will not be able to get my old IP #. I thought by 
adding in hosts allow that the other set of IP #'s (24.64.136 and 
24.64.138) would be sufficient. But it seems not to be. I guess 
what I am saying is that for many things to run well, they must go 
via the ethernet and not out to the internet. Which just slows things 
down to a snails pace.

Thank you in advance for any help which you may be able to offer.

Lanny Baron

Hi

If I understand your situation corretly, you have all your pcs connected to
a hub (via rj-45?) which is also the cable-modem that connects you to your
provider. The clients get their ip-address thru dhcp from the provider.

Normally (at least with win95) pc connected to the SAME ethernet can only
"speak" to each other correctly if they are in the same subnet - if
they are
not, all the traffic will go thru your cable-modem which is of course slow.

With Linux or FreeBSD you can simply do the following:
I assume PC1 has 192.168.10.1 (netmask 255.255.255.0)
and PC2 has 192.168.20.1 (netmask 255.255.255.0)

Then you add BOTH nets on BOTH PC:
route add -net 127.0.0.1 lo (i guess everyone has a loopback device...)
route add -net 192.168.10.0 eth0
route add -net 192.168.20.0 eth0
route add default gateway <whatever your gateway ist> eth0

I guess with Win95 you can do the same, but win95 identifies interfaces not
with eth0, eth1 like linux (i guess freebsd is similar) does, but via the
ip-address of the interface. I never tried to manually add routes in win95,
but there is a program called route with should enable you to do this.

Have a lot of fun with 95...

                                                greetings, fgp