Date: Wed, 15 Nov 2000 17:03:37 +0000 From: John Murphy <john253@crosswinds.net> To: questions@freebsd.org Subject: hisaddr = 10.0.0.1 ? Message-ID: <c7751tot3dm6ivgvdbn2lrqa084romg5dt@4ax.com>
next in thread | raw e-mail | index | archive | help
I think I may have broken my ISP. My home network firewall/gateway runs FreeBSD-4.1 Release. ppp facilitates both firewall and nat. Its private IP is 10.0.0.2 I mainly use a win95 pc with IP 10.0.0.1 'lexx.my.domain'. Everything worked well until yesterday after a new custom kernel #5, some changes to rc.conf and a mouse/modem port change around. ppp runs in -auto -nat mode, and checking for e-mail with lexx to an SMTP server dialed and connected to the ISP as usual, but the SMTP connection timed out, as did http requests. ifconfig -a on 10.0.0.2 (wall.my.domain) showed a usual address for myaddr eg. 195.222.222.222 but hisaddr =3D 10.0.0.1 Connections to other ISPs worked fine and obtain a valid hisaddr. I changed lexx to 10.0.0.3 and SMTP and HTTP works ok but ifconfig still shows 10.0.0.1 for hisaddr. I was convinced it was 'me' due to the coincidental 10.0.0.1 so I logged IPCP and found the following: IPCP: Using trigger address 0.0.0.0=20 Phase: deflink: lcp -> open=20 Phase: bundle: Network=20 IPCP: FSM: Using "deflink" as a transport=20 IPCP: deflink: State change Initial --> Closed=20 IPCP: deflink: LayerStart.=20 IPCP: deflink: SendConfigReq(1) state =3D Closed=20 IPCP: IPADDR[6] 0.0.0.0=20 IPCP: COMPPROTO[6] 16 VJ slots with slot compression=20 IPCP: deflink: State change Closed --> Req-Sent=20 IPCP: deflink: RecvConfigReq(1) state =3D Req-Sent # The line above is RecvConfigReq(12) with another 'good' ISP. # What do these numbers refer to ^^ ? IPCP: IPADDR[6] 10.0.0.1=20 IPCP: deflink: SendConfigAck(1) state =3D Req-Sent=20 IPCP: IPADDR[6] 10.0.0.1=20 IPCP: deflink: State change Req-Sent --> Ack-Sent=20 IPCP: deflink: RecvConfigRej(1) state =3D Ack-Sent # I only get the 'Rej' above with the 'faulty' ISP IPCP: COMPPROTO[6] 16 VJ slots with slot compression=20 IPCP: deflink: SendConfigReq(2) state =3D Ack-Sent=20 IPCP: IPADDR[6] 0.0.0.0=20 IPCP: deflink: RecvConfigNak(2) state =3D Ack-Sent=20 IPCP: IPADDR[6] 195.222.222.222=20 IPCP: IPADDR[6] changing address: 0.0.0.0 --> 195.222.222.222 IPCP: deflink: SendConfigReq(3) state =3D Ack-Sent=20 IPCP: IPADDR[6] 195.222.222.222=20 IPCP: deflink: RecvConfigAck(3) state =3D Ack-Sent=20 IPCP: deflink: State change Ack-Sent --> Opened=20 IPCP: deflink: LayerUp.=20 IPCP: myaddr 195.222.222.222 hisaddr =3D 10.0.0.1=20 (myaddr numbers changed 'cause their server is probably insecure, as is, and I don't want to broadcast the fact) After changing back the rc.conf changes I had made, and reverting to the previous kernel with no improvement, I got a friend who uses the same ISP with a straight win95 DUN to enable his ppp logging. He gets the same IP for hisaddr! So I guess it's 'them'. Thing is, I'd love to be able to tell them what's wrong, but I still feel I may have caused it somehow. Is it possible? =46or my own education purposes bpf is enabled in the firewall/gateway kernel and tcpdump was in use on tun0 before the problem started. Sorry this has been a long question and probably OT. Thanks again John. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?c7751tot3dm6ivgvdbn2lrqa084romg5dt>