LinuxMCE Forums

General => Users => Topic started by: Matthew on November 09, 2007, 09:40:56 pm

Title: Changing CORE IP#?
Post by: Matthew on November 09, 2007, 09:40:56 pm
When I installed LMCE, I accepted its offer to run a DHCP server, even though my LAN already has one running, and the LMCE PC has only one ethernet port, which is connected to that LAN. Now I can't ping between the LMCE host and other hosts on the LAN. Or to the router on the LAN (so, eg. (apt-get update) fails to connect).

How can I make the LMCE PC use the LAN DHCP? Is its IP# stored anywhere but in its own DHCP config (and its DHCP client's cache, which seems to be pointing at its own DHCPd)? If I just remove the DHCPd startup from the Kubuntu startup scripts, can I just expect the LMCE to start up, use its DHCP client to get an address from my existing LAN DHCPd, and count on the IP# to propagate throughout LMCE properly?

I'd prefer to use an LMCE UI to fix this, but I'll use the Kubuntu desktop (and its commandline shell) without reservation if that's the only way.
Title: Re: Changing CORE IP#?
Post by: tschak909 on November 09, 2007, 10:00:28 pm
I recommend using LMCE's DHCP server, otherwise you will lose a great deal of plug and play functionality. With that said, the Web Admin gives you the ability to turn on and off the DHCP server.

-Thom
Title: Re: Changing CORE IP#?
Post by: teedge77 on November 09, 2007, 10:48:59 pm
how'd i know someone was gonna say that?  :D
Title: Re: Changing CORE IP#?
Post by: tschak909 on November 10, 2007, 02:41:58 am
i'm tellin ya... i'm gonna make a set of macros for us with canned responses. I'm getting slightly tired of people asking the same questions over and over without at least...seeing...oh...if they've been asked before...

-Thom
Title: Re: Changing CORE IP#?
Post by: Zaerc on November 10, 2007, 03:13:59 am
i'm tellin ya... i'm gonna make a set of macros for us with canned responses. I'm getting slightly tired of people asking the same questions over and over without at least...seeing...oh...if they've been asked before...

-Thom

That's more or less how I use the wiki, easier to paste an url then to repeat the same things over and over again.

