This is the new home of the egghelp.org community forum.
All data has been migrated (including user logins/passwords) to a new phpBB version.
For more information, see this announcement post . Click the X in the top right-corner of this box to dismiss this message.
Old posts that have not been replied to for several years.
r
ribe
Post
by ribe » Sun Jan 06, 2002 9:13 pm
My problem is as subject.
[00:05] Refused 217.208.96.01/64909 (bad src port)
Never ever experienced this problem!?!
Any suggestions in the solving of this?
Is it the the hub bots problem or the "client bot"? I have tried linking both ways and it is the same problem.
ppslim
Revered One
Posts: 3914 Joined: Sun Sep 23, 2001 8:00 pm
Location: Liverpool, England
Post
by ppslim » Sun Jan 06, 2002 9:50 pm
Now you have either changed the output you gave, or somthing is screwed.
An IP ending with 01
r
ribe
Post
by ribe » Mon Jan 07, 2002 8:59 am
Very stupid of me, it should be .1
Well the ip adress is correct.
ppslim
Revered One
Posts: 3914 Joined: Sun Sep 23, 2001 8:00 pm
Location: Liverpool, England
Post
by ppslim » Mon Jan 07, 2002 11:58 am
By any chance, are you lining windrops to eggdrops?
r
ribe
Post
by ribe » Mon Jan 07, 2002 1:30 pm
This is two eggdrops running eggdrop-1.6.7 on two proper working OpenBSD machines. Ports are open on the FW to them to communicate. And there are no filters for outgoing traffic.
I managed to link them when using simple.conf
but not now with the advanced.conf. Maybe the problem can be there?
Note. I tried setting up an eggdrop from an other location with the same config file (modified ofcourse) and I recive the same error.
ppslim
Revered One
Posts: 3914 Joined: Sun Sep 23, 2001 8:00 pm
Location: Liverpool, England
Post
by ppslim » Mon Jan 07, 2002 4:52 pm
Try changing the portrange values in the config files.
guppy
eggdrop engineer
Posts: 199 Joined: Mon Sep 24, 2001 8:00 pm
Location: Canada
Contact:
Post
by guppy » Wed Jan 09, 2002 12:27 am
On 2002-01-07 13:52, ppslim wrote:
Try changing the portrange values in the config files.
*nod* This is the reason <g>
This is why I removed that setting in newer 1.6.x (I think 1.6.7+).
Jeff