All of lore.kernel.org
 help / color / mirror / Atom feed
From: "\"C. Bergström\"" <cbergstrom@netsyncro.com>
To: lartc@vger.kernel.org
Subject: [LARTC] Forwarding between untagged vlans
Date: Tue, 01 May 2007 09:39:59 +0000	[thread overview]
Message-ID: <46370AEF.7030305@netsyncro.com> (raw)

I'm trying to implement simple untagged vlans on our switch and have
misconfigured something..

ISP gw is on the default vlan1 (untagged)

Router
    eth1 is setup on the switch with default vlan1 and member of vlan4.
    eth0 is default vlan4 which connects to the clients that are all
default members of vlan4


eth0 is x.x.x.86/28 This is what clients are connecting to as their gw..
(no nat)
eth1 is x.x.x.82/26

default route is .65/26 dev eth1

If client is default vlan4, but a member of vlan1 then it all works.. 
As soon as I remove client from being a member of vlan1.. The router
stops forwarding.  Is this to be expected and how can I correct this?

I've tried adding a rule like this for the test client which is on .87
# Trying to fix vlan
iptables -A FORWARD -i ${WAN} -d x.x.x.87 -o ${LAN} -j ACCEPT
iptables -A FORWARD -i ${LAN} -s x.x.x.87 -o ${WAN} -j ACCEPT

I see the packets from the lan trying to get out, but on ingress I don't
see them..

Thanks in advance.

Christopher
_______________________________________________
LARTC mailing list
LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/cgi-bin/mailman/listinfo/lartc

             reply	other threads:[~2007-05-01  9:39 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-05-01  9:39 "C. Bergström" [this message]
2007-05-04 13:45 ` [LARTC] Forwarding between untagged vlans Michael Alger
2007-05-04 15:35 ` "C. Bergström"

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=46370AEF.7030305@netsyncro.com \
    --to=cbergstrom@netsyncro.com \
    --cc=lartc@vger.kernel.org \
    /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.