This topic

Need some help

SmugeeBear — Wed, 09 Aug 2023 16:09:41 GMT

Hi im having some issues with my smart hub 2 and a device im trying to connect with it.

basically its a raspberry pi with some software which allows it to act as a bridge between the hub and the old dial up modem of a sega dreamcast.

the issue im having is the hub seems to get confused because the pi has one ip address 192.168.1.183 when it connects but when the console connects it switches to 192.168.1.98 which is classed as a static ip

but when i restart the pi it gets assigned the last ip address which is the one ending in 98 when it should be the other one but it seems like even if i change the DHCP range it still happens. because i changed the range to .100 to .253

Also the hub software doesnt seem to allow me to do much thats if it isnt getting confused or automatically doing some wierd things.

like it also sseems to randomly switch a manually typed ip address i have in the dmz with the ip address of another device connected to it.

i just need some advice because constantly going into the hub manager to manually adjust it all the time isnt working and then other posts dont mention any solution.

Because another option BT on social media suggested was disable DHCP but didnt actually elaborate on what it was fore etc.

Re: Need some help

licquorice — Wed, 09 Aug 2023 16:25:35 GMT

Simply give the Pi a static address of whatever you want it to be on the Pi itself. If it is possible, also give the sega a different static address on the sega itself.

Don't turn off DHCP or non of your other devices will obtain an IP address.

Re: Need some help

SmugeeBear — Wed, 09 Aug 2023 19:06:39 GMT

i cant give the sega a different ip is a static non changeable one

could try and set an ip address in the pi itself but the issue is with the software in it i think it has an auto config which might conflict with it.

its kind of ironic that originally when the sega dreamcast came out bt were the original dial up provider for them in the uk.

so i guess theres no option for a ip reservation or exclusion?

Re: Need some help

licquorice — Wed, 09 Aug 2023 19:10:54 GMT

The BT Hub supports address reservation but obviously the IP addresses need to be in the DHCP range.

Re: Need some help

SmugeeBear — Wed, 09 Aug 2023 21:54:46 GMT

how do i do that then? or is it business customers only?

because i've set the pi to a static address of 192.168.1.183 and it seem fine its jsut when it bridges to .98 it has issues when the pi is powered off and then rebooted as the hub still seems to hold onto .98

Re: Need some help

licquorice — Thu, 10 Aug 2023 06:55:33 GMT

I'm totally confused as to what you are doing and possibly your terminology.

Static addresses by definition can only be set on the device itself, not on a router. A router has a facility called Address Reservation which is often misnamed Static Addressing.

Address reservation is achieved by a router issuing an IP address via DHCP but always the same address. On the hub select 'Yes' in the Always Use This Address option.

How are you determining the address of the Pi is changing? The Hub network list is notoriously hopeless.

When Port Forwarding, select the IP address you wish to forward to rather than the device name.

Re: Need some help

SmugeeBear — Thu, 10 Aug 2023 10:17:30 GMT

quick version is i have a raspberry pi device that switches ip addresses depending on the mode its in.

the hub gets confused and will do several things hold onto the last ip address the device used which is usually the secondary static address on the device.

But it causes issues when the device boots up because it ends up clashing when it goes into its second mode and causes connections issues.

the second issue i have is with the hub is it randomly keeps swapping an ip address of a random device on my hub/wifi disc with an ip address i have in the DMZ. Which is an issue being that it leaves a device vulnerable

the reason why there is a ip address in the DMZ is to help the raspberry pi in its second mode as the old console that is connected to it works better in it.

As to my first issue how do i reserve the ip address so stop the hub going hey i'll use the last ip address the device has? or at least tell it hands off

because even giving the raspberry pi a static address on the device in its first mode doesnt seemed to cleared the issue with the hub

second issue seems more of a bug tbh

Re: Need some help

SmugeeBear — Thu, 10 Aug 2023 10:23:31 GMT

how do i know the ip address of the pi is changing?

with how the pi is set up now it has a ip address of 192.168.1.183 when it boots up, when it goes into its second mode when i use the pi to connect the dreamcast online the ip address switches to the console which is always either 192.168.1.98 or 99 I know that for certain.

also in the hub list the ip address of the device changes but how will port forwarding help?

also if i tell the hub to use always use this address it will continue to use the last ip address it got

Re: Need some help

licquorice — Thu, 10 Aug 2023 12:04:43 GMT

Ok, I assumed it was the Pi that was in the DMZ and hence why IP address was important.

If it isn't in the DMZ or has any ports forwarded to it, why is it a problem what IP address it has?

I can't see how the hub or any router can be expected to cope with what you are doing. As far as it is concerned there are 2 devices, the Pi and the Sega. The physical Pi will always have one address when first booted and then a second when the software runs.

Re: Need some help

SmugeeBear — Thu, 10 Aug 2023 19:36:04 GMT

well i need the hub to stop assigning 192.168.1.98

because i've tried setting a static ip for the pi even trying to look into the hub settings but the hub is still holding onto that last ip address and then forcing it onto the raspberry pi even though its got its own ip

or there has to be a way for the hub to reset the ip address when the pi disconnects?

Re: Need some help

licquorice — Thu, 10 Aug 2023 19:48:17 GMT

