# Default 192.168.1.0/24 network issues behind some routers **URL:** \ **Category:** Atom\ **Created:** [December 30, 2016, 5:35am UTC](https://community.na.baicells.com/t/default-192-168-1-0-24-network-issues-behind-some-routers/185 "2016-12-30T05:35:41Z")\ **Posts on this page:** 3\ **Page:** 1
**Author:** ![jeremylu](https://avatars.discourse-cdn.com/v4/letter/j/58956e/32.png) [@jeremylu](https://community.na.baicells.com/u/jeremylu)\ **Post date:** [December 30, 2016, 5:35am UTC](https://community.na.baicells.com/t/default-192-168-1-0-24-network-issues-behind-some-routers/185/1 "2016-12-30T05:35:42Z")
Most of our customers have TP-Link routers, which are 192.168.0.0/24 by default, so the 192.168.1.1 gateway the CPE has is conflicting. Bridge mode is advantageous here, but seems to not be recommended/usable from BaiCells support, so we haven’t tried it. What we did do was change the network on the CPE to 192.168.15.0. Having 2 routers directly behind each other both at 192.168.1.1 is likely to cause numerous issues ---
**Author:** ![jeremylu](https://avatars.discourse-cdn.com/v4/letter/j/58956e/32.png) [@jeremylu](https://community.na.baicells.com/u/jeremylu)\ **Post date:** [December 30, 2016, 5:38am UTC](https://community.na.baicells.com/t/default-192-168-1-0-24-network-issues-behind-some-routers/185/2 "2016-12-30T05:38:16Z")
Whoops, my first sentence is what is conflicting, I meant other routers that have a 192.168.1.1 are having issues, not the TP-Link which is 192.168.0.1 ---
**Author:** ![rick.harnish](https://sea2.discourse-cdn.com/flex016/user_avatar/community.na.baicells.com/rick.harnish/32/17_2.png) [@rick.harnish](https://community.na.baicells.com/u/rick.harnish)\ **Post date:** [December 30, 2016, 5:57pm UTC](https://community.na.baicells.com/t/default-192-168-1-0-24-network-issues-behind-some-routers/185/3 "2016-12-30T17:57:30Z")
Jeremy, We expect L2 bridging to be available in the next CPE firmware upgrade.