04-01-2009
I hope it's not too late. For the first question - you should be able to ping the router. Then, you will pass the traffic the same you pass the traffic now, towards your main router. But, if you want only those four machines to route the data there, just create rules in respective firewall. If you have to kill the existing tunnel, you have to think of another way - new VLAN or new tunnel. I didn't understand, however, the big picture - why MPLS in the middle of the normal LAN ? You need to use MPLS paths and respective protocols to manage the traffic from the MPLS router.
8 More Discussions You Might Find Interesting
1. IP Networking
I have SCO Unix. I have 2 routers. as it is now, when someone telnets to UNIX and goes through router #1 everything is fine. The users who go through router #2 can not connect at all. I talked to CISCO and they said I need to set up a second Gateway on UNIX. They said what is happening is that... (1 Reply)
Discussion started by: john fli
1 Replies
2. IP Networking
ok i configured my gateway and IP address(es) using ifconfig and route.. but how can i bind unique IPs to users ? (im using FreeBSD 4.2 RELEASE #3) (9 Replies)
Discussion started by: DevilGREEN
9 Replies
3. UNIX for Advanced & Expert Users
Hi,
in which file and how shuold be decalred a gateway and its IP adresse ?
Where and how add a gateway ?
Many thanks before. (4 Replies)
Discussion started by: big123456
4 Replies
4. AIX
I know that IBM's official stance is that NIM does not work on etherchannel environment, but has anyone able to get around it?
I'm working on a p5-590 LPAR system, and the NIM master and clients are all on the same frame.
Any help is appreciated. (1 Reply)
Discussion started by: pdtak
1 Replies
5. UNIX for Advanced & Expert Users
hello;
i m trying to install mpls linux in fedora 5. so i recompiled the kernel. the compilation is successful.the commandes mpls nhlfe..., mpls ilm.., etc are known so mpls is working well.
but when i try the commande like
#mpl mhlfe add key 0instructions push gen 1000 nexthop eth0 ipv4... (1 Reply)
Discussion started by: jalil smail
1 Replies
6. AIX
Hi All,
I know there is a way to do this in routers. The question is whether it is posisble to do this in AIX.
For our Web Focus ODBC connection to the Disaster Recovery servers, we want to restrict the access to the ODBC ports so that only the IP address of the Web Focus server can get to... (1 Reply)
Discussion started by: strunz
1 Replies
7. Linux
Dear Sir
I am a newbie in the world of IP telephony. I have been working with Asterisk PBX (SIP) and Cisco Call Manager (MGCP) but now I am learning on how to work GNUGK for H.323 Gatekeeper.
I am having a problem, configuring static call routing on GNUGK
in the section
... (0 Replies)
Discussion started by: mfondoum
0 Replies
8. IP Networking
Hey there,
I am a network administrator of a student dorm. Me and my team (we do this in our spare time) have the task to upgrade and rebuild our dorm intern network. But unfortunately we don't have that much experience with server setup and ip-routing and stuff. So here is the topic I want to... (8 Replies)
Discussion started by: mrgruen
8 Replies
LEARN ABOUT DEBIAN
if_faith
FAITH(4) BSD Kernel Interfaces Manual FAITH(4)
NAME
faith -- IPv6-to-IPv4 TCP relay capturing interface
SYNOPSIS
device faith
DESCRIPTION
The faith interface captures IPv6 TCP traffic, for implementing userland IPv6-to-IPv4 TCP relay like faithd(8).
Each faith interface is created at runtime using interface cloning. This is most easily done with the ifconfig(8) create command or using
the cloned_interfaces variable in rc.conf(5).
Special action will be taken when IPv6 TCP traffic is seen on a router, and the routing table suggests to route it to the faith interface.
In this case, the packet will be accepted by the router, regardless of the list of IPv6 interface addresses assigned to the router. The
packet will be captured by an IPv6 TCP socket, if it has the IN6P_FAITH flag turned on and matching address/port pairs. As a result, faith
will let you capture IPv6 TCP traffic to some specific destination addresses. Userland programs, such as faithd(8) can use this behavior to
relay IPv6 TCP traffic to IPv4 TCP traffic. The program can accept some specific IPv6 TCP traffic, perform getsockname(2) to get the IPv6
destination address specified by the client, and perform application-specific address mapping to relay IPv6 TCP to IPv4 TCP.
The IN6P_FAITH flag on a IPv6 TCP socket can be set by using setsockopt(2), with level IPPROTO_IPV6 and optname IPv6_FAITH.
To handle error reports by ICMPv6, some ICMPv6 packets routed to an faith interface will be delivered to IPv6 TCP, as well.
To understand how faith can be used, take a look at the source code of faithd(8).
As the faith interface implements potentially dangerous operations, great care must be taken when configuring it. To avoid possible misuse,
the sysctl(8) variable net.inet6.ip6.keepfaith must be set to 1 prior to using the interface. When net.inet6.ip6.keepfaith is 0, no packets
will be captured by the faith interface.
The faith interface is intended to be used on routers, not on hosts.
SEE ALSO
inet(4), inet6(4), faithd(8)
Jun-ichiro itojun Hagino and Kazu Yamamoto, An IPv6-to-IPv4 transport relay translator, RFC3142.
HISTORY
The FAITH IPv6-to-IPv4 TCP relay translator first appeared in the WIDE hydrangea IPv6 stack.
BSD
April 10, 1999 BSD