RE: (#67371691) [ISSUE REPORT] connman ipv4 server no response
이원영 <[email protected]> Fri, 05 Jun 2026 13:45:42 +0900
| Newsgroups | dev.linux.lists.connman |
|---|---|
| Message-ID | <20260605044542epcms1p5828aae799c74b4d70eb9a5c7d9218e49@epcms1p5> |
Dear connman server team, There are lots of VOCs caused by connman ipv4 server issue in Korea. And I am trying to access ticket URL which you shared before (https://suppo= rt.bytemark.co.uk/en/tickets/view/67371691), however, I could not access it. Could you share the current status? ---------Original Message--------- Sender: Bytemark <support=40bytemark.co.uk>=C2=A0=0D=0ADate:=202026-06-04= =2010:16=20(GMT+9)=0D=0ATitle:=20(=2367371691)=20=5BISSUE=20REPORT=5D=20con= nman=20ipv4=20server=20no=20response=0D=0A=0D=0A-=23-=23-=20Please=20reply= =20above=20this=20line=20-=23-=23-=0D=0A=0D=0ADear=20wy1115.lee=40samsung.c= om,=0D=0A=C2=A0=0D=0AWe=20have=20received=20your=20request=20and=20someone= =20will=20be=20looking=20at=20it=20shortly.We=20are=20committed=20to=20reso= lving=20every=20ticket=20as=20promptly=20as=20possible,=20and=20we=20encour= age=20you=20to=20let=20us=20know=20if=20you=20have=20anyadditional=20concer= ns=20or=20questions=20by=20replying=20to=20this=20email.You=20will=20receiv= e=20an=20email=20when=20any=20action=20has=20been=20taken=20on=20your=20tic= ket.=0D=0ATicket=20Details=0D=0ATicket=20=23:=2067371691=0D=0A=C2=A0Subject= :=20=5BISSUE=20REPORT=5D=20connman=20ipv4=20server=20no=20response=0D=0A=C2= =A0Department:=20Technical=20Support=0D=0A=C2=A0Status:=20Open=0D=0A=C2=A0P= riority:=20Standard=0D=0Awy1115.lee=40samsung.com=0D=0AUser=20-=2004/06/202= 6=2002:14=0D=0A=20Dear=20Marcel=20and=20connman=20server=20engineers,=0D=0A= =0D=0AHello,=20this=20is=20Wonyoung=20Lee=20working=20in=20Samsung=20Eletro= nics.=0D=0AI=20had=20reported=20connman=20server=20issue=20before=20Nov=202= 023.=0D=0A=0D=0AOne=20of=20Samsung=20device=20uses=20ipv4.connman.net/onlin= e/status.html=20to=20check=20internet=20connectivity.=0D=0AHowever,=20curre= ntly=20it=20has=20no=20responsed=20as=20timeout=20(CURL=20error=2028)=0D=0A= I=20have=20checked=20the=20issue=20in=20South=20Korea.=0D=0A=0D=0ACould=20p= lease=20you=20check=20it=20ASAP?=0D=0A=0D=0A=0D=0AThe=20following=20email= =20thread=20is=20the=20issue=20that=20I=20reported=20in=20Nov=202023.=0D=0A= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=0D=0AHi=20Lee,=0D=0A=0D=0A>=20Thank=20you=20= for=20quick=20fix.=0D=0A>=20It=20is=20very=20impressive=20experience=20for= =20me.=0D=0A>=20=0D=0A>=20=0D=0A>=20I=20hope=20to=20ask=20the=20following= =20questions.=0D=0A>=201.=20Could=20you=20share=20the=20reason=20of=20=22Co= nnection=20timeout=22=20if=20possible?=0D=0A>=202.=20When=20I=20face=20http= s://protect2.fireeye.com/v1/url?k=3D1976931a-78fd8651-19771855-74fe485fb305= -851354a353402d09&q=3D1&e=3Db29b7ab0-c5df-40c5-9f7f-1a01fa44f015&u=3Dhttp%3= A%2F%2Fipv4.connman.net%2Fonline%2Fstatus.html=20access=20issue,=20can=20I= =20report=20to=20this=20way?=20=0D=0A=0D=0Aafter=20fixing=20ipv6.connman.ne= t=20<https://protect2.fireeye.com/v1/url?k=3Dbe9ca340-df17b60b-be9d280f-74f= e485fb305-8fbadceb1da3c1e7&q=3D1&e=3Db29b7ab0-c5df-40c5-9f7f-1a01fa44f015&u= =3Dhttp%3A%2F%2Fipv6.connman.net%2F>=20it=20took=20away=20capacity=20from= =20ipv4.connman.net=20<https://protect2.fireeye.com/v1/url?k=3D853a0b6d-e4b= 11e26-853b8022-74fe485fb305-c3b592569573a2ff&q=3D1&e=3Db29b7ab0-c5df-40c5-9= f7f-1a01fa44f015&u=3Dhttp%3A%2F%2Fipv4.connman.net%2F>.=20Seems=20there=20a= re=20a=20lot=20of=20systems=20capable=20of=20IPv6=20these=20days=20compared= =20to=20back=20in=20the=20days=20when=20the=20service=20was=20created.=20Th= e=20majority=20is=20still=20IPv4,=20but=20I=20have=20seen=20substantial=20I= Pv6=20usage=20recently.=20So=20just=20increasing=20the=20capacity=20for=20I= Pv4=20leveled=20this=20back=20to=20normal.=0D=0A=0D=0AYou=20might=20have=20= noticed=20that=20ipv6.connman.net=20<https://protect2.fireeye.com/v1/url?k= =3Da6941fc0-c71f0a8b-a695948f-74fe485fb305-4fd99c96e08c8959&q=3D1&e=3Db29b7= ab0-c5df-40c5-9f7f-1a01fa44f015&u=3Dhttp%3A%2F%2Fipv6.connman.net%2F>=20wen= t=20through=20actually=20and=20ipv4.connman.net=20<https://protect2.fireeye= .com/v1/url?k=3D29c3bf12-4848aa59-29c2345d-74fe485fb305-6ed4e43dcdcfbd31&q= =3D1&e=3Db29b7ab0-c5df-40c5-9f7f-1a01fa44f015&u=3Dhttp%3A%2F%2Fipv4.connman= .net%2F>=20took=20a=20connection=20timeout=20hit=20every=20now=20and=20then= =20(still=20a=20large=20percentage=20succeeded).=20The=20preference=20of=20= answering=20IPv6=20over=20IPv4=20is=20something=20that=20I=20don=E2=80=99t= =20understand=20and=20I=20have=20to=20investigate=20(for=20pure=20personal= =20interest),=20but=20that=20should=20no=20longer=20be=20an=20issue.=0D=0A= =0D=0AIssues=20can=20be=20reported=20here=20or=20the=20newly=20created=20Sl= ack=20channel=20(which=20I=20still=20have=20to=20put=20into=20the=20README)= .=0D=0A=0D=0ARegards=0D=0A=0D=0AMarcel=0D=0A=3D=3D=3D=3D=3D=3D=3D=3D=0D=0AY= ou=20can=20review=20the=20ticket=20by=20going=20to:=0D=0A=C2=A0https://supp= ort.bytemark.co.uk/en/tickets/view/67371691=0D=0A=C2=A0=0D=0AKind=20Regards= ,=0D=0A=C2=A0Bytemark