Closed. This question is off-topic. It is not currently accepting answers.
Want to improve this question? Update the question so it's on-topic for Stack Overflow.
Closed 10 years ago.
Improve this question
I am running linux machine between two IP Phone with Two NIC card's. all of the traffic passthroug between eth0 and eth1 should move through TCP/IP stack.currently,IP-forwarding is enabled in linux and traffic route directly at Kernel level. If I am doing port forwarding using IPtables, I can get the traffic in TCP/IP stack but I dont want to perform port forwarding. Every time traffic is having different port, its difficult to map the port again with its original port.
Is there any other mechanism, I can get every packet in tcp/IP stack without port forwarding either using some routing or creating virtual interface/loopback interface?
Related
Closed. This question is off-topic. It is not currently accepting answers.
Want to improve this question? Update the question so it's on-topic for Stack Overflow.
Closed 9 years ago.
Improve this question
I have 2 computers with debian installed on both. One computer has no sceen or othe prepherels accept ethernet port. I've connected them through a lan cable and shared the intenet to be used by the computer that has no sceen. However, I'd like to ssh this computet but I don't know its ip address. BtW, I dont have a router.
Use Angry IP Scanner. It will give you the list of devices in the network.
Closed. This question is off-topic. It is not currently accepting answers.
Want to improve this question? Update the question so it's on-topic for Stack Overflow.
Closed 9 years ago.
Improve this question
I am using RHEL 6.3 (2.6.x kernel). I have tcp based client server applications. I noticed that when i run them on the same host, the throughput is approx the same, irrespective whether server binds to loopback or local IP assigned to NIC.
What is the reason behind it? My understanding is that loopback is software based routing, where as when local IP assigned to NIC is involved, the hardware is involved in the data path. Is that true?
The hardware does not get involved.
As soon as the routing function knows that the destination address is local, the packet is switched to ingress path. Which is incidentally why sniffers can't capture such packets, because that hook happens to be after the point of this decision.
Closed. This question is off-topic. It is not currently accepting answers.
Want to improve this question? Update the question so it's on-topic for Stack Overflow.
Closed 10 years ago.
Improve this question
I have an Ooma VoIP device on my home network. I do not want it to act as the router to the internet as I already have a dual-nic linux box that is working just fine. I do want to start using a priority qdisc to make all traffic from the ooma device as high priority, torrents as low priority, and everything else as normal priority. I've tried a variety of settings and I must not be doing it quite right as everything I try dumps nearly all packets in the middle priority class. On my linux box (CentOS 6) eth1 is the internal network and eth0 goes to the internet.
Thanks!
Closed. This question is off-topic. It is not currently accepting answers.
Want to improve this question? Update the question so it's on-topic for Stack Overflow.
Closed 10 years ago.
Improve this question
AnalogX makes a handy useful Windows utility named Portmapper. It listens on any ports you like and forwards traffic to another IP address. So you can open a range of ports in your router, all mapped to one machine. That machine then forwards each specific port to any address you like within the LAN.
This is a good solution for routers with a limited number of NAT entries available. Just point a range to a single PC and let it do the rest. It can forward port 80 traffic to 192.168.1.101, port 5900 to 192.168.1.102, and port 5901 to 192.168.1.103:5900, etc.
I'm looking for a linux-based replacement. Either a program where I create a config file detailing the port numbers and IPs to forward, or a strategy to use a built-in solution like iptables. Any suggestions on how to do this?
Well you can do that natively in Linux with iptables:
http://www.debuntu.org/how-to-redirecting-network-traffic-a-new-ip-using-iptables
http://ramblings.narrabilis.com/ip-forward-using-iptables-port-and-host-redirect
http://www.revsys.com/writings/quicktips/nat.html
Closed. This question is off-topic. It is not currently accepting answers.
Want to improve this question? Update the question so it's on-topic for Stack Overflow.
Closed 10 years ago.
Improve this question
Can somebody tell me what are the ways of routing packets in a linux system. I have an external and internal network interfaces on my linux system. I want to forward packets arriving at my external network to an internal network.
I do not have iptables. What are the other ways to this? What commands are offered by native linux. Should Netfilter always be enabled for this? My kernel does not come with Netfilter.
So please suggest.
Thanks in advance
Assuming you're talking about real routing, and not any form of Network Address Translation (NAT), you just need to enable IP forwarding, and put the relevant routes in your routing table:
echo 1 > /proc/sys/net/ipv4/ip_forward
Configuring NAT does require iptables.