Message Board -  Archive

[ Login ] [ Create Account ]
[ Board List ] [ View Board ] [ Post Reply ]
  Author  Subject: Re: Samba
Archive  

Posted on 05-15-2000 03:33 a.m. ET  reply

Original Poster: Mark Krentel

About Samba ... Well, I don't run samba, roadrunner or dhcp, but this
is really a network issue, not a samba issue. I'm guessing that your
Linux samba server has one ethernet card and that the line from your
cable modem goes directly to your hub and then to your two machines.
Right?

The best solution is to use two network cards. Connect one (eth0) to
the cable modem and the other (eth1) to your hub and then on to the
rest of the private network. You let DHCP do its thing with eth0.
You configure eth1 with a simple, static 10.0.0.1 address. No fuss,
no interference, it works, and ethernet cards are cheap.

Now, if you insist on using one network card, here's your quicky
lesson on IP aliasing. Read the NET-3-HOWTO and the IP-Alias mini
howto. Configure your kernel with IP Aliasing, compile and install
the custom kernel. You can then put aliases on your interface with
names like eth0:0. For example:

# ifconfig -a
eth0 Link encap:Ethernet HWaddr 00:40:05:4D:35:63
inet addr:192.168.1.1 Bcast:192.168.1.255 Mask:255.255.255.0
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
...
# ifconfig eth0:0 192.168.1.100
# ifconfig -a
eth0 Link encap:Ethernet HWaddr 00:40:05:4D:35:63
inet addr:192.168.1.1 Bcast:192.168.1.255 Mask:255.255.255.0
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
...
eth0:0 Link encap:Ethernet HWaddr 00:40:05:4D:35:63
inet addr:192.168.1.100 Bcast:192.168.1.255 Mask:255.255.255.0
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1

After setting the aliases, the interface will respond to both 192.168.1.1
and 192.168.1.100. Now, I'm not sure what DHCP will do about the alias.
You may have to reset it manually after DHCP runs. But definitely put a
10.0.0.1 address on the interface. Don't mess with the samba config file.

--Mark

< Previous 1 Next >

Site Contents