Messages

46

Users / Routing Configuration Question

« on: February 12, 2008, 09:31:19 pm »

I have one more configuration issue I'm trying to resolve with my networking configuration.

Here is the scenerio:  I have a 500GB HP MediaVault  that currently has an IP address of 192.168.1.50, which I defined as static. Therefore it communicates fine with all my "regular" home w/s on this same subnet. I keep all my audio, pictures, and videos here.  However, the problem is the CORE hasn't mapped any CIFS shares to it, presumably because the way the CORE works it wants the HP unit to be on the 192.168.80.x subnet to discover it.
 
But, if I put it on this side of the LAN, I can't see it anymore from the "regular w/s" on the 192.168.1.x subnet. Acutally, I can't ping or see anything on the 192.168.80.x subnet from them.

So maybe I need some routing entries defined on the CORE so that they will see it, is this correct?  If so, is this done by adding routes, and what would the entries have to say?

For example would it be the following?

$ sudo route add -net 192.168.80.0 netmask 255.255.255.0 gw 192.168.80.1 dev eth0 (eth0 being the external interface 192.168.1.100)


  If I leave it the way it is now, I possibly could manually configure the network shares. But are there advantages to having the HP unit on the 192.168.80.x subnet besides the discoverabilty factor?

Thanks in advance for any input on this.

-fins

47

Users / Re: Network configuration questions

« on: February 12, 2008, 03:38:37 pm »

I have one more configuration issue I'm trying to resolve with my networking configuration.

Here is the scenerio:  I have a 500GB HP MediaVault  that currently has an IP address of 192.168.1.50, which I defined as static. Therefore it communicates fine with all my "regular" home w/s on this same subnet. I keep all my audio, pictures, and videos here.  However, the problem is the CORE hasn't mapped any CIFS shares to it, presumably because the way the CORE works it wants the HP unit to be on the 192.168.80.x subnet to discover it.
 
But, if I put it on this side of the LAN, I can't see it anymore from the "regular w/s" on the 192.168.1.x subnet. I can't ping or see anything on the 192.168.80.x subnet from them.

So maybe I need some routing entries defined on the CORE so that they will see it, is this correct?  If so, where in LCME admin would I do this, and what would the entries have to say.  If I leave it the way it is now, I possibly could manually configure the network shares. But are there advantages to having the HP unit on the 192.168.80.x subnet besides the discoverabilty factor?

Thanks in advance for any input on this.

-fins

48

Users / Re: Network configuration questions

« on: February 12, 2008, 01:53:34 am »

10-4.  I will go ahead and turn on DHCP on my external side and leave it on. 

49

Users / Re: Network configuration questions

« on: February 11, 2008, 10:14:59 pm »

Well that was happening before I think...well it's all fuzzy now. I think that was when I was using 1 network card.

50

Users / Re: Network configuration questions

« on: February 11, 2008, 10:02:43 pm »

Ok I think I have a handle on the firewall but DHCP is still confusing me.

Consider this:

If the CORE is the only DHCP server and then if I tell my  WIFI workstation which connects to the Belkin router to request a DHCP address, the CORE will respond with an IP address  on the 192.168.80.x subnet.    Right?  So then doesn't that mean the CORE DHCP service is advertising on both lan segments?  And if so, wouldn't that cause problems if two DHCP servers were running?

Thanks alot,

fins

51

Users / Re: Network configuration questions

« on: February 11, 2008, 09:39:05 pm »

I Appreciate the quick replies. I think I gather my setup is ok. Then really all I really need to do is figure out how to configure the CORE firewall. When I have the Firewall on and I try to ping from a 192.168.1.x w/s to the 192.168.1.100 CORE external interface, I don't get thru. When I turn the firewall off the ping requests work.  So then this is a port issue? If so  then which port does it use?   I think also I will leave the broadband router DHCP off, less chance of confusion, and turn it on briefly if I have to configure a new piece of network equipment, like my network storage device.

52

Users / Network configuration questions

« on: February 11, 2008, 09:05:26 pm »

Ok, I realize this may have been asked already ad naseum, but searching the forum I still don't seem to find the answer to this question:

First, this is my current setup.  My CORE has 2 network interfaces, ETH0: 192.168.1.100, and ETH1: 192.168.80.1.
ETH0 goes to my Belkin Wifi Router (192.168.1.1). ETH1 goes to a 10/100mbit switch.  My M/D's all connect to this switch.  My regular w/s's all use wifi to connect to the Belkin router, and DHCP is turned off here. DHCP is on of course on the CORE.

My concern is this: If I let my regular worstations get their DHCP address from the CORE (i.e. if they all get 192.168.80.x addresses) how will they get routed to the internet if the CORE happens to be not up. Because in reality the CORE is going to be down at times.  Will they be unable to since the CORE isn't able to route the data? Since my wife gets pretty frustrated with me if the "internet" is down, I don't want to implement this networking topology.

What I've done instead is assign static IP addresses to my "regular computers" (which use wifi, i.e. 192.168.1.x ip addresses) which don't depend on the CORE being up to get to the internet.  This seems to work fine except that if I want to see the COREs external IP address  I have to disable the CORE firewall all-together.  This doesn't really bother me since is inside the hardware firewall anyway.  This allows me to install Windows Orbiters and other good stuff.

Is this the "correct" and accepted way of setting up this network scheme? Are there any firewall rules I can implement on the CORE instead of turning off the firewall?  If I turn on DHCP on the Belkin broadband router will this cause problems on the internal network? 

53

Installation issues / Re: Blank screen after installation

« on: February 03, 2008, 04:25:24 am »

I had the same problem. I changed the driver from "Nvidia" back to  "vesa" in the /etc/X11/xorg.conf file, saved it, and rebooted. This time X started in graphics mode and I was able to continue installing MCE.  So far so good.

-finsdown

54

Users / Re: Any issue ?

« on: January 23, 2008, 08:09:38 pm »

Rafik,

I for one would be very interested in this method for my MD's.  I would be pushing HD content thru it so I can provide feedback on any bandwidth problems. Can you provide more details?

Thanks.