Forums before death by AOL, social media and spammers... "We can't have nice things"
|    alt.internet.wireless    |    Fun with wireless Internet access    |    55,960 messages    |
[   << oldest   |   < older   |   list   |   newer >   |   newest >>   ]
|    Message 55,442 of 55,960    |
|    Java Jive to Patrick    |
|    Re: Desktop PC to Android Mobile Hotspot    |
|    22 Feb 24 18:29:46    |
      XPost: comp.mobile.android, alt.comp.os.windows-10       From: java@evij.com.invalid              On 22/02/2024 14:47, Patrick wrote:       >       > On Wed, 21 Feb 2024 13:40:06 +0000, Java Jive wrote:       >>       >> As long as the desktop PC was previously set to accept a DHCP IP & DNS       >> from the main router, nothing should need to change; however, if it       >> was using a fixed IP, then obviously that would need to change because       >> x in the settings above is now going to be different.       >       > Maybe the problem is the PC has a static IP address, but I don't see       > anywhere in the DD-WRT setup as a "Repeater Bridge" where it cares.       >       > The PC's IP address, as far as I can figure out, is set on the PC.       > The DD-WRT "Repeater Bridge" doesn't seem to care what IP address it is.       >       > [snip]       >       > I guess what you're suggesting I think about is that the phone, when put in       > hotspot mode, is on a DIFFERENT subnet - which I'm sure it is.              Yes, exactly. To spell it out in more detail ...              The Repeater-Bridge - BTW you said earlier up thread that it was a       Client Bridge, which is a different possible configuration - doesn't       care how the PC is configured, but, obviously, the PC does, because       unless it is configured correctly, it won't interact with the network.              As I tried to explain in my last mail, the third number in the IP       Address range being used by the two arrangements - the normal router       and the mobile hotspot - is very likely to be different, I used x       before, so let's call the two numbers x(r) and x(h) for the router and       the hotspot respectively.              The subnet created by your main router will be in the range ...        192.168.x(r).0 to 192.168.x(r).255       ... with the router's IP address usually, but not certainly, being ...        192.168.x(r).1       Very often, but again not certainly, x(r) will be a low number, such as       0 or 1.              The subnet created by the mobile hotspot will be in the range ...        192.168.x(h).0 to 192.168.x(h).255       ... with the phone's IP address usually, but not certainly, being ...        192.168.x(h).1       Very often, x(h) will be a larger number, ISTR that mine is 47, but the       actual value is relatively unimportant, as long as *ALL* devices on the       network that are configured with a fixed IP are re-configured to use IP       addresses in hotspot's subnet rather than the router's.              So now consider things from the PoV of the PC, or indeed any other       device, if it has a fixed IP address. Almost certainly, it will still       be in the router's subnet range and therefore of the form ...        192.168.x(r).y       ... where y is some number between 1 & 255 and hopefully different from       those of the IPs of the router or any other device on the network,       whereas for the mobile hotspot it needs to have an IP of the form ...        192.168.x(h).y       ... as otherwise it will sit there receiving only traffic in the subnet       range of the hotspot, all of which it will simply & steadfastly ignore       because it's configured to interact with a subnet range different from       the all the traffic that it's seeing.              I suggest that before you do anything else, you log into the desktop PC,       open a Command Prompt with Administrator rights, and run ...        IPConfig /all       ... and see which of the two subnet ranges the IP address range is in;       if it's that of the router rather than the hotspot, there's your problem.              > I am looking at the suggestion from Andy about DNSmasq to maybe fix that.       > https://wiki.dd-wrt.com/wiki/index.php/DNSMasq_as_DHCP_server              I don't think you need should need DNSMasq, or use special DNS settings,       etc. Just get the basics right, as described above and in my previous       post, and it should work:        Configure the Repeater Bridge to have an IP in the hotspot's subnet;        Configure the PC either to use DHCP to set its IP & DNS, or        else configure it with a fixed IP in the hotspot's subnet.              --              Fake news kills!              I may be contacted via the contact address given on my website:       www.macfh.co.uk              --- SoupGate-Win32 v1.05        * Origin: you cannot sedate... all the things you hate (1:229/2)    |
[   << oldest   |   < older   |   list   |   newer >   |   newest >>   ]
(c) 1994, bbs@darkrealms.ca