Sponsored Content
Operating Systems Linux Lan card not reaching Gateway Post 302679933 by dextergenious on Wednesday 1st of August 2012 03:46:51 AM
Old 08-01-2012
Linux as router

Hi,

I have two subnets (172.16.18.0, 192.168.10.0) and a RH linux box. I know linux can act as router, but specifically want to ask if this acts as a router without any route addition on all nodes of two subnets. I mean , I need Not to add anything at each of the subnet nodes (obviously gateway is there) but only add routes in the linux box. I have checked enabling ip forwarding in files /etc/syscntl.conf and /proc/sys/net/ipv4/ip_forward. But that donot make any difference . I am unable to ping the node of 2nd subnet with the node of 1st subnet. My linux box has two nic's with 172.16.18.2 and 192.168.10.2

172.16.18.3 (node s1) ----> 172.16.18.2, 192.168.10.2 <---- 192.168.10.3 (node s2)

Firstly, is it achievable that by only adding routes on linux box I can make two subnets communicate. If yes then what route I need to put on this. (I donot want to add any route on the subnet nodes except the subnet gateway - 172.16.18.2 and 192.168.10.2)


Thanks in advance ,


Dexter
 

10 More Discussions You Might Find Interesting

1. UNIX for Advanced & Expert Users

LAN Card Problem !

The Lan card in one of our UIII WS's seem doesn't work,so with ping command i can not see any of the machines in LAN and with some other tests i'm sure it's not OK. I tried to use the second card on PCI port ,but the replaced card was one of the ordinary card for PC's ...by the way after... (1 Reply)
Discussion started by: nikk
1 Replies

2. Cybersecurity

lan card autonegotiation?

what is lan card autonegotiation ? how to enable and disable this feature? (2 Replies)
Discussion started by: nabil_boussetta
2 Replies

3. SCO

LAN card problem

Dear all Im facing one problem in SCO 5.0.5 , its that in the server there are three LAN cards INTEL PRO 100 series but when we configure all the three cards then LAN stops working . self ping is possible but no one can ping the server. If we remove driver of any one card LAN starts working. Is... (1 Reply)
Discussion started by: ccvyas
1 Replies

4. Solaris

Does x86 solaris 9 support PCI RealTek Lan Card

Hi, i have a RealTek Lan Card on my machine. Does Solaris 9 supports this lan card . Thank You, Shafi (3 Replies)
Discussion started by: sol8admin
3 Replies

5. SCO

lan card not detecting

hi all i have installed SCO 5.0.5 on a "Netfinity 5000" IBM server. But the OS is not detecting the lan card. how can i detect it.... help and thanks in advance . bidhayak (3 Replies)
Discussion started by: bidhayakm
3 Replies

6. Programming

LAN card status Information

Please tell me API in Solaris / Linux / UNIX to get status information of LAN card. (1 Reply)
Discussion started by: mansoorulhaq
1 Replies

7. Linux

How to check the LAN card?

Hi. I have a lan card installed on my server. I want to check the duplex speed of it. How can I check it? Help is appreciated. Thank you. (3 Replies)
Discussion started by: Amol21
3 Replies

8. Solaris

Can't ping new PCI LAN card x4270_m2

