LinuxQuestions.org
Register a domain and help support LQ
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Networking
User Name
Password
Linux - Networking This forum is for any issue related to networks or networking.
Routing, network cards, OSI, etc. Anything is fair game.

Notices



Reply
 
Search this Thread
Old 02-11-2008, 06:59 AM   #1
Salmus
LQ Newbie
 
Registered: Jun 2007
Posts: 2

Rep: Reputation: 0
2 ISP - 2 LAN's - 2 GATEWAYS - 1 Rooter


Hello,

1st of all please forgive me about my bad language, I'm trying to spell it right but ... mistakes may occur.

I'm trying over 5 hours to figure out why my slackware server doesn't work well with my new ISP . My network topology is:

eth0 (public IP) --> SWITCH --> Local Servers Cabinet (public IP's)
eth1 = ISP 1 - Fiber Optic (public IP - 89.165.208.90)

ISP1 is routing for me 89.165.150.160/27, so 89.165.150.161 will be used on eth0 and 89.165.150.162 will be used on the 1st server connected with eth0 .


eth4 - Local Area Connection --> Switch --> Desktop computers (private IP's)
eth5 - ISP 2 - UTP Connection (public IP - 85.121.148.20)


The goal is :

eth4 --> eth5 --> INTERNET (ISP 2) -- SNAT
eth1 --> eth0 --> INTERNET (ISP 1) -- Forwarding

In this moment, the SNAT (NAT) in eth4 local area connection works, but i have the following problems:

1) eth1 - Doesn't respond to ICMP packets comming from outside

2) Doesn't respond to ICMP packets comming to eth1 destination eth0 (89.165.150.160/27)

3) Servers located on internal network eth0 (89.165.150.160/27) do not have internet connection thru rooter (eth1)


More informations:

Rooter
-------
eth0 - 89.165.150.161 --> LOCAL SERVERS CONNECTION
eth1 - 89.165.208.90 --> ISP CONNECTION 1
eth4 - 192.168.0.1 --> LOCAL AREA CONNECTIOn
eth5 - 85.121.148.20 --> ISP CONNECTION 2

Described above

Server 1
---------
eth0 - with IP 89.165.150.162

Server 1 --> ROOTER --> ISP CONNECTION 1



More informations:



root@Rooter-Node1:~# ip route l
89.165.208.88/30 dev eth1 proto kernel scope link src 89.165.208.90
89.165.150.160/27 dev eth0 proto kernel scope link src 89.165.150.161
192.168.0.0/24 dev eth4 proto kernel scope link src 192.168.0.1
85.121.148.0/24 dev eth5 proto kernel scope link src 85.121.148.20
127.0.0.0/8 dev lo scope link
default via 85.121.148.1 dev eth5 metric 1
default via 89.165.208.89 dev eth1 metric 2
root@Rooter-Node1:~#


root@Rooter-Node1:~# ifconfig
eth0 Link encap:Ethernet HWaddr 00:1C:F0:11:F8:85
inet addr:89.165.150.161 Bcast:89.165.150.191 Mask:255.255.255.224
inet6 addr: fe80::21c:f0ff:fe11:f885/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:787 errors:0 dropped:0 overruns:0 frame:0
TX packets:434 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:92476 (90.3 KiB) TX bytes:40216 (39.2 KiB)
Interrupt:21

eth1 Link encap:Ethernet HWaddr 00:1C:F0:11:F8:5E
inet addr:89.165.208.90 Bcast:89.165.208.91 Mask:255.255.255.252
inet6 addr: fe80::21c:f0ff:fe11:f85e/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:953 errors:0 dropped:0 overruns:0 frame:0
TX packets:12417 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:593850 (579.9 KiB) TX bytes:5165588 (4.9 MiB)
Interrupt:17

eth4 Link encap:Ethernet HWaddr 00:C0F:0A:32:0B
inet addr:192.168.0.1 Bcast:192.168.0.255 Mask:255.255.255.0
inet6 addr: fe80::2c0:dfff:fe0a:320b/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:303693 errors:0 dropped:0 overruns:0 frame:0
TX packets:189536 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:307372143 (293.1 MiB) TX bytes:42731462 (40.7 MiB)
Interrupt:23 Base address:0xdd00

