Main Area and Open Discussion > General Software Discussion

How to determine ipaddress of mini-webserver on a wireless network

<< < (3/3)

patteo:
Actually the mini-webserver is my laptop (call it laptop "A"). So if I take laptop "A" to Starbucks, then if I'm set to a static ip, I might not be able to get a wireless connection at Starbucks unless this Alternate configuration stuff works.

In any case, there may be a alternative solution even if I leave my Linksys Wireless WRT54G router on DHCP, because they have another configuration tab that is called Port Triggering.

It seems, that you can do some settings so that whatever Dynamic IP, I may have been assigned, the router would be smart enough to find it. ie whether I have been dynamically assigned 192.168.1.100 or 101 or 102 etc.

I could be wrong but I'm trying to understand what I'm reading here.

"Port Forwarded Only On Specific IP Address - ZeroPaid
"The answer might be found under port triggering in the tab next to forwarding. I used triggering on my Netgear router and it worked woof well, following my computer to whatever IP it was using that day."
http://www.zeropaid.com/bbs/archive/index.php/t-43203.html

So if it turns out to be right, that would be ideal - have your cake and eat it, leave my laptop alone, leave the Linksys DHCP setting on, but tweak the Port Triggering tab.

It's a bit of an info overload for my tiny brain - but I hope the solution lies here.

Has anyone heared of Port Triggering before. The Linksys configuration tab on Part Triggering is as clear as mud.

Update:
As far as I can determine, Port Triggering is not the answer.

Port triggering - Wikipedia, the free encyclopedia
"Port triggering"
http://en.wikipedia.org/wiki/Port_triggering

"The disadvantage of port triggering is that it only allows one client on the network to supply a particular service that uses a particular incoming port. Port triggering is unsuitable for putting servers behind a NAT router because it relies on the computer to make an outgoing connection before it can receive incoming ones; servers should use port forwarding."
http://en.wikipedia.org/wiki/Port_triggering

I have to rethink this again. Meanwhile, any suggestions would be most welcome.

Thanks once again to everyone who made a suggestion here.

patthecat:
Patteo - glad you were able to sort things out.

You may want to see if your Linksys router has this feature that I have found and used on a business level Netgear router.  The router allows to assign a specific IP address if it sees a specific MAC address from a wired/wireless network card.  For example, router assigns DHCP and wireless card set to get IP address automatically.  Each network card has a unique serial number / MAC address.  You put that MAC address in the router and tell it to reserve/assign a specific local IP address so that anytime that router sees that network card request for an IP address it always assigns the same one.

If your router does not have this feature then you would have to keep on changing your laptop's wireless card to go between specific vs. dynamic IP addressing.  I use NetSetMan, the free version (http://www.netsetman.com) to keep network profiles so I can switch between specific and dynamic ip addresses for the wireless and ethernet network card on my laptop.

steeladept:
Another option would be to assign a static ip to the laptop on the alternate config, and leave the default config on auto. The problem with this approach is that sometimes it won't work as expected and you have to disconnect/connect a few times until it figures out it should be using the static ip.
-jgpaiva (September 23, 2007, 11:31 AM)
--- End quote ---
I was under the same impression as jgpaiva - that the server was not on the laptop.  In your case, I think the above option is the way to go.  I have never had issues with multiple profiles on my laptops, but they are using the Intel 2200bg wireless card that is VERY GOOD compared to any other card I have seen.  They came with this card and the software (IntelPROSet Wireless) with it allows me to order the profiles.  If it finds the connection for the top profile it stops; if not, it goes to the next to try.  It prevents the issues mentioned.  If you can find a wireless package similar to the PROSet Wireless package and use it in place of Windows wireless services, I think you can avoid the unexpected issues jgpaiva mentioned.

Oh, and if anyone knows of a package as good as Intel's PROSet Wireless package that works on windows with Broadcom wireless cards - PLEASE LET ME KNOW.  I have SO many clients that want wireless on their laptops, and I always direct them to the Intel cards because they work.  The Broadcom cards work fairly well too, but are not 100% Cisco compatible (required for many enterprise wireless setups), and they do not have a good package to manage it.  It is a bit cheaper than the Intel cards though.  I will checkout the NetSetMan, but if others know of any, I am listening.

Thanks.

Navigation

[0] Message Index

[*] Previous page