Hi, I've recently moved my pci LAN card from Slot2 Slot5 on my sun x4270_m2 server (solaris 10). I've done the touch / reconfigure and devfsadm, however my issue is that im able to configure the e1000g7 port with an ip address (192.168.0.1) but if i plug my laptop (set with static ip... (7 Replies)
Discussion started by: kerrygold
7 Replies

9. Red Hat

PC cannot reach two lan card Linux box

we have red hat 6 linux box There are two lan card one lan card eth0 have ip 10.82.190.31/24 GW 10.82.190.254 2th lan card eth1 have ip 10.82.188.33/24 GW 10.82.188.254 I have below route ... I use two route table root@xxx# netstat -rn Kernel IP routing table Destination Gateway ... (5 Replies)
Discussion started by: chuikingman
5 Replies

10. UNIX for Beginners Questions & Answers

Inconsistency between RedHat 6.5 global gateway and single gateway leads to loss of default gateway

Dear friends I use RedHat 6.5, which sets the gateway in the configuration file / etc / sysconfig / network as GATEWAY = 192.168.1.26, and the gateway in the configuration file / etc / sysconfig / network-scripts / ifcfg-eth11 as GATEWAY = 192.168.1.256. The two gateways are different.... (6 Replies)
Discussion started by: tanpeng
6 Replies
PPTPD.CONF(5)							File Formats Manual						     PPTPD.CONF(5)

NAME
pptpd.conf - PPTP VPN daemon configuration DESCRIPTION
pptpd(8) reads options from this file, usually /etc/pptpd.conf. Most options can be overridden by the command line. The local and remote IP addresses for clients must come from the configuration file or from pppd(8) configuration files. OPTIONS
option option-file the name of an option file to be passed to pppd(8) in place of the default /etc/ppp/options so that PPTP specific options can be given. Equivalent to the command line --option option. stimeout seconds number of seconds to wait for a PPTP packet before forking the pptpctrl(8) program to handle the client. The default is 10 seconds. This is a denial of service protection feature. Equivalent to the command line --stimeout option. debug turns on debugging mode, sending debugging information to syslog(3). Has no effect on pppd(8) debugging. Equivalent to the command line --debug option. bcrelay internal-interface turns on broadcast relay mode, sending all broadcasts received on the server's internal interface to the clients. Equivalent to the command line --bcrelay option. connections n limits the number of client connections that may be accepted. If pptpd is allocating IP addresses (e.g. delegate is not used) then the number of connections is also limited by the remoteip option. The default is 100. delegate delegates the allocation of client IP addresses to pppd(8). Without this option, which is the default, pptpd manages the list of IP addresses for clients and passes the next free address to pppd. With this option, pptpd does not pass an address, and so pppd may use radius or chap-secrets to allocate an address. localip ip-specification one or many IP addresses to be used at the local end of the tunnelled PPP links between the server and the client. If one address only is given, this address is used for all clients. Otherwise, one address per client must be given, and if there are no free addresses then any new clients will be refused. localip will be ignored if the delegate option is used. remoteip ip-specification a list of IP addresses to assign to remote PPTP clients. Each connected client must have a different address, so there must be at least as many addresses as you have simultaneous clients, and preferably some spare, since you cannot change this list without restarting pptpd. A warning will be sent to syslog(3) when the IP address pool is exhausted. remoteip will be ignored if the dele- gate option is used. noipparam by default, the original client IP address is given to ip-up scripts using the pppd(8) option ipparam. The noipparam option pre- vents this. Equivalent to the command line --noipparam option. listen ip-address the local interface IP address to listen on for incoming PPTP connections (TCP port 1723). Equivalent to the command line --listen option. pidfile pid-file specifies an alternate location to store the process ID file (default /var/run/pptpd.pid). Equivalent to the command line --pidfile option. speed speed specifies a speed (in bits per second) to pass to the PPP daemon as the interface speed for the tty/pty pair. This is ignored by some PPP daemons, such as Linux's pppd(8). The default is 115200 bytes per second, which some implementations interpret as meaning "no limit". Equivalent to the command line --speed option. NOTES
An ip-specification above (for the localip and remoteip tags) may be a list of IP addresses (for example 192.168.0.2,192.168.0.3), a range (for example 192.168.0.1-254 or 192.168.0-255.2) or some combination (for example 192.168.0.2,192.168.0.5-8). For some valid pairs might be (depending on use of the VPN): localip 192.168.0.1 remoteip 192.168.0.2-254 or localip 192.168.1.2-254 remoteip 192.168.0.2-254 ROUTING CHECKLIST - PROXYARP Allocate a section of your LAN addresses for use by clients. In /etc/ppp/options.pptpd. set the proxyarp option. In pptpd.conf do not set localip option, but set remoteip to the allocated address range. Enable kernel forwarding of packets, (e.g. using /proc/sys/net/ipv4/ip_forward ). The server will advertise the clients to the LAN using ARP, providing it's own ethernet address. bcrelay(8) should not be required. ROUTING CHECKLIST - FORWARDING Allocate a subnet for the clients that is routable from your LAN, but is not part of your LAN. In pptpd.conf set localip to a single address or range in the allocated subnet, set remoteip to a range in the allocated subnet. Enable kernel forwarding of packets, (e.g. using /proc/sys/net/ipv4/ip_forward ). The LAN must have a route to the clients using the server as gateway. The server will forward the packets unchanged between the clients and the LAN. bcrelay(8) will be required to support broadcast protocols such as NETBIOS. ROUTING CHECKLIST - MASQUERADE Allocate a subnet for the clients that is not routable from your LAN, and not otherwise routable from the server (e.g. 10.0.0.0/24). Set localip to a single address in the subnet (e.g. 10.0.0.1), set remoteip to a range for the rest of the subnet, (e.g. 10.0.0.2-200). Enable kernel forwarding of packets, (e.g. using /proc/sys/net/ipv4/ip_forward ). Enable masquerading on eth0 (e.g. iptables -t nat -A POSTROUTING -o eth0 -j MASQUERADE ). The server will translate the packets between the clients and the LAN. The clients will appear to the LAN as having the address corre- sponding to the server. The LAN need not have an explicit route to the clients. bcrelay(8) will be required to support broadcast proto- cols such as NETBIOS. FIREWALL RULES
pptpd(8) accepts control connections on TCP port 1723, and then uses GRE (protocol 47) to exchange data packets. Add these rules to your iptables(8) configuration, or use them as the basis for your own rules: iptables --append INPUT --protocol 47 --jump ACCEPT iptables --append INPUT --protocol tcp --match tcp --destination-port 1723 --jump ACCEPT SEE ALSO
pppd(8), pptpd(8), pptpd.conf(5). 29 December 2005 PPTPD.CONF(5)
All times are GMT -4. The time now is 12:32 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy