Internal Router IP address

[krys]

Does the core change the default IP address on the internal router? I configured my router using 192.168.1.1 and today i cant get back to that same IP address. I can however get to the external router which is 192.168.2.1, any ideas? is there a command i can use to tell me what the IP address is? I am trying to access it from a computer that is wired directly into it, i need to get back in to set up my wireless network.
Thanks,
Krys

[colinjones]

What do you mean "internal router"?

Some points - the core's internal NIC/network should always be 192.168.80.1 static and you mustn't change it. It will then hand out DHCP leases on the 192.168.80.0/24 subnet to your internal devices. This NIC should be eth1.

The core's external NIC/network can be anything you want, including a public IP address. It is recommended that you allow this interface to get its IP address, etc from either your own broadband router's DHCP server or your ISP's DHCP server. This interface should be eth0.

[krys]

by internal router I mean the router that is connected to the internal NIC on the core, instead of just using a switch for the internal network I used a wireless router so I could take advantage of some wireless orbiters.

as far as eth0 and eth1 I have another post talking about some netboot issues and I am concerned because for some reason I think that LMCE assigned the NIC's backwards. here is the link, I would appreciate some input on how to get the core to assign these NIC's properly, even if I need to do a reinstall I would prefer now as opposed to when I have 1TB of data on it.

http://forum.linuxmce.org/index.php?topic=6570.0

[colinjones]

1. I strongly recommend that you place your media on another machine than the LMCE core (eg a PC or NAS) as this will make it vastly more convenient to rebuild your system whenever you need to.

2. If you have already experimented with the networking page of the admin site (it has a button to switch the NICs) and this didn't get the interfaces the correct way around, then you can either use a udev rule or edit the iftab file, both methods described in this thread http://forum.linuxmce.org/index.php?topic=6504.0

3. Be abolutely sure that you are not using the wireless router as a router. The internal network must be only 1 subnet and only 1 broadcast domain/segment/vlan. Routers that have LAN ports are OK, just do not use any WAN port (it maybe described differently) and DHCP must be off.

[totallymaxed]

1. I strongly recommend that you place your media on another machine than the LMCE core (eg a PC or NAS) as this will make it vastly more convenient to rebuild your system whenever you need to.

...or just install a 2nd drive inside your Core. Eg have a smallish 80gb - 160Gb drive for the system installation then have one or more additional drives purely for media storage. If you have the drive bays in your Core this works just as well - its just an alternate route... not better or worse than Colin's suggestion in anyway ;-)

All the best

Andrew

[krys]

thats actually the way I am doing it, 80 gig main internal, then a 1tb 2nd internal.
Also I got my router issue fixed thanks to Collin, I used the reset button on my router, then flipped eth0 and eth1 on the admin website. Unfortunately I still get a kernel panic from the same MD that has never succesfully net booted. I might try to net boot a third MD to see if its the core or the MD then try and figure out a way to get it to work.

[totallymaxed]

thats actually the way I am doing it, 80 gig main internal, then a 1tb 2nd internal.
Also I got my router issue fixed thanks to Collin, I used the reset button on my router, then flipped eth0 and eth1 on the admin website. Unfortunately I still get a kernel panic from the same MD that has never succesfully net booted. I might try to net boot a third MD to see if its the core or the MD then try and figure out a way to get it to work.

The Kernel panic is more than likely because the initramfs is missing a module that your MD needs to boot.

Andrew

[krys]

The Kernel panic is more than likely because the initramfs is missing a module that your MD needs to boot.

Andrew

Andrew, not sure what I am supposed to do with this info, could you enlighten me?
Thanks,
Krys