eth5 Link encap:Ethernet HWaddr 00:18:F3:CE7:36
inet addr:85.121.148.20 Bcast:85.121.148.255 Mask:255.255.255.0
inet6 addr: fe80::218:f3ff:fece:d736/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:211645 errors:0 dropped:0 overruns:0 frame:0
TX packets:287642 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:43451827 (41.4 MiB) TX bytes:301966517 (287.9 MiB)
Interrupt:22 Base address:0xd400

lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:4 errors:0 dropped:0 overruns:0 frame:0
TX packets:4 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:272 (272.0 b) TX bytes:272 (272.0 b)

root@Rooter-Node1:~#


root@Rooter-Node1:~# route -n
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use Iface
89.165.208.88 0.0.0.0 255.255.255.252 U 0 0 0 eth1
89.165.150.160 0.0.0.0 255.255.255.224 U 0 0 0 eth0
192.168.0.0 0.0.0.0 255.255.255.0 U 0 0 0 eth4
85.121.148.0 0.0.0.0 255.255.255.0 U 0 0 0 eth5
127.0.0.0 0.0.0.0 255.0.0.0 U 0 0 0 lo
0.0.0.0 85.121.148.1 0.0.0.0 UG 1 0 0 eth5
0.0.0.0 89.165.208.89 0.0.0.0 UG 2 0 0 eth1
root@Rooter-Node1:~#

root@Rooter-Node1:~# ping -I eth1 194.105.24.1 -c 1
PING 194.105.24.1 (194.105.24.1) from 89.165.208.90 eth1: 56(84) bytes of data.
64 bytes from 194.105.24.1: icmp_seq=1 ttl=252 time=0.518 ms

--- 194.105.24.1 ping statistics ---
1 packets transmitted, 1 received, 0% packet loss, time 0ms
rtt min/avg/max/mdev = 0.518/0.518/0.518/0.000 ms
root@Rooter-Node1:~#

root@Rooter-Node1:~# ping -I eth5 194.105.24.1 -c 1
PING 194.105.24.1 (194.105.24.1) from 85.121.148.20 eth5: 56(84) bytes of data.
64 bytes from 194.105.24.1: icmp_seq=1 ttl=250 time=2.33 ms

--- 194.105.24.1 ping statistics ---
1 packets transmitted, 1 received, 0% packet loss, time 0ms
rtt min/avg/max/mdev = 2.334/2.334/2.334/0.000 ms
root@Rooter-Node1:~#


THANK YOU !!
 
Old 02-23-2008, 10:30 AM   #2
rayfordj
Member
 
Registered: Feb 2008
Location: Texas
Distribution: Fedora, RHEL, CentOS
Posts: 475

Rep: Reputation: 73
please review my post on your other thread
http://www.linuxquestions.org/questi...haring-620318/

I think you are looking for information on configuring/using "Linux Advanced Routing & Traffic Control"
 
  


Reply


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off


Similar Threads
Thread Thread Starter Forum Replies Last Post
Why did redirect me to rooter Sergios24 Linux - Networking 3 12-28-2006 02:21 PM
Wireless LAN's with SuSE seanlinux Linux - Distributions 10 06-14-2006 10:24 PM
Help connecting two Lan's on same server with IPTABLES cipx2 Linux - Networking 7 08-06-2004 06:02 AM
!building a tunnel between two LAN's telephones pudhiyavan Linux - Networking 0 06-15-2004 03:31 AM
DNS setup problem for webhosting behind a rooter batmanu Linux - Networking 3 06-02-2004 09:45 PM


All times are GMT -5. The time now is 09:31 PM.

Main Menu
Advertisement
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
identi.ca: @linuxquestions
Facebook: linuxquestions Google+: linuxquestions
Open Source Consulting | Domain Registration