On Sat, 18 May 2002, David Smead wrote:
> Tom,
>
> thevenin:/etc# cat /proc/sys/net/ipv4/ip_forward
> 1
>
> I did that explicitly. I probably should have installed shorewall but
> since all I want to do is forward all traffic between two internal nets I
> figured it would be easy enough just t
added list back in in case others are interested. They carry three types of ide to
compact flash adapters. There
is a new model shipping next week that plugs right into the motherboard without a
cable called CFDISK.5b. It is the
cheapest - $13 + shipping etc.
http://pcengines.com/testordr.htm
On Sat, 18 May 2002, David Smead wrote:
> I probably should have installed shorewall but since all I want to do is
> forward all traffic between two internal nets I figured it would be easy
> enough just to dump a few rules into iptables.
>
> Wrong!
>
Looks like it's time to dig out tcpdump
Tom,
thevenin:/etc# cat /proc/sys/net/ipv4/ip_forward
1
I did that explicitly. I probably should have installed shorewall but
since all I want to do is forward all traffic between two internal nets I
figured it would be easy enough just to dump a few rules into iptables.
Wrong!
thevenin:/etc/
On Sat, 18 May 2002, David Smead wrote:
> Tom,
>
> Thanks for the reply. Here's route on the 192.168.3.245. eth0 is down,
> otherwise it would have the route you suggest.
>
> knuth:/etc/init.d# route -n
> Kernel IP routing table
> Destination Gateway Genmask Flags Metric Ref
Tom,
Thanks for the reply. Here's route on the 192.168.3.245. eth0 is down,
otherwise it would have the route you suggest.
knuth:/etc/init.d# route -n
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use Iface
192.168.3.0 0.0.0.0 255.255.255.0
On Sat, 18 May 2002, David Smead wrote:
> I'm playing with forwarding using a couple of Debian machines, before
> finalizing a Bering firewall.
>
> I'm missing something.
>
> 192.168.3.245 is connected to 192.168.3.254. The latter also has a NIC on
> 192.168.8.24. There are other machines on
I'm playing with forwarding using a couple of Debian machines, before
finalizing a Bering firewall.
I'm missing something.
192.168.3.245 is connected to 192.168.3.254. The latter also has a NIC on
192.168.8.24. There are other machines on the .8.0/24 network.
I can ping 192.168.8.24 from 192.
On Sat, 2002-05-18 at 14:35, Michael Leone wrote:
> Now this is embarassing ...
>
> I just had to reboot my dachstein (floppy) router/firewall for the first
> time in 108 days. And now I've forgotten my root password . :-(
>
> I must have changed it, and forgotten what it was.
>
> Ordinarily, I
Now this is embarassing ...
I just had to reboot my dachstein (floppy) router/firewall for the first
time in 108 days. And now I've forgotten my root password . :-(
I must have changed it, and forgotten what it was.
Ordinarily, I would do a "linux single" at the boot prompt. Except that
there's
With the help of Dave Anderson, I have added a new chapter in the Bering
user's guide which covers PPPoA connections. It comes with the 2.4.0b2
patched version of pppd which is the only one providing a functionnal
pppoatm.so plugin for pppd.
http://leaf.sf.net/devel/jnilo/busers.html
I think t
On Sat, 2002-05-18 at 00:40, David Douthitt wrote:
> I've the following configuration:
>
> [host1/ssh]>[Oxygen/Masq/PPP]-->[ISPDialup/PPP]>[host2/ssh]
>
> The forwarding is from port 110 (POP3) or 143 (IMAP) to host2.
> Unfortunately, host2 now seems to think that the route to host1 is
I've the following configuration:
[host1/ssh]>[Oxygen/Masq/PPP]-->[ISPDialup/PPP]>[host2/ssh]
The forwarding is from port 110 (POP3) or 143 (IMAP) to host2.
Unfortunately, host2 now seems to think that the route to host1 is
over the net instead of over the ssh tunnel. What did I do w
Brad Fritz wrote:
> > My goal is to mail the dyanmaic ip address to another client. The
> > client needs to ssh to backup files on a LEAF protected network.
>
> It seems like you should be able to use the dhclient hooks and
> the the mail command to do exactly what you want. I've never
> pla
14 matches
Mail list logo
