[deleted]
Is it possible for clients to access a non-routing subnet on the server side.
The server (Windows 7) has an IP is the WAN let's say 10.1.1.2 which is accessable from clients.
The server can also access a 192.168.1.x non-routed subnet if I added a second IP to the server.
I could add IP 192.168.1.2 to the server if needed (a second IP) which I do for those at the server site who need access to the 192.168.1.x subnet.
The 10.1.1.x and 192.168.1.x subnets are on the same physical subnet (VLAN) on the server side.
I want to give clients an IP in the 192.168.1.x subnet to access PLCs (ethernet controllers) that do not support routing on the server side.
Do I need to do bridging?
Without bridging are the clients basically just talking to the server and each other (isolated)?
I will probably setup a raspberry pi on server side if I can get this working.
Thanks.
[deleted]
I think I can do this. Use port forwarding to forward port 1194 from 10.1.1.x network to the 192.168.x.x subnet.
Maybe use both IPs on a linux box and redirect the port in iptables or something.
Should work.
[deleted]
Got it working. I ending up bridging the tap device to the nic and then creating two IPs on the bridge interface.
So my bridge-start ends in these steps:
ifconfig $br 192.168.1.2 netmask 255.255.255.0 broadcast 192.168.1.255
ifconfig $br:0 10.1.1.9 netmask 255.255.255.0 broadcast 10.1.1.255
route add default gw 10.1.1.1
The :0 is an alias for assigning multiple IPs.
