[opensuse] Correct config for dual nic's

newer
[opensuse] BASH - Better way to...

older
[opensuse] KDE Virtual Desktops...

Chris Arnold

31 Mar 2009 31 Mar '09

12:50

Using SLES10 SP2 and need to get multi-nic configured correctly. 1 nic is on a network and the other nic is on another network. Using yast->routing what is the correct way to configure this 2 nic (on the 192.168.123 network)? When I put in the expert config section of routing, dest 192.168.123.0 and give it a gateway of the 192.168.123 network, somethings stop working. So my question is how is a dual nic system suppose to be setup using routing? -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

Show replies by date

Theo van Werkhoven

31 Mar 31 Mar

22:14

Chris Arnold wrote:

...

Using SLES10 SP2 and need to get multi-nic configured correctly. 1 nic is on a network and the other nic is on another network. Using yast->routing what is the correct way to configure this 2 nic (on the 192.168.123 network)? When I put in the expert config section of routing, dest 192.168.123.0 and give it a gateway of the 192.168.123 network, somethings stop working. So my question is how is a dual nic system suppose to be setup using routing?

Using YaST for these tasks is not my tool of choice. In /etc/sysconfig/network/routes you can easily add routes with an editor. You do not give enough info to show you what to put in this table, so you have to read routes(5) and figure that out for yourself. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

Chris Arnold

1 Apr 1 Apr

22:35

Anyone can help? Just need to know what goes in the destination field? Dest to nic ip or what? On 3/31/09 8:50 AM, "Chris Arnold" wrote:

...

Using SLES10 SP2 and need to get multi-nic configured correctly. 1 nic is on a network and the other nic is on another network. Using yast->routing what is the correct way to configure this 2 nic (on the 192.168.123 network)? When I put in the expert config section of routing, dest 192.168.123.0 and give it a gateway of the 192.168.123 network, somethings stop working. So my question is how is a dual nic system suppose to be setup using routing?

-- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

Anders Johansson

22:54

...

On 3/31/09 8:50 AM, "Chris Arnold" wrote:

...
Using SLES10 SP2 and need to get multi-nic configured correctly. 1 nic is on a network and the other nic is on another network. Using yast->routing what is the correct way to configure this 2 nic (on the 192.168.123 network)? When I put in the expert config section of routing, dest 192.168.123.0 and give it a gateway of the 192.168.123 network, somethings stop working. So my question is how is a dual nic system suppose to be setup using routing?

It depends on what you want to achieve. Normally you don't have to do anything. One NIC is on one network, with a netmask, so all packets destined for that network will automatically go through that NIC. The other NIC is on another network, again with a netmask, so all packets destined for that network will automatically go through that NIC. And then the system has one default gateway, which is on one of the two networks, so it will be automatically found, and used for all packets destined for machines not on one of the two local networks. For most setups, this will happen absolutely automatically when you assign addresses to the two NICs. The only problem I have seen is when people think you should have more than one default gateway, which you shouldn't have. If you want anything more complex than this, then you need to study up on routing. If 192.168.123.0 is one of the two local networks, it doesn't need a gateway. A gateway for a network is a machine through which you go when trying to get to a non-local subnet Anders -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

Chris Arnold

2 Apr 2 Apr

01:37

On 4/1/09 6:54 PM, "Anders Johansson" wrote:

...

...
On 3/31/09 8:50 AM, "Chris Arnold" wrote:

...
Using SLES10 SP2 and need to get multi-nic configured correctly. 1 nic is on a network and the other nic is on another network. Using yast->routing what is the correct way to configure this 2 nic (on the 192.168.123 network)? When I put in the expert config section of routing, dest 192.168.123.0 and give it a gateway of the 192.168.123 network, somethings stop working. So my question is how is a dual nic system suppose to be setup using routing?

It depends on what you want to achieve. I ust want my email to work without any dropped connection error from the email client

And then the system has one default gateway, which is on one of the two networks, so it will be automatically found, and used for all packets destined for machines not on one of the two local networks.

For most setups, this will happen absolutely automatically when you assign addresses to the two NICs. The addresses on these nic's are static If you want anything more complex than this, then you need to study up on routing.

If 192.168.123.0 is one of the two local networks, it doesn't need a gateway. A gateway for a network is a machine through which you go when trying to get to a non-local subnet

Anders With nothing entered into the routing in yast, email client comes back with a dropped connection. With 192.168.123.0 and gw of 192.168.123.x, email works fine but other novell services stop working. Also, a traceroute from a client pc to the server shows 2 hops and a traceroute from server to the same client pc shows 1 hop. The packet should return the same path it took and I think this is where the problem is, I believe.

-- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

Per Jessen

08:28

Chris Arnold wrote:

...

On 4/1/09 6:54 PM, "Anders Johansson" wrote:

...
...
On 3/31/09 8:50 AM, "Chris Arnold" wrote:

...
Using SLES10 SP2 and need to get multi-nic configured correctly. 1 nic is on a network and the other nic is on another network. Using yast->routing what is the correct way to configure this 2 nic (on the 192.168.123 network)? When I put in the expert config section of routing, dest 192.168.123.0 and give it a gateway of the 192.168.123 network, somethings stop working. So my question is how is a dual nic system suppose to be setup using routing?

It depends on what you want to achieve.

I ust want my email to work without any dropped connection error from the email client

I'm pretty certain Anders anted to know what you want to achieve with your routing setup and your dual NICs. Unless we know your objective, it's virtually impossible to answer your question.

...

With nothing entered into the routing in yast, email client comes back with a dropped connection.

That would suggest your email-server is not on either of your local networks, which means you need a default gateway (or a static route) to get access to it. What is the address of your default router? /Per -- Per Jessen, Zürich (8.2°C) -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

Ciro Iriarte

1 Apr 1 Apr

22:39

2009/3/31 Chris Arnold :

...

Using SLES10 SP2 and need to get multi-nic configured correctly. 1 nic is on a network and the other nic is on another network. Using yast->routing what is the correct way to configure this 2 nic (on the 192.168.123 network)? When I put in the expert config section of routing, dest 192.168.123.0 and give it a gateway of the 192.168.123 network, somethings stop working. So my question is how is a dual nic system suppose to be setup using routing?

What are you trying to accomplish?, failover?, double throughput? Regards, -- Ciro Iriarte http://cyruspy.wordpress.com -- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

Chris Arnold

22:51

Just trying to get all resources working. Some work when a certain entry is entered and some do not. Can you see via webex? I have webex account On 4/1/09 6:39 PM, "Ciro Iriarte" wrote:

...

2009/3/31 Chris Arnold :

...
Using SLES10 SP2 and need to get multi-nic configured correctly. 1 nic is on a network and the other nic is on another network. Using yast->routing what is the correct way to configure this 2 nic (on the 192.168.123 network)? When I put in the expert config section of routing, dest 192.168.123.0 and give it a gateway of the 192.168.123 network, somethings stop working. So my question is how is a dual nic system suppose to be setup using routing?

What are you trying to accomplish?, failover?, double throughput?

Regards,

-- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

David C. Rankin

2 Apr 2 Apr

04:35

Chris Arnold wrote:

...

Just trying to get all resources working. Some work when a certain entry is entered and some do not. Can you see via webex? I have webex account

On 4/1/09 6:39 PM, "Ciro Iriarte" wrote:

...
2009/3/31 Chris Arnold :

...
Using SLES10 SP2 and need to get multi-nic configured correctly. 1 nic is on a network and the other nic is on another network. Using yast->routing what is the correct way to configure this 2 nic (on the 192.168.123 network)? When I put in the expert config section of routing, dest 192.168.123.0 and give it a gateway of the 192.168.123 network, somethings stop working. So my question is how is a dual nic system suppose to be setup using routing?

What are you trying to accomplish?, failover?, double throughput?

Regards,

Chris, Sorry, I've been following along, but I still don't know enough about your network topology to make a guess at how to make your "email work without any dropped connection error from the email client" I know Theo, Anders and Ciro could give you a one sentence solution to your problem it they had a good picture of your layout and what it is you are trying to do. And... Sometimes a picture is worth a 1000 words. So could you try and give us a simple picture of what you have? Something simple like the following would help. Just make the changes needed and post it back: Box -------- | IP: 192.168.123.1 NIC1: +-----------------------[ cable/dsl router ]------[ internet ]-------> | IP: 192.168.123.0 | NM: 255.255.255.0 | | 192.168.124.0/24 NIC2: +----------------------[ switch ]------[client 1] IP:........ | IP: 192.168.124.0 | \ | NM: 255.255.255.0 | \ -------- | ------[client 2] IP:........ | [client 3] IP:......... Also, give: 04:22 nirvana:/srv/www/download/screenshots/ms> route -n Kernel IP routing table Destination Gateway Genmask Flags Metric Ref Use Iface 192.168.6.0 0.0.0.0 255.255.255.0 U 0 0 0 eth0 169.254.0.0 0.0.0.0 255.255.0.0 U 0 0 0 eth0 127.0.0.0 0.0.0.0 255.0.0.0 U 0 0 0 lo 0.0.0.0 192.168.6.13 0.0.0.0 UG 0 0 0 eth0 The you can explain that you are on [client 2] running kmail trying to access your mail on [x.y.z.a] and you get the following error: -- David C. Rankin, J.D.,P.E. Rankin Law Firm, PLLC 510 Ochiltree Street Nacogdoches, Texas 75961 Telephone: (936) 715-9333 Facsimile: (936) 715-9339 www.rankinlawfirm.com -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

