To test your binkd just send a file "test" to 2:221/6; the callback service will call you back!
04 Nov 16 09:05, Tommi Koivula wrote to Miguel Ortiz:
To test your binkd just send a file "test" to 2:221/6; the callback
service will call you back!
A question about your callback service...
How do you get the IP for your return call?
Do you do a nodelist lookup on the address, build a f.n.z.binkp.net,
or use the IP that you connected with when you got the "test" file?
How do you get the IP for your return call?
First try the ip address where the call is coming. If that fails, and
the caller is nodelisted, then try the address in the nodelist.
09 Jun 17 17:19, Tommi Koivula wrote to Fred Riccio:
How do you get the IP for your return call?
First try the ip address where the call is coming. If that fails,
and the caller is nodelisted, then try the address in the
nodelist.
Ok, Thanks. I was asking because I thought my system had gone
unreachable possibly because of a DNS update problem. I hadn't seen
any incoming connects for almost a month, so I tried your callback service. Then I started wondering if it was a valid test for the
problem I was investigating. As it turns out it wasn't valid. Since
then I've had incoming sessions, so I know I'm OK.
I can connect you. :)
Sysop: | digital man |
---|---|
Location: | Riverside County, California |
Users: | 1,027 |
Nodes: | 17 (0 / 17) |
Uptime: | 62:07:48 |
Calls: | 502,334 |
Calls today: | 2 |
Files: | 100,779 |
D/L today: |
10,523 files (928M bytes) |
Messages: | 300,074 |