similar to: adding static route

Mike Lander wrote: > I am building a shorewall box that the last post has the SSH error and > wanted > some feedback from the list if possible. At first I thought the two ISP''s > I > building this > for had two T-1''s with FQ ip''s as it. I have the box built for this ready > to > go. > Now I find out that one of the T-1''s is

I hope any of you shorewall freaks would be able to help me with my problem. First a little network description: I have two zones: WAN net = eth0 (One IP address from my Internet Service Provider) LAN loc = eth1 (192.168.23.0/24) Default gateway (the Internet) for the local clients are 192.168.23.2 (the IP address of eth1) I have used all the guides at the homepage of Shorewall,

Hi Michael, Once it was a pane in the neck for me to set this up as I had almost the same problem. First you have to find out in your Linux distribution where do you setup a permanent route entry. I mainly use Mandrake, but it had changed the way it handles this, but look at the file "/etc/sysconfig/static-routes", it had a syntax similar to the command that you stated below without the

Hi I''m using shorewall 2.1.10 on redhat 9 .. The machine have 2 network card eth1 inside network and eth0 internet(router) I define a static route on the linux system ( route add..) to another router But when I try to ping to the host/router I get "fw kernel : shorewall: forward: reject: in eth1 out=eth1...." Eth1= 192.168.220.254 Route add -net 192.114.122.111 netmask

I have openvpn set up and can get to every computer in the office side of the net work using the open vpn example as reference to "office" However from the office to the remote vpn pinging or searching for computers above 128 ip''s show timeouts and searching for computers with windows shows timeouts above 128. example ping from home to office "ping 10.19.227.129" or

Hi, We have a shorewall firewall running on SUSE 10. We have three nic''s, Lan, DMZ and Internet. We also have a Cisco Pix 506e. We moved from sending all our traffic through the pix to using the Suse box yesterday. The PIX is in the DMZ, with a connection to the LAN switch, the idea being that VPN users can connect to the pix to the lan. The Pix is on the 10.0.1.x subnet, the lan is

Hi I have a default route to 192.168.1.1 as soon as I start shorewall the default route dissapear. What do I need to do to have it not disappear. Kind Regards My network setup /etc/network/interfaces: # The primary network interface auto eth0 iface eth0 inet static address 192.168.1.17 netmask 255.255.255.0 network 192.168.1.0 broadcast 192.168.1.255

Hello, You may recall some of My Dmz question around Thanksgiving. While I have configured a Proxy arp Dmz. I would like to practice with the routed setup you suggested Tom as your network was simular. Here is one of your quotes "The configuration of eth2 is largely irrelevant but you certainly don''t want to confuse things by assigning any default gateway out of that

ClarkConnect Home 3.2 eth0 - WAN - inet - ip:192.168.1.2 gw:192.168.1.1 (connected to my www.woosh.co.nz gatway) wlan - WAN - private community wireless networt - ip:10.252.16.16 gw:10.252.16.1 eth1 - LAN - ip:192.168.2.1 # route add -net 10.0.0.0 netmask 255.0.0.0 gw 10.252.16.1 [root@bowenvale etc]# route Kernel IP routing table Destination Gateway Genmask Flags Metric Ref Use Iface

In an effert move my Dmz from a snapqear roouter to Linux with shorewall. Question is I have network 64.42.53.200/29 which makes default gw 64.42.53.201 network 64.42.53.200 broadcast 64.42.53.207 mask 255.255.255.248 and I want to set up shorewall with eth0 64.42.53.202 eth1 local eth2 dmz where dmz will use say 64.42.53.203 for web and email server. Where I do not need or should I say use

Hi, I''m completly lost with vlan and route configuration on my debian. This is my architecture : eth1.401 eth1.2338 eth2 Voice Vlan Public IP Local Network 10.150.11.90 84.16.x.x 192.168.1.1 255.255.255.240 255.255.255.128

Greetings. I run an Amateur Radio system (ampr.org) that requires 2 public ip''s on a RH 9.0 box. The primary one is 209.52.173.97 and is used for connections to the normal linux system and the usual apps such as web, ssh, smtp, etc. The secondary address is 209.52.173.98 and is routed via a pseudoslip link to the systems ampr address of 44.135.163.21. This setup takes place in the

Hi, How can I define static routes to be created at boot time with a specific metric? I have two NICs that ultimately end up at the same peer, but literally go through two completely different networks. IOW, each NIC connects to a different layer 3 device. Also, note that the machine actually has three total NICs: the third is the owner of the default route. The two mentioned above are for a

I want to add the following route command route add -net 192.168.2.0/27 gw 192.168.2.3 via the normal network setup. The result should be the following routing table (the first line): 192.168.2.0/27 via 192.168.2.3 dev xenbr1 scope link 192.168.2.0/27 dev eth2 proto kernel scope link src 192.168.2.4 192.168.2.0/27 dev xenbr1 proto kernel scope link src 192.168.2.3 192.168.1.0/24 dev xenbr0

Why ping google ??? you should either ping your assigned external ip address ( make your config dhcp for your external ip address even if it is static ) ( If your dsl link is up you sould have an address if not you should not ) If for some reson you cannot do that, ping your isp''s default gw or someone closer. With google you never know what is going on. I do something similar with -m

I am faced with a network that needs to autoswitch to isdn should T-1 go down. After a shorewall search it looks to be quite a deal with routing config with linux. Like scripts written to deal with knowing the T-1 is down. I looked into a cisco router that does this. around $3000 This network has used shorewall as the gateway for 4 years now. Currently Fedora as op. system. It appears to me

Hey Tom, This is my T-1 slash 27 network btw. How does this look??? for---- net eth0 66.224.62.120 ----dmz eth1 66.224.62.120 This box is for practice Dmz we talked about. with the pratice Dmz server''s Ip 66.224.62.121 routing and interface''s below [root@66-224-62-120 root]# ifconfig eth0 Link encap:Ethernet HWaddr

Hello! I'm trying to make a wireless mesh network with b.a.t.m.a.n. protocol, and I would like to secure the wireless links with tinc. My test network is 2 wireless routers with OpenWRT Kamikaze firmware, and the network topology is the following: |CLIENT|eth0: 192.168.180| <--> |eth0: 192.168.1.1|MESH-NODE|ath0: 192.168.5.54| <~~> |ath0: 192.168.5.51|GW|eth1: 192.168.1.51|

Right, time to (as someone said) put this thread to a proper rest. Some of you have probably read my VPN/Routing/Lost packages hassles in the last week, well, here is the rundown. Look at http://statler.mupp.net/shorewall/Layout.jpg Basically. The shorewall knows the route to the .224.0/24 net is through .221.221. The systems in .221.0/24 has the FW as their default gw. The FW could reach

hi. Are you add only 0.0.0.0/1 as route, not 128.0.0.0/1 too? Did you tried to add route to 5.6.7.8 via C with lesser metric then via B? If you have to add static routes only on a few servers, you can add them to the $HOST-up scripts. On Mon, Feb 29, 2016 at 11:12 AM, Zhang Jun <gb2313 at gmail.com> wrote: > my network: > > local pc(192.168.1.2)-->openwrt_adsl_router A(