Recommended Posts

Dear Neowin member,

Sorry I have lots of questions lately. Please bear with me.

I have a Linksys WRT54G router and my computer connects to the wireless router using a WUSB54G adapter, while my sister connects it wiredly. Anyways, my sister's DHCP address is 192.168.1.100 while mine is 192.168.1.101 .. which means hers is the host or the start or whatever you call it. Right? I hope so. Anyways, how do I change it so I am the 100 and my sister is the 101? Help would be GREATLY appreciated.

Thank you for your attention!

dL

Link to comment
https://www.neowin.net/forum/topic/157248-dhcp-client-question/
Share on other sites

i believe what you are talking about is the dmz host setting which allows you to be openly connected to the internet (without any sort of hardware firewall), go to advanced settings and enter your local IP for the DMZ host. :D

and as was said before, the local IP addresses have nothing to do with hosting, etc. If your sister turns her computer off, and you reboot, you will likely become ... .100 and she will be .101 when she restarts.

I would recommend you not turn on the dmz host setting.. Renders your firewall useless.

Check the diagram below to see why you can use netmeeting when you're 100 and not when you're 101. To make it so that you're always .100, you can set yourself as a Static IP in the LAN config section of your router (at least, I can ;)).

Although, it doesnt matter if you're .100 or .101... There isnt any "start" or anything, all computers get data the same no matter if they're .100 or .199

post-32-1081835456.jpg

  HellBender said:
I would recommend you not turn on the dmz host setting.. Renders your firewall useless.

Check the diagram below to see why you can use netmeeting when you're 100 and not when you're 101. To make it so that you're always .100, you can set yourself as a Static IP in the LAN config section of your router (at least, I can ;)).

Although, it doesnt matter if you're .100 or .101... There isnt any "start" or anything, all computers get data the same no matter if they're .100 or .199

is this a joke?

  HellBender said:
Um.. no? Why would it be? :dontgetit:

just the diagram mostly........is not really how it works at all. the port the data comes in on in no way correlates with the local IP addresses. you could have a local IP address set as any given numbers and as long as either you enable DMZ hosting / open the necessary ports.....everything should work fine......

unless I'm really really lost?? :huh:

EDIT: okay, i've been looking at it more, and I kinda understand what you are saying. you are saying that someone set up the router to forward the data entering netmeetings ports to local IP [...].100 ???

Edited by rumbleph1sh
  rumbleph1sh said:
just the diagram mostly........is not really how it works at all. the port the data comes in on in no way correlates with the local IP addresses. you could have a local IP address set as any given numbers and as long as either you enable DMZ hosting / open the necessary ports.....everything should work fine......

unless I'm really really lost?? :huh:

EDIT: okay, i've been looking at it more, and I kinda understand what you are saying. you are saying that someone set up the router to forward the data entering netmeetings ports to local IP [...].100 ???

That's how data travels without DMZ Hosting involved. The thread starter obviously hasnt and doesn't want to set up DMZ hosting, so what he must have done is forwarded port 100 to IP address 192.168.1.100, and so he can use netmeeting fine. But once he pops to 192.168.1.101, the data for netmeeting is sent to 192.168.1.100, so he doesnt receive it, thus rendering netmeeting useless.

  HellBender said:
That's how data travels without DMZ Hosting involved. The thread starter obviously hasnt and doesn't want to set up DMZ hosting, so what he must have done is forwarded port 100 to IP address 192.168.1.100, and so he can use netmeeting fine. But once he pops to 192.168.1.101, the data for netmeeting is sent to 192.168.1.100, so he doesnt receive it, thus rendering netmeeting useless.

alright, thanks for clarifying. i'm sorry , i guess I was just reading the diagram wrong. :blush: everything seems in order now

  dL said:
HellBender is right. That's what I think, and his/her diagram is exactly what I think the problem is. I'm not sure if it's true though.

dL

If thats indeed the problem, then all you have to do is assign yourself a static IP (like me and Smeg earlier mentioned). This means that every time you connect to the DHCP server, it will assign you the same IP no matter what order you connect in. That way, you'll always be 192.168.1.100 and you'll always get the netmeeting traffic.

  HellBender said:
