# Standard Gateway Adress is set to Robot IP after restart

**URL:** <https://forum.universal-robots.com/t/standard-gateway-adress-is-set-to-robot-ip-after-restart/5064>\
**Category:** Technical Questions\
**Tags:** bugs\
**Created:** [September 5, 2019, 10:34am UTC](https://forum.universal-robots.com/t/standard-gateway-adress-is-set-to-robot-ip-after-restart/5064 "2019-09-05T10:34:01Z")\
**Posts on this page:** 9\
**Page:** 1

<div class="post-metadata">

**Author:** ![m.birkholz](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.universal-robots.com/m.birkholz/32/7084_2.png) [@m.birkholz](https://forum.universal-robots.com/u/m.birkholz)\
**Post date:** [September 5, 2019, 10:34am UTC](https://forum.universal-robots.com/t/standard-gateway-adress-is-set-to-robot-ip-after-restart/5064/1 "2019-09-05T10:34:01Z")

</div>

**Software version** : …5.4.3  
**Robot generation** : … UR10e #20195000516

**Steps to reproduce** :

1. First step  
Setup the STATIC IP Adress:  
Robot 192.168.100.5  
Mask 255.255.255.0  
Gateway 192.168.100.1

2. Second step  
Restart Robot

**Expected behavior** :  
Gateway Adress is Still 192.168.100.1  
**Actual behavior** :  
Gateway Adress is set to the Robots IP: 192.168.100.5

Having this Bug, we can’t use our desired Remote URCap Update solution so, @Ebbe, @jbm please fix this 🙂

---

<div class="post-metadata">

**Author:** ![Ebbe](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.universal-robots.com/ebbe/32/1413_2.png) [@Ebbe](https://forum.universal-robots.com/u/Ebbe)\
**Post date:** [September 6, 2019, 5:54am UTC](https://forum.universal-robots.com/t/standard-gateway-adress-is-set-to-robot-ip-after-restart/5064/2 "2019-09-06T05:54:07Z")

</div>

Does it work until you restart the robot?

---

<div class="post-metadata">

**Author:** ![m.birkholz](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.universal-robots.com/m.birkholz/32/7084_2.png) [@m.birkholz](https://forum.universal-robots.com/u/m.birkholz)\
**Post date:** [September 6, 2019, 6:27am UTC](https://forum.universal-robots.com/t/standard-gateway-adress-is-set-to-robot-ip-after-restart/5064/3 "2019-09-06T06:27:16Z")

</div>

Yes, but after restart, we can not initialize the remote SSH connection because of the overwritten Gateway Adress

---

<div class="post-metadata">

**Author:** ![Ebbe](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.universal-robots.com/ebbe/32/1413_2.png) [@Ebbe](https://forum.universal-robots.com/u/Ebbe)\
**Post date:** [September 6, 2019, 7:02am UTC](https://forum.universal-robots.com/t/standard-gateway-adress-is-set-to-robot-ip-after-restart/5064/4 "2019-09-06T07:02:18Z")

</div>

I tried to add it from the terminal using “route add default gw 192.168.100.1” and then it seems to be persisted.  
Hopefully this can work as a workaround until it is fixed.

---

<div class="post-metadata">

**Author:** ![mmi](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.universal-robots.com/mmi/32/691_2.png) [@mmi](https://forum.universal-robots.com/u/mmi)\
**Post date:** [September 6, 2019, 12:52pm UTC](https://forum.universal-robots.com/t/standard-gateway-adress-is-set-to-robot-ip-after-restart/5064/5 "2019-09-06T12:52:16Z")

</div>

Do you have Profinet enabled?

---

<div class="post-metadata">

**Author:** ![m.birkholz](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.universal-robots.com/m.birkholz/32/7084_2.png) [@m.birkholz](https://forum.universal-robots.com/u/m.birkholz)\
**Post date:** [September 6, 2019, 1:03pm UTC](https://forum.universal-robots.com/t/standard-gateway-adress-is-set-to-robot-ip-after-restart/5064/6 "2019-09-06T13:03:09Z")

</div>

Yes, Profinet has to be enabled.

---

<div class="post-metadata">

**Author:** ![m.birkholz](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.universal-robots.com/m.birkholz/32/7084_2.png) [@m.birkholz](https://forum.universal-robots.com/u/m.birkholz)\
**Post date:** [February 21, 2020, 11:09am UTC](https://forum.universal-robots.com/t/standard-gateway-adress-is-set-to-robot-ip-after-restart/5064/7 "2020-02-21T11:09:56Z")

</div>

this bug is still present. is there any suitable workaround? we actually overwrite the settings in the /etc/network/interfaces config file

---

<div class="post-metadata">

**Author:** ![m.birkholz](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.universal-robots.com/m.birkholz/32/7084_2.png) [@m.birkholz](https://forum.universal-robots.com/u/m.birkholz)\
**Post date:** [June 29, 2020, 5:49am UTC](https://forum.universal-robots.com/t/standard-gateway-adress-is-set-to-robot-ip-after-restart/5064/8 "2020-06-29T05:49:18Z")

</div>

Hi,

is there any news about this bug?

---

<div class="post-metadata">

**Author:** ![mmi](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.universal-robots.com/mmi/32/691_2.png) [@mmi](https://forum.universal-robots.com/u/mmi)\
**Post date:** [March 10, 2021, 11:36am UTC](https://forum.universal-robots.com/t/standard-gateway-adress-is-set-to-robot-ip-after-restart/5064/9 "2021-03-10T11:36:12Z")

</div>

As far as I understand this is not a bug in our profinet stack, but rather a feature of the protocol. For what we know is that PLC can overwrite some settings in network configuration.  
What kind of software and PLC are you using?  
We’re looking into our profinet stack now, so maybe some changes will appear soon.
