Routes
Mar 29, 2007
Just wondering if anyone can offer any thoughts on this. I'm currently in the process of setting up an Exchange frontend server which will (hopefully) be connected to two different connectivity providers.
On the two NIC's we have for example:
ISP1 - 1.1.1.1/24 with gateway 1.1.1.2
ISP2 - 2.2.2.1/24 with gateway 2.2.2.2
My assumption was that when a connection to the internet is required, providing the metric is set correctly, it would route from the NIC connected to ISP1. However if a connection came in from ISP2, it would note the interface that the connection came in on and reply on that interface (SMTP traffic), however I'm told this isn't right.
View 0 Replies
May 18, 2007
I have a small network at my colo provider.
Colo Provider
|
My HP 2650
| |
server1 serverN
I want to setup static routes on my servers so that my colo provider won't bill me for traffic among my servers.
I use FreeBSD 6 on my servers. I read the FreeBSD handbook on this and it looks like i should do this:
route add -net 0.0.0/24 0.0.0.3
where 0.0.0/24 is the C class I have from my provider and 0.0.0.3 is the IP address of my server (one of them/any of them).
However, this route appears to already exist as i get this error when running that route command:
route: writing to routing socket: File exists
add net 0.0.0: gateway 0.0.0.3: route already in table
Do I need to use a non-routeable ip block (eg 192.168.x.x) for this? Can I use "real"/routeable ips? Does FreeBSD take care of this for me automatically?
View 5 Replies
View Related
Apr 30, 2009
Sometimes in the Dedicated Hosting Offers section you see people ping the providers IP and can discover other companies they go through, or if they are a reseller. Im wondering how I can go about finding out this information as well?
View 5 Replies
View Related
Nov 7, 2009
I really wanna know if you've seen any other trace routes similar to this?
Wanna know the catch? Look what I put into CMD...
tracert core2.te5-2-bbnet2.wdc002.pnap.net
Code:
Tracing route to core2.te5-2-bbnet2.wdc002.pnap.net.changeme.com [216.34.131.135]
over a maximum of 30 hops:
2 <1 ms <1 ms <1 ms tr3.tpa-rt1.hivelocity.net [69.46.31.105]
3 3 ms <1 ms <1 ms xe-8-0-0.bar1.Tampa1.Level3.net [4.53.172.1]
4 18 ms 31 ms 18 ms ae-6-6.ebr2.Atlanta2.Level3.net [4.69.137.114]
5 22 ms 19 ms 19 ms ae-73-70.ebr3.Atlanta2.Level3.net [4.69.138.20]
6 37 ms 35 ms 35 ms ae-2.ebr1.Washington1.Level3.net [4.69.132.86]
7 41 ms 35 ms 35 ms ae-71-71.csw2.Washington1.Level3.net [4.69.134.134]
8 33 ms 34 ms 33 ms ae-2-79.edge2.Washington4.Level3.net [4.68.17.83]
9 33 ms 33 ms 33 ms savvis-level3-te.Washington1.Level3.net [4.68.110.102]
10 34 ms 34 ms 34 ms cr1-tengig0-7-2-0.washington.savvis.net [204.70.197.242]
11 85 ms 85 ms 85 ms cr2-pos0-0-0-0.sanfrancisco.savvis.net [204.70.192.90]
12 90 ms 90 ms 90 ms kar1-ge-1-0-0.SanFranciscosfo.savvis.net [206.24.211.22]
13 90 ms 91 ms 91 ms 204.70.200.142
14 86 ms 86 ms 86 ms cr1-gigabitethernet-0-7-1-0.SanFrancisco.savvis.net [206.24.211.9]
15 86 ms 86 ms 85 ms er1-7-0-0.SanJoseEquinix.savvis.net [204.70.200.197]
16 86 ms 86 ms 86 ms hr1-te-1-0-0.santaclarasc8.savvis.net [204.70.200.214]
17 86 ms 86 ms 86 ms hr1-te-2-0-1.santaclarasc9.savvis.net [204.70.200.18]
18 * 325 ms 322 ms csr11-ve242.santaclarasc8.savvis.net [66.35.194.98]
19 832 ms 86 ms 87 ms 216.34.131.135
Trace complete.
if you know any carrier that doesn't peer with Level3, Cogent, and Global Crossing...
View 5 Replies
View Related
Apr 11, 2007
Does anyone have a good lead on any providers who have sub-cable between seattle & aus?
View 5 Replies
View Related
Mar 29, 2009
Attached is a (badly) drawn diagram of two sites, connected by a vpn.
The site to the left, is network 10.0.0.0/24 which runs a linux server as the router for the network.
The site to the right, is network 10.1.0.0/24 which runs a windows 2003 server as the router for the network.
Now, my problem is, the clients behind the windows 2003 server can ping any machine on the first network because i setup a static route to route all traffic to 10.0.0.0/24 over the vpn interface.
now, my problem is, only the linux server can ping any machine on the windows 2003 network, any client behind the linux server cant seem to route over the interface.
I have the following route on the linux server: .....
View 0 Replies
View Related
