Change WL310 settings using ethernet interface?

[Olle Mattsson_1]

Hi,

Since obviousle noone knows how to totally reset the WL310 (which I'm going to smash out trough the window VERY SOON!) I'll ask a different question.

Is there any way to CHANGE WL310 settings using the ETHERNET interface? If this is the case, how can I do it?

[Max_34]

HI. Don't smash anything. I've experienced similar problems.
You've probably disabled the DHCP on the wireless interface, thus "it does no longer let you in". WHat you can do is either set a static ip (temporarily) on your wlan adapter. this ip must be in the range that you had preconfigured. or connect the wl310 using a CROSSED cable. if dhcp is set on ethernet-interface, than you should immediately have access throug APmanager. If not (which you can assume it is if your ethernet adapter doesn't receive an ip (start/run cmd ipconfig). in that case set a static ip on your ehternet adapter (again temporarily) and open the AP manager. good luck. believe me it works.

[Olle Mattsson_1]

ah okay... so you need a crossover. I missed that part. I hope I get it to work, I'm just about buyng a d-link gateway for 150 ??? instead :-/ Goddamit!

[Olle Mattsson_1]

Ok so now I've got this thing online again. And there's a new problem. From the computer connected to the wireless network I can't ping anything. Neither the wl310 itself nor the switch the wl310 is connected to. Has this got to do something with the "bridging" and "NAT" options available in the AP Manager.

And should I set the DHCP servers (wl310) default gateway to the WL310's IP or to the switch's IP? I can't seem to figure this out...

some info:
- swith's IP: 10.0.2.1 (which in turn is connected to my ISP)
- WL310's IP: 10.0.2.100 for the WLAN clients and 10.0.2.3 for the LAN
- DHCP (WL310) from 10.0.2.101~199 and default gateway set to 10.0.2.100 (WL310), DNS set to whatever (10.16.11.16 (the address my ISP provided me with))
- NAT on
- Briding on

Help would me much appreciated!

[Max_34]

Well, that's exactly where I am now, too. I have the exact same problem. I think bridging is only there to be used as a modem.

To be honest, I don't know, has it ever worked? I'ver just got it from a friend who's been using it with a ADSL-router, and it worked. I have a cable-modem and it doesn't. To be more specific: my WL310 obvously gets through to the internet; it receives an IP from the ISP, as well as a the correct DNS and it changes my *default gateway* to an ISP IP. I manage to ping my WL310 on the private IP and on the public IP (!!!) but I cannot ping anything else! This does not make any sense to me.
p.s.: make sure, that you select half-duplex mode

[Olle Mattsson_1]

ok, so what's really the difference between public and private IP? Is the private IP the IP the wireless clients see and the public is the IP that the wired (LAN) devices see?

Why should you use half instead of full duplex? I changed from full to half and now my wireless clients can no longer connect to the WL310... odd!

[Max_34]

hmmm... half duplex is supposed to send data in one direction and then wait for the reply to come, while full duplex does both at once. The support guy from my ISP sounded pretty sure, that half duplex would be more reliable. But as you say it doesn't...

About the IPs: the wl310 should get an IP assigend from the ISP, this is the actual IP that any website will get when you eventually will surf. That's the public IP towrds the WAN (wide area network), it will change at least once a day with adsl. The "private IP" is the one of your wl310 inside the lan (local area network). This is usually the DHCP router IP too (when you use your wl310 as a router distributing dynamic IPs), but I've never tried to separate the wl310 private ip and the DHCP router ip. Maybe this would work...

[Max_34]

what kind of ISP connetction do you have? how is your switch connected to the ISP? I just reread your message with the specs and it seems to me, that if your switch is rather a dhcp router on his own, you might try usinge either your wl310 as non-standalon, disabling the dhcp funktion and letting your switch handle the ip assigning, or you need to change completely the ip ranges eg. your switch/router 192.168.1.1, the wl310 10.10.1.1 - ehat do you think?

[Olle Mattsson_1]

This is how it works for me:

My switch (10.0.2.1) is connected to an ADSL modem which in turn is connected to my ISP, Sonera, which gives out static IP's / Mac address. The switch is connected to two computers plus the WL310. The WL310 is (or SHOULD BE) connected to all the Wireless clients (three at the moment). Now the WLAN creates a network inside a network, thus the WL310 has a one IP that the switch sees (10.0.2.3) and one IP that the clients see (10.0.2.100).

Now here's the problem (apart from the clients not being able to connect to that gaddoamned WL310!): When pinging from the server machine which is connected to the switch, to the WL310 I do get a reply. BUT when trying to ping "beyond" theh WL310 (any of the wireless clients) I get no reply at all.

The clients themselves can't even ping the WL310...

As I already mentioned I'm also having problems getting any connection between the clients and the WL310 at all, so to me it more and more looks like there's an error within the WL310, BECAUSE it worked just a week ago. Then all of a sudden it just stopped working and that's why I've been micing with different settings, trying to figure out what caused the failiure.

Yesterday I was able to get one of the clients connected but that lasted only for about 20-30 minutes and then the connection went dead again...

VERY curious....

[Olle Mattsson_1]

I should also add that the switch does not have DHCP enabled. The WL310 does have it enabled but only on the wireless interface. So both the swith's and the wl310's ips are static.