Sponsored Content
Full Discussion: ISP VPS, routing traffic
Special Forums IP Networking Proxy Server ISP VPS, routing traffic Post 302909414 by solaris_user on Wednesday 16th of July 2014 06:16:39 PM
Old 07-16-2014
Routing traffic from ISP datacenter to enterprise LAN

Hi guys

I need to setup server/router in my firm. We got from our ISP dedicated server in their data center. It has a static IP and it servers as replacement for out DSL connection. I configured our internal server to be border gateway and to connects to data center. "Remote" admin installed squid and IT staff can access to the websites but other can't. I want to remove that proxy server. I think I really don't need it.

Here is the picture how above situation looks

Image

Server router has two NICs, one is connected to ISP router which we can't access, and one nic is connected to our private LAN. I use CentOS Linux 6.5 x64 to act as router. I added in iptables firewall to forward all traffic from eth0 to eth1 (from internal to public) and allowed traffic to leave server. All output traffic is nated.

Problem is on the other site. I'm not a network engineer but only with some knowledge in networking and formal IT education at the firm. My problem is I can't ping anything on the Internet while our VPS can. On that same server only port 80 and 22 are opened. People who setup proxy can connect to outside world but can't ping, can't use other networking software.

I have some questions:

How I can see my private LAN from ISP network, I will need to setup VPN in the short time ?
Is possible to avoid proxy and just with firewall NAT get data from the net back to the hosts in the private LAN ?

I am afraid to mess with ISP server because they administrate that server, we are and I really won't to understand how configure a network.

Thanks for reading and suggestions.

Last edited by solaris_user; 07-16-2014 at 07:26 PM..
 

8 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

Linux for an internet server to an ISP

I just moved away from a T3 line back to a dial up I just wanted to know would a P200 with 64meg and a 4 gig hard drive be ok for a linux server for an additional 3 pcs all running win98. I will be dialing into an isp using a 56k v90 modem. Any support or help will be great. (3 Replies)
Discussion started by: izrailov
3 Replies

2. UNIX for Dummies Questions & Answers

Cannot connect to my ISP

I'm totally frustrated, my administrator has left the state and me high and dry! My modem cannot connect to my ISP all it does is start to ping and the a high pitched squeal for about a minute. I have logged on as the "root" in hope to get into my /etc/ppp/ppp.conf file however I get a... (8 Replies)
Discussion started by: coolteach
8 Replies

3. IP Networking

Routing Network Traffic With Mandrake

I am running Mandrake 8.0 (KDE ver 2.1.1) on a machine with 2 NICs. This is a college project. I am attempting to configure this machine as a firewall, and to pass packets from one network to another. Eth0 is on my external network. Eth1 is on my internal network. I set the gateway in "netconf"... (1 Reply)
Discussion started by: Deuce
1 Replies

4. UNIX for Dummies Questions & Answers

schedule dial-out different ISP's

Hi, I'm running user ppp on FreeBSD. I have an internet account which gives me the oppertunity to login for free (say €25 a month :)) during specific hours. Outside these hours I pay the normal fee. I also have another ISP which gives me the oppertunity to log in for a reduced fee all times. ... (2 Replies)
Discussion started by: Hansaplast
2 Replies

5. IP Networking

2 ip from one subnet my isp

Hi. my english is not so good. sorry. i have some problem. My isp give me second ip from subnet. One network is working, but secong don't. fxp0 - my network dc0 - network isp (that working) re0 - network isp (don't working) i try use ng_one2many, but it's don't working ngctl mkpeer... (0 Replies)
Discussion started by: kil
0 Replies

6. IP Networking

Routing traffic problem between 3G and Office Lan Network

Hi, I would like to ask some networking solution regarding my work LAN and 3G usb network problem. I want to route my internet traffic to the 3G network and sometimes connect to some of my work network for ssh to configure some workstation or print something. Currently my problem is i can't... (0 Replies)
Discussion started by: jao_madn
0 Replies

7. Solaris

Traffic routing through wrong interface

Solaris-9 server is having one primary IP 10.41.161.14 on qfe0 and 10.41.116.0 on qfe3:1. Traffic is going through virtual interface instead of physical interface. How should I force traffic to go with primary interface. root@smtsrvn01:/# netstat -nr Routing Table: IPv4 Destination ... (2 Replies)
Discussion started by: solaris_1977
2 Replies

8. IP Networking

Multiple isp physical connection

Hello all my friends see picture to understand my problem http://www.imageurlhost.com/images/8mf8ni4btu6r4qy1rp9_Networking-photo.png i want to know that how my company can connect multiple isp via switch and output from switch is directly connected to linux firewall. Any help Thanks (1 Reply)
Discussion started by: rink
1 Replies
WVDIAL.CONF(5)							File Formats Manual						    WVDIAL.CONF(5)

