46
Installation issues / Re: Can access internet but not network or router?
« on: March 07, 2008, 08:57:20 pm »Quote
Actually, I think it is just the nature of DHCP and subinterfaces - DHCP uses an Ethernet broadcast, which will be visible on both the main interface and subinterface. So even though the DHCP server is supposed to be serving the internal network only, the DHCP request from the external interface will still make it there, and so screw up your network connectivity if you are using different subnets for "internal" and "external".... it also means that you will see the strange behaviour of the DHCP-PnP system "discovering" itself as a fileserver, and ask you if you want to add it! It appears as DCEROUTER of course and can be a bit confusing. You should definitely so no, and don't ask again to this...that is what i figured.
Quote
If the external and internal subnets are the same, you have one NIC, and you configure the LMCE DHCP server so that the gateway is your "real" router (say, the broadband router) as opposed to itself. Then turn off all other DHCP servers other than the LMCE one, you should have a network that works, doesn't push all the external traffic through the core, lets you add wireless APs, but LMCE's PnP system will still work. You won't have QoS for your telephony, and it may cause obscure problems because LMCE doesn't understand its own topology... but it should work OK. But definitely no VLANs...I think it's personal preference, but i'd rather use the DHCP server on my existing router/firewall/linuxbox/whatever if it's been proving to work reliably and remain stable. Splitting your dependencies for internet connectivity should be a very HUGE no no. I would disable the lmce dhcp server. If not, then something happens to your lmce box, it's off, it's got a broken install, whatever, now your stuck taking extra steps to manually assign ip's to the other computers on your network to get internet connectivity while you repair your lmce box. That is just one scenario of splitting your gateways responsibilities up.
I will admit i'm not too sure if disabling lmce's dhcp server will break it's device management, like for net shares, and definately no booting MD's without modifying your other DHCP server settings to point it in the right direction for it's boot kernel and filesystem. So I see it as a toss up, if you don't plan on use MD's then i'd disable the lmce dhcp.
We use vlans in our datacenters, and can understand why they are needed in an enterprise environment, hell i maintain our switches, but why would home users want to use vlans? other than they have too much money and time and just feel like buying expensive cisco switches that support vlans...
I mean, whatever on all counts really, it comes down to personal preference, collin and I have put all the relevant information you need to make a sound decision on your network config... have fun...
I will leave this thread with my setup.
_____ ___________ _____________________________ ___________
|Inet| - |Cablemodem| - |Firewall Box/Wifi/Router/Whatever| - |Computer 1|
----- ------------- --------------------------------- -------------
^Running DHCP server^ | Computer 2|
Configured to serve MDs ----------------
|LinuxeMCE Box| < 1 Network card, DHCP disabled
---------------
Like I said, doing it like that requires some extra configuration to get diskless booting media directors to work. I might make a wiki entry on how to do this one day when I run out of lmce stuff to troubleshoot.