Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

[danf]

We have three DFL-800 boxes in our organization.

Recently, we got an upgrade to service at one of our sites.

We wound up with a true static ip and not an infinite dhcp lease.

At our other site, the ISP gave me all of the required information. (IP, netmask, network, gateway, broadcast.) Was no issues setting it up.

This new ISP gives me IP, Gateway and netmask only - this is enough to get it working in Windows. I tried a Windows laptop after pulling my hairs out trying to configure the DFL. I phoned in to the ISP to confirm the missing information I'd calculated only to get a "We don't support that." response. Great.

IP: 192.168.160.93
Gateway: 192.168.160.1
Mask: 255.255.252.0 (or /22)

I've calculated the network should be 192.168.160.0/22.

So I've tried:
wan1_ip: 192.168.160.93
wan1_gw: 192.168.160.1
wan1_net: 192.168.160.0/22

And all I can do is ping my IP 192.168.160.93 from the DFL ping screen. Wondering if some existing rules were causing an issue I backed up the ruleset and re-initialized the DFL with the default "allow all" rule. Still no luck.

Actually, now that I'm looking at it, I never calculated the broadcast address. I wonder if that is why it is failing. Aaargh.

Plugging in the old DHCP DSL modem and reloading my rules work fine.

Is there any other thing that could cause this to not work?

[danilovav]

Actually, you don't need calculate broadcast.
By default, you just need to specify wan params (and also disable DHCP) and it will works.

[danf]

Hmm. I wonder if it associated the MAC address with the laptop then. I'll have to try to set it up again.