Print

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

[vimfuego]

Hi All,

I haven't had much success so far with my new DFL-260E (running the most current firmware too).
My config is I am running an ADSL Modem in bridge mode in to the DFL WAN Port using PPPoE, that side of it is working ok as far as I can tell because the DFL is showing all the right info on that ports summary....

PPP Assigned IP : 121.220.63.87
PPP Primary DNS : 61.9.134.49
PPP Seconday DNS : 61.9.194.49
PPPoE Server MAC : 00-90-1a-a4-df-3d
PPPoE Client State: Open
PPPoE Service name: "xxxxx"

I want to have a DHCP Pool from 192.168.0.2 to 192.168.0.50, with the gateway as 192.168.0.1, I have set that up correctly with certain MAC address's being assigned the IP address I linked them to (eg, net printer always at 192.168.0.8 ).
So the LAN side of things is working as far as the DHCP goes, but none of these devices have an internet connection.

What rule do I need to create to have the devices within the DHCP Pool see the internet connection? I did set this up using the wizard so I would have assumed by default it would allow all traffic between nets?

Thanks in advance for any advice.

[vimfuego]

Awesome, looks like this thing is going to become a $350 paper weight.
Is this forum an official D-Link support outlet?

[vimfuego]

For sale, one DFL-260E, probably a good product if you can figure out how to use it BY YOURSELF! Thanks Dlink

[Rara Avis]

Vimfuego,

No this isn't a D-Link support outlet, I do think there are mods who hangs out in most of the other product forums posting "Have you contacted TS yet for your TS issue?" as the second post in most threads.

Give D-Link a call, they have been happy to help every time I have.

You mentioned the wizard as your setup method, but your DHCP network doesn't match the default LAN network, and I don't think the wizard offers to change the LAN IP/network for you.  Are you will logging into the DFL at 192.168.10.1/24?

If that looks right to you, then it sounds to me like you need to change Objects->Address Book->InterfaceAddresses->lan_ip/lannet to 192.168.0.1 and 192.168.0.0/24 respectively.

[vimfuego]

Cheers for the response, I thought this was an official Dlink forum, it looks like it is 

So I reset the DFL back to factory defaults, ran through the wizard again and stuck with the IP's it defaults to.

This is how it is currently configured.

lan_ip = 192.168.10.1
lannet = 192.168.10.0/24

lan_dhcpserver_gw = 192.168.10.1
lan_dhcpserver_netmask = 255.255.255.0
lan_dhcpserver_dns1 = 192.168.10.1
lan_dhcpserver_range = 192.168.10.2-192.168.10.50

Ipconfig report from PC:
IPv4 Address. . . . . . . . . . . : 192.168.10.2(Preferred)
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.10.1
DHCP Server . . . . . . . . . . . : 192.168.10.1
DNS Servers . . . . . . . . . . . : 192.168.10.1
NetBIOS over Tcpip. . . . . . . . : Enabled

Still no internet access. Is there other rules I must set up or have I goofed something up in the above config? I am assuming the DFL gives everything open access by default and I have to close the gaps manually?

I did try calling DLink here in Australia but the guy I spoke to said nobody was familiar with that product and to try an overseas office, ahh, no thanks. But to be honest he sounded like he was having a bad day and probably did not want to deal with more than "have you entered your password in correctly".

[PacketTracer]

Hi,

I would suggest you read the manual. On page 136 it says:

There are two possible approaches to how traffic traversing the NetDefend Firewall could be dealt
with:

• Everything is denied unless specifically permitted.
• Or everything is permitted unless specifically denied.

To provide the best security, the first of these approaches is adopted by NetDefendOS. This means
that when first installed and started, the NetDefendOS has no IP rules defined in the main IP rule set
and all traffic is therefore dropped. In order to permit any traffic to traverse the NetDefend Firewall
(as well as allowing NetDefendOS to respond to ICMP Ping requests), some IP rules must be
defined by the administrator.

Good luck!
PT

[Rara Avis]

I would hazard a guess that you do have internet now, just no DNS.

You set the DFL as your DNS server, it doesn't perform DNS resolution/relay like a home router.  Try that same config, but with 8.8.8.8 (google's DNS server, though you could use any you like) as your DNS server.

[vimfuego]

You set the DFL as your DNS server, it doesn't perform DNS resolution/relay like a home router.

I was not aware of that, thanks. Changing the DNS to 8.8.8.8 from what I had fixed the problem, thanks so much, now I have to learn the rest of this box