> I have been setting up dial-up ppp on my Linux 2.0.30 box
> with masquerading for my home 3xW95 box ethernet LAN and
> seem to have hit a brick (fire)wall :-<.
>
> I have been running a TCP/IP network using Samba for a few years
> now and have got this running very sweetly.
>
> But I have read all the FAQ's, HOWTOs, mini-HOWTOs and
> think that I have done everything correctly but the firewall won't
> forward.
>
> I'll run through what I've done so far and explain what I've seen.
>
> I start a ppp session by running the script /etc/ppp/melbpc/33k-loc
> This passes a 'phone number to /etc/ppp/melbpc/ppp-on
> which invokes the chat script /etc/ppp/melbpc/chatscript
> and uses /etc/ppp/melbpc/PAP-auth for the PAP authorisation
> dialog. At the conclusion of PAP (which the /var/log/debug file
> indicates is successful) the /etc/ppp/ip-up script is called with
> correct parameters. This creates the /etc/ppp/ip.$1 and
> /etc/ppp/ip.$1.server files correctly and calls the /etc/ppp/firewall.up
> script. (the /var/log/*.log files show the interface and configuration
> which
> results). The firewall.up script was lifted out of the MASQ-HOWTO
> and edited to use IP numbers from command-line arguments.
> The required modules (except ppp.o -- ppp support is compiled permanently
> into the kernel code - see /usr/src/Linux/linux.cfg in the enclosed .tar
> file) are
> loaded at boot time by the /etc/rc.d/rc.masq script which is called from
> the
> /etc/rc.d/rc.S script. (load is successful according to listings in
> /proc).
> I have enclosed a .tar file and a .zip file containing all the relevant
> configuration,
> script and log files for you to look at.
>
> <<masq.tar>> <<masq.zip>>
>
> A description of the events that led to the /var/log/debug,
> /var/log/messages and
> /var/log/syslog files.
>
> The log files were deleted, then the system was cold-booted. I ran the
> /etc/ppp/melbpc/33k-loc
> script. It timed out, syslog entry indicates that "could not find module
> ppp0" (but PPP support is
> compiled into the kernel???).
> Ran the script again, this time it went right through and successfully ran
> the firewall.up script.
> The /var/log/debug file shows that username & password was sent and
> received an ack.
>
> OK. Local W95 machine 192.168.12.4 tries to telnet to a melbpc nameserver
> at 203.12.152.1:23 -- the var/log/messages file shows that the firewall
> denies the required forwarding.
>
> The linux box 192.168.12.2 tries to telnet to emu.melbpc.org.au. The
> /var/log/messages file shows
> that several UDP packets to 203.12.152.1 (the melbpc nameserver) are
> denied forwarding.
>
> Why?
>
> =====================================
> _--_|\ [EMAIL PROTECTED] (Business)
> / DSTO \ Combatant Protection & Nutrition Branch, AMRL.
> \_.--._/ Defence Science & Technology Organisation
> v Fax : 61-3-9626 8410 Voice: 61-3-9626 8411
> Peter Sanders
> [EMAIL PROTECTED] (Private)
> Voice: 61-3-9337-6612
> BMW K100RT (Brunnhilde the Blue)
> =====================================
>
[demime 0.91c removed an attachment of type application/octet-stream which had a name
of masq.tar]
[demime 0.91c removed an attachment of type application/octet-stream which had a name
of masq.zip]
_______________________________________________
Masq maillist - [EMAIL PROTECTED]
http://tiffany.indyramp.com/mailman/listinfo/masq
Admin requests can be handled by web (above) or [EMAIL PROTECTED]
