[opensuse] Routing Question
Hello All: I have a home network with 6 mixed os machines connected to a router for internet access, this all works great. I would like to add another network card to my main machine just for a VNC connection on a seperate network, as this would be an endpoint I am not sure how to proceed and all of the books I have don't cover anything like this or are just too old. TIA, Mike -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Saturday 30 December 2006 11:03, ka1ifq wrote:
Hello All:
I have a home network with 6 mixed os machines connected to a router for internet access, this all works great. I would like to add another network card to my main machine just for a VNC connection on a seperate network, as this would be an endpoint I am not sure how to proceed and all of the books I have don't cover anything like this or are just too old.
What is an "endpoint"? Do you mean that it will be connected directly to the internet (the same one your router is connected to) or do you have another network connection all together (another router?) Also do you intend to run VNC as a server, (allowing others to connect to your machine) or are you only running VNC as a client (connecting to other machines located elsewhere)? Either of the above, over the same internet connection should not require a separate nic. Perhaps just a entry in the router table of the firewall/router if you are going to be a VNC server. OTOH, if it is a totally separate internet connection, all you need to do is slap in a nic, reboot and use Yast to configure it to your needs and set ROUTING = No. -- _____________________________________ John Andersen
On Saturday 30 December 2006 19:44, John Andersen wrote:
On Saturday 30 December 2006 11:03, ka1ifq wrote:
Hello All:
I have a home network with 6 mixed os machines connected to a router for internet access, this all works great. I would like to add another network card to my main machine just for a VNC connection on a seperate network, as this would be an endpoint I am not sure how to proceed and all of the books I have don't cover anything like this or are just too old.
What is an "endpoint"?
Do you mean that it will be connected directly to the internet (the same one your router is connected to) or do you have another network connection all together (another router?)
Also do you intend to run VNC as a server, (allowing others to connect to your machine) or are you only running VNC as a client (connecting to other machines located elsewhere)?
Either of the above, over the same internet connection should not require a separate nic. Perhaps just a entry in the router table of the firewall/router if you are going to be a VNC server.
OTOH, if it is a totally separate internet connection, all you need to do is slap in a nic, reboot and use Yast to configure it to your needs and set ROUTING = No.
Thanks for the info John. The plan was to have a seperate connection for only 2 machines so I could use VNC between them to not hog the main internet network. By endpoint I meant that the end of the second network would be my main machine, so there really needs to be no routing. It looks like I setup a second nic in my main machine and point my remote machine at it. Thanks, Mike -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Saturday 30 December 2006 16:38, ka1ifq wrote:
On Saturday 30 December 2006 19:44, John Andersen wrote:
On Saturday 30 December 2006 11:03, ka1ifq wrote:
Hello All:
I have a home network with 6 mixed os machines connected to a router for internet access, this all works great. I would like to add another network card to my main machine just for a VNC connection on a seperate network, as this would be an endpoint I am not sure how to proceed and all of the books I have don't cover anything like this or are just too old.
What is an "endpoint"?
Thanks for the info John.
The plan was to have a seperate connection for only 2 machines so I could use VNC between them to not hog the main internet network.
By endpoint I meant that the end of the second network would be my main machine, so there really needs to be no routing. It looks like I setup a second nic in my main machine and point my remote machine at it.
Thanks, Mike
Ok, but its still not clear to me if you have a separate connection to your ISP for this second nic, or if it all leaves the building on the same wire. If only one connection to your ISP, there's no point in doing a second nic. VNC isn't that bad on bandwidth utilization if you set it for 256 colors. -- _____________________________________ John Andersen
On Saturday 30 December 2006 22:26, John Andersen wrote:
On Saturday 30 December 2006 16:38, ka1ifq wrote:
On Saturday 30 December 2006 19:44, John Andersen wrote:
On Saturday 30 December 2006 11:03, ka1ifq wrote:
Hello All: I have a home network with 6 mixed os machines connected to a router for internet access, this all works great. I would like to add another network card to my main machine just for a VNC connection on a seperate network, as this would be an endpoint I am not sure how to proceed and all of the books I have don't cover anything like this or are just too old.
What is an "endpoint"?
Thanks for the info John.
The plan was to have a seperate connection for only 2 machines so I could use VNC between them to not hog the main internet network.
By endpoint I meant that the end of the second network would be my main machine, so there really needs to be no routing. It looks like I setup a second nic in my main machine and point my remote machine at it.
Thanks, Mike
Ok, but its still not clear to me if you have a separate connection to your ISP for this second nic, or if it all leaves the building on the same wire.
If only one connection to your ISP, there's no point in doing a second nic.
VNC isn't that bad on bandwidth utilization if you set it for 256 colors.
Here is the setup, Machine 1, my main machine Machine 2, Remote Machine ( in same building ) Nic 1, Network 1, connects to internet ( Nic 1, Network 1 ) - possible... via router. Nic 2, Network 2, just for VNC to Machine 1 Nic 2, Network 2, just for VNC to Machine 2 I think I could just do a swap cable between the two nic 2's . I haven't done much with multi-nic routing. I did a software router / firewall about 8 years ago.. Thanks, Mike -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Saturday 30 December 2006 19:57, ka1ifq wrote:
On Saturday 30 December 2006 22:26, John Andersen wrote:
On Saturday 30 December 2006 16:38, ka1ifq wrote:
On Saturday 30 December 2006 19:44, John Andersen wrote:
On Saturday 30 December 2006 11:03, ka1ifq wrote:
Hello All: I have a home network with 6 mixed os machines connected to a router for internet access, this all works great. I would like to add another network card to my main machine just for a VNC connection on a seperate network, as this would be an endpoint I am not sure how to proceed and all of the books I have don't cover anything like this or are just too old.
What is an "endpoint"?
Thanks for the info John.
The plan was to have a seperate connection for only 2 machines so I could use VNC between them to not hog the main internet network.
By endpoint I meant that the end of the second network would be my main machine, so there really needs to be no routing. It looks like I setup a second nic in my main machine and point my remote machine at it.
Thanks, Mike
Ok, but its still not clear to me if you have a separate connection to your ISP for this second nic, or if it all leaves the building on the same wire.
If only one connection to your ISP, there's no point in doing a second nic.
VNC isn't that bad on bandwidth utilization if you set it for 256 colors.
Here is the setup, Machine 1, my main machine Machine 2, Remote Machine ( in same building ) Nic 1, Network 1, connects to internet ( Nic 1, Network 1 ) - possible... via router. Nic 2, Network 2, just for VNC to Machine 1 Nic 2, Network 2, just for VNC to Machine 2
I think I could just do a swap cable between the two nic 2's .
I haven't done much with multi-nic routing. I did a software router / firewall about 8 years ago..
Thanks, Mike
Since Machine 1 and Machine 2 are in the same building, are Nic1 on both machines in the same subnet? Does Machine 1 have direct access to Machine 2, ie. not haveing to go through the router? Mike -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Sunday 31 December 2006 00:02, Mike Noble wrote:
Here is the setup, Machine 1, my main machine Machine 2, Remote Machine ( in same building ) Nic 1, Network 1, connects to internet ( Nic 1, Network 1 ) - possible... via router. Nic 2, Network 2, just for VNC to Machine 1 Nic 2, Network 2, just for VNC to Machine 2
I think I could just do a swap cable between the two nic 2's .
I haven't done much with multi-nic routing. I did a software router / firewall about 8 years ago..
Thanks, Mike
Since Machine 1 and Machine 2 are in the same building, are Nic1 on both machines in the same subnet? Does Machine 1 have direct access to Machine 2, ie. not haveing to go through the router?
Mike
Yes they are on the same subnet, but there is no direct connect only via the router. I would like to do a direct connect between them just for the VNC and would have to be on another subnet (as I see it) , thus all the questions (I'm learning). Thanks, Mike -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Saturday 30 December 2006 21:30, ka1ifq wrote:
On Sunday 31 December 2006 00:02, Mike Noble wrote:
Here is the setup, Machine 1, my main machine Machine 2, Remote Machine ( in same building ) Nic 1, Network 1, connects to internet ( Nic 1, Network 1 ) - possible... via router. Nic 2, Network 2, just for VNC to Machine 1 Nic 2, Network 2, just for VNC to Machine 2
I think I could just do a swap cable between the two nic 2's .
I haven't done much with multi-nic routing. I did a software router / firewall about 8 years ago..
Thanks, Mike
Since Machine 1 and Machine 2 are in the same building, are Nic1 on both machines in the same subnet? Does Machine 1 have direct access to Machine 2, ie. not haveing to go through the router?
Mike
Yes they are on the same subnet, but there is no direct connect only via the router. I would like to do a direct connect between them just for the VNC and would have to be on another subnet (as I see it) , thus all the questions (I'm learning). Thanks, Mike
This does not make sense, if both machines are on the same subnet, the router would not know which side to route to. Let me make sure we are talking about the same thing. Example: Machine 1 - 192.168.1.2 nic 1 on router Machine 2 - 192.168.1.3 nic 2 on router nic X where X is a specific nic on the router. The subnet here is 192.168.1 Mike -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
ka1ifq wrote:
Yes they are on the same subnet, but there is no direct connect only via the router. I would like to do a direct connect between them just for the VNC and would have to be on another subnet (as I see it) , thus all the questions (I'm learning). Thanks, Mike
If they are on the same subnet, both connecting through the router to the internet, you can already connect through the router's switch. They don't need a direct connection. It is probably a 100Mbps network, and should easily handle the bandwidth. -- Joe Morris Registered Linux user 231871 running openSUSE 10.2 x86_64 -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Saturday 30 December 2006 21:51, Joe Morris (NTM) wrote:
ka1ifq wrote:
Yes they are on the same subnet, but there is no direct connect only via the router. I would like to do a direct connect between them just for the VNC and would have to be on another subnet (as I see it) , thus all the questions (I'm learning). Thanks, Mike
If they are on the same subnet, both connecting through the router to the internet, you can already connect through the router's switch. They don't need a direct connection. It is probably a 100Mbps network, and should easily handle the bandwidth.
-- Joe Morris Registered Linux user 231871 running openSUSE 10.2 x86_64
If they are on the same subnet then it would have to look like this: internet or firewall | | router __| | ____ subnet 182.168.1 | | subnet 192.168.1 Under this layout the router would not know which subnet to route to. It must there for either be different subnets or both machines are connected to the same interface and therefor can talk to each other without having to access the router. Mike -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Saturday 30 December 2006 22:06, Mike Noble wrote:
On Saturday 30 December 2006 21:51, Joe Morris (NTM) wrote:
ka1ifq wrote:
Yes they are on the same subnet, but there is no direct connect only via the router. I would like to do a direct connect between them just for the VNC and would have to be on another subnet (as I see it) , thus all the questions (I'm learning). Thanks, Mike
If they are on the same subnet, both connecting through the router to the internet, you can already connect through the router's switch. They don't need a direct connection. It is probably a 100Mbps network, and should easily handle the bandwidth.
-- Joe Morris Registered Linux user 231871 running openSUSE 10.2 x86_64
If they are on the same subnet then it would have to look like this:
internet or firewall
router __| | ____ subnet 182.168.1 | | subnet 192.168.1
Under this layout the router would not know which subnet to route to. It must there for either be different subnets or both machines are connected to the same interface and therefor can talk to each other without having to access the router.
Mike
Alright lets as this question, what is the subnet mask being used? It is possible that they have spit up the subnet. Mike -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Sun, 2006-12-31 at 00:30 -0500, ka1ifq wrote:
On Sunday 31 December 2006 00:02, Mike Noble wrote:
Here is the setup, Machine 1, my main machine Machine 2, Remote Machine ( in same building ) Nic 1, Network 1, connects to internet ( Nic 1, Network 1 ) - possible... via router. Nic 2, Network 2, just for VNC to Machine 1 Nic 2, Network 2, just for VNC to Machine 2
I think I could just do a swap cable between the two nic 2's .
I haven't done much with multi-nic routing. I did a software router / firewall about 8 years ago..
Thanks, Mike
Since Machine 1 and Machine 2 are in the same building, are Nic1 on both machines in the same subnet? Does Machine 1 have direct access to Machine 2, ie. not haveing to go through the router?
Mike
Yes they are on the same subnet, but there is no direct connect only via the router. I would like to do a direct connect between them just for the VNC and would have to be on another subnet (as I see it) , thus all the questions (I'm learning)
There is _no_ need for the separate nic as VNC uses very little bandwidth. Eliminating the router will not make it any faster. I have used VNC across dialup to an office in another state and although it was slow it worked (and was faster then flying there to fix a problem). -- Ken Schneider UNIX since 1989, linux since 1994, SuSE since 1998 -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Sat, 2006-12-30 at 22:57 -0500, ka1ifq wrote:
Here is the setup, Machine 1, my main machine Machine 2, Remote Machine ( in same building ) Nic 1, Network 1, connects to internet ( Nic 1, Network 1 ) - possible... via router. Nic 2, Network 2, just for VNC to Machine 1 Nic 2, Network 2, just for VNC to Machine 2
If the distance is short, or cabling between rooms are under your control, you can connect both NIC2s with a cross-over cable (transmit and receive pairs need to be swapped somewhere inbetween) without switch or router. Toshi -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Sunday 31 December 2006 00:31, Toshi Esumi wrote:
On Sat, 2006-12-30 at 22:57 -0500, ka1ifq wrote:
Here is the setup, Machine 1, my main machine Machine 2, Remote Machine ( in same building ) Nic 1, Network 1, connects to internet ( Nic 1, Network 1 ) - possible... via router. Nic 2, Network 2, just for VNC to Machine 1 Nic 2, Network 2, just for VNC to Machine 2
If the distance is short, or cabling between rooms are under your control, you can connect both NIC2s with a cross-over cable (transmit and receive pairs need to be swapped somewhere inbetween) without switch or router.
Toshi
Yes, true. The distance is not a problem as I could run another cable or split the existing one. I am more interested in the internal logistics of getting the VNC working, will there be a problem with the 2 nics in the main machine. Thanks, Mike -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Sun, 2006-12-31 at 00:43 -0500, ka1ifq wrote:
Yes, true. The distance is not a problem as I could run another cable or split the existing one. I am more interested in the internal logistics of getting the VNC working, will there be a problem with the 2 nics in the main machine.
Thanks, Mike I personally hasn't done this myself, but I would say "it shouldn't cause any problems."
Toshi -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Sunday 31 December 2006 01:06, Toshi Esumi wrote:
On Sun, 2006-12-31 at 00:43 -0500, ka1ifq wrote:
Yes, true. The distance is not a problem as I could run another cable or split the existing one. I am more interested in the internal logistics of getting the VNC working, will there be a problem with the 2 nics in the main machine.
Thanks, Mike
I personally hasn't done this myself, but I would say "it shouldn't cause any problems."
Toshi
I have to pick up a couple things ( patch cables & a powered usb hub ) and I am going to give it a try, I guess I keep second guessing, to be on the safe side I guess. Thanks to all for the info, I'll post my results. Thanks, Mike -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Sunday 31 December 2006 07:39, ka1ifq wrote:
On Sunday 31 December 2006 01:06, Toshi Esumi wrote:
On Sun, 2006-12-31 at 00:43 -0500, ka1ifq wrote:
Yes, true. The distance is not a problem as I could run another cable or split the existing one. I am more interested in the internal logistics of getting the VNC working, will there be a problem with the 2 nics in the main machine.
Thanks, Mike
I personally hasn't done this myself, but I would say "it shouldn't cause any problems."
Toshi
I have to pick up a couple things ( patch cables & a powered usb hub ) and
NOOOO, not a hub Mike, get a switch. A little 5port switch is cheap. It will keep all that machine to machine traffic from even seeing any of the other machines. Besides, most hubs are only 10meg, and 100meg switches are easy to find. Hub bad. Switch good. -- _____________________________________ John Andersen -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
John Andersen wrote:
On Sunday 31 December 2006 07:39, ka1ifq wrote:
I have to pick up a couple things ( patch cables & a powered usb hub ) and
NOOOO, not a hub Mike, get a switch. A little 5port switch is cheap. It will keep all that machine to machine traffic from even seeing any of the other machines. Besides, most hubs are only 10meg, and 100meg switches are easy to find.
Hub bad. Switch good.
I believe he said USB hub, not ethernet. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Monday 01 January 2007 08:08, James Knott wrote:
John Andersen wrote:
On Sunday 31 December 2006 07:39, ka1ifq wrote:
I have to pick up a couple things ( patch cables & a powered usb hub ) and
NOOOO, not a hub Mike, get a switch. A little 5port switch is cheap. It will keep all that machine to machine traffic from even seeing any of the other machines. Besides, most hubs are only 10meg, and 100meg switches are easy to find.
Hub bad. Switch good.
I believe he said USB hub, not ethernet.
Oh, so he did... WTF does that have to do with this topic then? -- _____________________________________ John Andersen
I think I saw where the previous problem was solved so now I have a network/routing question(s). First: Suse 10.1 Second: We have two high speed ISP's. Two Routers. Possibility of two networks. Third: I want to install another network card and plug in the secondary network. Question(s): 1) Do I need to set up the router of the secondary with a different subnet etc.? I assume I will have to do something like the primary router uses 198.168.0.1 as its base and the secondary use something like 197.168.0.1. 2) Do I need different network names? Like MSHOME, the default Windows name on one, and TUXNET on the other. 3) Anything else I should know? -- (o:]>*HUGGLES*<[:o) Billie Walsh The three best words in the English Language: "I LOVE YOU" Pass them on! -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Sun, 2006-12-31 at 15:02 -0600, Billie Erin Walsh wrote:
I think I saw where the previous problem was solved so now I have a network/routing question(s).
First: Suse 10.1 Second: We have two high speed ISP's. Two Routers. Possibility of two networks. Third: I want to install another network card and plug in the secondary network.
I think, first, you need to ask yourself this question: How do you want to use two different ISP's Internet connections, like specific destinations (or type of traffic) via ISP1, and the others via ISP2, or loadbalancing, or ISP2 as the backup in case ISP1's connection is down. Toshi -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On 12/31/2006 Toshi Esumi wrote:
or loadbalancing, or ISP2 as the backup in case ISP1's connection is down.
Yeah. Something like that. It's a royal pain in the B___ to have to pull the computer out and switch cables then reboot to get the new address right in the middle of doing something. Once upon a time long long ago in one of my windows setups I had a setting where I could use the high speed through the local network or it would automatically connect through the modem and share the connection if the high speed failed. Load sharing would be nice sometimes, like doing multiple downloads with kget or ktorrent. AND an automatic backup connection would be great. One drops and the other just takes up the load. OH heck! Who am I kidding. OK, the straight skinny. It's there!!!! And it ain't hooked up to my computer!! -- (o:]>*HUGGLES*<[:o) Billie Walsh The three best words in the English Language: "I LOVE YOU" Pass them on! -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Sun, 2006-12-31 at 16:46 -0600, Billie Erin Walsh wrote:
On 12/31/2006 Toshi Esumi wrote:
or loadbalancing, or ISP2 as the backup in case ISP1's connection is down.
Yeah. Something like that. It's a royal pain in the B___ to have to pull the computer out and switch cables then reboot to get the new address right in the middle of doing something. Once upon a time long long ago in one of my windows setups I had a setting where I could use the high speed through the local network or it would automatically connect through the modem and share the connection if the high speed failed.
Load sharing would be nice sometimes, like doing multiple downloads with kget or ktorrent.
AND an automatic backup connection would be great. One drops and the other just takes up the load. I don't know how Linux routing works for your requirement but the device that make the routing decision needs to detect a connectivity down on one of ISPs. The simplest idea is to switch the default gateway from the router for your main ISP to the other when you found the main ISP is down. Another solution is to have a device specifically designed for load balancing for two internet connections. We used one of those, namely Nexland ISB Pro 800, in our office until a couple of months ago but I decided taking it out. Because it was causing strange problems, like intermittent connection loss without ISP's problems. It was too cheap for office use, I guess (US$400). It can be set to ping public IPs via both interfaces to detect connection downs. Idea itself was good but just didn't work well for us.
Toshi -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
participants (8)
-
Billie Erin Walsh -
James Knott -
Joe Morris (NTM) -
John Andersen -
ka1ifq -
Kenneth Schneider -
Mike Noble -
Toshi Esumi