Next I'm willing to bet Matthew is going to comment how he just wants a media center without the other features... ;)
Title: Re: Changing CORE IP#?
Post by: Matthew on November 12, 2007, 02:57:59 am
I did search the forums for "dhcp", but I got a long list of results to comb through, with very few matching my config (single NIC, version 0704). The one thread (http://forum.linuxmce.org/index.php?topic=2144.0) that specifically addressed my actual question included some flat assertions that changing the /etc/network/interfaces value was the simple answer, with no complex intermediary dependencies distributed throughout the rest of LMCE, and then some contradictions with evidence of that. As well as some confused anwsers, including some from you, Zaerc. But not a conclusive answer of whether changing the IP# in its OS-authoritave location would create inconsistencies among other LMCE dependencies not updating properly.

And I couldn't find any other clear answer to why the LMCE has to be the DHCP server for my network. Or any discussion of why its DHCPd would set up a subnet that can't connect to my router, when there's an existing DHCPd running on that router.

Maybe this question is indeed asked quite a lot. That's what a FAQ is for. Such a FAQ is a lot more helpful than insulting responses that the question is asked a lot, without offering a useful answer. Which in turn makes this problem look even more like a bug, really a design flaw, since a single NIC LMCE on an existing network seem the most common setup for an installer to expect, especially with the project in its current state (ie. attracting a lot of people trying it out before committing to using it).

But the bottom line is that even after I did search the forums, the people who did respond to this question didn't give me any info to help solve my problem - and therefore the problem of probably others who will find my question when they do their search.

So I'll ask again: given my predictable, automatically installed IP config on my LAN with my existing DHCP server, how can I assign LMCE an IP# on the existing LAN segment so it can route to the Internet, and without disconnecting other LMCE services which will still look for the original IP#? Can I just edit /etc/network/interfaces ? Should I edit LMCE's DHCPd configs? Must I disable my existing DHCPd, and let my whole LAN get its IP#s from LMCE (rebooting every LAN host)? Or is there another best way to handle this common problem?
Title: Re: Changing CORE IP#?
Post by: Zaerc on November 12, 2007, 04:36:24 am
The best way is to use 2 network cards and put the LMCE core (or hybrid) in between the internet and the rest of your network and let the lmce core do the DHCP on the internal network. http://wiki.linuxmce.org/index.php/Why_dual_network_cards%3F

Is that the answer you were looking for?  Because I can't make heads or tails out of your question (both times), beyond that it seems to have something to do with DHCP and a single NIC setup. ::)  Try reading: http://www.catb.org/~esr/faqs/smart-questions.html maybe that helps a bit.

Also feel free to update the FAQ, it is in the WIKI after all, but aparently nobody that "suffered" from this horrendous problem seemed to care enough to bother. 

Now if you'll excuse me, I have other things to do besides answering the same question over and over and over again, just because some people who can't figure things out for themselves don't feel like using the recommended setup.  And just to get things straight, your self inflicted problem is not my responsability.

Is there anything else you'd like to lecture us on?
Title: Re: Changing CORE IP#?
Post by: 1audio on November 12, 2007, 06:47:12 am
Matthew:
Zaerc can get a little cranky when its this far past his bedtime. And he is doing very useful stuff with the DC ripping system. However I have answered this question many times myself for installations very like yours. Here goes again.
If all you want to try is a stand alone box then disable the internal DHCP server and make sure the external IP is set to DHCP in advanced-network-network settings. and turn off the firewall so you can access it from the network. Don't change anything elsewhere or you may never recover. The scripts drive everything.
You can play with it to your hearts content then. But to get the value and utility you will need to set it up in a more standard mode- single NIC: disable the DHCP on your router, set a fixed IP for the box in the router's range, turn on DHCP and you may as well use the default IP range. Restart or reset the network on any other device you have in your network so they get new IP addresses from the LMCE box. I currently have 30 devices on my network and no problems managing them.
I use network magic on my PC's and it lets me see the devices and their mac addresses, which is a great diagnostic tool.
If I can figure out the WiKi editing I'll give it a try again. (The last few times I couldn't find a way in.)
Title: Re: Changing CORE IP#?
Post by: Hagen on November 12, 2007, 12:32:48 pm
Rule #1
LMCE should be the DHCP server

Rule #2
There should not be other DHCP servers

Rule #3
LMCE is more than a media centre

At worst, if you have set up a lot of port forwarding or access trough your router just disable the LMCE internal firewall (in the web admin) and rely on the router as firewall.

And you might have found a bit more with a search 'single NIC', if you find 'too many posts to comb trough' then narrow your search.
Title: Re: Changing CORE IP#?
Post by: teedge77 on November 12, 2007, 03:23:25 pm
Rule #4
Theres exceptions to every rule (ie "rule 1")

Zaerc admires some who take the path of most resistance and despises others. I wouldnt worry much about it. Definitely search exhaustively before asking for help though.


Title: Re: Changing CORE IP#?
Post by: Zaerc on November 12, 2007, 05:02:38 pm
Rule #4
Theres exceptions to every rule (ie "rule 1")

Zaerc admires some who take the past of most resistance and despises others. I wouldnt worry much about it. Definitely search exhaustively before asking for help though.

I'm so glad you're around to tell me what I admire and despise... ::)
Title: Re: Changing CORE IP#?
Post by: teedge77 on November 12, 2007, 05:27:39 pm
sure thing. oh...and i fixed it....path...not past...

http://forum.linuxmce.org/index.php?topic=2639.0 (http://forum.linuxmce.org/index.php?topic=2639.0)


and i dont think i need to post how many people you despise.   :D
Title: Re: Changing CORE IP#?
Post by: Matthew on November 12, 2007, 06:12:58 pm
The best way is to use 2 network cards and put the LMCE core (or hybrid) in between the internet and the rest of your network and let the lmce core do the DHCP on the internal network. http://wiki.linuxmce.org/index.php/Why_dual_network_cards%3F

