Recommended Posts

hello

i have forgotten how to set up a wireless router as a access point----no natting. if someone would be kind enough to give me a few pointers to get me going.

bought an Netgear WNR2000v3 N300 for cheap. i wanted to use it only for my android connections because its 2.4/N and my regular accesspoint is G. it still works great but wondering if a more recent equipment/radio would give me better pageloads.so i spent $16 and bought it.

i have a firewall router(dhcp) into a switch with wireless handled by an accesspoint(no dhcp).

live in the country and use mac filtering and have my android devices set in the filter.

now in the n300 i did not setup the internet connection, unchecked where it said use router for dhcp,turned on the wireless radio switch, set the ip, subnet,gateway as static. took a cable and pluged it one of the 4 lan ports and the other end in the switch.

did i miss anything? Thanks

Turn off DHCP and then plug your existing router into one of the LAN ports and leave the WAN port unused.

This works for any router.

(Except for some F*&((*&* D-Link I had to configure which hijacked the DHCP packets and replaced the default gateway even when DHCP was switched off)

And what dlink was that - I really find that hard to believe with the way that dhcp works.

So you have say router 1 with a few lan ports, maybe even another switch hanging off 1st router, then say your dlink being used as AP plugged into either first router lan or switch.

Now your client sends out dhcp discover broadcast. Any dhcp server on the network that sees that will send out a dhcp offer, again broadcast to 255.255.255.255, lets assume this is your router. That broadcast will go out every port on its lan switch, then every port on switch and should go out then every other port on your AP dlink, and the wireless even.

So your saying that your dlink intercepted this packet, and changed the dhcp option (3 I do believe) in the packet to its IP, and then resent the packet?? What about devices that were connected to the routers lan port, or the switch. There would be no possible way for the dlink to mess with those packets.

My guess is more that you dlink did not actually turn off its dhcp server, etc.

But you are correct turning off dhcp and just using a lan port is how you use any wireless router as just an accesspoint. What I would suggest is you also change the router your going to use as ap lan IP to something that is on your first routers network, outside its dhcp scope of course so that you can then access the now AP and setup its wireless network how you want, ssid, psk, security options, etc.

I don't remember which model it was, it was for a client. I suspect that when DHCP was turned 'off' in the settings it was actually still turned on, maybe in attempt to be a DHCP relay agent, because all the DNS settings etc. configured on the actual DHCP server was the same, only the gateway was changed to the D-Link's IP address.

There must have been two devices responding to DHCP at the same time - the D-Link and the main router, except that the D-Link was always quicker to give out the leases. Unplugging the D-Link fixed the problem (DHCP leases given out with the D-Link as the default gateway). I also tried factory resets.

I ended up doing a firmware update, which fixed the problem permanently. I checked the release notes after and there was no mention in the release notes about this being an issue. I suspect they just didn't document it.

Just through I would mention it in case anyone else comes across this problem with D-Link. I suspect that most IT folk would not come across this problem because we like to stay away from D-Link for all Wireless Gear because of their bad reputation (well deserved in this case for having such an absurd bug), but sometimes we find ourselves stuck with it when it is bought by someone else.

would love to see that bug actually. Were the only clients that were seeing this change of the router wireless?

How would it know to hand out the dns that was configured on the first dhcp server? And again it can not stop the packets from being seen by the other clients that are broadcasted. So it would be impossible for it to be faster while changing out the router and then rebroadcasting it.

While I don't doubt there was something odd going on, think we are missing the details of the actual problem. Changing out the gateway of some other dhcp servers packets with its own does not seem viable as what was actually going on to be honest.

But yes you need to make sure that your dhcp server on your router you want to use as AP is disabled!! Or you can have clients that don't work because they point to AP as their gateway when its not.

And if was acting as a dhcp relay, that too would be after the other packets have already been put on the wire for the AP to relay them. Yes a dhcp relay modifies the packet, has to change the mac, etc.. But relays are meant to work across segments not relay the traffic back out, even if was relaying the packet when it was not suppose to.. How would it block the other broadcast? So there is no way this relay would be there before the first broadcasts, etc.

would love to see that bug actually. Were the only clients that were seeing this change of the router wireless?

How would it know to hand out the dns that was configured on the first dhcp server? And again it can not stop the packets from being seen by the other clients that are broadcasted. So it would be impossible for it to be faster while changing out the router and then rebroadcasting it.

While I don't doubt there was something odd going on, think we are missing the details of the actual problem. Changing out the gateway of some other dhcp servers packets with its own does not seem viable as what was actually going on to be honest.

OK maybe it wasn't "relaying" it or "changing packets on the fly" maybe it was listening for other DHCP servers on the network, then taking the liberty to automatically become a 'secondary' DHCP server even though DHCP was turned 'off' by cloning the records given out by the other DHCP server, and then due to a bug (apart from doing this without being told) the default gateway is not cloned properly and sets itself as the default gateway even when it's not. Maybe the technical term is "doing some pretty weird stuff". Maybe it is D-Link trying to be smarter than what they actually are and then not testing their product in this configuration to see if this actual 'feature' works.

The D-Link was connected to the rest of the network via one of it's LAN port, therefore it was part of the same segment as the rest of the network.

All clients on the network set to get a DHCP address were experiencing the issue, even if not directly connected to the D-Link. Occasionally a client would get the correct address (1 out of 10 chance - rough estimate). If I unplugged the D-Link from the network, clients on the rest of the network would always get given the correct default gateway 10 times out of 10. Plug D-Link back in and same problem starts. The main DHCP server was a Netgear router, and not due to latency or anything, I think it was just a tiny bit slower giving out DHCP addresses most of the time, but still appeared to be a race condition.

This topic is now closed to further replies.
  • Posts

    • WhatsApp is getting usernames, and you can reserve your preferred one now by Fiza Ali Sharing your phone number isn't always something you want to do, especially with people you've just met. Whether it's someone from a class, a local community group, or a sports team chat, handing over your number can feel like giving away more personal information than necessary. That's exactly the problem WhatsApp is trying to solve with its upcoming usernames feature. The company has announced that users can now reserve a unique WhatsApp username ahead of the feature's wider rollout later this year. Once usernames become available, they'll let people connect without revealing their phone numbers. It's a change that makes a lot of sense for group chats. Right now, everyone in the group can see your phone number. With usernames enabled, that won't necessarily be the case when someone contacts you for the first time. WhatsApp says it's opening username reservations early because more than three billion people use the app, meaning plenty of people are likely to want the same usernames. Reserving one now gives users a better chance of securing the name they actually want before the feature launches more broadly. If your preferred username is already taken, WhatsApp will also offer a built-in username generator to suggest available alternatives. The feature isn't only aimed at individual users. Creators, businesses, and organisations will be able to claim the same username they already use on Instagram or Facebook, making it easier to keep a consistent identity across Meta's apps. Furthermore, privacy is a big part of how WhatsApp is introducing usernames. There won't be a public directory where people can browse or search for usernames. Instead, people will need to know your exact username before they can start a conversation with you. Additionally, users can also choose to enable a username key, which adds another layer of control by requiring people to enter that key before sending a message. Once the feature rolls out, people who choose to use a username will no longer have their phone number shown when messaging a person or business for the first time. If you want to reserve a username, make sure you're running the latest version of WhatsApp, then head to Settings > Account > Username. The tech giant says usernames will roll out gradually over the coming months, and users will receive an in-app notification when the feature becomes available in their country.
    • When I think about a network, there are really two aspects, the hardware and the wiring. So here is what I would do for both. Wiring: Use Cat6A for the patch panel, outlets, and all structured cables (cables installed in walls). Run plenty of Wireless Access Point (WAP) cables, as a general rule, assume a signal can only pass through 2-3 walls and can't pass through a floor (that is conservative, but trust me on this if you want strong WiFi)  Cat6 patch cables are fine for now if you don't plan to run 10gig, those are easy to replace later if needed. Run OS2 single-mode fiber to anywhere you think you may have a server or sub-switch. (yes, single-mode for everything on a small network, don't mess with multimode unless you have entire racks of servers and that minor module cost and power savings will matter). If you really want to future proof, also run fiber to any high density WAP locations, it is likely that WiFi 8 WAPs will push the limits of 10g. Run 6-12 pairs of single-mode fiber between your MDF and the building's MDF, even if you only need 1 or 2 pairs now, those extra pairs will pay off down the road. Hardware: (its easy to say "get all the features incase you need them", so instead of futureproofing, I am going to take approach of suggesting areas worth investing in, and areas you can save money). Don't overspend thinking you need every feature on every port. You don't need 10g on every port, you don't need PoE on every port. Don't overspend on redundancy either, unless you are ready to buy two of everything, don't waste money buying two of some things and not others. Dual power supplies are worthwhile, but probably not HA or multi-path redundancy.  Get 1 "distribution layer" switch that your router/firewall will connect to as well as all your access layer switches below. This should be a fully managed 10g+ switch with a combination of copper and SPF ports, a few 25g uplink ports are nice for this switch. Given that you said it is a small network, I suggest also using that distribution layer switch for servers and WAPs, meaning it will need PoE. Speaking of wireless, get good professional tri-band WAPs, and either turn on the band stirring options, or limit 2.4 to an IoT only SSID. This will provide a solid WiFi capable nearly everything but the highest of bandwidth clients...you could even consider skipping wiring workstations depending on usage. Access layer switch for workstations and printers can be cheaper switches, 2.5g is a good sweet spot between price and future proofing, but even 1g is fine for most individual clients (the kind that could probably be fine on WiFi). You can consider saving a little on access layer switches by only getting 1 PoE switch for whatever needs it (remember your WAPs are connecting to the distribution switch, not here), and non-PoE for your workstations, because desk phones are falling out of favor. You can also save money here by not buying managed switches if you don't need them--but really do some soul searching there, if you go this route, then anything that isn't on your workstation VLAN would either need to be connected to the distribution switch, or its own access layer switch. Also, don't feel like you need a fancy fabric stacking switches for your access layer, that is the point of the higher-end distribution layer, to remove the need for things like that at this level. Home Hardware: I'm realizing the above assumed an office setting, if this if for your house and home lab then the above still applies, but you'll probably want everything managed and PoE, just because, but you probably also don't need multiple access layer switches. If your total port count is below 24, just skip separating distribution layer and access layer and just get one nice switch with the features you want. If you are at the point of considering a 48-port switch, I would instead get a nice high-end distribution switch for things that need it, and cheaper access layer switches with specs based on the needs of connected devices. For home use, don't worry about home running every device to the main switch, there is nothing wrong with running sub-switches for your media areas and office, those essentially become your access layer, just look for sub-switches with a 10g uplink so sharing bandwidth isn't an issue. Just make sure you always connect them to your distribution/main switch, don't daisy chain, the path should never have more steps than Client>Access>Distribution>Firewall>Internet.
    • Google Meet brings Gemini note-taking to AI Pro and Ultra subscribers by Karthik Mudaliar Google's Gemini-powered "Take notes for me" feature inside Google Meet is now available to Google AI Pro and Ultra subscribers. The features work on Google Meet for web as well as on mobile, and Google says that subscribers can use it for meetings they host in many supported languages. As the name suggests, "Take notes for me" allows Gemini to listen to a meeting, generate a summary, identify action items, and save the notes as a Google Doc in the user’s Drive. After the meeting, the organizer receives an email recap with the summary and action items, while the notes can also be attached to the related Calendar event depending on the meeting setup and sharing settings. The feature isn't automatically turned on for everyone, though. Google says that all meeting participants are notified when note-taking is turned on, and users can start it from the pencil icon in Meet or enable it for future calls through Meet’s meeting records settings. For work or school accounts, administrators can also control whether the feature is available and may require explicit participant consent for note-taking, recording, or transcription features. The feature first launched back in 2024, when it was available just for selected Workspace users. Over the years, Google added refinements and more options, including the ability to enable it when scheduling meetings via Google Calendar. Google's support docs say that the feature currently supports English, French, German, Italian, Japanese, Korean, Portuguese, and Spanish, but only one language at a time. Meetings with multiple spoken languages are not currently supported, and Google recommends using the tool for meetings between 15 minutes and eight hours. The new feature makes Google Meet closer to its rivals that have AI tools already built in. Microsoft Teams has recently started offering Copilot and intelligent recap features that summarize meetings, surface highlights, and help with follow-ups, while Zoom’s AI Companion can also generate meeting summaries from desktop and mobile meetings.
    • GnuCash 5.16 by Razvan Serea GnuCash is a personal and small business finance application, freely licensed under the GNU GPL and available for GNU/Linux, BSD, Solaris, Mac OS X and Microsoft Windows. It’s designed to be easy to use, yet powerful and flexible. GnuCash allows you to track your income and expenses, reconcile bank accounts, monitor stock portfolios and manage your small business finances. It is based on professional accounting principles to ensure balanced books and accurate reports. GnuCash can keep track of your personal finances in as much detail as you prefer. If you are just starting out, use GnuCash to keep track of your checkbook. You may then decide to track cash as well as credit card purchases to better determine where your money is being spent. When you start investing, you can use GnuCash to help monitor your portfolio. Buying a vehicle or a home? GnuCash will help you plan the investment and track loan payments. If your financial records span the globe, GnuCash provides all the multiple-currency support you need. Between 5.15 and 5.16, the following bugfixes were accomplished: Bug 421610 - RFE: Include logical dates for View->Filter by "date range"The Select Range section of the Date tab of the register's Filter By dialog box is changed to provide relative, specific date, or days ago options for the start and end of the filter range. The Show number of days item label is changed to Show from days ago to better reflect what it does. Bug 436105 - esc key not working as expected in register: Enable the escape key to cancel a field edit. Bug 797384 - Gnucash doesn't handle commodity prices with big numerator/denominator properly. Bug 798004 - Next gen UI for stock transactions Bug 799314 - Add "enter now" option in scheduled transaction editor. tab to allow users to select the scheduled transactions to be included in a “Since Last Run…” window. If there are no instances of a selected transaction triggered by today’s date, the next instance is triggered. Bug 799751 - autocomplete crash Bug 799759 - Users can't Enable entries via Checkboxes on Scheduled Transactions PageAllow the Enabled box in the list of scheduled transactions to be operated instead of having to open the transaction editor dialog and change the Enabled checkbox. Also added use of the Name column as the secondary column sort for all the other columns. Bug 799762 - Poor handling of cases where hidden/placeholder accounts are used in the account register Bug 799766 - Double line preference not respected in search register Bug 799767 - POST /accounts in bindings/python/example_scripts/rest-api is broken Bug 799777 - `xaccSplitSetParent`: reparenting a committed split silently drops its KVP slots (online_id, cap-gains links) Other changes & improvements: Numeric values may now be selected to copy in the Accounts page. Add new Finance::Quote source Finnhub.io: Free API key (personal/non-professional use) available at https://finnhub.io. Set FINNHUB_API_KEY environment variable to API key to use this source. As of June 2026, free tier API limit is 60 API calls/minute. The Investment Lots report has new optional columns for Computed Annual Growth Rate. Python Bindings: Improved translation of primary object (Account, Transaction, Split, etc.) so that they can be treated as normal Python objects. This is accomplished with SWIG magic so no existing code is obsoleted. Python Bindings: Better conversion of GLists to Python lists. Python Bindings: Destroy the QofSession in the Python Session dtor to prevent leaving the database locked. [engine] Add first-class online_id accessors for Split and Account and make them available to Python bindings, removing the unused Transaction online_id property. Improve C++ implementation of QofBook. Correct the Doxygen doc for qof_instance_get/set_kvp. [gnc-log-replay.cpp] fix incorrect guid dump Add some Boost library requirements needed by libgnucash-guile to CMakeLists.txt so that missing feature will fail at configure time. Use Compile-time Regular Expressions instead of std::regex in gnc-filepath-utils.cpp and instead of boost::regex in the CSV importer, with the CTRE v3.11.1 header added to borrowed [gnc-filepath-utils.cpp] null check char* arguments Add ChartJS licenses. Removed AEX from list of commodities. euronext.com is now using JS based anti-webscraping. [report-core] always offer options summary in reports. This is useful to debug reports. The Add options summary option is removed because it's no longer optional. Remove remaining obsolete IMContext from sheet Fix blurry text in HiDPI offscreen-rendered widgets Add port field to database connection dialog: The convention of appending the port number after the host isn't obvious. When editing a split in the register treat the account as being changed only if it isn't the one selected before editing instead of if the user performed an edit Return immediately from qof_book_destroy if hash_of_collections is null. If qof_book_destroy is called on a QofBook* freshly created with qof_book_new (usually because it was used to create a session that now must be destroyed) it would try to empty the non-existent hash tables, crashing. Clean up Flathub metadata to solve warnings at flatpak build time. Be consistent in naming GncPluginPage and GncPluginPageRegister HTML: Remove unimplemented function declarations. [gnc-html.cpp] remove unused buggy string conversion functions Convert libgnc-html to C++ Apply -Wall -Werr -Wmissing-prototypes to C++ compilation on Windows and fix the resulting errors. New and Updated Translations: Arabic, Croatian, Danish, Dutch, German, Finnish, Hungarian, Korean, Norwegian-Bokmal, Spanish Download: GnuCash 5.16 | 176.0 MB (Open Source) Links: GnuCash Home page | Other Operating Systems | Screenshot Get alerted to all of our Software updates on Twitter at @NeowinSoftware
    • Microsoft finally launches WSL Containers in public preview by David Uzondu Microsoft has announced that WSL containers, a feature that allows developers to run Linux containers natively inside Windows without the need for Docker Desktop, is now available in public preview several weeks after Microsoft previewed it at Build 2026. To use the new container feature, you first have to install the latest pre-release version of the Windows Subsystem for Linux by running a quick update command in your terminal: wsl --update --pre-release After installing, you'd get access to the new Linux container CLI (wslc.exe) and the programmable API. Microsoft said that the CLI has a "familiar format" that matches the toolsets developers already use every day. If you know standard Docker commands, your muscle memory will translate directly to wslc.exe, which even features a built-in alias called container.exe. You can quickly run a full Ubuntu KDE desktop container by exposing ports, or pass your graphics card straight into a machine learning environment to run PyTorch workloads. Passing the --gpus all flag inside the run command instantly links your hardware. Image via Microsoft As for the API, developers can now embed Linux container operations directly inside native Windows applications without exposing the command line to users. The team integrated the API directly into MSBuild and CMake, so developers can define container steps directly in project files. Apart from bringing the CLI and API into public preview, Microsoft also said that it's working on a new default file system called virtiofs to speed up file transfer rates between Windows and Linux. Microsoft also introduced an experimental networking mode named consomme, which resolves compatibility issues with corporate VPNs by routing Linux network traffic straight through Windows. One thing to note about WSL containers is that they don't run in your standard WSL distributions; instead, every application and CLI session spawns its own lightweight Hyper-V utility VM in the background. This basically reduces the chances of one app snooping on the container of another app.
  • Recent Achievements

    • Reacting Well
      NovaEdgeX earned a badge
      Reacting Well
    • Week One Done
      NovaEdgeX earned a badge
      Week One Done
    • One Year In
      BA the Curmudgeon earned a badge
      One Year In
    • Conversation Starter
      rosiecharles earned a badge
      Conversation Starter
    • First Post
      KMilenkoski1202 earned a badge
      First Post
  • Popular Contributors

    1. 1
      +primortal
      535
    2. 2
      +Edouard
      269
    3. 3
      PsYcHoKiLLa
      150
    4. 4
      Steven P.
      98
    5. 5
      macoman
      66
  • Tell a friend

    Love Neowin? Tell a friend!