How to expose a box on the 63.x subnet with a route to the 192?

 
Thread Tools Search this Thread
Operating Systems Linux Red Hat How to expose a box on the 63.x subnet with a route to the 192?
# 1  
Old 05-23-2011
How to expose a box on the 63.x subnet with a route to the 192?

Hi all,

I'm trying to expose a CentOS box on the 63.x subnet with a route to the 192 as our firewall doesn't allow a VPN. Would someone please let me know how I can do this?

Thanks
Login or Register to Ask a Question

Previous Thread | Next Thread

7 More Discussions You Might Find Interesting

1. Linux

Add two different subnet public IPs to single NIC or two different NIC on same box

Hello Admins, My ask is how can I add two different subnet IPs to same box with two different gateways? The issue is I can connect to the box when I am on ethernet LAN, but I am not able to connect to the same IP when I am on wifi. The server is RHEL 7 VM on vmware. How can I get connected... (4 Replies)
Discussion started by: snchaudhari2
4 Replies

2. Cybersecurity

DSL Modem 192.168.a.b botnet member me?

I need a hint or a clue. Some four weeks or even more I try to change the password for my wifi access of the DSL Router without success. I access 192.168.x.x and filling in username as well as the password I am stuck. Literally nothing happens and the support line tells me that this is not... (2 Replies)
Discussion started by: 1in10
2 Replies

3. IP Networking

Problem with linux-box and subnet

I wish to have the folowing setup on my network: --- Internet -----eth1-| Linux box |- eth2 --- IP Ranges 192.168.100. 0-255 and 192.168.101. 0-255 ... (0 Replies)
Discussion started by: rbuelund
0 Replies

4. IP Networking

Migrating existing Subnet to a new subnet and changing ip addresses in UNIX

Hi, My project needs to migrate the existing Subnet (255.255.255.0) to a new subnet and change the ipaddresses (currently C class). How can I do that. I need some information. John (0 Replies)
Discussion started by: johnmarsh
0 Replies

5. IP Networking

publishing 192.168 address internally

OK this is what I want to do: On server1 I want to type <ping server2> and be able to get: pinging 192.168.0.12 ...... etc. and by server2, I mean one-word, not server2.example.com I know if I add the addresses to /etc/hosts I can achieve this, but I would like to not have to update all... (2 Replies)
Discussion started by: vertical98
2 Replies

6. Solaris

Setting up route on subnet

I was told this worked on an HP system (same network as the sun server I am trying to set this up on)> but I get "netmask: bad value"2when I try it on the Sun: route add net 199.42.23.192 netmask 255.255.255.192 204.104.63.30 1 I've tried many different iterations (leaving out netmask, only... (2 Replies)
Discussion started by: nhmeanie
2 Replies

7. IP Networking

add route to a subnet - Solaris 2.6

WE are running Unix - Solaris 2.6, we create a subnet. In the windows enviroment we are able to add a static route by using route add -p 172.16.10.0 mask 255.255.255.0 172.16.17.224, but when we add the route in Solaris as route add -net 172.16.10.0 255.255.255.0 172.16.17.224, we receive an... (5 Replies)
Discussion started by: cassy
5 Replies
Login or Register to Ask a Question
Route classifier in tc(8)					       Linux						 Route classifier in tc(8)

NAME
route - route traffic control filter SYNOPSIS
tc filter ... route [ from REALM | fromif TAG ] [ to REALM ] [ classid CLASSID ] [ action ACTION_SPEC ] DESCRIPTION
Match packets based on routing table entries. This filter centers around the possibility to assign a realm to routing table entries. For any packet to be classified by this filter, a routing table lookup is performed and the returned realm is used to decide on whether the packet is a match or not. OPTIONS
action ACTION_SPEC Apply an action from the generic actions framework on matching packets. classid CLASSID Push matching packets into the class identified by CLASSID. from REALM fromif TAG Perform source route lookups. TAG is the name of an interface which must be present on the system at the time of tc invocation. to REALM Match if normal (i.e., destination) routing returns the given REALM. EXAMPLES
Consider the subnet 192.168.2.0/24 being attached to eth0: ip route add 192.168.2.0/24 dev eth0 realm 2 The following route filter will then match packets from that subnet: tc filter add ... route from 2 classid 1:2 and pass packets on to class 1:2. NOTES
Due to implementation details, realm values must be in a range from 0 to 255, inclusive. Alternatively, a verbose name defined in /etc/iproute2/rt_realms may be given instead. SEE ALSO
tc(8), ip-route(8) iproute2 21 Oct 2015 Route classifier in tc(8)