Is that the answer you were looking for?  Because I can't make heads or tails out of your question (both times), beyond that it seems to have something to do with DHCP and a single NIC setup. ::)  Try reading: http://www.catb.org/~esr/faqs/smart-questions.html maybe that helps a bit.
I was perfectly clear in specifying that I have a single NIC. Others have had no trouble either understanding the question or replying helpfully. I recommend you studying the wisdom of not saying anything if you don't have anything helpful to say.

Also feel free to update the FAQ, it is in the WIKI after all, but aparently nobody that "suffered" from this horrendous problem seemed to care enough to bother.
When I've got a tested answer, I'll update the FAQ. I did post it keeping in mind that a single NIC setup on a cablemodem or other router whose DHCP might not be optional is likely a popular situation that LMCE can probably handle if configured right, so others will probably benefit from a correct answer if I find it. People who have something useful to offer, other than flames, get the useful info before answering the question. And don't post merely self indulgent flames that damage the community.

Now if you'll excuse me, I have other things to do besides answering the same question over and over and over again, just because some people who can't figure things out for themselves don't feel like using the recommended setup.  And just to get things straight, your self inflicted problem is not my responsability.
I didn't ask you to take responsibility for this problem, which I "inflicted" on myself by doing a basic LMCE install according to its instructions, which left me with a system with basic defects (like not routing to the Internet). You volunteered your low S/N posts yourself - why bother, when you could be doing something useful?

Is there anything else you'd like to lecture us on?
No, I think you've got enough to work on for now.
Title: Re: Changing CORE IP#?
Post by: teedge77 on November 12, 2007, 06:28:59 pm
single nic might have been a better search than dhcp. there can be a few hoops to jump through to get the single nic setup working correctly. it might tell you how to change the dhcp settings to work with the single nic setup and you can work it so that you are changing it to use the dhcp from the other dhcp server. you might try this one

http://forum.linuxmce.org/index.php?topic=1367.0 (http://forum.linuxmce.org/index.php?topic=1367.0)

i tried for a while to do the single nic but it was easier to just vlan the switch instead. sorry if this wasnt much help.
Title: Re: Changing CORE IP#?
Post by: Hagen on November 12, 2007, 06:37:46 pm
Put it this way, if the core is not the DHCP server it requires you to have all your media on the core itself.
You can't use other MDs (less they all be independent neutered cores).
You woun't find any media on any other machine (without a bunch of hassle and manual set-up)
You can't stream any content.. oh, I allready covered that...

Basicly you'll be having a dumb neutered box, and if that's what you want you can simply switch the internal DHCP off in the web-admin.
(requires a reboot as well)
For such a use 'mediaportal' might arguably be better.
Title: Re: Changing CORE IP#?
Post by: teedge77 on November 12, 2007, 07:07:30 pm
hagen....did you read his question?


Quote
given my predictable, automatically installed IP config on my LAN with my existing DHCP server, how can I assign LMCE an IP# on the existing LAN segment so it can route to the Internet, and without disconnecting other LMCE services which will still look for the original IP#? Can I just edit /etc/network/interfaces ? Should I edit LMCE's DHCPd configs? Must I disable my existing DHCPd, and let my whole LAN get its IP#s from LMCE (rebooting every LAN host)? Or is there another best way to handle this common problem?

matthew...you need to disable whatever dhcp router you are using now. it will need to be running on the core after that. you will need to assign an ip address to the external nic of the core. you also have an "internal" nic, which is really a virtual nic. it shows up as eth "0:0". that also needs an address. the part i had trouble with (i suck at linux) was getting it to use the proper gateway...i didnt want to use the core as the gateway. i never got it to assign another gateway ip. if you dont care about it using the core as the gateway then it should set up that way automatically i think. theres also the issue of subnets and having the external and "internal" nics on same or separate subnets. you wont have to reboot all the hosts unless its easier for you. you can just renew the dhcp addresses and it would pick it up off the core then. i hope this helps a little more at least.
Title: Thank You
Post by: Matthew on November 12, 2007, 07:30:24 pm
I've complained about some unhelpful answers, so I want to thank the people who have answered helpfully - I think there's enough info in this thread for me to proceed. When I fix the problem I will try to reply and update the Wiki.
Title: Re: Changing CORE IP#?
Post by: Zaerc on November 12, 2007, 07:30:52 pm
The best way is to use 2 network cards and put the LMCE core (or hybrid) in between the internet and the rest of your network and let the lmce core do the DHCP on the internal network. http://wiki.linuxmce.org/index.php/Why_dual_network_cards%3F

Is that the answer you were looking for?  Because I can't make heads or tails out of your question (both times), beyond that it seems to have something to do with DHCP and a single NIC setup. ::)  Try reading: http://www.catb.org/~esr/faqs/smart-questions.html maybe that helps a bit.
I was perfectly clear in specifying that I have a single NIC. Others have had no trouble either understanding the question or replying helpfully. I recommend you studying the wisdom of not saying anything if you don't have anything helpful to say.
Well that is the "best way to handle this common problem".  And if everyone understands your question so well, then why haven't you fixed your "problem" yet? 

Also feel free to update the FAQ, it is in the WIKI after all, but aparently nobody that "suffered" from this horrendous problem seemed to care enough to bother.
When I've got a tested answer, I'll update the FAQ. I did post it keeping in mind that a single NIC setup on a cablemodem or other router whose DHCP might not be optional is likely a popular situation that LMCE can probably handle if configured right, so others will probably benefit from a correct answer if I find it. People who have something useful to offer, other than flames, get the useful info before answering the question. And don't post merely self indulgent flames that damage the community.
If you think that was flaming, then I'd leave it at that right now if I were you.  Maybe you should take your own advice regarding posting flames instead of throwing a hissy fit over nothing.

Now if you'll excuse me, I have other things to do besides answering the same question over and over and over again, just because some people who can't figure things out for themselves don't feel like using the recommended setup.  And just to get things straight, your self inflicted problem is not my responsability.
I didn't ask you to take responsibility for this problem, which I "inflicted" on myself by doing a basic LMCE install according to its instructions, which left me with a system with basic defects (like not routing to the Internet). You volunteered your low S/N posts yourself - why bother, when you could be doing something useful?
These "basic defects", "bugs" and "design flaws" were caused by yourself as you didn't feel like using the recommended setup, and didn't feel like turning off your existing DHCP server either (as indicated in the documentation).  These issues have been adressed over and over again.  In fact it was the first answer you got here.  And I'm not sure what me "volunteering my low serial number posts" has got to do with anything.

Is there anything else you'd like to lecture us on?
No, I think you've got enough to work on for now.
Typical, saying no and doing yes.
Title: Re: Changing CORE IP#?
Post by: Zaerc on November 12, 2007, 07:50:30 pm
sure thing. oh...and i fixed it....path...not past...

http://forum.linuxmce.org/index.php?topic=2639.0 (http://forum.linuxmce.org/index.php?topic=2639.0)


and i dont think i need to post how many people you despise.   :D

Please do post how many people I despise, aparently it's more then I'm aware of, better yet, could you list them by name?

By the way do you still beat your wife?
Title: Re: Changing CORE IP#?
Post by: Hagen on November 12, 2007, 08:23:39 pm
hagen....did you read his question?
Actually I did, but it soon became apparent that Matthev here had no intention of solving it the easy way, the way he himself actually has in the very first post...
Hence my
Rule #1
LMCE should be the DHCP server

Rule #2
There should not be other DHCP servers
Simple, to the point and totally true.
You can't have two DHCP servers on the network, wich Matthev brilliantly concluded in the first post.
But LMCE wount work well (it woun't, I have tried. True you can boot the machine and watch local content, but that's not what LMCE is all about) if it is not the DHCP server.

Title: Re: Changing CORE IP#?
Post by: teedge77 on November 12, 2007, 08:33:20 pm
Quote
By the way do you still beat your wife?

 :D no ...but thats not to say she wouldnt deserve it now and then....you still chokin that chicken or did it finally die on you? sorry...no time to post it all by name...but youre obviously not a fan of anyone that isnt groveling at your feet.  :-*

hagen...i just meant that he seemed to finally see it needed to be the dhcp. somehow he seemed sonfused about it still though. i think the single nic problem confuses him along with the dhcp "issue". if he gets rid of the dhcp server hes using now then everything to set it up on the core should be in the webadmin right?
Title: Re: Changing CORE IP#?
Post by: Hagen on November 12, 2007, 08:33:56 pm
The core is best left as the gateway for the network, like I said you can disable the LMCE firewall and it becomes transparent to the user (and the DHCP works as intended).
The router you allready have (that is currently the DHCP) is then assigned as the gateway and DNS for the core.
And the DHCP server in that one needs to come off.

If you do however only have a router (from a broadband company for example) that is hellbendt on being the DHCP you need either a router after that and connect the BB router to the WAN port or, you need two NICs in the core.
There is no practical way to use a single NIC core with a router as DHCP as well.

The core usually wants to give itself the ***.***.***.01 IP, but it's easily changeable in the web-admin under 'advanced' 'network settings'.
For other IP, NIC and general fiddling work you can also use the 'advanced' 'device settings' and select 'core'


Hope this helps, but posting it time after time is ... slightly exhaustive.
Title: Re: Changing CORE IP#?
Post by: Zaerc on November 12, 2007, 08:39:08 pm
Quote
By the way do you still beat your wife?

 :D no ...but thats not to say she wouldnt deserve it now and then....you still chokin that chicken or did it finally die on you? sorry...no time to post it all by name...but youre obviously not a fan of anyone that isnt groveling at your feet.  :-*

I'm glad to hear you stopped beating her.  You're obviously not a fan of women who talk back.
Title: Re: Changing CORE IP#?
Post by: teedge77 on November 12, 2007, 08:45:32 pm
yeah good one zaerc. youre on a roll. when did i say i beat my wife?  ::)

silly little zaerc...with his poor twisted panties.
Title: Re: Changing CORE IP#?
Post by: Zaerc on November 12, 2007, 09:03:23 pm
yeah good one zaerc. youre on a roll. when did i say i beat my wife?  ::)

silly little zaerc...with his poor twisted panties.

Actually she did when I slept with her, I've never seen such nasty bruises on a woman.

Are you sure you want to go down this road?  You might get your feelings hurt again just like the last time. 
Title: Re: Changing CORE IP#?
Post by: teedge77 on November 12, 2007, 09:10:01 pm
 :D thats the gayest thing ive ever heard. when you slept with her... :D good one. sounds like youve had your feelings hurt already if youre trying to find ways to "offend" me. whats next zaerc? my mom? go ahead...have fun. is my mom so fat gravy pours out or is it my moms so stupid or my moms so ugly? hurt my feelings like last time? i dont think there ever has been or ever could be a time when you could hurt my feelings. but....A for effort i guess. if its that important to you to best me and come out on top. keep trying. you may get there with a little hard work.  :-*
Title: Re: Changing CORE IP#?
Post by: tschak909 on November 12, 2007, 09:17:59 pm
okay fellas, let's try to return this thread to sanity.

-Thom
Title: Re: Changing CORE IP#?
Post by: Zaerc on November 12, 2007, 09:23:22 pm
Aww and I was just about to link the post where he told me I hurt his feelings (in a very manly way of course).  Oh well I'm sure it won't be long untill he feels the need to attack me again. 
Title: Re: Changing CORE IP#?
Post by: teedge77 on November 12, 2007, 09:36:52 pm
attack?  ::)
Title: Re: Changing CORE IP#?
Post by: tschak909 on November 12, 2007, 09:46:16 pm
seriously, come on, you know you two get on each others nerves... why don't you both use that information to.. oh, i don't know... agree to disagree? stay away from each other, perhaps? ;)

-Thom
Title: Re: Changing CORE IP#?
Post by: teedge77 on November 12, 2007, 09:47:50 pm
i cant stay away from him...hes always over here banging my wife. ::)
Title: Solved (Mostly)
Post by: Matthew on November 13, 2007, 10:12:59 pm
After research, discussion in this thread, some more research, and finally just working through the configs on my own network, I have solved the problem of properly configuring a single NIC LMCE to properly serve a LAN by DHCP, switched over from an existing DHCP server. AFAICT, this technique doesn't leave any wrong configurations anywhere inside either LMCE's complex interdependencies or the remnants of the previously existing DHCP system.

