This discussion has been locked.

You can no longer post new replies to this discussion. If you have a question you can start a new discussion

RED DHCP issues - remote network

I'm trying to setup the Split Tunnel configuration, using the RED Initial Setup Guide from the kb (https://support.astaro.com/support/index.php/RED_Initial_Setup).

As part of this setup, a static route must be set to forward all traffic to the connected LAN port of the RED device. This is where the problem seems to arise. None of the 4 LAN ports on the RED device make a DHCP request, so they don't get a LAN IP that I can use to setup a standard static gateway route. The WAN port does make a request and gets a local LAN ip just fine.

So, what's the trick here? I need something to forward the traffic to on the remote network router.

There may also be NAT issues at work here, as there are three separate subnets involved. The ASG the RED device is registered to is at work and the work LAN is 192.168.2.0, the RED virtual interface network (RVIN) on the ASG is 192.168.100.0, and the home network the RED device is physically at is 192.168.1.0 (using Astaro at home as well). I need to be able to access network resources at work from home through the RED. If I connect a PC at home directly to a RED LAN port, it is given an IP from the DHCP server setup on the ASG at work that's assigned to the RVIN interface and everything works.

If somebody has gotten the split tunnel setup described in the guide to work, please post the steps you had to take to finagle it. [:)]

This thread was automatically locked due to age.

Parents

0 Scott_Klassen over 14 years ago

Thanks for the response.

I knew about the RED Lan port, RED WAN port, and PC all plugged into the switch. I only tried direct connecting a PC to the RED LAN port to rule out any issue with the RED device.

Interesting idea about routing by the 192.168.100.1, but I don't quite see how that would work, since it's not being broadcast into the home LAN, so no arp table entries for the switch and still no way to define the RED LAN port being used on the router (astaro) for building a route table entry. I think that this weekend, I might hook a passive tap between the LAN port of the RED and the switch and run the output through wireshark to see exactly what's passing through.

I think that there's something missing in the steps documented. Maybe a skipped step, a wrong step, or even the doc was put together using a beta version that had more robust functionality.

__________________
ACE v8/SCA v9.3

...still have a v5 install disk in a box somewhere.

http://xkcd.com
http://www.tedgoff.com/mb
http://www.projectcartoon.com/cartoon/1
Cancel
Vote Up 0 Vote Down

Cancel

Reply

0 Scott_Klassen over 14 years ago

Thanks for the response.

I knew about the RED Lan port, RED WAN port, and PC all plugged into the switch. I only tried direct connecting a PC to the RED LAN port to rule out any issue with the RED device.

Interesting idea about routing by the 192.168.100.1, but I don't quite see how that would work, since it's not being broadcast into the home LAN, so no arp table entries for the switch and still no way to define the RED LAN port being used on the router (astaro) for building a route table entry. I think that this weekend, I might hook a passive tap between the LAN port of the RED and the switch and run the output through wireshark to see exactly what's passing through.

I think that there's something missing in the steps documented. Maybe a skipped step, a wrong step, or even the doc was put together using a beta version that had more robust functionality.

__________________
ACE v8/SCA v9.3

...still have a v5 install disk in a box somewhere.

http://xkcd.com
http://www.tedgoff.com/mb
http://www.projectcartoon.com/cartoon/1
Cancel
Vote Up 0 Vote Down

Cancel

Children

No Data