Hey all there,
I'm facing some problem with my ASG120 V8 and RED device at the moment and my CEOs get more impatient so a solution has to be found. Unfortuantelly I'm not able to do this on my own so I have to ask all of you.
We do have two 2MBit PPPoE SDSL connections. Both with an explicit external address. At site1 there's the ASG120 behind the modem for the dial-up, at site2 there's Netgear RP614. The internet connection at site1 is working pretty fine so I'll tell you the facts of site2.
Short description what I've done:
I set up the RED with the Helper Tool on the ASG120. I double-checked the settings I made so they should be right.
At site2 there I connected the Netgear Internetport into our modem. I tested its settings with my laptop and the internet connection has been established and working.
Next I plugged in the RED device at one of the LAN ports of the Netgear router. On the RED device I choose the WAN-port.
The settings in the Netgear router has been set to DHCP mode so every device should get an IP from there.
I didn't plug in any other device and I'm 100% sure that there is no other DHCP server running.
Unfortunatelly there now appear two phenomens:
First: Only Power is flashing
Second: Power:flashing, System/Internet:blinking, Tunnel:flashing.
As from the Astaro Manual it means a DHCP fallback and a reboot within a period of time.
Also I read, that after the first configuration of the RED device, we have to alter the router settings whe nwe do have another IP-range. So it is.
Router standard: 192.168.1.1 with DHCP
ASG120 site1: 192.168.10.254
RED site2 expected via Helper in ASG120: 192.168.10.251
Company LAN: 192.168.10.0/24
Let's go on. So after some blinking and flashing from the RED device I thought it now got its configuration via internet. Next step: Change the settings in the Netgear Router so that its IP (192.168.10.251) could reach the internet again. I logged into the webadmin of the Netgear changed it's IP to 192.168.10.119 (isn't busy in our LAN I checked this). This automatically changed the DHCP range of the router, too. I modified the DHCP-range to 192.168.10.120 - 130 (free addresses in our LAN).
With my belief, I did everything in the correct way, I waited till the Netgear restarted with the altered settings. I again checked if the internet is working. And so it did - with a DHCP-address of the range I told it to take. Now I took the first look at the RED device but it didn't change - same phenomens as described above.
I tried to remember:
1. Set up the RED in the ASG120 with the helper. Typed in all it wanted. Only thing changed was the DHCP to static and took 192.168.10.251 for the RED device. GW IP 192.168.10.254 (ASG120), DNS IP ***.***.***.***. RED ID - correct.
2. Provide a router and DHCP server at the site of the RED
3. Just plug in the RED that it can get an DHCP address
4. the RED gets its configuration automatically and reboots.
5. After the reboot the RED doesn't get an internet connection (IP settings router - alter them so that it can)
6. After the router IP changed the RED now has access with its new IP (192.168.10.251) over the router (192.168.10.119) and can establish the tunnel to the ASG120.
I guessed that perhaps the RED config file hasn't been taken. So the be safe I deleted the RED config in the ASG120 and set it up again with the unlock code. But this didn't help and got the same result.
Now I'm asking you whether I'm too blind or just pretty silly in working with a RED device.
I'll be very very very glad if someone could help me. I'll give any information you still need but a livelog. I can't test it whenever I want to because the daily work is going on and I only have a couple of days per month to do it. However I hope that we can get a solution.
THANKS A LOT! Really - I don't want to dream of firewalls and VPNs anymore [:)]
Best regards from Germany
Stocky
This thread was automatically locked due to age.
