From: Mark Frey <markfrey@sympatico.ca>
To: Owain McGuire <owain@ofrm.demon.co.uk>
Cc: linux-diald@vger.kernel.org
Subject: Re: tap0 or ppp0?
Date: Fri, 21 Mar 2003 21:02:47 -0500 [thread overview]
Message-ID: <3E7BC447.5050309@sympatico.ca> (raw)
In-Reply-To: <009d01c2efcb$778cf040$0200000a@tower>
Hi Owain,
I'm not sure what your firewall script looks like, but I think it will
have to have masquerade rules for both the ppp0 and tap0 interfaces.
It sounds like there are no forward/masq rules for tap0, so diald
doesn't get any packets from the masqueraded machines if the link is down.
You might try to edit the script and duplicate the masq rules
substituting tap0 for ppp0.
Hope that helps!
Mark.
Owain McGuire wrote:
> Simple question really??
>
> I have upgraded from diald 0.9 to 1.0 and sorted out all of the
> ethertap stuff. The only thing is that the masqueraded machines don't
> seem to be able to bring up the ppp connections themselves. The
> "server" machine can though. I have followed the IP_Masq_Howto for
> 2.4 kernels but I have a question for the rc.firewall-2.4 script.
> Should the external interface be tap0 or ppp0? I am confused as to
> how the flow or handoever of traffic from tap0 to ppp0 works.
>
> I currently have it set to ppp0 which seems fine when the link is up
> since ifconfig gives me:
>
> ppp0 Link encap:Point-to-Point Protocol
> inet addr:158.152.189.169 P-t-P:158.152.1.222
> Mask:255.255.255.255
> UP POINTOPOINT RUNNING NOARP MULTICAST MTU:1500 Metric:1
> RX packets:3520 errors:0 dropped:0 overruns:0 frame:0
> TX packets:3294 errors:0 dropped:0 overruns:0 carrier:0
> collisions:0 txqueuelen:3
> RX bytes:1531219 (1.4 Mb) TX bytes:250596 (244.7 Kb)
>
> tap0 Link encap:Ethernet HWaddr FE:FD:00:00:00:00
> UP BROADCAST RUNNING NOARP MULTICAST MTU:1500 Metric:1
> RX packets:2 errors:0 dropped:0 overruns:0 frame:0
> TX packets:2 errors:0 dropped:0 overruns:0 carrier:0
> collisions:0 txqueuelen:0
> RX bytes:142 (142.0 b) TX bytes:142 (142.0 b)
> Interrupt:5
>
> But when the link is down it is:
>
> tap0 Link encap:Ethernet HWaddr FE:FD:00:00:00:00
> inet addr:158.152.189.169 Bcast:0.0.0.0
> Mask:255.255.255.255
> UP BROADCAST RUNNING NOARP MULTICAST MTU:1500 Metric:1
> RX packets:2 errors:0 dropped:0 overruns:0 frame:0
> TX packets:2 errors:0 dropped:0 overruns:0 carrier:0
> collisions:0 txqueuelen:0
> RX bytes:142 (142.0 b) TX bytes:142 (142.0 b)
> Interrupt:5
>
> which suggests that ppp0 as an external interface is wrong.
>
> Or is it that my default route isn't set up correctly? Should it not
> point to tap0?
>
> Destination Gateway Genmask Flags Metric Ref
> Use Iface
> demon-du.demon. * 255.255.255.255 UH 0 0
> 0 ppp0
> 10.0.0.0 * 255.255.255.0 U 0 0
> 0 eth0
> loopnet * 255.0.0.0 U 0 0
> 0 lo
> default * 0.0.0.0 U 0 0
> 0 ppp0
>
>
> Thanks in advance.
>
> O.
>
>
>
> -
> To unsubscribe from this list: send the line "unsubscribe linux-diald" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
next prev parent reply other threads:[~2003-03-22 2:02 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-21 17:01 tap0 or ppp0? Owain McGuire
2003-03-22 2:02 ` Mark Frey [this message]
2003-03-30 23:22 ` Mike Jagdis
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=3E7BC447.5050309@sympatico.ca \
--to=markfrey@sympatico.ca \
--cc=linux-diald@vger.kernel.org \
--cc=owain@ofrm.demon.co.uk \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.