Hello guys, I'm at my wits end.. hope someone can help.. this is the deal. I have setup a linux box to serve as a "gateway" for our internal lan. Running 2.0.34 slakware. I have 2 nic cards.. One for our "internal" lan (192.168.2.0) and the "external" lan..I have gotten the OS to see both of them, but when trying to get DHCP to work with both, it kept barfing.. so i used ip_aliasing on the external nic and put the "internal" host address (192.168.2.1) on eth0:1. DHCPD seemed to work.. then i installed and configured ip_masq. That worked.. Now i installed samba. the latest. This compiled and setup with no problem, but looking at network neighborhood, i cant see my server.. Now going thru the archives i see other people put, the nic cards on the win95 machines to lm announce to yes and browser master to automatic.. this did nothing.. putting the samba server in the same workgroup didn't change it either.. Its odd that i cant telnet to the machine using its ip or its host name from one of the win95 clients, but the machines are getting there dynamicip from it. the DNS is set for our DNS server that knows about the linux machine also.. also by doing a "winipcfg" i see that the win95 clients sees the DHCP server as our "external" ip not the "internal" one. and i suspect that to be the cause ( related to the ip_alaising for dhcp). Anyone have some clues or pointers as to where to look further? My smb.conf file is at http://www.successnet.net/~hshaw/dowloads/smb.conf Thanks.. Terrelle Shaw
Hello guys,
I have CC'd this to the dhcp-server mailling also to see if anyone can
offer help.
Presently im using dhcp-2.0.b1pl1 but as of this writing im d/l hdcp-2.0b1pl6.
I'm at my wits end.. hope someone can help.. this is the deal.
I have setup a linux box to serve as a "gateway" for our internal lan.
Running 2.0.34 slakware. I have 2 nic cards.. One for our "internal"
lan
(192.168.2.0) and the "external" lan..I have gotten the OS to see
both of them, but when trying to get DHCP to work with both, it kept
barfing.. so i used ip_aliasing on the external nic and put the
"internal"
host address (192.168.2.1) on eth0:1. DHCPD seemed to work.. then i
installed and configured ip_masq. That worked.. Now i installed samba.
the latest. This compiled and setup with no problem, but looking at
network neighborhood, i cant see my server.. Now going thru the archives
i see other people put, the nic cards on the win95 machines to lm announce
to yes and browser master to automatic.. this did nothing.. putting the
samba server in the same workgroup didn't change it either..
Its odd that i cant telnet to the machine using its ip or its host name
from one of the win95 clients, but the machines are getting there
dynamicip from it. the DNS is set for our DNS server that knows about the
linux machine also.. also by doing a "winipcfg" i see that the win95
clients sees the DHCP server as our "external" ip not the
"internal" one.
and i suspect that to be the cause ( related to the ip_alaising for dhcp).
Anyone have some clues or pointers as to where to look further?
My smb.conf file is at http://www.successnet.net/~hshaw/dowloads/smb.conf
Thanks..
Terrelle Shaw
hshaw@successnet.net
"I sync, therefore i think.."
> Just for others on the list.. > "barfing" meaning it gives some errors and refuses to start. I have sense > gotten it to at least work with ip_aliasing the "external" interface NIC > card, and configured the other NIC card to not be > configured upon boot up in order to get DHCPD to run correctly. > If it sees the other nic card upon boot..it.. "blows" , just doesn't run. > Hope this helps.. > Is anyone else running DHCPD with two NIC cards installed on there box, > and have dhcpd serving clients from ONE of those NIC's?How about 4 NICs, DHCPD on 3 of them, and NATD (ip masquerading) on 1 of them? de0 <Digital 21140A Fast Ethernet> rev 32 int a irq 12 on pci0:10:0 de0: 21140A [10-100Mb/s] pass 2.0 de0: address 00:80:c8:3e:34:02 de1 <Digital 21040 Ethernet> rev 35 int a irq 10 on pci0:11:0 de1: 21040 [10Mb/s] pass 2.3 de1: address 00:c0:d1:30:08:02 ed0 at 0x310-0x31f irq 5 maddr 0xcc000 msize 8192 on isa ed0: address 02:60:8c:a2:d5:b3, type 3c503 (8 bit) ep0 at 0x300-0x30f irq 15 on isa ep0: aui/utp[*AUI*] address 00:a0:24:0a:ed:f6 DHCPD on de0, de1, and ed0. NATD on ep0. This is with dhcp-2.0b1pl1 on FreeBSD, not Linux, though... Dan Eischen eischen@no-spam.vigrid.com
> > > "barfing" meaning it gives some errors and refuses to start. > > ARRRRGGHGHGGHHGGGG@!!!!!!! > > OBVIOUSLY that's what BARFING means. What I was ASKING for were the > ERROR MESSAGES it PRINTED!!!!! ARRGGGHHH!!! Why are people so shy > about sending actual *information* in their bug reports?!? > > *pant* > > Sorry. I just had to get that off my chest. > > > Is anyone else running DHCPD with two NIC cards installed on there box, > > and have dhcpd serving clients from ONE of those NIC's? > > Yes. It shouldn't be barfing on Linux 2.0.34. That's why I asked > you what error message it printed. This time, please send us the > error message, rather than further explaining what barfing means. > :'} > > _MelloN_ >As i have explained, i got it working with ip_aliasing on one of my NICS, so the error mesg. whtat was produced i no longer have. When i get physical access to the box, and reconfigure it I'll try again and send in the error i get. I was at least 3 weeks ago when i tried this so i don't even remember what it was vaguely... Thanks for your concern, i'll email you the error when i get a chance..