* In existing router/gateway
- Disable DHCPd
- Assign LAN IP# on desired subnet (eg 192.168.0.1 )
- Ensure router/gateway is configured to route properly between the newly specified subnet and the other network

* In LMCE Admin site:
- Homepage -> Advanced -> Network -> Network Settings
- Change all 192.168.80.x IP#s to desired subnet (eg. 192.168.0.x )
- Set both NICs to the same IP# (and proper subnet info)
- Reload DCERouter
- Check Homepage -> Advanced -> Network -> Network Settings to be sure settings were properly retained

* /etc/dhcp3/dhcpd.conf :
- Exclude router/gateway IP# from allocatable ranges
- Change "host px[1,2]" lines from 192.168.80.x IP#s to desired subnet IP#s (eg. 192.168.0.253 )
- /etc/init.d/dhcp3-server restart
- Force a LAN host to reset its network configs by DHCP, then test pinging across the router

* Force each host on the LAN to reread its network configs by DHCP (eg. run its DHCP client or reboot if its DHCP client runs at startup).

Note that the dhcpd.conf file regenerated by the LMCE Admin site's Network Settings form has a bug (#3469 (http://mantis.linuxmce.org/view.php?id=3469)) which doesn't change all the IP#s properly. There might be other bugs, so check the whole file to be sure it's correct.

This technique leaves a problem in that any configs of your original router/gateway DHCPd are not available to the LMCE DHCPd, unless you manually recreate them in the LMCE's dhcpd.conf file. Also, the router/gateway LAN IP# must be manually discovered/set, and then the LMCE LAN subnet must be manually configured to accommodate it. There is no way to fix that problem, unless the router/gateway allows its LAN IP# to be set by DHCP (ie. a DHCP client running on the router/gateway that is set by the LMCE DHCPd). Conversely, there is no way for LMCE to insert into the router/gateway DHCPd configs the configs that LMCE needs clients for its own services (like IP phones) to automatically get from a DHCPd when they're plugged into a network. The only way to make DHCP fully automatic for LMCE is to use the recommended network architecture of a pair of ethernet ports on the LMCE server (or use a router/gateway DHCPd that can be remotely configured by the LMCE, and a script to glue them together).

I will now attempt to update the wiki...

