Howdy, Stranger!

It looks like you're new here. If you want to get involved, click one of these buttons!

Sign In Register

Quick Links


Categories

In this Discussion

› › Multiple Dynamic IP address
New on LowEndTalk? Please Register and read our Community Rules.

All new Registrations are manually reviewed and approved, so a short delay after registration may occur before your account becomes active.

Multiple Dynamic IP address

praburampraburam Member
in Help

I know its noob question..

I have a broadband and whenever i turn off and on router. Im getting new dynamic ip address.

I need multiple Dynamic address for my each wifi user. It is possible? 🤔

Comments

  • blackjack4494blackjack4494 Member

    No.

  • JabJabJabJab Member
    edited December 2024

    That's a question to your provider.

    Until you want to proxy/tunnel your traffic via many VPSes/IPs on single VPS - then most likely doable

  • kevindskevinds Member, LIR

    @praburam said:
    I know its noob question..

    I have a broadband and whenever i turn off and on router. Im getting new dynamic ip address.

    I need multiple Dynamic address for my each wifi user. It is possible? 🤔

    You are talking about IPv4 correct?

    Is your ISP using PPPoE?

    You need multiple dynamic addresses for each WiFi host? Or you want/need one IPv4 address for each WiFi host?

    IPv6 that is the default setup..

    IPv4, yes, it is technically possible.. Will your ISP allow it? By default probably not, but if it is something you need, you should be willing to pay for it, then it can be done.

  • lowendtalkxdaxlowendtalkxdax Member
    1. Avoid DynDNS, it's trash
    2. Buy a 1€ VPS and get yourself a static IPv4
    3. Connect your home router to the VPS using a VPN
  • let_rockslet_rocks Member

    @praburam said: I need multiple Dynamic address for my each wifi user.

    IPv6 has this built-in ;).

    Thanked by 2yoursunny tentor
  • yoursunnyyoursunny Member, IPv6 Advocate

    @kevinds said:
    IPv4, yes, it is technically possible.. Will your ISP allow it? By default probably not, but if it is something you need, you should be willing to pay for it, then it can be done.

    I mistakenly connected the FiOS ONT to the LAN port of the home router.
    This resulted in every WiFi device receiving a public IPv4 from Verizon DHCP server.
    Thus, it's technically possible, but definitely against ToS.

  • TimboJonesTimboJones Member

    I'm wondering if he's really just wanting DHCP reservation in his router.

    Thanked by 1Riz
  • blackjack4494blackjack4494 Member

    @yoursunny said:

    @kevinds said:
    IPv4, yes, it is technically possible.. Will your ISP allow it? By default probably not, but if it is something you need, you should be willing to pay for it, then it can be done.

    I mistakenly connected the FiOS ONT to the LAN port of the home router.
    This resulted in every WiFi device receiving a public IPv4 from Verizon DHCP server.
    Thus, it's technically possible, but definitely against ToS.

    Huh. How can this even happen? Your home/wifi router should give each client an internal nat ipv4 address. No way the devices would skip your router and directly talk to ISP dhcp. Seems there was a major misconfiguration?

  • LeviLevi Member

    @blackjack4494 said:

    @yoursunny said:

    @kevinds said:
    IPv4, yes, it is technically possible.. Will your ISP allow it? By default probably not, but if it is something you need, you should be willing to pay for it, then it can be done.

    I mistakenly connected the FiOS ONT to the LAN port of the home router.
    This resulted in every WiFi device receiving a public IPv4 from Verizon DHCP server.
    Thus, it's technically possible, but definitely against ToS.

    Huh. How can this even happen? Your home/wifi router should give each client an internal nat ipv4 address. No way the devices would skip your router and directly talk to ISP dhcp. Seems there was a major misconfiguration?

    This happens when you rent router from the isp. They often modify router os to hardcode dns servers and dhcp server. That’s why I always buy my own router. Plus, always use dns crypt.

    Thanked by 1tentor
  • greenhost_cloudgreenhost_cloud Member

    @praburam said:
    I know its noob question..

    I have a broadband and whenever i turn off and on router. Im getting new dynamic ip address.

    I need multiple Dynamic address for my each wifi user. It is possible? 🤔

    Each time you restart your router, you get a new dynamic IP address assigned by your ISP, but you can't control how many different IPs you get for each user. If you need separate addresses for each user, you might want to use a VPN or a different network setup.

  • yoursunnyyoursunny Member, IPv6 Advocate
    edited December 2024

    @blackjack4494 said:

    @yoursunny said:

    @kevinds said:
    IPv4, yes, it is technically possible.. Will your ISP allow it? By default probably not, but if it is something you need, you should be willing to pay for it, then it can be done.

    I mistakenly connected the FiOS ONT to the LAN port of the home router.
    This resulted in every WiFi device receiving a public IPv4 from Verizon DHCP server.
    Thus, it's technically possible, but definitely against ToS.

    Huh. How can this even happen? Your home/wifi router should give each client an internal nat ipv4 address. No way the devices would skip your router and directly talk to ISP dhcp. Seems there was a major misconfiguration?

    This happened during a major version upgrade of OpenWrt.
    In this upgrade, Ethernet interface names are swapped: what used to be eth0 becomes eth1 and vice versa.

    In OpenWrt, eth1 is usually the LAN port, and it is placed into a br-lan bridge along with WiFi clients.
    Due to the interface name swap, the home router is now bridging the WiFi clients with the ISP line.
    Since the OpenWrt system is still starting, its DHCP server is not yet ready, so that WiFi clients received responses from ISP DHCP server first.

    This is resolved by (1) pulling the ISP line (2) editing OpenWrt configuration to consider eth0 as LAN.

    Thanked by 1tentor
  • blackjack4494blackjack4494 Member

    @yoursunny said:

    @blackjack4494 said:

    @yoursunny said:

    @kevinds said:
    IPv4, yes, it is technically possible.. Will your ISP allow it? By default probably not, but if it is something you need, you should be willing to pay for it, then it can be done.

    I mistakenly connected the FiOS ONT to the LAN port of the home router.
    This resulted in every WiFi device receiving a public IPv4 from Verizon DHCP server.
    Thus, it's technically possible, but definitely against ToS.

    Huh. How can this even happen? Your home/wifi router should give each client an internal nat ipv4 address. No way the devices would skip your router and directly talk to ISP dhcp. Seems there was a major misconfiguration?

    This happened during a major version upgrade of OpenWrt.
    In this upgrade, Ethernet interface names are swapped: what used to be eth0 becomes eth1 and vice versa.

    In OpenWrt, eth1 is usually the LAN port, and it is placed into a br-lan bridge along with WiFi clients.
    Due to the interface name swap, the home router is now bridging the WiFi clients with the ISP line.
    Since the OpenWrt system is still starting, its DHCP server is not yet ready, so that WiFi clients received responses from ISP DHCP server first.

    This is resolved by (1) pulling the ISP line (2) editing OpenWrt configuration to consider eth0 as LAN.

    Now that makes a whole lot of sense now. Lmao.
    But I doubt this would work in Germany. At least not with the major ISPs here (Telekom, Vodafone, o2). And even doubtful with smaller providers. Vast majority here is using routers offered by the ISP.

    I guess you got cgnat addresses?

  • yoursunnyyoursunny Member, IPv6 Advocate

    @blackjack4494 said:
    I guess you got cgnat addresses?

    Verizon gives public IPv4 to every DHCP client.
    I have one computer and two phones connected over WiFi, so they each got a public IPv4.

    However, the router itself didn't get public IPv4, because its "WAN" port eth0 isn't connected to the ISP line.
    Computers connected via wired Ethernet didn't get public IPv4 either, because they were attached to eth0 and weren't bridged with the ISP line.

Sign In or Register to comment.