Thanks, I appreciate all suggestions. My linux server is assigned a static
class 1 address (10.1.1.1) as are the other machines on my LAN (10.2.2.2
etc, when they are turned on). However, I am using dynamic address
allocation when connecting to my ISP on linux.
In my diald.conf I am using my real local IP address for 'local' (10.1.1.1)
and a fictional class 1 address (10.0.0.2) for 'remote'.
Here is the output for ifconfig and my routing table if I force diald to
quit:
# ifconfig
lo Link encap:Local Loopback
inet addr:127.0.0.1 Bcast:127.255.255.255 Mask:255.0.0.0
UP BROADCAST LOOPBACK RUNNING MTU:3584 Metric:1
RX packets:81 errors:0 dropped:0 overruns:0 frame:0
TX packets:81 errors:0 dropped:0 overruns:0 carrier:0
collisions:0
eth0 Link encap:Ethernet HWaddr 00:A0:CC:23:0C:F4
inet addr:10.1.1.1 Bcast:10.255.255.255 Mask:255.255.255.0
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:461 errors:0 dropped:0 overruns:0 frame:0
TX packets:409 errors:0 dropped:0 overruns:0 carrier:0
collisions:0
Interrupt:11 Base address:0xe400
# route-n
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use
Iface
10.1.1.0 0.0.0.0 255.255.255.0 U 0 0 4 eth0
127.0.0.0 0.0.0.0 255.0.0.0 U 0 0 6 lo
And here is the output for ifconfig and my routing table when diald is up
(and regrettably my ISP connection is live full-time):
# ifconfig
lo Link encap:Local Loopback
inet addr:127.0.0.1 Bcast:127.255.255.255 Mask:255.0.0.0
UP BROADCAST LOOPBACK RUNNING MTU:3584 Metric:1
RX packets:77 errors:0 dropped:0 overruns:0 frame:0
TX packets:77 errors:0 dropped:0 overruns:0 carrier:0
collisions:0
eth0 Link encap:Ethernet HWaddr 00:A0:CC:23:0C:F4
inet addr:10.1.1.1 Bcast:10.255.255.255 Mask:255.255.255.0
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:309 errors:0 dropped:0 overruns:0 frame:0
TX packets:278 errors:0 dropped:0 overruns:0 carrier:0
collisions:0
Interrupt:11 Base address:0xe400
sl0 Link encap:Serial Line IP
inet addr:10.1.1.1 P-t-P:10.0.0.2 Mask:255.0.0.0
UP POINTOPOINT RUNNING MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:11 errors:0 dropped:0 overruns:0 carrier:0
collisions:0
ppp0 Link encap:Point-to-Point Protocol
inet addr:207.208.139.103 P-t-P:207.208.2.81 Mask:255.255.255.0
UP POINTOPOINT RUNNING MTU:1500 Metric:1
RX packets:262 errors:0 dropped:0 overruns:0 frame:0
TX packets:295 errors:0 dropped:0 overruns:0 carrier:0
collisions:0
Memory:6ba1038-6ba1c04
# route -n
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use
Iface
10.0.0.2 0.0.0.0 255.255.255.255 UH 0 0 0 ppp0
10.0.0.2 0.0.0.0 255.255.255.255 UH 1 0 0 sl0
207.208.2.81 0.0.0.0 255.255.255.255 UH 0 0 0 ppp0
10.1.1.0 0.0.0.0 255.255.255.0 U 0 0 4 eth0
127.0.0.0 0.0.0.0 255.0.0.0 U 0 0 6 lo
0.0.0.0 0.0.0.0 0.0.0.0 U 0 0 36 ppp0
0.0.0.0 0.0.0.0 0.0.0.0 U 1 0 10 sl0
Do you see any problems with the diald.conf or output that I've listed?
Regards,
Jeff Rudnick
> -----Original Message-----
> From: Hutton, John W [mailto:[EMAIL PROTECTED]]
>
> What's your output of ifconfig and route -n look like? Also what
> is in your
> diald.conf? The addresses used in diald.conf have to be different
> than your
> ISP or your local net. These are just dummy addresses used for slip. When
> you connect, your PPP interface will have the correct IP
> addresses assigned
> by your ISP. I'm assuming that you are using dynamic address allocation.
>
> -----Original Message-----
> From: Jeffrey P. Rudnick [mailto:[EMAIL PROTECTED]]
>
> I did add debug 31 to my diald.conf and restarted the daemon. Of course
> there are many messages in /var/log/messages. At the time the link starts
> up, I do see the following message which looks suspicious:
>
> Aug 24 20:44:51 redhat1 diald[1183]: filter accepted rule 1
> proto17 len 160
> packet 207.208.139.10,513 => 10.255.255.255,513
>
> Regrettably, I don't know if this message is applicable. Or should I be
> looking at messages from named or some other daemon? If someone knows if
> the above message is meaningful, please let me know how to interpret and
> change my configuration to restrict diald connections to when deliberate
> attempts to connect are made.
>
>
> > -----Original Message-----
> > From: Hutton, John W [mailto:[EMAIL PROTECTED]]
>
> > You can access your log file by typing in tail -f /var/log/messages. I
> > usually do this on a second console (ALT - F2). You can increase
> > your debug
> > level in diald by putting in debug 31 in your diald.conf file.
> This should
> > help you see what causing the link to stay up. I have the same
> > problem, but
> > it's related to another interface (satellite link). Good luck!
> >
-
To unsubscribe from this list: send the line "unsubscribe linux-diald" in
the body of a message to [EMAIL PROTECTED]