If thats indeed the problem, then all you have to do is assign yourself a static IP (like me and Smeg earlier mentioned). This means that every time you connect to the DHCP server, it will assign you the same IP no matter what order you connect in. That way, you'll always be 192.168.1.100 and you'll always get the netmeeting traffic.

Now How do I do that with my WRT54G Linksys router?

Can I do it in the Wireless Network Connection, underneath TCP/IP properties in My Network Place?

dL

  HellBender said:
If thats indeed the problem, then all you have to do is assign yourself a static IP (like me and Smeg earlier mentioned). This means that every time you connect to the DHCP server, it will assign you the same IP no matter what order you connect in. That way, you'll always be 192.168.1.100 and you'll always get the netmeeting traffic.

I don't understand this. Just because it was set up with port forwarding to work a specific way on his OLD router, why should it be set up on his new router already? You must manually open ports/ re-setup the port forwarding on your new router in order for it to work properly.

  dL said:
Now How do I do that with my WRT54G Linksys router?

Can I do it in the Wireless Network Connection, underneath TCP/IP properties in My Network Place?

dL

No, you'll have to go into your router admin... I think its http://192.168.1.1 for you.. Enter your user/pass in and find something that says Static IP. I dont have a linksys router, so I can't tell you exactly where it is.. hopefully someone will come along who can.

to set your lan connection to be a static IP:

Right-click on My Network Places.

- Left-click on Properties.

- Double-click on Local Area Connection.

- Click on the Properties button.

- Highlight TCP/IP, then double-click on it.

- Select "Use the following IP address." Then enter the IP address 192.168.1.100 with Network Mask of 255.255.255.0.

- Set the Default Gateway to 192.168.1.1 which is the default address for the linksys.

or in the router setup (192.168.1.1) click on advanced and there are options for setting up static routing

