I found that it is the problem of routing on my test machine on the
192.168.1.0/24 network, fixed.
On Thursday 27 October 2011 18:08:06 you wrote:
> I'm now on a router in 3 networks, where eth0 and eth1 are in 2 LANs and
> eth2 are in a WAN. Here are the details:
>
> root@debian:/home/michael#
I'm now on a router in 3 networks, where eth0 and eth1 are in 2 LANs and eth2
are in a WAN. Here are the details:
root@debian:/home/michael# ifconfig
eth0 Link encap:Ethernet HWaddr 00:e0:4c:4d:77:06
inet addr:192.168.1.1 Bcast:192.168.1.255 Mask:255.255.255.0
inet6
Mike, Alex & others,
Sorry for the broken thread.
mb> 2) That joule knows the route to cantor (via dalton)
Just what I was missing; thanks!
Now, where to specify this route?
(1) "up route add ..." can not go in the eth0
stanza in /etc/network/interfaces because
tun0 is configured after eth
On Sat, Aug 02, 2008 at 10:18:17PM -0700, Mike Bird wrote:
> On Sat August 2 2008 18:31:40 [EMAIL PROTECTED] wrote:
> > My network is illustrated here now.
> > http://carnot.pathology.ubc.ca/Network.jpg
[snip]
> > "no connection".
>
> That routing table shows that dalton knows the route to joule
On Sat August 2 2008 18:31:40 [EMAIL PROTECTED] wrote:
> My network is illustrated here now.
> http://carnot.pathology.ubc.ca/Network.jpg
>
> Forwarding is always on.
> dalton:~# cat /proc/sys/net/ipv4/ip_forward
> 1
> Even without such a command this is the routing
> table on Dalton.
> Accor
Alex & others,
My network is illustrated here now.
http://carnot.pathology.ubc.ca/Network.jpg
Forwarding is always on.
dalton:~# cat /proc/sys/net/ipv4/ip_forward
1
as> ... routing tables commands have a look at man ip
OK; I've read route.man and ip.man.
as> for a machine at local lan a (say 1
On Sun, Jul 27, 2008 at 06:10:19PM -0700, [EMAIL PROTECTED] wrote:
> Alex and others,
>
> as> for a machine at local lan a (say 192.168.0.100)
> to talk to a machine at local lab b ( say 192.168.2.200).
> I would need a route on the gateway box in
> local lan A something like
> ip r a 192.168.
Alex and others,
as> for a machine at local lan a (say 192.168.0.100)
to talk to a machine at local lab b ( say 192.168.2.200).
I would need a route on the gateway box in
local lan A something like
ip r a 192.168.2.0/24 via 192.168.1.2
That command uses iptables doesn't it?
It seems reasonab
On Sun, Jul 27, 2008 at 10:03:50AM -0700, [EMAIL PROTECTED] wrote:
> Alex,
>
> > net.ipv4.ip_forward=1
> as> This is allow the kernel to do packet forwarding
>
> No problem there. My LAN machines have
> no problems accessing the 'net for http,
> pop3, ftp
Alex,
> net.ipv4.ip_forward=1
as> This is allow the kernel to do packet forwarding
No problem there. My LAN machines have
no problems accessing the 'net for http,
pop3, ftp.
as> turn which on ?
TUN packet forwarding through the firewall
(ref. original message, last weekend.)
ip_forward"
>
> That is an interactive approach whereas in /etc/sysctl.conf I set
> net.ipv4.ip_forward=1
This is allow the kernel to do packet forwarding
> .
>
> "man openvpn" continues,
> "... enable TUN packet forwarding through the firewall:
rward=1
.
"man openvpn" continues,
"... enable TUN packet forwarding through the firewall:
iptables -A FORWARD -i tun+ -j ACCEPT"
>From this I infer that permission for TUN packet forwarding
is distinct from general packet forwarding. Correct?
What would be the co
How can I set up the debian box to forward packets between the two networks? Do
I have to set up packet forwarding by adding:
net.ipv4.ip_forward=1
into /etc/sysctl.conf
?
Many thanks
andrew.
You can use something like be below script to accomplish what you want. This
script assumes th
On Mon, 29 Jan 2007 17:06:24 -0200
cassiano <[EMAIL PROTECTED]> wrote:
> Speaking of which...
>
> How do I de-activate logging to stdout in shorewall? It´s very
> annoying to have all firewall logged activity popping out on
> whichever tty I´m working on...
This is in sid (etch is probably the s
packets between the two networks? Do I have to set up packet forwarding by adding:
net.ipv4.ip_forward=1
into /etc/sysctl.conf
You really want shorewall. Trust me on this. Once you have it
installed, go to http://www.shorewall.net and look under the
documentation for the two-interface firewall
to forward packets between the two networks?
> Do I have to set up packet forwarding by adding:
> net.ipv4.ip_forward=1
> into /etc/sysctl.conf
>
You really want shorewall. Trust me on this. Once you have it
installed, go to http://www.shorewall.net and look under the
documentation f
I set up the debian box to forward packets between the
> two networks? Do I have to set up packet forwarding by adding:
> net.ipv4.ip_forward=1 into /etc/sysctl.conf
>
> ?
Google is your friend.
http://www.google.com/search?q=linux+enable+ip+forwarding
The 2nd link tells you exact
Hello everyone,
I am trying to set up a debian proxy such as this:
USERDEBIANINTERNET
The debian box will have two network cards.
How can I set up the debian box to forward packets between the two networks? Do
I have to set up packet forwarding by adding:
net.ipv4
18 matches
Mail list logo