Chris Arnold

11:51

On 4/2/09 12:35 AM, "David C. Rankin" wrote:

...

Chris Arnold wrote:

...
Just trying to get all resources working. Some work when a certain entry is entered and some do not. Can you see via webex? I have webex account

On 4/1/09 6:39 PM, "Ciro Iriarte" wrote:

...
2009/3/31 Chris Arnold :

...
Using SLES10 SP2 and need to get multi-nic configured correctly. 1 nic is on a network and the other nic is on another network. Using yast->routing what is the correct way to configure this 2 nic (on the 192.168.123 network)? When I put in the expert config section of routing, dest 192.168.123.0 and give it a gateway of the 192.168.123 network, somethings stop working. So my question is how is a dual nic system suppose to be setup using routing?

What are you trying to accomplish?, failover?, double throughput?

Regards,

Chris,

Sorry, I've been following along, but I still don't know enough about your network topology to make a guess at how to make your

"email work without any dropped connection error from the email client"

I know Theo, Anders and Ciro could give you a one sentence solution to your problem it they had a good picture of your layout and what it is you are trying to do. And... Sometimes a picture is worth a 1000 words. So could you try and give us a simple picture of what you have? Something simple like the following would help. Just make the changes needed and post it back:

Box -------- | IP: 192.168.123.4 NIC1: +-----------------------[ bound to specific ip for email ] | IP: 192.168.123.0 | NM: 255.255.255.0 | | 192.168.124.3/24 NIC2: +----------------------[ bound to specific ip for edir] IP:........ | IP: 192.168.124.0 | \ | NM: 255.255.255.0 | \ -------- | ------[client2]IP:........192.168.123.247 | [client 3] IP:.........

...

Also, give:

04:22 nirvana:/srv/www/download/screenshots/ms> route -n Kernel IP routing table Destination Gateway Genmask Flags Metric Ref Use Iface 192.168.6.0 0.0.0.0 255.255.255.0 U 0 0 0 eth0 169.254.0.0 0.0.0.0 255.255.0.0 U 0 0 0 eth0 127.0.0.0 0.0.0.0 255.0.0.0 U 0 0 0 lo 0.0.0.0 192.168.6.13 0.0.0.0 UG 0 0 0 eth0

Kernel IP routing table Destination Gateway Genmask Flags Metric Ref UseIface 192.168.124.0 0.0.0.0 255.255.255.0 U 0 0 0 eth1 192.168.123.0 0.0.0.0 255.255.255.0 U 0 0 0 eth0 169.254.0.0 0.0.0.0 255.255.0.0 U 0 0 0 eth0 127.0.0.0 0.0.0.0 255.0.0.0 U 0 0 0 lo 0.0.0.0 192.168.124.2 0.0.0.0 UG 0 0 0 eth1

...

The you can explain that you are on [client 2] running kmail trying to access your mail on [x.y.z.a] and you get the following error:

I am on client 2 running an email proggie (not kmail) entourage (remember this client is not the problem but the problem is on an opensuse system). When I access email I get a connection to the server has been dropped. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

Boyd Stephen Smith Jr.

15:40

In , Chris Arnold wrote:

...

Box -------- | IP: 192.168.123.4 NIC1: +-----------------------[ bound to specific ip for email ] | IP: 192.168.123.0 | NM: 255.255.255.0 | | 192.168.124.3/24 NIC2: +----------------------[ bound to specific ip for edir] IP:........ | IP: 192.168.124.0 | \ | NM: 255.255.255.0 | \ -------- | ------[client2]IP:........192.168.123.247 [client 3] IP:.........

