public inbox for documentation@lists.ipfire.org
 help / color / mirror / Atom feed
From: Michael Tremer <michael.tremer@ipfire.org>
To: documentation@lists.ipfire.org
Subject: Re: VLAN Konfig
Date: Mon, 22 Jul 2013 10:37:05 +0200	[thread overview]
Message-ID: <1374482225.11196.13.camel@rice-oxley.tremer.info> (raw)
In-Reply-To: <51EC4610.6010406@gmx.net>

[-- Attachment #1: Type: text/plain, Size: 6861 bytes --]

Hi,

you will have to grant access to every host on the blue network in the
WUI. Please go to Firewall -> Blue Access and do that over there.

-Michael

On Sun, 2013-07-21 at 22:35 +0200, Thomas Berthel wrote:
> Hi,
> 
> nobody any idea?
> 
> good night, Thomas
> 
> On 07/02/2013 12:14 AM, Thomas Berthel wrote:
> > Hi Michael,
> > 
> >> Please run /etc/init.d/network-vlans start
> > thanks. beginner error :-)
> > 
> > Here my document for vlan:
> > 
> > I configure my fire with the setup modus and change from green+red to
> > green+red+organge+blue
> > 
> > I setting up the network-ip's for blue & orange, then i became by the
> > end from the setup a message: orange device cant configure not devivce
> > found or so. Because it does not let me finish the setupmode i have
> > cloesed the console-connection.
> > 
> > I check my /var/ipfire/ethernet/settings and all information from my
> > change in the setup-menu was written there.
> > 
> > for example one snipp:
> > 
> > BLUE_ADDRESS=192.168.2.1
> > BLUE_NETMASK=255.255.255.0
> > BLUE_NETADDRESS=192.168.2.0
> > BLUE_BROADCAST=192.168.2.255
> > 
> > but, no MAC-Address and no DEV was in there.
> > 
> > The ifconfig says nothing to blue or orange. Okay then the next step.
> > I configure my /var/ipfire/ethernet/vlans as follows:
> > 
> > BLUE_PARENT_DEV=green0
> > BLUE_VLAN_ID=300
> > BLUE_MAC_ADDRESS=00:22:4D:84:A5:30
> > ORANGE_PARENT_DEV=green0
> > ORANGE_VLAN_ID=400
> > ORANGE_MAC_ADDRESS=00:22:4D:84:A5:40
> > 
> > Without "" for _PARENT_DEV="device1" and the _MAC_ADDRESS="11:22:33:..."
> > 
> > Then i do /etc/init.d/network-vlan start, this was my messages-output:
> > 
> > /etc/init.d/network-vlans start
> > + CONFIG_FILE=/var/ipfire/ethernet/vlans
> > + '[' -e /var/ipfire/ethernet/vlans ']'
> > ++ /usr/local/bin/readhash /var/ipfire/ethernet/vlans
> > + eval BLUE_PARENT_DEV=green0 BLUE_VLAN_ID=300
> > BLUE_MAC_ADDRESS=00:22:4D:84:A5:30 ORANGE_PARENT_DEV=green0
> > ORANGE_VLAN_ID=400 ORANGE_MAC_ADDRESS=00:22:4D:84:A5:40
> > ++ BLUE_PARENT_DEV=green0
> > ++ BLUE_VLAN_ID=300
> > ++ BLUE_MAC_ADDRESS=00:22:4D:84:A5:30
> > ++ ORANGE_PARENT_DEV=green0
> > ++ ORANGE_VLAN_ID=400
> > ++ ORANGE_MAC_ADDRESS=00:22:4D:84:A5:40
> > + action=start
> > + for interface in green0 blue0 orange0
> > + case "${interface}" in
> > + PARENT_DEV=
> > + VLAN_ID=
> > + MAC_ADDRESS=
> > + case "${action}" in
> > + '[' -z '' ']'
> > + continue
> > + for interface in green0 blue0 orange0
> > + case "${interface}" in
> > + PARENT_DEV=green0
> > + VLAN_ID=300
> > + MAC_ADDRESS=00:22:4D:84:A5:30
> > + case "${action}" in
> > + '[' -z green0 ']'
> > + '[' -d /sys/class/net/blue0 ']'
> > + '[' '!' -d /sys/class/net/green0 ']'
> > + '[' -z 300 ']'
> > + echo 'Creating VLAN interface blue0...'
> > Creating VLAN interface blue0...
> > + vconfig add green0 300
> > Added VLAN with VID == 300 to IF -:green0:-
> > + ip link set green0.300 name blue0
> > + '[' -n 00:22:4D:84:A5:30 ']'
> > + ip link set blue0 address 00:22:4D:84:A5:30
> > + ip link set green0 up
> > + for interface in green0 blue0 orange0
> > + case "${interface}" in
> > + PARENT_DEV=green0
> > + VLAN_ID=400
> > + MAC_ADDRESS=00:22:4D:84:A5:40
> > + case "${action}" in
> > + '[' -z green0 ']'
> > + '[' -d /sys/class/net/orange0 ']'
> > + '[' '!' -d /sys/class/net/green0 ']'
> > + '[' -z 400 ']'
> > + echo 'Creating VLAN interface orange0...'
> > Creating VLAN interface orange0...
> > + vconfig add green0 400
> > Added VLAN with VID == 400 to IF -:green0:-
> > + ip link set green0.400 name orange0
> > + '[' -n 00:22:4D:84:A5:40 ']'
> > + ip link set orange0 address 00:22:4D:84:A5:40
> > + ip link set green0 up
> > 
> > Yeah! The finale countdown ;-)
> > 
> > So, i checket my ifconfig and only the device with no IP was displayed:
> > 
> > blue0     Link encap:Ethernet  HWaddr 00:22:4D:84:A5:30
> >           UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
> >           RX packets:0 errors:0 dropped:0 overruns:0 frame:0
> >           TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
> >           collisions:0 txqueuelen:0
> >           RX bytes: (0 Kb)  TX bytes: (0 Kb)
> > 
> > WTF? okay. I configure my /var/ipfire/ethernet/settings once again as
> > described here:
> > 
> > BLUE_DEV=blue0
> > BLUE_MACADDR=00:22:4d:84:a5:30
> > BLUE_DESCRIPTION='"pci: Intel Corporation 82574L Gigabit Network
> > Connection"'
> > BLUE_DRIVER=e1000e
> > BLUE_ADDRESS=192.168.2.1
> > BLUE_NETMASK=255.255.255.0
> > BLUE_NETADDRESS=192.168.2.0
> > BLUE_BROADCAST=192.168.2.255
> > 
> > Next step - reboot firewall! then the result from ifconfig said:
> > 
> > blue0     Link encap:Ethernet  HWaddr 00:22:4D:84:A5:30
> > 	  inet addr:192.168.2.1  Bcast:192.168.2.255  Mask:255.255.255.0
> >           UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
> >           RX packets:0 errors:0 dropped:0 overruns:0 frame:0
> >           TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
> >           collisions:0 txqueuelen:0
> >           RX bytes: (0 Kb)  TX bytes: (0 Kb)
> > 
> > BUT - my firewall droped my DNS and HTTP requests. I tried to change the
> > rules with the firewall-mode from 1 to 0 and in the WUI by mode 1 to set
> > rules for wireless to allow this connections. Without success!
> > 
> > for example:
> > Jul  1 21:23:10 ipfw kernel: DROP_WirelessinputIN=blue0 OUT=
> > MAC=00:22:4d:84:a5:30:7c:61:93:16:2f:82:08:00 SRC=192.168.2.10
> > DST=192.168.2.1 LEN=69 TOS=0x00 PREC=0x00 TTL=64 ID=25514 DF PROTO=UDP
> > SPT=1083 DPT=53 LEN=4
> > 
> > Any idea?
> > 
> > BG, Thomas
> > 
> > Am 01.07.2013 11:53, schrieb Michael Tremer:
> >> On Sun, 2013-06-30 at 15:37 +0200, Thomas Berthel wrote:
> >>> Hi @ all,
> >>>
> >>> i have checked the /etc/init.d/network-vlans Script and become following
> >>> messages: Invalid action
> >>>
> >>> The dubug output says:
> >>>
> >>> (/var/ipfire/ethernet):/etc/init.d/network-vlans
> >>> + CONFIG_FILE=/var/ipfire/ethernet/vlans
> >>> + '[' -e /var/ipfire/ethernet/vlans ']'
> >>> ++ /usr/local/bin/readhash /var/ipfire/ethernet/vlans
> >>> + eval '#GREEN_VLAN_ID=20' BLUE_VLAN_ID=300 ORANGE_VLAN_ID=400
> >>> + action=
> >>> + for interface in green0 blue0 orange0
> >>> + case "${interface}" in
> >>> + PARENT_DEV=
> >>> + VLAN_ID=
> >>> + MAC_ADDRESS=
> >>> + case "${action}" in
> >>> + echo 'Invalid action: '
> >>> Invalid action:
> >>> + exit 1
> >>
> >> Please run /etc/init.d/network-vlans start or /etc/init.d/network-vlans
> >> to start and stop the virtual interfaces.
> >>
> >> -Michael
> >>
> > 
> > _______________________________________________
> > Documentation mailing list
> > Documentation(a)lists.ipfire.org
> > http://lists.ipfire.org/mailman/listinfo/documentation
> > 
> 
> _______________________________________________
> Documentation mailing list
> Documentation(a)lists.ipfire.org
> http://lists.ipfire.org/mailman/listinfo/documentation


  reply	other threads:[~2013-07-22  8:37 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <51D03494.7090008@gmx.net>
2013-07-01  9:53 ` Michael Tremer
2013-07-01 22:14   ` Thomas Berthel
2013-07-21 20:35     ` Thomas Berthel
2013-07-22  8:37       ` Michael Tremer [this message]
2013-08-08 18:12         ` Thomas Berthel
2013-08-08 18:24           ` Thomas Berthel
     [not found] <A74BA195-E17C-4CD6-A81A-DC0E246BF1E2@ipfire.org>
2013-06-09 11:58 ` Thomas Berthel
2013-06-09 13:31   ` Erik K.
2013-06-09 16:40     ` Thomas Berthel
2013-06-08 11:42 Thomas Berthel
2013-06-09  4:54 ` Erik K.
2013-06-09  7:37   ` Thomas Berthel
2013-06-10 10:22 ` Michael Tremer

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=1374482225.11196.13.camel@rice-oxley.tremer.info \
    --to=michael.tremer@ipfire.org \
    --cc=documentation@lists.ipfire.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox