Routing through other network

0 pts.
Tags:
Active Directory
Bind
Cisco
DataCenter
DHCP
DNS
General Directories
Hardware
LDAP
Lotus Domino
Microsoft Windows
Network management software
Networking
Networking services
Remote management
Security
hi,there is a problem.it was heavy rains since few days becouse of which our connection to our ISP has been broken.there is another network in the neighbourhood which is connected to the same ISP. how can we route our traffic through there link,what hardware n software configuration changes we need to make? thanks for any help.
ASKED: July 27, 2005  7:55 AM
UPDATED: July 28, 2005  1:53 PM

Answer Wiki

Thanks. We'll let you know when a new response is added.

Have you lost physical connectivity to the outside world? If so you’ll have to roll a wire to the nearest live point. Ethernet needs a booster every 100m. Or you could use a phone line. You’ve then got a choice of dial-up or ADSL. This may seem foolish but why not get an engineer in to fix it?

Discuss This Question: 6  Replies

 
There was an error processing your information. Please try again later.
Thanks. We'll let you know when a new response is added.
Send me notifications when members answer or reply to this question.

REGISTER or login:

Forgot Password?
By submitting you agree to receive email from TechTarget and its partners. If you reside outside of the United States, you consent to having your personal data transferred to and processed in the United States. Privacy
  • Howard2nd
    A - do you have a physical connection to the other network? B - are they willing to share their bandwidth with you? C - how are your IP addresses distributed (dhcp) and what sort of firewall/gateway are you using? D - How long until your connection will be repaired? Those questions set the facts with which you can make reasonable dicisions and a plan. A - UTP versus fiber versus wireless. Wireless is severely interrupted by rain. UTP is limited to 100 meters without repeater or using transceievers to convert from Ethernet to WAN signals. (A LOT of choices out there.) Fiber is expensive for a temporary fix. Labor and materials can easily put the cost of a new physical connection at a thousand plus. B - Bandwidth. What size connection did you have to the ISP? What size connection does your neighbor have? Will their gateway/firewall support a second zone for you? If there are costs for equipment at their site, they are YOUR costs, but have written agreements about the equipment ownership after the emergency is over. C - directly relates to 'B'. IP addresses are handled how? 1 - distributed by the ISP to each machine, dramatic increase in cost to your neighbor as the ISP thinks he has lots of new machines AND your IP addresses are all different. 2 - ISP issues one address to you and you have a dhcp server behind the firewall gateway to generate internal addresses (NAT - native address translation). In this case if the neighbor's gateway/firewall can route your IP separate from his own then you connect his feed to your firewall/gateway and things work normally. 3 - If his gateway/firewall is an appliance cable modem, dsl modem, isdn, then you need to set up a second unit at his site and feed your connection. D - Now, once you have the costs written down and can look at the problem logically - get the connection repaired. Good Luck.
    30 pointsBadges:
    report
  • Redrose
    hi thanks for the replies. yes we have lost physical connectivity.our neighbours are ready to provide us a spare link of theres which although has a very small bandwidth,no matter something is better than nothing :-).n there network is within 100 meter range so we can use copper.they have suggested to use a server of theres to connect to our switch.n change the default route on our router to there server's.they will create a reverse route on there server to our router. i just wish to know is it a good solution,will it work fine?or is there some other better solution?we have cisco router n switch .
    0 pointsBadges:
    report
  • HumbleNetAdmin
    Questions; Do you have a firewall? Once you connect to their network, you will be apart of their network, security issue. Also, does their network use the same subnet as yours? IE? Your networks IP's are 192.168.1.0 255.255.255.0 and theirs is also, if yes, then all you need to do is provide an Ethernet link between a core switch on your network and a core switch on theirs. However if you have disparate network subnets then you will need a router in between to connect those networks, lets say a router with two Ethernet cards, one on your network with an IP from your network, and the other connecting to their network with I an IP from their network. Then your default gateway would be the IP of the Ethernet card in the router connected to your network, the routers gateway the IP address of the Ethernet card connecting to their network. I don?t know this for sure, but I think VLAN capable switch may be able to accomplish the same thing, don?t hold me to that however
    0 pointsBadges:
    report
  • Cptrelentless
    Depends on your switch. If it's a routing switch (a big one, like a 3Com 4050 or similar) it'll be able to route between the links. Otherwise it won't. However if there is one upstream in the adjacent network you could hang your switch off a VLAN on their network and have your equipment on the VLAN. You'll have to get your network allowed through their router to the outside otherwise you'll have no internut.
    0 pointsBadges:
    report
  • Douger
    Another thought on how to do this. I assume you have some sort of firewall and so do they. Run your copper from the untrusted side of your firewall to a switch or even an old hub that sits between their internet router and the untrusted side of their firewall. That way you have no ip addressing issues as your public ip address on your firewall will be routed through your neighbor's connection along with yours. All you need is the wire and an inexpensive switch. An alternative to the wire would be a wireless bridge setup, but as indicated above that can get dicey depending on the path that the signal needs to travel and weather conditions if it is going outside. Good luck.
    0 pointsBadges:
    report
  • Astronomer
    My first response here is to suggest fixing your connection. Now, assuming you still want to use the other company, there are several issues. Do you have a service visible to the internet? If so, pointing things to the new connection could be a problem, depending on the ISP. There may need to be some translations to get to your net. If you are just a client of the internet, things are considerably simpler. I assume you have internal private addressing and get your public address via DHCP from the ISP. Since the clients get proxied going to the internet, the internal addresses don't matter that much. If you do use identical addresses, one solution is what linux documentation refers to a twice NAT. This is an ugly hack but it can be done. Arrange for your proxy/firewall machine to have an address accessible from the other company so the requests can get out and the responses can get in. If you stick a net between the proxy and other company, you can avoid the twice NAT hack, but it will probably complicate routing and DNS. You may have to cascade thru their proxy. I haven't tried it but have been told this can be done. Also, you may have to reconfigure your DNS and route table on your firewall/proxy. This depends on how much things were automated in your existing ISP connection and how the other company provides things internally. As other respondents have already mentioned, be aware on any security issues raised by this kind of connection. You can do this but I would still recommend fixing the connection. rt
    15 pointsBadges:
    report

Forgot Password

No problem! Submit your e-mail address below. We'll send you an e-mail containing your password.

Your password has been sent to:

To follow this tag...

There was an error processing your information. Please try again later.

REGISTER or login:

Forgot Password?
By submitting you agree to receive email from TechTarget and its partners. If you reside outside of the United States, you consent to having your personal data transferred to and processed in the United States. Privacy

Thanks! We'll email you when relevant content is added and updated.

Following