Hi,
I have installed from DVD onto a PC has one NIC. I have the PC connected to a switch and a laptop also connected to the switch no ADSL router in sight :)
The core allocates an IP address internal 192.168.80.1 with external 192.168.80.254.
I have my laptop, running windows XP to obtain a DHCP address supposedly from the core but it does not. If I manually allocate 192.168.80.5 to my laptop it allows me to connect to the Admin webpage.
I want to PXE boot my laptop but if DHCP is not working on the core what chance have I got?
I have installed and reinstalled about 4 times now.
HELP !!!!!
Incidentally is there any way from the DVD install to only install Core not Media Director also?
Thanks
Search the wiki for DHCP for your DHCP problems.
I wouldn't have posted this if I had found anything on DHCP not working.
I cannot connect with static IP on PC but when I put that magic little dot in the circle next to obtain IP from DHCP the CORE doesn't seem to work.
Is there any way to see if DHCP is working or Not????
You could try to 'repair network connection' in XP?
I have not seen this problem you describe ever, so sorry if this was not very helpful.
Quote from: ibexcentral on November 14, 2007, 12:36:22 PM
Hi,
I have installed from DVD onto a PC has one NIC. I have the PC connected to a switch and a laptop also connected to the switch no ADSL router in sight :)
The core allocates an IP address internal 192.168.80.1 with external 192.168.80.254.
I have my laptop, running windows XP to obtain a DHCP address supposedly from the core but it does not. If I manually allocate 192.168.80.5 to my laptop it allows me to connect to the Admin webpage.
I want to PXE boot my laptop but if DHCP is not working on the core what chance have I got?
I have installed and reinstalled about 4 times now.
HELP !!!!!
Incidentally is there any way from the DVD install to only install Core not Media Director also?
Thanks
One thing you could try is to change the external ip to a static ip on a different subnet. something like 192.168.81.1 and set a static for the internal ip for the core to 192.168.80.1
The external and internal should not share the same subnet.
I think I know what's going wrong here, what IP addresses do your modem and/or switch have? (whatever is connected directly to your LMCE box).
"Hi,
I have installed from DVD onto a PC has one NIC. I have the PC connected to a switch and a laptop also connected to the switch no ADSL router in sight Smiley
The core allocates an IP address internal 192.168.80.1 with external 192.168.80.254.
I have my laptop, running windows XP to obtain a DHCP address supposedly from the core but it does not. If I manually allocate 192.168.80.5 to my laptop it allows me to connect to the Admin webpage.
I want to PXE boot my laptop but if DHCP is not working on the core what chance have I got?"
You need Two NIC's in the PC if you want linuxmce to work properly (aka the way it was designed).
The 192.168.80.254 is a default bogus as there is no external NIC.
No ADSL router in sight, but you mentioned ADSL router. How do you get to the internet ?
Let's start over...to use linuxmce to it's full potential you need internet access and Two NIC's in the core (it will be limited otherwise)
To the internet, you have some sort of modem/router in a bridge, NAT, FW or combination thereof. Unless you have paid for static you have a DHCP assigned IP address to your connection from you provider. In your case, you have a laptop so connect it directly to the modem, with the appropriate cable, set the laptop to dhcp client request and do a ifconfig -a or windoze ipconfig /all...what's the IP address assigned ?
It will be either, public IP or a private address IP typically 192.168.1.x which is a NAT'd router typically with a firewall.
Add the second NIC and connect it to the modem. Connect the original NIC to the switch. Reboot and check the reported settings again from linuxmce (an external of 192.168.1.x and internal 192.168.80.1) you should be able to pull up google and youtube video under advanced - computing I think (not at my linuxmce test server I'm afraid)
Adding you laptop back on the switch and rebooting should give you a 192.168.80.x address
Reboot any other DHCP client systems and reset the static IP's to the 192.168.80.x range.
It's a lot simpler this way plus you have (depending on your ADSL box) a primary FW and a secondary linuxmce FW so if the primary is cracked, you have the secondary hopefully on a different code base.
You can run LMCE with a single NIC, as explained in the wiki's DHCP entry section on "Single NIC".
What this setup requires is that LMCE run as the only DHCP server on the network, which means that if your switch, or any other device on your network, is assigning IP#s by running a DHCP server, then that old server has to be switched off. There probably is one running, or else how would your notebook have gotten its old IP#? If it got it by manual assignment, then you have to either continue manually assigning an IP# on the subnet that the LMCE DHCP server is on and assigning in, or you have to set the notebook to get its IP# by DHCP. Which is a first step to getting the notebook to boot by PXEboot anyway.
Then you have to make sure any other machine connecting to the LMCE server is also set to get its IP# by DHCP, or is manually set to a number on the LMCE subnet. You make them all on the same subnet by looking at the IP# that LMCE is assigning itself (in its Network Settings, but default is 192.168.80.1) and manually assigning numbers in that subnet to the other machine, or setting the LMCE DHCP server to assign IP#s on the other machines' subnet (and excluding those other machines IP#s from the range assignable by LMCE, to avoid conflicts) or by setting the other machines to use DHCP, which lets LMCE assign their IP#. Pick the method for each machine, including LMCE, that lets them all share the same subnet. Often routers/gateways (like cablemodems etc) don't allow using a DHCP client to set their internal LAN IP#, but either assign themselves one from their own internal DHCP server, or let you set them manually. Since that internal DHCP server must be turned off, you'd have to set it manually.
There are more details on working around bugs in LMCE DHCP configuration included in that DHCP wiki page.
Please return the favor of all this help by letting us know how it goes for you. If it still doesn't work, and this is a new case, we can fix it and document the scenario for the next person to encounter it.
Matthew said :-
You can run LMCE with a single NIC, as explained in the wiki's DHCP entry section on "Single NIC".
Yes, that's why I said on my first line...
"You need Two NIC's in the PC if you want linuxmce to work properly (aka the way it was designed)."
ie. instead of just making sure you have the cables in the correct NIC's (in most cases), if you have one NIC you have to:-
1) Turn off DHCP in your modem/NAT Router (as they usually come turned on by default)
2) Assign a static IP to Linuxmce
Which is beyond most newbies as evidenced from the repeated questions in the forums.
You also lose the FW plus bandwidth control ie. think priority on the network for VOIP and video.
For the sake of a $20 or less gigabit ethernet card (or less for 100Mb) and all the hassle and loss, I don't think it's worth it, but go knock yourself out. YMMV (Your Mileage May Vary).
Indeed, it's just not worth saving the $5 or so on an 100mbit PCI nic unless you know what you're doing.
Quote from: marrandy on November 16, 2007, 05:24:51 PM
Matthew said :-
You can run LMCE with a single NIC, as explained in the wiki's DHCP entry section on "Single NIC".
Yes, that's why I said on my first line...
"You need Two NIC's in the PC if you want linuxmce to work properly (aka the way it was designed)."
ie. instead of just making sure you have the cables in the correct NIC's (in most cases), if you have one NIC you have to:-
1) Turn off DHCP in your modem/NAT Router (as they usually come turned on by default)
2) Assign a static IP to Linuxmce
Which is beyond most newbies as evidenced from the repeated questions in the forums.
You also lose the FW plus bandwidth control ie. think priority on the network for VOIP and video.
For the sake of a $20 or less gigabit ethernet card (or less for 100Mb) and all the hassle and loss, I don't think it's worth it, but go knock yourself out. YMMV (Your Mileage May Vary).
It's not the $20 for the card that matters. It's the ability to use an existing PC without any HW work at all to
try out LMCE casually. Especially if one is making a nondedicated core, or dualbooting, or using an old notebook, or just casually trying it out, just installing the SW and making some configs is going to appeal to a lot of people, some of whom will like it enough to get serious. Which is how successful projects grow: lower the barriers to entry while offering organized instructions for doing it right. Which means keeping the docs (like the wiki) current with those uses, rather than just leave people twisting in the wind in unanswered (or crankily answered) forum posts.
a large selling point of lmce is supposed to be allowing nontechnical or mildly technical people to set this all up. installing new network cards, switches and routers isnt always as easy for them as pluggin in one cable. i know it takes a lot of work now to get a single nic going and obviously thats just as bad of a hurdle. maybe that will (should) get fixed one day to make it a little easier. it has been suggested before.
Well if you want easy... http://fiire.com/
sorry...for the nontechinical reader ill repeat myself
Quotea large selling point of lmce is supposed to be allowing nontechnical or mildly technical people to set this all up.
thats where the constant "plug n play" stuff comes from. its supposed to be easy to get it ALL set up. a single NIC install makes it easier for someone who doesnt know how to put in a switch or cant figure out how plugging two cables from the same computer into the dsl/wireless router they have now works and what they have to do. theres no reason it cant be made to allow a single nic install.
There's nothing stopping anyone from doing a single nic install.
However the recommended setup is with 2 NICs so that the nontechnical or mildly technical people can set this all up.
As with most things in life, you can't really have it both ways.
yeah thats very true you cant. i do agree that it really simplifies to just do it the way its intended. i think people would just like the option. idk...maybe supporting a single nic install isnt a good idea. maybe it would just overcomplicate it. people are going to have to buck up and learn something either way i guess.
I would agree in that all too often "the pro's" can give some really unhelpful posts where more effort is spent in picking holes than anything...
I'm from UK, and a complete LinUX failiure. Ask me about WiMAX/4G and I'll take you through the network but.....
I would also agree that there is something to be said for just trying MCE in modes (and with existing hardware) that it says it supports (even if they are not ideal) in order than you get a feel for what it is like without a major investment of time and money.
I have the same problem, that the DHCP on the MCE core appears not to be issuing IP addresses to devices on the 'local' network. I've used the latest DVD installer 7.4 and the hole process completed first time with no errors and relatively quickly, it has come on miles since the first ones I tried.
I am an experienced PC user, but an absolute LiNUX amature. I am sure at some point I've done something 'drastically wrong' but like the person who started this subject, I've reinstalled and read all the wiki-docs I could find many, many times. I've been involved (i.e. trying to get MCE working) on an off for over a year I think but still to no avail. A big selling point for me is the boot off LAN using many 'thin' or light weight clients to create a whole house solution.
Basically the question is does anyone successfully have the DHCP server working from their core with ONLY ONE NIC?
My setup is two PCs (both with only 1 NIC and no PCI for any more). There is no WAN so no internet, so no other DHCP. One PC is the core and the other has a WindowsXP disk but has 'boot on lan' higher in Boot Sequance (where it spends 10seconds everytime it restarts, requesting an IP).
As far as I know, I setup MCE 'normally' and followed all on-screan instructions. Checking in the MCE-admin that DHCP is enabled, etc.
The core (which is a hybrid) boots fine everytime and leaves you in the GUI where you can get to the MCE-admin website with access to all configuration settings.
When the boot on lan gives up, the comment is that it did not receive an IP address, press F1 to continue, etc.If you leave the 2nd (WindowsXP) PC to boot, it will not be assigned an IP address dynamically, even if you 'repair' (from windows) or 'release' and 'renew' (from Prompt) the connection.
Using wire-shark on the windows PC once it has booted, you see DHCP requests being generated by the windows PC, but they are not being answered.
The MCE hybrid is however generating many many ARP calls, which it is also not getting any response to. If it is the DHCP server surely it knows the MAC of each device its trying to get in touch with so why does it need ARP and why might the DHCP not be responding to the 'Discovery' requests??? Its as if the core's 'internal ethernet card' is not active or at least not visibile....
On one occasion I manually assigned the windowsXP PC with an IP and MCE immediately acknowledged the device and asked if it was a fileserver...? So they're definitely on the same network.
Does anyone have any ideas on this problem.... I would be really greatful if anyone could offer some creative input on this issue (that revolves around only having 1 NIC).
------------------------------------------------------------------------------------------------
Failing I have tracked down a free NIC and a friend's PC (which is also installed with MCE). Is there any plug and play with devices like NICs? because after we installed the card and restarted the MCE hybrid, there was no difference and no more eth's offered in the network settings from MCE-admin. Or is this a re-install job???
------------------------------------------------------------------------------------------------
At the very least I thank any of you for taking the time to read this ;D
I would recommend reinstalling the DVD after putting in the second NIC, there is no plug and play code to re-assign the devices yet.
You can try changing the Network Settings in the web admin.
-Thom
There is a wiki page describing the steps you'll need to add a second nic here: http://wiki.linuxmce.org/index.php/Single_to_Double_NIC as it involves a few changes in different places.
Quote from: jthomsit on December 09, 2007, 05:40:39 PM
Does anyone have any ideas on this problem.... I would be really greatful if anyone could offer some creative input on this issue (that revolves around only having 1 NIC).
From the various test results you posted, it sounds to me like there's something wrong with the
Windows machine's network behavior. Have you ever tested thte Windows machine to properly get its network configs from
any DHCP server?
Because the LMCE DHCP situation isn't really that complicated. The only trick is that the various network boots of devices that use LMCE services need to get
their configs from a DHCP server, which has to be the LMCE DHCP server (or some other you can insert those configs into, but since you usually can't do that - like with cablemodem or DSL routers etc - you have to use the core as the DHCP server), which means there cannot be another DHCP server on the LAN. Those are the reasons, but all it means is that LMCE has to be the DHCP server, and there's no other. And that's what you've got.
What you might try is to burn an Ubuntu liveCD, then boot your Windows machine off that, and see if Ubuntu gets its network configs properly from your LMCE DHCPd. If so, it's just Windows, which you sound like you can fix with your experience (like just reinstalling, like everyone else does :)). If that Ubuntu liveCD boot doesn't work either, it still sounds like it could be your Windows network card, so you should try that Ubuntu liveCD boot with a new NIC (either the free one you found, or some other - they cost $5-10 for 10/100Mbps, just get a popular one like a 3Com 3C905 or similar).
If its still not working, or even if it is, please keep posting in this thread, and we'll see how to work it out. Because unless its your unique individual HW or some corrupt Windows install, then others will probably have the problem, and we'll be fixing it for them, too.
Quote from: jthomsit on December 09, 2007, 05:40:39 PM
I would agree in that all too often "the pro's" can give some really unhelpful posts where more effort is spent in picking holes than anything...
I'm from UK, and a complete LinUX failiure. Ask me about WiMAX/4G and I'll take you through the network but.....
I would also agree that there is something to be said for just trying MCE in modes (and with existing hardware) that it says it supports (even if they are not ideal) in order than you get a feel for what it is like without a major investment of time and money.
I have the same problem, that the DHCP on the MCE core appears not to be issuing IP addresses to devices on the 'local' network. I've used the latest DVD installer 7.4 and the hole process completed first time with no errors and relatively quickly, it has come on miles since the first ones I tried.
I am an experienced PC user, but an absolute LiNUX amature. I am sure at some point I've done something 'drastically wrong' but like the person who started this subject, I've reinstalled and read all the wiki-docs I could find many, many times. I've been involved (i.e. trying to get MCE working) on an off for over a year I think but still to no avail. A big selling point for me is the boot off LAN using many 'thin' or light weight clients to create a whole house solution.
Basically the question is does anyone successfully have the DHCP server working from their core with ONLY ONE NIC?
Hi there... we're in the UK too ;-)
All our Cores are setup as standard with a single NIC. So single NIC installations are 100% the norm for us.
Our setups are as follows;
Wireless Router (WAN side hooked up to broadband router and usually DHCP from broadband provider)
Wireless router has LAN side DHCP off and we set them up as follows;
Local IP of Wireless Router: 192.168.20.1
Subnet Mask: 255.255.255.0
Gateway: 192.168.20.1
The Core/Hybrid is setup as follows;
EXTERNAL_IFACE eth0
EXTERNAL_MAC XX:XX:XX:XX:XX:XX
EXTERNAL_IP 192.168.20.99
EXTERNAL_NETMASK 255.255.255.0
EXTERNAL_DHCP 0
INTERNAL_IFACE eth0:0
INTERNAL_MAC XX:XX:XX:XX:XX:XX
INTERNAL_IP 192.168.80.1
INTERNAL_NETMASK 255.255.255.0
GATEWAY 192.168.20.1
DNS1 192.168.20.1
DNS2 192.168.20.1
As you can see from the above info the Core's External IFACE is set to a fixed IP of 192.168.20.99 (ie in the same range as the Wireless Router) while its internal IFACE is set to 192.168.80.1 with its Gateway & DNS set to the IP of the Wireless Router (make sure that the 'Use a static IP address' is selected in Web Admin -> Adbanced -> Network -> Network Settings). The Wireless router will then issue addresses in 80.1 range (perfect for any mobile devices that you might want to connect to your Core/Hybrid). Devices set to PXE boot like your Windows XP machine should be connected either directly, or via additional routers if required, to one of the LAN ports on the Wireless Router. They will then boot of the network and be issued DHCP addresses in the 80.2 & upwards range.
Thats all there is too it ;-)
Hope this helps you
Andrew
Hey guys,
Firstly I'd like to say thanks for the responses (shocked by how quick you've all responded), this is obviously a reasonably hot topic ;) and you've certainly given me some great options and I'm sure at least one will get me unstuck.
1) really positive that you've got systems that are running problem free with one NIC
2) I think the window's system is fine because when I try 'boot on lan' on a network 'owned' by an ADSL modem/router, it did receive an IP assignment (obviously still didn't boot as there is nothing on that network to boot from)
I'll definitely try the manual settings posted by totallymaxed however I've also been trailing the forums and found... http://wiki.linuxmce.org/index.php/Known_Issues (http://wiki.linuxmce.org/index.php/Known_Issues)
This matches up with 'totallymaxed' config.... MCE has named the 'virtual' internal ethernet card 'eth1' not 'eth0:0', this may be just a really small bug/funny, hopefully this will get everything working (fingers crossed).
One question about that config... how did you enter 'XX:XX:XX:XX:XX:XX' is that literally it or is it left blank?
Thanks all, I'm out of the country for a bit but I'll try to update on progress ASAP...
Quote from: jthomsit on December 09, 2007, 08:30:32 PM
I'll definitely try the manual settings posted by totallymaxed however I've also been trailing the forums and found... http://wiki.linuxmce.org/index.php/Known_Issues (http://wiki.linuxmce.org/index.php/Known_Issues)
This matches up with 'totallymaxed' config.... MCE has named the 'virtual' internal ethernet card 'eth1' not 'eth0:0', this may be just a really small bug/funny, hopefully this will get everything working (fingers crossed).
One question about that config... how did you enter 'XX:XX:XX:XX:XX:XX' is that literally it or is it left blank?
Thanks all, I'm out of the country for a bit but I'll try to update on progress ASAP...
The settings i provided are just the end result of a normal install.
The 'XX:XX:XX:XX:XX:XX' was just me 'blanking' out my Mac Addresses... your installation will get these from your NIC automatically.
Cheers, I'll give it a try ;)
Quote from: jthomsit on December 10, 2007, 01:59:26 PM
Cheers, I'll give it a try ;)
Keep us updated on how you get on ;-)
Hello, I would just like to tell you that I have a core setup with only 1 NIC and it is doing it all! I did scratch my head for a couple hours and reinstalled several times before I figured out something I had missed! After enabling the DHCP server during the install you have to go to the Admin website and configure it. Advanced -> Network -> Network Settings. You have to identify an ip address for both Pluto and non-Pluto devices! If not then the DHCP server appears not to function! Hope this helps. By the way a single NIC is very easy to use!