On Wed, Oct 23, 2002 at 09:25:30AM +0100, Randy Orrison wrote:
> | -----Original Message-----
> | From: [EMAIL PROTECTED] [mailto:shaulka@;bezeqint.net]
> | Sent: 22 October 2002 15:54
> |
> | One advantage of PCI is that irq/port are done automatically
> | for you, or so I believe. Is the card a PCI type of card? You
> | might also try lspci for more readable output.
>
> I now have the card recognized and dialling out, and the connection sort
> of works. Here's my setup: My debian box has an internal ISDN card and
> an external modem. I'm running pdnsd
I am not familiar with pdnsd. I will igonre it but someone else might be
able to tell whether it gets in the way.
> and squid and ipmasq. I'm
> connecting to the internet from a Windows box using the squid cache on
> my debian box. Using pppd and the external modem everything works fine
> (but at the speed you'd expect for a modem). Using isdnutils and ipppd
> and the internal ISDN card when I try to access a site there's a really
> long delay (after the ISDN card connects to my ISP) and then the whole
> page appears wonderfully quickly. Click a link, long delay then fast
> load. Click a link: long delay and fast load (and sometimes it doesn't
> load at all). It's not disconnecting in between. I'm not sure where to
> look... I have noticed that the routing information is different
> between the ppp setup and ippp.
>
> Here's the output of route -n when using ppp:
> debian:/etc# route -n
> Kernel IP routing table
> Destination Gateway Genmask Flags Metric Ref
> Use Iface
> 195.92.168.34 0.0.0.0 255.255.255.255 UH 0 0
> 0 ppp0
> 10.0.0.0 0.0.0.0 255.255.255.0 U 0 0
> 0 eth0
> 0.0.0.0 195.92.168.34 0.0.0.0 UG 0 0
> 0 ppp0
>
> (My internal network addresses are 10.0.0.*)
>
> Here's the output when using ippp:
> debian:/etc# route -n
> Kernel IP routing table
> Destination Gateway Genmask Flags Metric Ref
> Use Iface
> 195.92.168.33 0.0.0.0 255.255.255.255 UH 0 0
> 0 ippp0
> 10.0.0.0 0.0.0.0 255.255.255.0 U 0 0
> 0 eth0
> 0.0.0.0 0.0.0.0 0.0.0.0 U 0 0
> 0 ippp0
>
There should be a /etc/ppp/ip-up.d/00-ipppd that is taking care of the
default route setting. At least with this is how things are done here.
> But I've tried manually deleting the default route and recreating it
> with the gateway set and that hasn't made any difference. I don't know
> what else to look at...
Are you sure you run the correct commands? Perhaps you can run the
commands in /etc/ppp/ip-up.d/00-ipppd manually one after the other?
Nothing else that I can think of at the moment.
>
> Here's the section of /var/log/messages where it dials out on the isdn
> card:
> Oct 23 09:19:05 debian ipppd[24716]: Found 1 device:
> Oct 23 09:19:05 debian ipppd[24718]: ipppd i2.2.12 (isdn4linux version
> of
> pppd by MH) started
> Oct 23 09:19:05 debian ipppd[24718]: init_unit: 0
> Oct 23 09:19:05 debian ipppd[24718]: Connect[0]: /dev/ippp0, fd: 8
> Oct 23 09:19:12 debian kernel: OPEN: 10.0.0.1 -> 212.58.224.112 TCP,
> port: 61151 -> 80
That line is of no relevance here, isn't it?
> Oct 23 09:19:12 debian kernel: ippp0: dialing 1 08089916001...
> Oct 23 09:19:13 debian kernel: HiSax: W6692 XDUN/XCOL
> Oct 23 09:19:15 debian ipppd[24718]: Local number: 29, Remote number:
> 0808xxxxxxx, Type: outgoing
> Oct 23 09:19:15 debian ipppd[24718]: PHASE_WAIT -> PHASE_ESTABLISHED,
> ifunit: 0, linkunit: 0, fd: 8
> Oct 23 09:19:15 debian kernel: isdn_net: ippp0 connected
> Oct 23 09:19:16 debian ipppd[24718]: Remote message:
> Oct 23 09:19:16 debian ipppd[24718]: MPPP negotiation, He: No We: No
> Oct 23 09:19:19 debian ipppd[24718]: local IP address 62.136.208.169
> Oct 23 09:19:19 debian ipppd[24718]: remote IP address 195.92.168.33
> Oct 23 09:19:21 debian kernel: Packet log: output DENY ippp0 PROTO=1
> 62.136.208.169:8 195.92.195.95:0 L=28 S=0x00 I=40215 F=0x0000
> T=64 (#8)
> Oct 23 09:19:21 debian kernel: IP_MASQ:ip_fw_masquerade(): change
> masq.addr
> from 10.0.0.1 to 62.136.208.169
> Oct 23 09:19:21 debian kernel: Packet log: output DENY ippp0 PROTO=6
> 62.136.208.169:61151 212.58.224.112:80 L=48 S=0x00 I=14114
> F=0x4000 T=127 SYN (#8)
>
Isn't your firewall denies desirable connections because the firewall
gets confused about 62.136.208.169, which is actually one of your
interfaces?
> Any suggestions, or is there any other info that would be useful?
>
> Thanks!
>
> Randy Orrison
>
>
> --
> To UNSUBSCRIBE, email to [EMAIL PROTECTED]
> with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
>
--
Shaul Karl, [EMAIL PROTECTED] e t
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
