Linux - Networking This forum is for any issue related to networks or networking.
Routing, network cards, OSI, etc. Anything is fair game. |
Notices |
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
Are you new to LinuxQuestions.org? Visit the following links:
Site Howto |
Site FAQ |
Sitemap |
Register Now
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
|
|
|
11-21-2013, 01:00 PM
|
#16
|
LQ Newbie
Registered: Sep 2013
Posts: 20
Original Poster
Rep:
|
Quote:
Originally Posted by enyawix
You can have two default gateways you get equal cost load balancing assuming the administrative distance is the same for each link. Cisco routers do this all the time. I am sure Linux can do it to.
|
Now why do I have to use 10.0.0.0 and not 10.146.123.0 which is the network address on the IP range for that NIC?
Sorry I am a bit of a noob when it comes to TCP/IP
|
|
|
11-21-2013, 01:16 PM
|
#17
|
Member
Registered: Sep 2003
Location: ky
Distribution: gentoo
Posts: 409
Rep:
|
linuxr00lz2013 based on what you posted looks like you need to build service routes. Packets need to be routed
end to end. Traffic from. 169.254.95.0 and 169.254.0.0 have no return routes. So packets can get to 10.146.112.1
and 10.146.123.1 but can not get back, so ping fails.
|
|
|
11-21-2013, 01:20 PM
|
#18
|
Moderator
Registered: Jun 2001
Location: UK
Distribution: Gentoo, RHEL, Fedora, Centos
Posts: 43,417
|
Quote:
Originally Posted by enyawix
You can have two default gateways you get equal cost load balancing assuming the administrative distance is the same for each link. Cisco routers do this all the time. I am sure Linux can do it to.
|
You need to READ the thread before answering. You're talking about something he's not asking about, and you're just confusing him.
|
|
|
11-21-2013, 01:21 PM
|
#19
|
Moderator
Registered: Jun 2001
Location: UK
Distribution: Gentoo, RHEL, Fedora, Centos
Posts: 43,417
|
Quote:
Originally Posted by linuxr00lz2013
Now why do I have to use 10.0.0.0 and not 10.146.123.0 which is the network address on the IP range for that NIC?
Sorry I am a bit of a noob when it comes to TCP/IP
|
I said to use 10.0.0.0/8 as I *presumed* that covered all the internal networks that would head off in that direction.
10.146.123.0 doesn't need any routing. you are already on it. you KNOW where that network is. It's everything else that is NOT internet that you need to provide routing information for.
Last edited by acid_kewpie; 11-21-2013 at 01:33 PM.
|
|
|
11-21-2013, 01:30 PM
|
#20
|
LQ Newbie
Registered: Sep 2013
Posts: 20
Original Poster
Rep:
|
Quote:
Originally Posted by acid_kewpie
I said to use 10.0.0.0/8 as I *presumed* that covered all the internal networks that would head off in that direction.
10.146.123.0 doesn't need any routing. you are already on it. you KNOW where that network is. It's everything else that is NOT internet that you need to provide routing information for.
Looking back at your earlier posts... you're only trying to hit a machine that's on the same local network currently? Well that's nothing to do with routing at all, as above, you're already there. no gateway anythings required to reach that.
|
I was able to get this to work in a Red Hat box earlier... I posted in the forums and I got some good advice.. Here is the thread:
http://www.linuxquestions.org/questi...ic-4175482942/
Seeing that Ubuntu has its network config files set up differently.. I have no idea how to replicate the same process but on Ubuntu.
|
|
|
11-21-2013, 01:34 PM
|
#21
|
Moderator
Registered: Jun 2001
Location: UK
Distribution: Gentoo, RHEL, Fedora, Centos
Posts: 43,417
|
you follow the link I posted earlier, and when asked to confirm you've reloaded the network and to show your routing tables you actually do it.
|
|
|
11-21-2013, 01:41 PM
|
#22
|
LQ Newbie
Registered: Sep 2013
Posts: 20
Original Poster
Rep:
|
Quote:
Originally Posted by acid_kewpie
you follow the link I posted earlier, and when asked to confirm you've reloaded the network and to show your routing tables you actually do it.
|
thank you for your reply. I appreciate the quick replies
I did follow that link and I posted the output after I did the reload. It still didnt work
|
|
|
11-21-2013, 01:52 PM
|
#23
|
Member
Registered: Sep 2003
Location: ky
Distribution: gentoo
Posts: 409
Rep:
|
Quote:
Originally Posted by linuxr00lz2013
I was able to get this to work in a Red Hat box earlier... I posted in the forums and I got some good advice.. Here is the thread:
http://www.linuxquestions.org/questi...ic-4175482942/
Seeing that Ubuntu has its network config files set up differently. I have no idea how to replicate the same process but on Ubuntu.
|
Reading that post you have return routes definded simply using routing list. reread post 14. Using dynamic routing would be simpler, but is far beyond the scope of this forum. If you intend to become a network engineer you need to know sub netting and dynamic routing like rip, ospf, and isis.
intro to dynamic routing
http://www.youtube.com/watch?v=DT-pmXMCOS8
intro to sub netting
http://www.youtube.com/watch?v=AJPZxXwOc-4
|
|
|
11-21-2013, 01:56 PM
|
#24
|
LQ Newbie
Registered: Sep 2013
Posts: 20
Original Poster
Rep:
|
Quote:
Originally Posted by enyawix
Reading that post you have return routes definded simply using routing list. reread post 14. Using dynamic routing would be simpler, but is far beyond the scope of this forum. If you intend to become a network engineer you need to know sub netting and dynamic routing like rip, ospf, and isis.
intro to dynamic routing
http://www.youtube.com/watch?v=DT-pmXMCOS8
intro to sub netting
http://www.youtube.com/watch?v=AJPZxXwOc-4
|
thank you for the links! ill definitely check them out!
|
|
|
11-21-2013, 02:55 PM
|
#25
|
LQ Newbie
Registered: Sep 2013
Posts: 20
Original Poster
Rep:
|
Quote:
Originally Posted by acid_kewpie
you follow the link I posted earlier, and when asked to confirm you've reloaded the network and to show your routing tables you actually do it.
|
Here is the modified /etc/network/interfaces file:
Code:
cat /etc/network/interfaces
# This file describes the network interfaces available on your system
# and how to activate them. For more information, see interfaces(5).
# The loopback network interface
auto lo
iface lo inet loopback
# The primary network interface
auto eth0
iface eth0 inet static
address 10.146.112.34
netmask 255.255.255.0
gateway 10.146.112.1
auto eth1
allow-hotplug eth1
iface eth1 inet static
address 10.146.123.8
netmask 255.255.255.0
post-up route add -net 10.146.123.0 netmask 255.255.255.0 gw 10.146.123.1
and the route -n output
Code:
route -n
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use Iface
10.146.112.0 0.0.0.0 255.255.255.0 U 0 0 0 eth0
10.146.123.0 10.146.123.1 255.255.255.0 UG 0 0 0 eth1
10.146.123.0 0.0.0.0 255.255.255.0 U 0 0 0 eth1
169.254.95.0 0.0.0.0 255.255.255.0 U 1 0 0 usb0
169.254.0.0 0.0.0.0 255.255.0.0 U 1000 0 0 eth0
0.0.0.0 10.146.112.1 0.0.0.0 UG 100 0 0 eth0
Unfortunately, i am still getting the same problem
|
|
|
11-21-2013, 04:39 PM
|
#26
|
Moderator
Registered: Jun 2001
Location: UK
Distribution: Gentoo, RHEL, Fedora, Centos
Posts: 43,417
|
your route statement there makes NO sense. As I already said, You're already ON that network.
10.146.123.0 is NOT NOT NOT reachable via 10.146.123.1. Just read what that says... it's like driving to the garage to get your car... nonsense.
delete that entry if the only thing you want to get to via eth1 is other machines on the same subnet. there is no work at all to even do there. no routes or anything.
|
|
|
11-22-2013, 12:08 PM
|
#27
|
LQ Newbie
Registered: Sep 2013
Posts: 20
Original Poster
Rep:
|
Quote:
Originally Posted by acid_kewpie
your route statement there makes NO sense. As I already said, You're already ON that network.
10.146.123.0 is NOT NOT NOT reachable via 10.146.123.1. Just read what that says... it's like driving to the garage to get your car... nonsense.
delete that entry if the only thing you want to get to via eth1 is other machines on the same subnet. there is no work at all to even do there. no routes or anything.
|
Ok well I commented out the entry for the route for eth1 in /etc/network/interfaces and I reloaded the service. Here is the output of my route -n:
Code:
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use Iface
10.146.112.0 0.0.0.0 255.255.255.0 U 0 0 0 eth0
10.146.123.0 0.0.0.0 255.255.255.0 U 0 0 0 eth1
169.254.95.0 0.0.0.0 255.255.255.0 U 1 0 0 usb0
169.254.0.0 0.0.0.0 255.255.0.0 U 1000 0 0 eth0
0.0.0.0 10.146.112.1 0.0.0.0 UG 100 0 0 eth0
But its still not working for me.
Also, I checked with one of my network engineers and previously in RedHat and also in windows we set up the NIC to route through 10.146.123.1 and it routed fine and backups ran fine. I still dont know what I am doing incorrectly thats causing this to behave strangely.
|
|
|
11-22-2013, 03:52 PM
|
#28
|
Moderator
Registered: Jun 2001
Location: UK
Distribution: Gentoo, RHEL, Fedora, Centos
Posts: 43,417
|
if that's still not working, then it's something else. iptables, physical connectivity or something.
|
|
|
11-22-2013, 04:00 PM
|
#29
|
LQ Newbie
Registered: Sep 2013
Posts: 20
Original Poster
Rep:
|
Quote:
Originally Posted by acid_kewpie
if that's still not working, then it's something else. iptables, physical connectivity or something.
|
ya we figured a part of it out... it was on the wrong VLAN.
now im working on configuring to get the routing proper
|
|
|
All times are GMT -5. The time now is 04:37 PM.
|
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
|
Latest Threads
LQ News
|
|