I've been following the thread loosely, and I still have no frackin' idea what you are trying to achieve. Also, 1. 192.168.123.0 is not a valid IP under a 255.255.255.0 netmask. 2. 192.168.124.0 is not a valid IP under a 255.255.255.0 netmask. We appear to have 3 systems involved. oS (2 nics), the client (1 nic?), and the server (who knows?). What is the server IP? Why is the client sending packets through oS? Is oS playing the role of a router here? If so, have you correctly set that up that routing via (IIRC) the SuSEFirewall yast2 module? Does the server know that 192.168.123.0/24 is accessed via oS? If not, you'll probably need to do NAT. If so, you really just need to make sure oS knows to turn ip_forwarding on and either not firewall or poke enough holes through the firewall. -- Boyd Stephen Smith Jr. ,= ,-_-. =. bss@iguanasuicide.net ((_/)o o(\_)) ICQ: 514984 YM/AIM: DaTwinkDaddy `-'(. .)`-' http://iguanasuicide.net/ \_/

Chris Arnold

5 Apr 5 Apr

11:34

On 4/2/09 11:40 AM, "Boyd Stephen Smith Jr." wrote:

...

In , Chris Arnold wrote:

...
Box -------- | IP: 192.168.123.4 NIC1: +-----------------------[ bound to specific ip for email ] | IP: 192.168.123.0 | NM: 255.255.255.0 | | 192.168.124.3/24 NIC2: +----------------------[ bound to specific ip for edir] IP:........ | IP: 192.168.124.0 | \ | NM: 255.255.255.0 | \ -------- | ------[client2]IP:........192.168.123.247 [client 3] IP:.........

I've been following the thread loosely, and I still have no frackin' idea what you are trying to achieve.

Also, 1. 192.168.123.0 is not a valid IP under a 255.255.255.0 netmask. 2. 192.168.124.0 is not a valid IP under a 255.255.255.0 netmask.

We appear to have 3 systems involved. 2 systems oS (2 nics), the client (1 nic?) Yes, I nic , and the server (who knows?). What is the server IP? 192.168.123.x and 192.168.124.x Why is the client sending packets through oS? Email and edir resons Is oS playing the role of a router here? No If so, have you correctly set that up that routing via (IIRC) the SuSEFirewall yast2 module? Suse firewall is off Does the server know that 192.168.123.0/24 is accessed via oS? If not, you'll probably need to do NAT. If so, you really just need to make sure oS knows to turn ip_forwarding on and either not firewall or poke enough holes through the firewall. Holes already exist on the firewall. This has been working in the past, up until I added a 2nd nic so I could bind edir to it.

What I do know is when I add 192.168.123.0 and gw of 192.168.123.x and the subnet in yast->routing, email starts working again and other stuff stops working. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

Anders Johansson

11:50

On Sunday 05 April 2009 13:34:50 Chris Arnold wrote:

...

Holes already exist on the firewall. This has been working in the past, up until I added a 2nd nic so I could bind edir to it.

What I do know is when I add 192.168.123.0 and gw of 192.168.123.x and the subnet in yast->routing, email starts working again and other stuff stops working.

If your network card has an ip address starting with 192.168.123 (not including .0 and .255, those are invalid host addresses), and a netmask of 255.255.255.0, then the network/interface entry in the routing table should be added completely automatically. You don't need to add anything else anywhere to communicate with hosts on the 192.168.123 network. Unless of course those hosts are physically separated, and need to go through routers along the way, but this would be a bad network setup. Your diagram seemed to say that the 192.168.123.247 client was physically connected to the 192.168.124.3 NIC on the server. Is this correct, or just a misunderstanding of the diagram on my part? Anders -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

James Knott

13:24

Anders Johansson wrote:

...

On Sunday 05 April 2009 13:34:50 Chris Arnold wrote:

...
Holes already exist on the firewall. This has been working in the past, up until I added a 2nd nic so I could bind edir to it.

What I do know is when I add 192.168.123.0 and gw of 192.168.123.x and the subnet in yast->routing, email starts working again and other stuff stops working.

If your network card has an ip address starting with 192.168.123 (not including .0 and .255, those are invalid host addresses), and a netmask of 255.255.255.0

Actually, they can be valid addresses, provided your sub net mask allows it. In the /24 mask shown, they are indeed invalid. With a /23 mask, 192.168.123.0 would be valid, but not 192.168.123.255, etc. The highest and lowest addresses within the subnet are not usable. Everything else is. -- Use OpenOffice.org http://www.openoffice.org -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

Anders Johansson

13:29

On Sunday 05 April 2009 15:24:43 James Knott wrote:

...

Anders Johansson wrote:

...
On Sunday 05 April 2009 13:34:50 Chris Arnold wrote:

...
Holes already exist on the firewall. This has been working in the past, up until I added a 2nd nic so I could bind edir to it.

What I do know is when I add 192.168.123.0 and gw of 192.168.123.x and the subnet in yast->routing, email starts working again and other stuff stops working.

If your network card has an ip address starting with 192.168.123 (not including .0 and .255, those are invalid host addresses), and a netmask of 255.255.255.0

Actually, they can be valid addresses, provided your sub net mask allows it. In the /24 mask shown, they are indeed invalid. With a /23 mask, 192.168.123.0 would be valid, but not 192.168.123.255, etc. The highest and lowest addresses within the subnet are not usable. Everything else is.

Yes, correct, the parenthesis was misplaced. It refers to the IP address, but it was meant to include the proviso "...and a netmask of 255.255.255.0" Anders -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

Chris Arnold

18:22

I have a dim-dim account and would love to share my desktiop with someone so we can more clearly understand what is going on, how the server is setup and the client role/error. Please email and I will setup a meeting. On 4/5/09 9:29 AM, "Anders Johansson" wrote:

...

On Sunday 05 April 2009 15:24:43 James Knott wrote:

...
Anders Johansson wrote:

...
On Sunday 05 April 2009 13:34:50 Chris Arnold wrote:

...
Holes already exist on the firewall. This has been working in the past, up until I added a 2nd nic so I could bind edir to it.

What I do know is when I add 192.168.123.0 and gw of 192.168.123.x and the subnet in yast->routing, email starts working again and other stuff stops working.

If your network card has an ip address starting with 192.168.123 (not including .0 and .255, those are invalid host addresses), and a netmask of 255.255.255.0

Actually, they can be valid addresses, provided your sub net mask allows it. In the /24 mask shown, they are indeed invalid. With a /23 mask, 192.168.123.0 would be valid, but not 192.168.123.255, etc. The highest and lowest addresses within the subnet are not usable. Everything else is.

Yes, correct, the parenthesis was misplaced. It refers to the IP address, but it was meant to include the proviso "...and a netmask of 255.255.255.0"

Anders

-- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

Anders Johansson

20:42

On Sunday 05 April 2009 13:34:50 Chris Arnold wrote:

...

What I do know is when I add 192.168.123.0 and gw of 192.168.123.x and the subnet in yast->routing, email starts working again and other stuff stops working.

Problem understood and fixed. Just a quick summary for the benefit of the list: The server has two interfaces, 192.168.124.0/24 and 192.168.123.0/24. On the 124 interface, email was running, on 123 other services. The client has a 192.168.123.0/24 address, and a gateway of 192.168.123.1. The router didn't do any NAT between the two 192.168 networks Without any special rules on the server, the services on the 123 interfaces on the server worked. The client talked directly to them, and got a response from the 123 interface, no problem. But when talking to email, the client sent the packet to the router, expecting a reply back from the router. But the server answered directly on its 123 interface. The client ignored those responses, so email failed. With the routing rule on the server, all packets for the 123 network were sent to the router. Now email worked, because the client sent packets to the router and got responses from the router. But everything else failed, because those responses *also* came from the router, when the client expected responses directly from the server Solution: enable NAT when communicating from the 123 network to the 124 network. Now the server no longer sees the internal address as source for the email packets, so it responds correctly to everything Tricky :) Anders -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

David C. Rankin

2 Apr 2 Apr

04:40

Chris Arnold wrote:

...

Just trying to get all resources working. Some work when a certain entry is entered and some do not. Can you see via webex? I have webex account

On 4/1/09 6:39 PM, "Ciro Iriarte" wrote:

...
2009/3/31 Chris Arnold :

...
Using SLES10 SP2 and need to get multi-nic configured correctly. 1 nic is on a network and the other nic is on another network. Using yast->routing what is the correct way to configure this 2 nic (on the 192.168.123 network)? When I put in the expert config section of routing, dest 192.168.123.0 and give it a gateway of the 192.168.123 network, somethings stop working. So my question is how is a dual nic system suppose to be setup using routing?

What are you trying to accomplish?, failover?, double throughput?

Regards,

Chris, Here is a good page for network basics. It won't solve your routing issue, but it will help make sure we are talking apples to apples (no pun intended -- see the site name) http://www.faqintosh.com/risorse/en/guides/net/tcp/basic/ -- David C. Rankin, J.D.,P.E. Rankin Law Firm, PLLC 510 Ochiltree Street Nacogdoches, Texas 75961 Telephone: (936) 715-9333 Facsimile: (936) 715-9339 www.rankinlawfirm.com -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

5504

Age (days ago)

5509

Last active (days ago)

List overview

Download

17 comments

8 participants

participants (8)

Anders Johansson
Boyd Stephen Smith Jr.
Chris Arnold
Ciro Iriarte
David C. Rankin
James Knott
Per Jessen
Theo van Werkhoven