On 2/8/2002 Rogier R. Mulhuijzen [EMAIL PROTECTED] wrote:
RRM 1) Maybe the IP change isn't getting through to natd like it should.
RRM 2) Have ppp kill -9 natd on link down and start natd on linkup.
RRM Doc
Thank you for the suggestion, Doc. The IP change gets through to natd,
but the
I think I have to stick with the conventional setup, and go back to
trying to answer my original questions:
1. Why is the machine trying to send packets to its own previous IP?
2. How do I stop that?
1) Maybe the IP change isn't getting through to natd like it should.
2) Have ppp kill
I think I have to stick with the conventional setup, and go back to
trying to answer my original questions:
1. Why is the machine trying to send packets to its own previous IP?
2. How do I stop that?
I Well, for some brute-force debugging, maybe you can get some extra clues by
I
I'm starting to feel like I *almost* understand what's happening here. I'm
actually in the middle of making some changes to natd, but not to this part
of it. (I'm just fixing some bugs in the code that translates IRC DCC
control message packets.)
From the output you posted, things start out
I I'm starting to feel like I *almost* understand what's happening here. I'm
I actually in the middle of making some changes to natd, but not to this part
I of it. (I'm just fixing some bugs in the code that translates IRC DCC
I control message packets.)
I From the output you posted, things
Ian wrote:
Out [TCP] [TCP] 192.168.0.10:3979 - 207.69.200.225:110 aliased to
[TCP] 207.69.102.20:3979 - 207.69.200.225:110
Out [TCP] [TCP] 192.168.0.10:3979 - 207.69.200.225:110 aliased to
[TCP] 207.69.102.20:3979 - 207.69.200.225:110
Out [TCP] [TCP]
Thank you for your response, Rogier.
RRM 1) Have you told natd the interface is dynamic and might change IPs?
Yes, of course.
RRM 2) If you're using ppp, why even bother with natd? The NAT in ppp uses the
RRM exact same libalias and gives you less headaches with ipfw because the
RRM
M Thank you for your response, Rogier.
RRM 1) Have you told natd the interface is dynamic and might change IPs?
M Yes, of course.
RRM 2) If you're using ppp, why even bother with natd? The NAT in ppp uses the
RRM exact same libalias and gives you less headaches with ipfw because the
RRM
I think I have to stick with the conventional setup, and go back to
trying to answer my original questions:
1. Why is the machine trying to send packets to its own previous IP?
2. How do I stop that?
Well, for some brute-force debugging, maybe you can get some extra clues by
manually
DW On Sat, 2 Feb 2002, Marko wrote:
My question is concerning the popular netd[pid] failed to write
packet back [Permission denied] message.
DW This is caused by ipfw blocking packets after natd has translated them.
DW Check your firewall rules.
DW It might be an odd race of the rules
Natd is already running when a ppp session is set up each time. So is
ipfw. Ipfw is configured thourgh its own configuration file. So, it
seems I shouldn't have to set anything extra up in the ppp.linkup.
1) Have you told natd the interface is dynamic and might change IPs?
2) If you're
On Sat, 2 Feb 2002, Marko wrote:
My question is concerning the popular netd[pid] failed to write
packet back [Permission denied] message.
This is caused by ipfw blocking packets after natd has translated them.
Check your firewall rules.
It might be an odd race of the rules not getting
12 matches
Mail list logo