If you have set a static IP address on the Pi itself, the hub can't override it, end of. The Pi address will remain constant.

I'm not familiar with either the Sega or the software you are running but I suspect this creates a pseudo device which the hub is allocating the IP to.

I still don't understand why it is so important to have particular IP addresses if you are not forwarding any ports

Re: Need some help

SmugeeBear — Fri, 11 Aug 2023 17:59:19 GMT

alls i need is to reserve the ip address 192.168.1.98

how can i do that?

Re: Need some help

licquorice — Fri, 11 Aug 2023 18:17:45 GMT

By letting the hub allocate the address and then select 'always use this address' . However, you cannot determine what address the hub will allocate.

For the third time of asking, why is important to use a particular address? You seem reluctant to answer this simple question.

Re: Need some help

SmugeeBear — Sat, 12 Aug 2023 18:19:18 GMT

"For the third time of asking, why is important to use a particular address? You seem reluctant to answer this simple question."

Because 192.168.1.98 is the internal ip for the segas modem and cannot be changed it also causes connection issues if it is assigned to the raspberry pi which i have mentioned previously in this thread.

I'm trying to find a practical solution to the issue, not snarky comments.

"By letting the hub allocate the address and then select 'always use this address' . However, you cannot determine what address the hub will allocate."

It wont work because thats still tying the ip address to the device, which wont work because it will issue that ip address to the pi causing it not to work.

So any alternative solutions? Because I'm finding the hub is pretty restricted in its functionality especially when some of the answers i had off bt is become a business customer.

and when i had a previous isp before i moved house thier hub did allow me to filter/reserve via ip addresses not devices

Re: Need some help

SmugeeBear — Sat, 12 Aug 2023 19:39:09 GMT

Also it doesnt change the fact that the smart hub its automatically switching ip addresses on its own.

because its swapped out the manually typed in address i placed in the DMZ with random devices thats connected to the hub

so is my hub faulty or is there a faulty firmware because this needs to be address asap if its going to place devices at risk randomly.

because that seems to be the more concerning issue atm.

Re: Need some help

ptrduffy — Mon, 14 Aug 2023 16:42:29 GMT

If you need to reserve 192.168.1.98 and .99, then maybe the best thing to do is modify the hub's DHCP range so that it can never hand out those addresses. You can do this in 'Advanced Settings'->'MyNetwork'->'IPv4 Configuration' - there's a 'Server address range' option which you could set to '192.168.1.100 - 192.168.1.253', then the hub will never try to issue any address below 192.168.1.100.

This reduces the pool of available DHCP addresses (the default range start at .64), but as long as you have fewer than 154 devices you should be fine.

(I don't understand why you can't assign the Pi and Dreamcast IP addresses that are below the default range, but the above should work anyway.)

Re: Need some help

licquorice — Mon, 14 Aug 2023 16:46:54 GMT

That won't work at all. Any address requiring reservation has to be in the DHCP range. The address has to be issued by DHCP first and then reserved. You would need to do the opposite, I e DHCP only hands out the required address.

Re: Need some help

ptrduffy — Mon, 14 Aug 2023 16:58:06 GMT

@licquoricenot sure I understand? I'm suggesting @SmugeeBear configures his Pi with a static address outwith the DHCP range of the hub - then the hub wil never issue an IP address that can clash.

I do this with a NAS box that I want to have on a static IP - in my case I have it set to 192.168.1.10.

In the OP's case they are insisting that they need the Pi/Dreamcast to have .98/.99, so changing the DHCP range should work, unless I'm misunderstanding (entirely possible as the thread is a bit confusing).

Re: Need some help

licquorice — Mon, 14 Aug 2023 17:06:37 GMT

That's what I suggested in message 2 of the thread. I thought you were talking about address reservation on the hub rather than giving the devices a static address.

I'm really not sure why if the OP hasn't given the devices static addresses and doesn't require port forwarding the addresses need to be specific. He doesn't seem to wish to answer this simple question and calls me sarky for asking.

I'm totally confused by what he is trying to do.

Re: Need some help

SmugeeBear — Wed, 16 Aug 2023 17:07:31 GMT

Because you keep on mentioning port forwarding, and i'd said several times it might work for some things regarding it but it wont hence placing 192.168.1.98 into the DMZ.

Also i have tried changing the DHCP range on the hug that was the first thing i tried. didnt work because the hub will keep force assigning ip's even when on the DHCP toggle for use this ip address is unchecked.

again ip address 192.168.1.98 is static, the ip address for the pi's wlan port 192.168.1.183 i've tried to make static but the best i can do is try and force it to use the ip address mentioned.

for the hundreth time the smart hub 2 keep swapping ip addresses for different devices on the network whether its phones, fire tv boxes etc. it keeps replacing the the manually entered ip address 192.168.1.98 i've placed in the DMZ with the ip addresses of other devices and will swap ip addresses with different devices listed

the majority of these devices should have thier ip addresses reserved as the option us this ip address is turned on for them.

port forwarding isnt going to fix that issue as there obviously seems to be an issue with the smart hub 2 either its firmware or not.

because like i've mentioned previously this is becoming a bigger issue than the original issue this thread was originally created for