This topic is now closed to further replies.
  • Recently Browsing   0 members

    • No registered users viewing this page.
  • Posts

    • The $100 million mark was rejected a couple of days ago.
    • This super-powerful GaN charger with four ports is 50% off by Taras Buria Some time ago, I reviewed the Cuktech 10, a powerful 100W GaN charger with three ports. It left positive impressions, and since then, it has served me as my primary charger for my phone, watch, laptop, and tablet. Recently, Cuktech offered me the opportunity to take a look at the model 15, a more powerful 140W GaN charger, this time, with four ports. Right now, this powerful charger is available with a massive discount at just $50.99 (with coupon applied). The Cuktech 15 is the same as the Cuktech 10, just slightly bigger, more powerful, and with one extra port. It has a light metallic finish, but overall, it retains the brand's identity and features. The four ports are well spaced out, and the black plastic insert with a cyan rim has a ribbed texture for better grips. Although I live in Europe, Cuktech sent me a US variant with a retractable plug. Okay, I guess. The ability to retract the plug makes it extra portable, which is nice. A high-power 240W five-foot cable is also included. The charger measures 3.11 x 2.56 x 1.26 inches and weighs 0.737 lbs. The Cuktech 15 has four ports: two high-power Type-C ports, one Type-C port with a lower output, and one Type-A port. The first two Type-C ports can deliver a full 140W in single-port mode (PD 3.1 supported), which is nice—no asterisk or caveats here with combined power or something. If you need the full 140W for one device, you get it. Ports are capable of working in the following modes: Single-port Type-C1 / C2: 140W max 5V 2A, 5V 3A, 9V 3A, 11V 6.1A, 12V 3A, 15V 3A, 20V 5A, 28V 5A Type-C3: 33W max 5V 2A, 5V 2.4A, 9V 2A, 12V 1.5A, 11V 3A Type-A: 18W max 5V 2A, 5V 3A, 9V 2A, 12V 1.5A Multi-Port Type-C1 + C2: 100W + 33W or 65W + 65W Type-C1/C2 + Type-C3: 100W + 33W Type-C1/C2 + Type-A: 100W + 18W Type-C1 + Type-C2 + Type-C3: 65W + 60W + 7.5W or 45W + 45W + 18W Type-C1 + Type-C2 + Type-C3 + Type-A: 65W + 60W + 7.5W As you can see, the charger is pretty robust, and it can power two pretty powerful laptops at once and even have enough oomph to charge a smartphone, albeit at a lower power. Another thing worth mentioning is that the Cuktech 15 delivers "clean" power with pretty low pulsations at about 25-50 mV. The rule of thumb is that the lower the pulsations, the better the charger is for your device's battery health. In this area, Cuktech's charger does not disappoint, and they deliver way better results than 100 mV, which is considered a standard for a good charger. Cuktech uses gallium nitride technology, which enables smaller, more powerful and efficient charging. Speaking of efficiency, the charger is rated for 78% average or 64% at a 10% load. When charging at 120W, I received an average of 80-85%, which is good. Of course, when charging at peak power, it gets hot, but not too much. The Cuktech 15 140W usually costs $99.99, which is undoubtedly not cheap. However, right now, you can get it for half the price, which is a very good deal, considering you get a high-quality charger with plenty of ports and very high power output. Like with the Cuktech 10, you cannot go wrong with this one. CUKTECH 15 140W four-port GaN charger - $50.99 | 30% off + a 20% off coupon As an Amazon Associate, we earn from qualifying purchases.
    • Awesome book, just hope they don't screw up Rocky and the story
    • KDE's KClock is getting Wayland Picture-In-Picture support by David Uzondu The KClock app for KDE Plasma over the years has received a number of updates, like better integration with KRunner and a dedicated background service (kclockd) for managing alarms. Now, it looks like KDE devs want to add something cool: pop-out timers using the new Picture-in-Picture protocol for Wayland. Image: Kai Uwe Broulik This all started from a simple observation. Kai Uwe Broulik, a KDE developer, saw someone using a small timer window during a presentation and thought it was a good idea. The problem is that achieving this kind of "always on top" behavior is handled differently between the old X11 display server and the newer Wayland. With X11, an application could pretty much do whatever it wanted. If a program wanted to draw a drop-down menu, it would just create a borderless window, place it in a specific spot, and grab all user input. Wayland operates on a different philosophy. As Broulik notes, under Wayland, the application describes what it wants, and the compositor gets to decide how to handle it. A drop-down menu is an XDG Popup. The application tells the compositor which button spawned it, and the compositor handles the placement and behavior. This is much more secure and consistent. It also means an application cannot just decide to keep its window on top of everything else. This restriction prevents a web browser from implementing an overlay video player under Wayland. To get around this in a standardized way, a proper Wayland support model for Picture-in-Picture, or PiP, was needed. Enter the xx-pip-v1 protocol. It is a new protocol designed specifically for creating floating PiP windows, and KWin, Plasma's compositor, recently gained support for it. Because it is an experimental protocol, its use is gated behind an environment variable, KWIN_WAYLAND_SUPPORT_XX_PIP_V1. A new protocol is fine for demos, but it needs a real application to find its weaknesses. So Broulik implemented it in KClock. This work allows KClock to offer pop-out timers and even a pop-out stopwatch in a small PiP window. The user could get system-wide options to control where the PiP window appears, or if it appears at all, and have that setting apply to every single application that uses the protocol. You can check out the merge request on GitLab for more technical details about this feature.
    • Nothing of course; it is just a classic syndrome of MAGA pathology.
  • Recent Achievements

    • One Month Later
      CHUNWEI earned a badge
      One Month Later
    • Week One Done
      TIGOSS earned a badge
      Week One Done
    • First Post
      henryj earned a badge
      First Post
    • First Post
      CarolynHelen earned a badge
      First Post
    • Reacting Well
      henryj earned a badge
      Reacting Well
  • Popular Contributors

    1. 1
      +primortal
      475
    2. 2
      +FloatingFatMan
      195
    3. 3
      ATLien_0
      163
    4. 4
      Xenon
      81
    5. 5
      Som
      76
  • Tell a friend

    Love Neowin? Tell a friend!