route

  1. N

    cannot setup routing within connected containers

    I have two docker networks: docker network create --attachable --internal --subnet 10.241.32.0/24 nw_01_02 docker network create --attachable --internal --subnet 10.241.33.0/24 nw_02_03 I also have three docker containers: node01 10.241.32.12 on nw_01_02 node02 10.241.32.11 on 10.241.33.11...
  2. R

    Routing from unique IP address to two separate devices

    Hello everyone, recently I started working with some PLCs who have Linux installed as an operating system. In general, I managed to solve the request from our customer, but I am looking for a way to improve things. Our customer have a PC with an IP address of 192.168.100.9/16 - on that PC a...
  3. Nemesis

    (Solved) forward port to another computer?

    I've got one Linux server (Ubuntu) that has a public IP. I want by connecting to it, on a specified port, be routed to another Linux computer on the same local network. is this possible? found this online; iptables -t nat -A PREROUTING -p tcp --dport 49620 -j DNAT --to-destination...
  4. E

    Ping through 2 Namespaces in same Subnet

    Hi @ all, i´ve a question. I have the following setup, but cannot ping from ETHA to ETHB. If i check Namespace 1, i have the following configuration: root@default: ip netns exec ns1 ip a 1: lo: <LOOPBACK> mtu 65536 qdisc noop state DOWN group default link/loopback 00:00:00:00:00:00 brd...
Top