Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

net: Dial/ListenPacket w/ "ip:protocol" net string doesn't work well #2654

Closed
mikioh opened this issue Jan 4, 2012 · 6 comments
Closed

net: Dial/ListenPacket w/ "ip:protocol" net string doesn't work well #2654

mikioh opened this issue Jan 4, 2012 · 6 comments
Labels
FrozenDueToAge
Milestone
Go1

Comments

@mikioh
Copy link
Contributor

mikioh commented Jan 4, 2012 

On tip:
a) Dial cannot accept "ip:protocol" as net string,
b) ListenPacket has a bug which is misunderstanding on an err value from splitNetProto.
@adg
Copy link
Contributor

adg commented Jan 4, 2012

Comment 1:

Labels changed: added priority-go1.

@dhobsd
Copy link
Contributor

dhobsd commented Jan 8, 2012

Comment 3:

Hey Mikioh,
I wanted to look into this today, but I'm unable to reproduce issues with Dial
(net.Dial("tcp", "127.0.0.1:http") worked fine for me on current tip, and I was able to
read/write data on the returned TCPConn), and I don't quite understand what you mean
with regards to ListenPacket handling errors from splitNetProto. Could you provide some
sample code and / or explain further?
Thanks much!

@mikioh
Copy link
Contributor Author

mikioh commented Jan 8, 2012

Comment 4:

a) Dial("ip4:ospf", ...) dosen't work well. Also it might be nice if the 
Dial for raw IP sockets works with "" addr string.
b) In LinstenPacket "if rawnet, _, err = splitNetProto(net); err != nil" 
is wrong.

@robpike
Copy link
Contributor

robpike commented Jan 13, 2012

Comment 5:

Owner changed to builder@golang.org.

@mikioh
Copy link
Contributor Author

mikioh commented Jan 13, 2012

Comment 6:

Owner changed to @mikioh.

@mikioh
Copy link
Contributor Author

mikioh commented Jan 21, 2012

Comment 7:

This issue was closed by revision 68daa41.

Status changed to Fixed.

@rsc rsc added this to the Go1 milestone Apr 10, 2015
@rsc rsc removed the priority-go1 label Apr 10, 2015
@golang golang locked and limited conversation to collaborators Jun 24, 2016
This issue was closed.
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
FrozenDueToAge
Projects
None yet
Milestone
Go1
Development

No branches or pull requests
6 participants
@mikioh @rsc @dhobsd @robpike @adg @gopherbot