NAME
wvdial.conf - wvdial configuration file DESCRIPTION
When wvdial starts, it first loads its configuration from /etc/wvdial.conf, which contains basic information about the modem port, speed, and init string, along with information about your Internet Service Provider (ISP), such as the phone number, your username, and your pass- word. The configuration file /etc/wvdial.conf is in Windows "ini" file format, with sections named in square brackets and a number of variable = value pairs within each section. Here is a sample configuration file: [Dialer Defaults] Modem = /dev/ttyS2 Baud = 57600 Init = ATZ Init2 = AT S11=50 Phone = 555-4242 Username = apenwarr Password = my-password [Dialer phone2] Phone = 555-4243 [Dialer shh] Init3 = ATM0 [Dialer pulse] Dial Command = ATDP The sample configuration file above contains all of the options necessary to run the two sample command lines given above. Here is a com- plete list of settings that wvdial understands: Modem The location of the device that wvdial should use as your modem. The default is /dev/modem. Baud The speed at which wvdial will communicate with your modem. The default is 57600 baud. Init1 ... Init9 wvdial can use up to nine initialization strings to set up your modem. Before dialing, these strings are sent to the modem in numerical order. These are particularly useful when specifying multiple sections. See above for an example that uses Init3 to turn the modem's speaker off. The default is "ATZ" for Init1. Phone The phone number you want wvdial to dial. You can add up to 9 other phone numbers that wvdial will dial in order, by adding: Phone1 Phone2 Phone3 Phone4 Phone5 Phone6 Phone7 Phone8 Phone9 Dial Prefix wvdial will insert this string after the dial command and before the phone number. For example, to disable call waiting (in North America, anyway) set this to "*70,". Dial Command wvdial will use this string to tell the modem to dial. The default is "ATDT". Username You must set this to the username you use at your ISP. Login Prompt If your ISP has an unusual login procedure that wvdial is unable to figure out, you can use this option to specify a login prompt. When this prompt is received from your ISP, wvdial will send the Login string. Password You must set this to the password you use at your ISP. Ask Password By setting this option wvdial will prompt for your password on every dialin. Thus you don't have to save your password in /etc/wvdial.conf. (Option added by SuSE.) Password Prompt If your ISP has an unusual login procedure that wvdial is unable to figure out, you can use this option to specify a password prompt. When this prompt is received from you ISP, wvdial will send the Password string. PPPD Path If your system has pppd somewhere other than /usr/sbin/pppd, you will need to set this option. Auto DNS Try to get the Domain Nameserver (DNS) from the provider. This option is "on" by default. (Option added by SuSE.) Check DNS Check the Domain Nameserver (DNS) after the connection has been set up. This option is "on" by default. (Option added by SuSE.) DNS Test1 First DNS lookup for DNS check. (Option added by SuSE.) DNS Test2 Second DNS lookup for DNS check. (Option added by SuSE.) Check Def Route Check the default route after the connection has been set up. This option is "on" by default. (Option added by SuSE.) Force Address This option only applies if you have a static IP address at your ISP, and even then you probably don't need it. Some ISP's don't send the IP address as part of the PPP negotiation. This option forces pppd to use the address you give it. Remote Name If your ISP uses PAP or CHAP authentication, you might need to change this to your ISP's authentication name. In most cases, how- ever, it's safe to use the default value, "*". Carrier Check wvdial checks your modem during the connection process to ensure that it is actually online. If you have a weird modem that insists its carrier line is always down, you can disable the carrier check by setting this option to "no". Stupid Mode When wvdial is in Stupid Mode, it does not attempt to interpret any prompts from the terminal server. It starts pppd immediately after the modem connects. Apparently there are ISP's that actually give you a login prompt, but work only if you start PPP, rather than logging in. Go figure. Stupid Mode is (naturally) disabled by default. New PPPD You need this option if you have pppd version 2.3.0 or newer, to make wvdial create the file /etc/ppp/peers/wvdial. This option is enabled by default, thus if you have older pppd you need to set it to `no' (or upgrade pppd). Default Reply When wvdial detects a prompt, and it hasn't seen any clues that indicate what it should send as a response to the prompt, it defaults to sending "ppp". Sometimes this is inadequate. Use this option to override wvdial's default prompt response. Auto Reconnect If enabled, wvdial will attempt to automatically reestablish a connection if you are randomly disconnected by the other side. This option is "on" by default. Idle Seconds Set the hangup timeout in seconds. If there is inactivity for the given time the connection is shut down. A hangup timeout of 0 disables this feature. Abort on Busy If enabled, wvdial will not retry the connection if the modem says that the line is busy. This option is "off" by default. Abort on No Dialtone If enabled, wvdial will not retry the connection if the modem says that there is no dialtone. This option is "on" by default. Dial Attempts If value is set, wvdial will quit after that many tries .If set to 0, wvdial will happily keep dialling forever. Dial Timeout The maximum time in seconds that wvdial will wait for a connection to be made. Default value is 60 seconds. The wvdialconf(1) program can be used to detect your modem and fill in the Modem, Baud, and Init/Init2 options automatically. AUTHORS
Dave Coombs and Avery Pennarun for Net Integration Technologies Inc. Great contributions have been made by many people, including SuSE and RedHat. Thanks guys! SEE ALSO
wvdial(1), wvdialconf(1), pppd(8). WvDial December 2005 WVDIAL.CONF(5)
All times are GMT -4. The time now is 12:22 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy