Need some help

[SmugeeBear]

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.

[licquorice]

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.

[SmugeeBear]

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?

[licquorice]

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

[SmugeeBear]

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

[licquorice]

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.

[SmugeeBear]

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

[SmugeeBear]

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

[licquorice]

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.

[SmugeeBear]

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?