Matt,

I started with Dachstein, but could not get even the basics to work and so moved to 
Eiger.

The firewall is not active.

IP addr show reports:

1: lo: <LOOPBACK,UP> mtu 3924 qdisc noqueue 
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    inet 127.0.0.1/8 brd 127.255.255.255 scope global lo
2: brg0: <BROADCAST,MULTICAST> mtu 1500 qdisc noop 
    link/ether fe:fd:02:32:57:db brd ff:ff:ff:ff:ff:ff
3: eth0: <BROADCAST,MULTICAST,UP> mtu 1500 qdisc pfifo_fast qlen 100
    link/ether 00:01:03:31:a8:08 brd ff:ff:ff:ff:ff:ff
    inet x.x.150.253/24 scope global eth0
4: eth1: <BROADCAST,MULTICAST,UP> mtu 1500 qdisc pfifo_fast qlen 100
    link/ether 00:01:02:68:19:5d brd ff:ff:ff:ff:ff:ff
    inet x.x.153.254/24 brd x.x.153.255 scope global eth1

ip route show reports:

x.x.150.0/24 dev eth0  proto kernel  scope link  src x.x.150.253 
x.x.153.0/24 dev eth1  proto kernel  scope link  src x.x.153.254 
default via x.x.150.254 dev eth0

Thanks,
Jeff

>>> Matt Schalit <[EMAIL PROTECTED]> 11/14/01 10:48AM >>>
Jeff Groetsema wrote:
> 
> All,
> 
> I need to set up a basic router (no NAT, DNS, filtering, etc.) with three ports to 
>three subnets and one port to our Internet gateway.  My path to this end, was to 
>start with LRP Eiger, a default configuration and incrementally convert it to what I 
>need.  The first step was to set it up with two ports, one to an external net with an 
>address of x.x.150.253, one internal port with an address of 192.168.1.254, and a 
>gateway address of x.x.150.254.  After I fixed DNS, all was well and I could browse 
>the internet.  My next step was to replace the internal address with x.x.153.254.  
>After this change was made I could ping x.x.153.254 and x.x.150.253 but nothing else. 
> I turned off NAT, DNS, and filtering incase they were causing problems.  Still no 
>luck.
> 
> Any insite would be greatly appreciated.
> 
> Thanks,
> Jeff


You probably want to grab the Dachstein version, rather
than to try to do this on Eiger, mostly because Dachstein
is newer and more mature.

Most likely, Eiger is still putting rules in place to 
block the traffic.  You might try:

  ipchains -L -n -v
  ip addr show
  ip route show

And post those if you don't get anywhere.  Like Ray mentioned,
please be more specific in listing what you do and what you see.
Matthew

_______________________________________________
Leaf-user mailing list
[EMAIL PROTECTED] 
https://lists.sourceforge.net/lists/listinfo/leaf-user


_______________________________________________
Leaf-user mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/leaf-user

Reply via email to