I updated the wiki article DHCP Plug and Play: Single NIC & Existing DHCPd (http://wiki.linuxmce.org/index.php/DHCP_Plug_and_Play#Single_NIC_.26_Existing_DHCPd) and have updated it again, so it is more current than the discussion in this forum topic.
Title: Re: Changing CORE IP#?
Post by: Hagen on November 13, 2007, 10:24:37 pm
I usually just assign the IP range to the core that the router allready has, then I let theCore DHCP IP range start at 10.0.0.20 to allow for up to 19 routers/switches/+++ with manual IPs.
But wow, you do have a slick solution.
Title: Re: Changing CORE IP#?
Post by: Matthew on November 13, 2007, 11:01:02 pm
I usually just assign the IP range to the core that the router allready has, then I let theCore DHCP IP range start at 10.0.0.20 to allow for up to 19 routers/switches/+++ with manual IPs.
But wow, you do have a slick solution.
That's the short explanation of my process. I thought I'd give the explicit details of exactly how to configure the required settings, which is what I'd hoped I'd find in my own search.

A mystery in my process is how come the LMCE DHCPd config says "router <CORE-IP#>", the way it did after the default LMCE installation, but the devices on the network still are using the existing router (unspecified in any DHCPd configs) as Internet gateway. But it does work.
Title: Re: Changing CORE IP#?
Post by: 1audio on November 13, 2007, 11:04:37 pm
Matthew:
The remaining question is whether the PXE boot will work correctly. It may have some IP address issues hidden in some script that will appear out of nowhere (like so much else in this project). Will you be using a media director in your setup?
Title: Re: Changing CORE IP#?
Post by: Matthew on November 13, 2007, 11:23:59 pm
Matthew:
The remaining question is whether the PXE boot will work correctly. It may have some IP address issues hidden in some script that will appear out of nowhere (like so much else in this project). Will you be using a media director in your setup?

It looks like PXE boot (http://wiki.linuxmce.org/index.php/PXE) is designed to rely on DHCP rather than hardcode:
Quote from: /etc/dhcp3/dhcpd.conf
allow booting;
allow bootp;

option space pxelinux;
option pxelinux.magic code 208 = string;
option pxelinux.configfile code 209 = text;
option pxelinux.pathprefix code 210 = text;
option pxelinux.reboottime code 211 = unsigned integer 32;

(...)

# PXE booting machines
group {
        next-server 192.168.0.10;
        filename "/tftpboot/pxelinux.0";
        option pxelinux.reboottime = 30;

}
If there are any PXE boot dependencies not properly dependent on DHCP, then the switch I did should be a good test to expose them. However, I do not have any media director hosts on my network yet (I'm trying out LMCE piece by piece, and it's been a good strategy so far :)).
Title: Re: Changing CORE IP#?
Post by: Zaerc on November 13, 2007, 11:47:36 pm
Well if that is what you wanted, I guess you could just have turned off DHCP on the modem/router and configured the "external interface" (eth0 not the virtual eth0:0)  staticly in the modem/router's range.  Saves you the of trouble reconfiguring LMCE's DHCP server.
Title: Re: Changing CORE IP#?
Post by: Matthew on November 14, 2007, 12:27:51 am
Well if that is what you wanted, I guess you could just have turned off DHCP on the modem/router and configured the "external interface" (eth0 not the virtual eth0:0)  staticly in the modem/router's range.  Saves you the of trouble reconfiguring LMCE's DHCP server.
Yes, that is in fact what I wanted, except I also wanted the LMCE DHCP server to assign addresses in the existing LAN's Class C IP# range, and service LMCE devices that need LMCE's DHCP support. And I wanted to avoid (or recover from) the bug that regenerates the dhcpd.conf incorrectly. I also wanted to know what I was losing, the actual absolutely required losses, by using a single NIC. Know I know, and so does anyone else reading this thread (or the wiki, or the dhcpd.conf bug report).

What I wanted was for someone to explain how to do that, preferably point to an existing (and tested) explanation, since it's clearly a not uncommon setup. Now the next person will have a better chance of doing it in a few minutes, rather than a few hours, with a minimum of unnecessary noise as they search for the solution.
Title: Re: Changing CORE IP#?
Post by: Zaerc on November 14, 2007, 05:07:15 pm
Then why didn't you just ask that instead? 

Anyway I'm so glad you have solved this for once and for all so that we never have to answer these questions (http://forum.linuxmce.org/index.php?topic=3176.0) ever again...  ::)

And on a side note, don't you think it's just a little odd to give a virtual network adapter the exact same ip address as the physical adapter?
Title: Re: Changing CORE IP#?
Post by: Matthew on November 14, 2007, 05:53:05 pm
Then why didn't you just ask that instead? 

Anyway I'm so glad you have solved this for once and for all so that we never have to answer these questions (http://forum.linuxmce.org/index.php?topic=3176.0) ever again...  ::)

And on a side note, don't you think it's just a little odd to give a virtual network adapter the exact same ip address as the physical adapter?

It's easy (http://forum.linuxmce.org/index.php?topic=3176.msg15934#msg15934) when you know how.
Title: Re: Changing CORE IP#?
Post by: Zaerc on November 14, 2007, 09:06:09 pm
Then why didn't you just ask that instead? 

Anyway I'm so glad you have solved this for once and for all so that we never have to answer these questions (http://forum.linuxmce.org/index.php?topic=3176.0) ever again...  ::)

And on a side note, don't you think it's just a little odd to give a virtual network adapter the exact same ip address as the physical adapter?

It's easy (http://forum.linuxmce.org/index.php?topic=3176.msg15934#msg15934) when you know how.

My point wasn't really that it's hard to tell somebody to search the wiki.  :P