FAQ o OpenWrt | Sprzedam różne routery | Oddam

exeq17 · 2016-10-13 12:30:33

exeq17
Użytkownik
Nieaktywny

Zarejestrowany: 2016-10-13
Posty: 20

Temat: wykorzystanie vlanow do stworzenia dwoch sieci

Witam,

probuje już od dłuższego czasu uzyskac taki efekt na wr1043nd v3 z wgranym OpenWrt Chaos Calmer 15.05.1 r49398 / LuCI for-15.05 branch (git-16.168.30315-6920494) router 1043nd v3 bedzie wpiety do funboxa a dalej do portow wpiete switche:
porty (fizyczne oznaczenie na routerze) 1,2,3 na siec 192.168.1.1
port 4 (rownież fizycznie oznaczony na routerze) na siec 192.168.2.1

idea jest taka żeby kompy z portu 4 nie widziały kompów z portów 1,2,3 i na odwrót. Póki co udało mi się uzyskać cos takiego ze: na portach 1,2,3 internet dziala i siec dziala. na porcie numer 4 nie przydziela mi adresu ip tylko daje ip prywatne tzn 169.... bardzo proszę o pomoc. poniżej ustawienia:
uci show network

network.loopback=interface
network.loopback.ifname='lo'
network.loopback.proto='static'
network.loopback.ipaddr='127.0.0.1'
network.loopback.netmask='255.0.0.0'
network.globals=globals
network.globals.ula_prefix='fd6a:127c:3e9d::/48'
network.lan=interface
network.lan.ifname='eth1'
network.lan.force_link='1'
network.lan.type='bridge'
network.lan.proto='static'
network.lan.ipaddr='192.168.1.1'
network.lan.netmask='255.255.255.0'
network.lan.ip6assign='60'
network.wan=interface
network.wan.ifname='eth0'
network.wan.proto='dhcp'
network.wan6=interface
network.wan6.ifname='eth0'
network.wan6.proto='dhcpv6'
network.@switch[0]=switch
network.@switch[0].name='switch0'
network.@switch[0].reset='1'
network.@switch[0].enable_vlan='1'
network.@switch[0].mirror_source_port='0'
network.@switch[0].mirror_monitor_port='0'
network.@switch_vlan[0]=switch_vlan
network.@switch_vlan[0].device='switch0'
network.@switch_vlan[0].vlan='1'
network.@switch_vlan[0].vid='1'
network.@switch_vlan[0].ports='0 2 3 4'
network.@switch_vlan[1]=switch_vlan
network.@switch_vlan[1].device='switch0'
network.@switch_vlan[1].vlan='2'
network.@switch_vlan[1].ports='5 6'
network.@switch_vlan[1].vid='2'
network.@switch_vlan[2]=switch_vlan
network.@switch_vlan[2].device='switch0'
network.@switch_vlan[2].vlan='3'
network.@switch_vlan[2].vid='3'
network.@switch_vlan[2].ports='0t 1'
network.vlan=interface
network.vlan.proto='static'
network.vlan.ifname='eth0.3'
network.vlan.ipaddr='192.168.2.1'
network.vlan.netmask='255.255.255.0'

uci show firewall

firewall.@defaults[0]=defaults
firewall.@defaults[0].syn_flood='1'
firewall.@defaults[0].input='ACCEPT'
firewall.@defaults[0].output='ACCEPT'
firewall.@defaults[0].forward='REJECT'
firewall.@zone[0]=zone
firewall.@zone[0].name='lan'
firewall.@zone[0].input='ACCEPT'
firewall.@zone[0].output='ACCEPT'
firewall.@zone[0].forward='ACCEPT'
firewall.@zone[0].network='lan'
firewall.@zone[1]=zone
firewall.@zone[1].name='wan'
firewall.@zone[1].input='REJECT'
firewall.@zone[1].output='ACCEPT'
firewall.@zone[1].forward='REJECT'
firewall.@zone[1].masq='1'
firewall.@zone[1].mtu_fix='1'
firewall.@zone[1].network='wan wan6'
firewall.@forwarding[0]=forwarding
firewall.@forwarding[0].src='lan'
firewall.@forwarding[0].dest='wan'
firewall.@rule[0]=rule
firewall.@rule[0].name='Allow-DHCP-Renew'
firewall.@rule[0].src='wan'
firewall.@rule[0].proto='udp'
firewall.@rule[0].dest_port='68'
firewall.@rule[0].target='ACCEPT'
firewall.@rule[0].family='ipv4'
firewall.@rule[1]=rule
firewall.@rule[1].name='Allow-Ping'
firewall.@rule[1].src='wan'
firewall.@rule[1].proto='icmp'
firewall.@rule[1].icmp_type='echo-request'
firewall.@rule[1].family='ipv4'
firewall.@rule[1].target='ACCEPT'
firewall.@rule[2]=rule
firewall.@rule[2].name='Allow-IGMP'
firewall.@rule[2].src='wan'
firewall.@rule[2].proto='igmp'
firewall.@rule[2].family='ipv4'
firewall.@rule[2].target='ACCEPT'
firewall.@rule[3]=rule
firewall.@rule[3].name='Allow-DHCPv6'
firewall.@rule[3].src='wan'
firewall.@rule[3].proto='udp'
firewall.@rule[3].src_ip='fe80::/10'
firewall.@rule[3].src_port='547'
firewall.@rule[3].dest_ip='fe80::/10'
firewall.@rule[3].dest_port='546'
firewall.@rule[3].family='ipv6'
firewall.@rule[3].target='ACCEPT'
firewall.@rule[4]=rule
firewall.@rule[4].name='Allow-MLD'
firewall.@rule[4].src='wan'
firewall.@rule[4].proto='icmp'
firewall.@rule[4].src_ip='fe80::/10'
firewall.@rule[4].icmp_type='130/0' '131/0' '132/0' '143/0'
firewall.@rule[4].family='ipv6'
firewall.@rule[4].target='ACCEPT'
firewall.@rule[5]=rule
firewall.@rule[5].name='Allow-ICMPv6-Input'
firewall.@rule[5].src='wan'
firewall.@rule[5].proto='icmp'
firewall.@rule[5].icmp_type='echo-request' 'echo-reply' 'destination-unreachable' 'packet-too-big' 'time-exceeded' 'bad-header' 'unknown-header-type' 'router-solicitation' 'neighbour-solicitation' 'router-advertisement' 'neighbour-advertisement'
firewall.@rule[5].limit='1000/sec'
firewall.@rule[5].family='ipv6'
firewall.@rule[5].target='ACCEPT'
firewall.@rule[6]=rule
firewall.@rule[6].name='Allow-ICMPv6-Forward'
firewall.@rule[6].src='wan'
firewall.@rule[6].dest='*'
firewall.@rule[6].proto='icmp'
firewall.@rule[6].icmp_type='echo-request' 'echo-reply' 'destination-unreachable' 'packet-too-big' 'time-exceeded' 'bad-header' 'unknown-header-type'
firewall.@rule[6].limit='1000/sec'
firewall.@rule[6].family='ipv6'
firewall.@rule[6].target='ACCEPT'
firewall.@include[0]=include
firewall.@include[0].path='/etc/firewall.user'
firewall.@rule[7]=rule
firewall.@rule[7].src='wan'
firewall.@rule[7].dest='lan'
firewall.@rule[7].proto='esp'
firewall.@rule[7].target='ACCEPT'
firewall.@rule[8]=rule
firewall.@rule[8].src='wan'
firewall.@rule[8].dest='lan'
firewall.@rule[8].dest_port='500'
firewall.@rule[8].proto='udp'
firewall.@rule[8].target='ACCEPT'
firewall.@zone[2]=zone
firewall.@zone[2].name='vlan'
firewall.@zone[2].input='ACCEPT'
firewall.@zone[2].forward='REJECT'
firewall.@zone[2].output='ACCEPT'
firewall.@zone[2].network='vlan'
firewall.@forwarding[1]=forwarding
firewall.@forwarding[1].dest='wan'
firewall.@forwarding[1].src='vlan'

route -n

Kernel IP routing table
Destination     Gateway         Genmask         Flags Metric Ref    Use Iface
0.0.0.0         192.168.1.1     0.0.0.0         UG    0      0        0 eth0
192.168.1.0     0.0.0.0         255.255.255.0   U     0      0        0 br-lan
192.168.1.0     0.0.0.0         255.255.255.0   U     0      0        0 eth0
192.168.1.1     0.0.0.0         255.255.255.255 UH    0      0        0 eth0
192.168.2.0     0.0.0.0         255.255.255.0   U     0      0        0 eth0.3

Cezary · 2016-10-13 12:37:24

Cezary
...
Nieaktywny

Skąd: Warszawa
Zarejestrowany: 2006-02-25
Posty: 116,322

Odp: wykorzystanie vlanow do stworzenia dwoch sieci

Wydzieliłeś ze switcha jeden z portów, zrobił się interfejs eth0.3 dla niego. Zrobiłeś dla niego sekcję o nazwie vlan. I teraz - dorób sekcję w /etc/config/dhcp żeby dnsmasq mogło go obsługiwać.

Masz niepotrzebny router, uszkodzony czy nie - chętnie przygarnę go.

exeq17 · 2016-10-13 13:25:39

exeq17
Użytkownik
Nieaktywny

Zarejestrowany: 2016-10-13
Posty: 20

Odp: wykorzystanie vlanow do stworzenia dwoch sieci

plik DHCP wygląda teraz tak, jednak dalej nie działa na porcie numer 4:

config dnsmasq
        option domainneeded '1'
        option boguspriv '1'
        option filterwin2k '0'
        option localise_queries '1'
        option rebind_protection '1'
        option rebind_localhost '1'
        option local '/lan/'
        option domain 'lan'
        option expandhosts '1'
        option nonegcache '0'
        option authoritative '1'
        option readethers '1'
        option leasefile '/tmp/dhcp.leases'
        option resolvfile '/tmp/resolv.conf.auto'
        option localservice '1'
        list rebind_domain 'free.aero2.net.pl'

config dhcp 'lan'
        option interface 'lan'
        option start '100'
        option limit '150'
        option leasetime '12h'
        option dhcpv6 'server'
        option ra 'server'

config dhcp 'wan'
        option interface 'wan'
        option ignore '1'

config odhcpd 'odhcpd'
        option maindhcp '0'
        option leasefile '/tmp/hosts/odhcpd'
        option leasetrigger '/usr/sbin/odhcpd-update'

config dhcp 'vlan'
        option start '100'
        option leasetime '12h'
        option limit '150'
        option interface 'vlan'

Cezary · 2016-10-13 13:35:30

Cezary
...
Nieaktywny

Skąd: Warszawa
Zarejestrowany: 2006-02-25
Posty: 116,322

Odp: wykorzystanie vlanow do stworzenia dwoch sieci

Zrestartowałeś go? Pokaż wynik logread

Masz niepotrzebny router, uszkodzony czy nie - chętnie przygarnę go.

exeq17 · 2016-10-13 13:39:27

exeq17
Użytkownik
Nieaktywny

Zarejestrowany: 2016-10-13
Posty: 20

Odp: wykorzystanie vlanow do stworzenia dwoch sieci

tak restartowany byl kilkukrotnie bo czasami porty 1,2,3 nie dają netu i nie mozna sią nawet do routera podpiąć..

logread:

Thu Oct 13 14:20:00 2016 kern.info kernel: [    5.490000] ehci-platform ehci-platform.0: TX-TX IDP fix enabled
Thu Oct 13 14:20:00 2016 kern.info kernel: [    5.500000] ehci-platform ehci-platform.0: irq 48, io mem 0x1b000000
Thu Oct 13 14:20:00 2016 kern.info kernel: [    5.520000] ehci-platform ehci-platform.0: USB 2.0 started, EHCI 1.00
Thu Oct 13 14:20:00 2016 kern.info kernel: [    5.520000] hub 1-0:1.0: USB hub found
Thu Oct 13 14:20:00 2016 kern.info kernel: [    5.530000] hub 1-0:1.0: 1 port detected
Thu Oct 13 14:20:00 2016 kern.info kernel: [    5.530000] ehci-platform ehci-platform.1: EHCI Host Controller
Thu Oct 13 14:20:00 2016 kern.info kernel: [    5.540000] ehci-platform ehci-platform.1: new USB bus registered, assigned bus number 2
Thu Oct 13 14:20:00 2016 kern.info kernel: [    5.550000] ehci-platform ehci-platform.1: TX-TX IDP fix enabled
Thu Oct 13 14:20:00 2016 kern.info kernel: [    5.550000] ehci-platform ehci-platform.1: irq 49, io mem 0x1b400000
Thu Oct 13 14:20:00 2016 kern.info kernel: [    5.580000] ehci-platform ehci-platform.1: USB 2.0 started, EHCI 1.00
Thu Oct 13 14:20:00 2016 kern.info kernel: [    5.580000] hub 2-0:1.0: USB hub found
Thu Oct 13 14:20:00 2016 kern.info kernel: [    5.590000] hub 2-0:1.0: 1 port detected
Thu Oct 13 14:20:00 2016 kern.info kernel: [    5.590000] ohci_hcd: USB 1.1 'Open' Host Controller (OHCI) Driver
Thu Oct 13 14:20:00 2016 kern.info kernel: [    5.600000] ohci-platform: OHCI generic platform driver
Thu Oct 13 14:20:00 2016 kern.info kernel: [    5.610000] usbcore: registered new interface driver usb-storage
Thu Oct 13 14:20:00 2016 user.info kernel: [    6.430000] init: - preinit -
Thu Oct 13 14:20:00 2016 kern.info kernel: [    6.980000] eth1: link up (1000Mbps/Full duplex)
Thu Oct 13 14:20:00 2016 kern.notice kernel: [    7.000000] random: procd urandom read with 11 bits of entropy available
Thu Oct 13 14:20:00 2016 user.info kernel: [   10.180000] mount_root: loading kmods from internal overlay
Thu Oct 13 14:20:00 2016 kern.notice kernel: [   10.540000] jffs2: notice: (421) jffs2_build_xattr_subsystem: complete building xattr subsystem, 0 of xdatum (0 unchecked, 0 orphan) and 0 of xref (0 dead, 0 orphan) found.
Thu Oct 13 14:20:00 2016 user.info kernel: [   10.560000] block: attempting to load /tmp/jffs_cfg/upper/etc/config/fstab
Thu Oct 13 14:20:00 2016 user.info kernel: [   10.570000] block: extroot: not configured
Thu Oct 13 14:20:00 2016 kern.notice kernel: [   10.660000] jffs2: notice: (417) jffs2_build_xattr_subsystem: complete building xattr subsystem, 0 of xdatum (0 unchecked, 0 orphan) and 0 of xref (0 dead, 0 orphan) found.
Thu Oct 13 14:20:00 2016 user.info kernel: [   10.890000] block: attempting to load /tmp/jffs_cfg/upper/etc/config/fstab
Thu Oct 13 14:20:00 2016 user.info kernel: [   10.910000] block: extroot: not configured
Thu Oct 13 14:20:00 2016 user.info kernel: [   10.910000] mount_root: switching to jffs2 overlay
Thu Oct 13 14:20:00 2016 kern.info kernel: [   10.950000] eth1: link down
Thu Oct 13 14:20:00 2016 user.info kernel: [   10.970000] procd: - early -
Thu Oct 13 14:20:00 2016 user.info kernel: [   10.970000] procd: - watchdog -
Thu Oct 13 14:20:00 2016 user.info kernel: [   11.730000] procd: - ubus -
Thu Oct 13 14:20:00 2016 user.info kernel: [   12.740000] procd: - init -
Thu Oct 13 14:20:00 2016 kern.info kernel: [   14.360000] NET: Registered protocol family 10
Thu Oct 13 14:20:00 2016 kern.info kernel: [   14.390000] gre: GRE over IPv4 demultiplexor driver
Thu Oct 13 14:20:00 2016 kern.info kernel: [   14.390000] ip_gre: GRE over IPv4 tunneling driver
Thu Oct 13 14:20:00 2016 kern.info kernel: [   14.400000] ip6_tables: (C) 2000-2006 Netfilter Core Team
Thu Oct 13 14:20:00 2016 kern.info kernel: [   14.430000] u32 classifier
Thu Oct 13 14:20:00 2016 kern.info kernel: [   14.440000]     input device check on
Thu Oct 13 14:20:00 2016 kern.info kernel: [   14.440000]     Actions configured
Thu Oct 13 14:20:00 2016 kern.info kernel: [   14.440000] Mirror/redirect action on
Thu Oct 13 14:20:00 2016 kern.info kernel: [   14.510000] fuse init (API version 7.23)
Thu Oct 13 14:20:00 2016 kern.info kernel: [   14.530000] usbcore: registered new interface driver cdc_acm
Thu Oct 13 14:20:00 2016 kern.info kernel: [   14.530000] cdc_acm: USB Abstract Control Model driver for USB modems and ISDN adapters
Thu Oct 13 14:20:00 2016 kern.info kernel: [   14.540000] usbcore: registered new interface driver cdc_wdm
Thu Oct 13 14:20:00 2016 kern.info kernel: [   14.550000] Loading modules backported from Linux version v4.4-rc5-1913-gc8fdf68
Thu Oct 13 14:20:00 2016 kern.info kernel: [   14.560000] Backport generated by backports.git backports-20151218-0-g2f58d9d
Thu Oct 13 14:20:00 2016 kern.info kernel: [   14.590000] ip_tables: (C) 2000-2006 Netfilter Core Team
Thu Oct 13 14:20:00 2016 kern.info kernel: [   14.610000] nf_conntrack version 0.5.0 (953 buckets, 3812 max)
Thu Oct 13 14:20:00 2016 kern.info kernel: [   14.650000] usbcore: registered new interface driver usblp
Thu Oct 13 14:20:00 2016 kern.info kernel: [   14.670000] usbcore: registered new interface driver usbserial
Thu Oct 13 14:20:00 2016 kern.info kernel: [   14.680000] usbcore: registered new interface driver usbserial_generic
Thu Oct 13 14:20:00 2016 kern.info kernel: [   14.680000] usbserial: USB Serial support registered for generic
Thu Oct 13 14:20:00 2016 kern.info kernel: [   14.750000] xt_time: kernel timezone is -0000
Thu Oct 13 14:20:00 2016 kern.info kernel: [   14.760000] usbcore: registered new interface driver cdc_ether
Thu Oct 13 14:20:00 2016 kern.info kernel: [   14.770000] usbcore: registered new interface driver cdc_ncm
Thu Oct 13 14:20:00 2016 kern.info kernel: [   15.050000] usbcore: registered new interface driver huawei_cdc_ncm
Thu Oct 13 14:20:00 2016 kern.info kernel: [   15.100000] PPP generic driver version 2.4.2
Thu Oct 13 14:20:00 2016 kern.info kernel: [   15.110000] PPP MPPE Compression module registered
Thu Oct 13 14:20:00 2016 kern.info kernel: [   15.120000] NET: Registered protocol family 24
Thu Oct 13 14:20:00 2016 kern.info kernel: [   15.120000] PPTP driver version 0.8.5
Thu Oct 13 14:20:00 2016 kern.info kernel: [   15.130000] usbcore: registered new interface driver qmi_wwan
Thu Oct 13 14:20:00 2016 kern.info kernel: [   15.140000] usbcore: registered new interface driver rndis_host
Thu Oct 13 14:20:00 2016 kern.info kernel: [   15.150000] usbcore: registered new interface driver sierra
Thu Oct 13 14:20:00 2016 kern.info kernel: [   15.150000] usbserial: USB Serial support registered for Sierra USB modem
Thu Oct 13 14:20:00 2016 kern.info kernel: [   15.160000] usbcore: registered new interface driver sierra_net
Thu Oct 13 14:20:00 2016 kern.info kernel: [   15.200000] usbcore: registered new interface driver cdc_mbim
Thu Oct 13 14:20:00 2016 kern.info kernel: [   15.210000] usbcore: registered new interface driver option
Thu Oct 13 14:20:00 2016 kern.info kernel: [   15.220000] usbserial: USB Serial support registered for GSM modem (1-port)
Thu Oct 13 14:20:00 2016 kern.info kernel: [   15.230000] usbcore: registered new interface driver qcserial
Thu Oct 13 14:20:00 2016 kern.info kernel: [   15.230000] usbserial: USB Serial support registered for Qualcomm USB modem
Thu Oct 13 14:20:00 2016 kern.debug kernel: [   15.260000] ath: EEPROM regdomain: 0x0
Thu Oct 13 14:20:00 2016 kern.debug kernel: [   15.260000] ath: EEPROM indicates default country code should be used
Thu Oct 13 14:20:00 2016 kern.debug kernel: [   15.260000] ath: doing EEPROM country->regdmn map search
Thu Oct 13 14:20:00 2016 kern.debug kernel: [   15.260000] ath: country maps to regdmn code: 0x3a
Thu Oct 13 14:20:00 2016 kern.debug kernel: [   15.260000] ath: Country alpha2 being used: US
Thu Oct 13 14:20:00 2016 kern.debug kernel: [   15.260000] ath: Regpair used: 0x3a
Thu Oct 13 14:20:00 2016 kern.debug kernel: [   15.280000] ieee80211 phy0: Selected rate control algorithm 'minstrel_ht'
Thu Oct 13 14:20:00 2016 kern.info kernel: [   15.280000] ieee80211 phy0: Atheros AR9550 Rev:0 mem=0xb8100000, irq=47
Thu Oct 13 14:20:02 2016 user.emerg syslog: 'radio0' is disabled
Thu Oct 13 14:20:02 2016 user.emerg syslog: 'radio0' is disabled
Thu Oct 13 14:20:03 2016 user.emerg syslog: this file has been obseleted. please call "/sbin/block mount" directly
Thu Oct 13 14:20:03 2016 daemon.err block: /dev/mtdblock3 is already mounted
Thu Oct 13 14:20:05 2016 authpriv.info dropbear[1268]: Not backgrounding
Thu Oct 13 14:20:08 2016 kern.info kernel: [   24.990000] eth1: link up (1000Mbps/Full duplex)
Thu Oct 13 14:20:08 2016 kern.info kernel: [   25.000000] device eth1 entered promiscuous mode
Thu Oct 13 14:20:08 2016 kern.info kernel: [   25.000000] IPv6: ADDRCONF(NETDEV_UP): br-lan: link is not ready
Thu Oct 13 14:20:08 2016 daemon.notice netifd: Interface 'lan' is enabled
Thu Oct 13 14:20:08 2016 daemon.notice netifd: Interface 'lan' is setting up now
Thu Oct 13 14:20:08 2016 daemon.notice netifd: Interface 'lan' is now up
Thu Oct 13 14:20:08 2016 daemon.notice netifd: Interface 'loopback' is enabled
Thu Oct 13 14:20:08 2016 daemon.notice netifd: Interface 'loopback' is setting up now
Thu Oct 13 14:20:08 2016 daemon.notice netifd: Interface 'loopback' is now up
Thu Oct 13 14:20:08 2016 kern.info kernel: [   25.020000] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
Thu Oct 13 14:20:08 2016 daemon.notice netifd: Interface 'wan' is enabled
Thu Oct 13 14:20:08 2016 daemon.notice netifd: Interface 'wan6' is enabled
Thu Oct 13 14:20:08 2016 daemon.notice netifd: Interface 'vlan' is enabled
Thu Oct 13 14:20:08 2016 daemon.notice netifd: Interface 'vlan' is setting up now
Thu Oct 13 14:20:08 2016 kern.info kernel: [   25.060000] IPv6: ADDRCONF(NETDEV_UP): eth0.3: link is not ready
Thu Oct 13 14:20:08 2016 daemon.notice netifd: Interface 'vlan' is now up
Thu Oct 13 14:20:08 2016 daemon.notice netifd: Network device 'eth1' link is up
Thu Oct 13 14:20:09 2016 daemon.notice netifd: Network device 'lo' link is up
Thu Oct 13 14:20:09 2016 daemon.notice netifd: Interface 'loopback' has link connectivity
Thu Oct 13 14:20:09 2016 kern.info kernel: [   26.060000] br-lan: port 1(eth1) entered forwarding state
Thu Oct 13 14:20:09 2016 kern.info kernel: [   26.060000] br-lan: port 1(eth1) entered forwarding state
Thu Oct 13 14:20:09 2016 kern.info kernel: [   26.070000] IPv6: ADDRCONF(NETDEV_CHANGE): br-lan: link becomes ready
Thu Oct 13 14:20:09 2016 daemon.notice netifd: Bridge 'br-lan' link is up
Thu Oct 13 14:20:09 2016 daemon.notice netifd: Interface 'lan' has link connectivity
Thu Oct 13 14:20:09 2016 user.notice firewall: Reloading firewall due to ifup of lan (br-lan)
Thu Oct 13 14:20:10 2016 user.emerg syslog: setting up led USB
Thu Oct 13 14:20:10 2016 user.emerg syslog: setting up led WLAN
Thu Oct 13 14:20:10 2016 kern.info kernel: [   27.060000] eth0: link up (1000Mbps/Full duplex)
Thu Oct 13 14:20:10 2016 kern.info kernel: [   27.060000] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
Thu Oct 13 14:20:10 2016 daemon.notice netifd: Network device 'eth0' link is up
Thu Oct 13 14:20:10 2016 daemon.notice netifd: Interface 'wan' has link connectivity
Thu Oct 13 14:20:10 2016 daemon.notice netifd: Interface 'wan' is setting up now
Thu Oct 13 14:20:10 2016 daemon.notice netifd: Interface 'wan6' has link connectivity
Thu Oct 13 14:20:10 2016 daemon.notice netifd: Interface 'wan6' is setting up now
Thu Oct 13 14:20:10 2016 daemon.notice netifd: VLAN 'eth0.3' link is up
Thu Oct 13 14:20:10 2016 daemon.notice netifd: Interface 'vlan' has link connectivity
Thu Oct 13 14:20:10 2016 kern.info kernel: [   27.110000] IPv6: ADDRCONF(NETDEV_CHANGE): eth0.3: link becomes ready
Thu Oct 13 14:20:11 2016 daemon.notice netifd: wan (1721): udhcpc (v1.23.2) started
Thu Oct 13 14:20:11 2016 daemon.notice netifd: wan (1721): Sending discover...
Thu Oct 13 14:20:11 2016 daemon.notice netifd: wan (1721): Sending select for 192.168.1.194...
Thu Oct 13 14:20:11 2016 daemon.notice netifd: wan (1721): Lease of 192.168.1.194 obtained, lease time 60
Thu Oct 13 14:20:11 2016 daemon.notice netifd: Interface 'wan' is now up
Thu Oct 13 14:20:11 2016 kern.info kernel: [   28.060000] br-lan: port 1(eth1) entered forwarding state
Thu Oct 13 14:20:11 2016 daemon.info procd: - init complete -
Thu Oct 13 14:20:12 2016 kern.info kernel: [   29.060000] Atheros AR8216/AR8236/AR8316 ag71xx-mdio.0:00: Port 4 is up
Thu Oct 13 14:20:12 2016 kern.info kernel: [   29.060000] Atheros AR8216/AR8236/AR8316 ag71xx-mdio.0:00: Port 5 is up
Thu Oct 13 14:20:17 2016 daemon.info dnsmasq[1797]: started, version 2.73 cachesize 150
Thu Oct 13 14:20:17 2016 daemon.info dnsmasq[1797]: compile time options: IPv6 GNU-getopt no-DBus no-i18n no-IDN DHCP no-DHCPv6 no-Lua TFTP no-conntrack no-ipset no-auth no-DNSSEC loop-detect inotify
Thu Oct 13 14:20:17 2016 daemon.info dnsmasq[1797]: DNS service limited to local subnets
Thu Oct 13 14:20:17 2016 daemon.info dnsmasq-dhcp[1797]: DHCP, IP range 192.168.2.100 -- 192.168.2.249, lease time 12h
Thu Oct 13 14:20:17 2016 daemon.info dnsmasq-dhcp[1797]: DHCP, IP range 192.168.1.100 -- 192.168.1.249, lease time 12h
Thu Oct 13 14:20:17 2016 daemon.info dnsmasq[1797]: using local addresses only for domain lan
Thu Oct 13 14:20:17 2016 daemon.info dnsmasq[1797]: reading /tmp/resolv.conf.auto
Thu Oct 13 14:20:17 2016 daemon.info dnsmasq[1797]: using local addresses only for domain lan
Thu Oct 13 14:20:17 2016 daemon.info dnsmasq[1797]: using nameserver 8.8.8.8#53
Thu Oct 13 14:20:17 2016 daemon.warn dnsmasq[1797]: ignoring nameserver 192.168.1.1 - local interface
Thu Oct 13 14:20:17 2016 daemon.info dnsmasq[1797]: read /etc/hosts - 1 addresses
Thu Oct 13 14:20:17 2016 daemon.info dnsmasq[1797]: read /tmp/hosts/dhcp - 1 addresses
Thu Oct 13 14:20:17 2016 daemon.info dnsmasq-dhcp[1797]: read /etc/ethers - 0 addresses
Thu Oct 13 14:20:19 2016 daemon.info dnsmasq[1797]: exiting on receipt of SIGTERM
Thu Oct 13 14:20:19 2016 daemon.info dnsmasq[1900]: started, version 2.73 cachesize 150
Thu Oct 13 14:20:19 2016 daemon.info dnsmasq[1900]: compile time options: IPv6 GNU-getopt no-DBus no-i18n no-IDN DHCP no-DHCPv6 no-Lua TFTP no-conntrack no-ipset no-auth no-DNSSEC loop-detect inotify
Thu Oct 13 14:20:19 2016 daemon.info dnsmasq[1900]: DNS service limited to local subnets
Thu Oct 13 14:20:19 2016 daemon.info dnsmasq-dhcp[1900]: DHCP, IP range 192.168.2.100 -- 192.168.2.249, lease time 12h
Thu Oct 13 14:20:19 2016 daemon.info dnsmasq-dhcp[1900]: DHCP, IP range 192.168.1.100 -- 192.168.1.249, lease time 12h
Thu Oct 13 14:20:19 2016 daemon.info dnsmasq[1900]: using local addresses only for domain lan
Thu Oct 13 14:20:19 2016 daemon.info dnsmasq[1900]: reading /tmp/resolv.conf.auto
Thu Oct 13 14:20:19 2016 daemon.info dnsmasq[1900]: using local addresses only for domain lan
Thu Oct 13 14:20:19 2016 daemon.info dnsmasq[1900]: using nameserver 8.8.8.8#53
Thu Oct 13 14:20:19 2016 daemon.warn dnsmasq[1900]: ignoring nameserver 192.168.1.1 - local interface
Thu Oct 13 14:20:19 2016 daemon.info dnsmasq[1900]: read /etc/hosts - 1 addresses
Thu Oct 13 14:20:19 2016 daemon.info dnsmasq[1900]: read /tmp/hosts/dhcp - 1 addresses
Thu Oct 13 14:20:19 2016 daemon.info dnsmasq-dhcp[1900]: read /etc/ethers - 0 addresses
Thu Oct 13 14:20:19 2016 user.notice firewall: Reloading firewall due to ifup of vlan (eth0.3)
Thu Oct 13 14:20:21 2016 user.notice firewall: Reloading firewall due to ifup of wan (eth0)
Thu Oct 13 14:20:22 2016 daemon.info dnsmasq-dhcp[1900]: DHCPREQUEST(br-lan) 192.168.1.212 20:cf:30:bb:75:56
Thu Oct 13 14:20:22 2016 daemon.info dnsmasq-dhcp[1900]: DHCPACK(br-lan) 192.168.1.212 20:cf:30:bb:75:56 WDF6
Thu Oct 13 14:20:23 2016 user.notice ddns-scripts[2166]: myddns_ipv4: PID '2166' started at 2016-10-13 14:20
Thu Oct 13 14:20:24 2016 user.warn ddns-scripts[2166]: myddns_ipv4: Service section disabled! - TERMINATE
Thu Oct 13 14:20:24 2016 user.warn ddns-scripts[2166]: myddns_ipv4: PID '2166' exit WITH ERROR '1' at 2016-10-13 14:20
Thu Oct 13 14:20:39 2016 kern.notice kernel: [   55.300000] random: nonblocking pool is initialized
Thu Oct 13 14:20:41 2016 daemon.notice netifd: wan (1721): Sending renew...
Thu Oct 13 14:20:41 2016 daemon.notice netifd: wan (1721): Lease of 192.168.1.194 obtained, lease time 60
Thu Oct 13 14:31:59 2016 daemon.notice netifd: wan (1721): Sending renew...
Thu Oct 13 14:31:59 2016 daemon.notice netifd: wan (1721): Lease of 192.168.1.194 obtained, lease time 60
Thu Oct 13 14:32:08 2016 kern.info kernel: [   97.440000] nf_conntrack: automatic helper assignment is deprecated and it will be removed soon. Use the iptables CT target to attach helpers instead.
Thu Oct 13 14:32:29 2016 daemon.notice netifd: wan (1721): Sending renew...
Thu Oct 13 14:32:29 2016 daemon.notice netifd: wan (1721): Lease of 192.168.1.194 obtained, lease time 60
Thu Oct 13 14:32:59 2016 daemon.notice netifd: wan (1721): Sending renew...
Thu Oct 13 14:32:59 2016 daemon.notice netifd: wan (1721): Lease of 192.168.1.194 obtained, lease time 60
Thu Oct 13 14:33:29 2016 daemon.notice netifd: wan (1721): Sending renew...
Thu Oct 13 14:33:29 2016 daemon.notice netifd: wan (1721): Lease of 192.168.1.194 obtained, lease time 60
Thu Oct 13 14:33:37 2016 authpriv.info dropbear[3934]: Child connection from 192.168.1.212:56317
Thu Oct 13 14:33:44 2016 authpriv.notice dropbear[3934]: Password auth succeeded for 'root' from 192.168.1.212:56317
Thu Oct 13 14:34:00 2016 daemon.notice netifd: wan (1721): Sending renew...
Thu Oct 13 14:34:00 2016 daemon.notice netifd: wan (1721): Lease of 192.168.1.194 obtained, lease time 60
Thu Oct 13 14:34:30 2016 daemon.notice netifd: wan (1721): Sending renew...
Thu Oct 13 14:34:30 2016 daemon.notice netifd: wan (1721): Lease of 192.168.1.194 obtained, lease time 60
Thu Oct 13 14:35:00 2016 daemon.notice netifd: wan (1721): Sending renew...
Thu Oct 13 14:35:00 2016 daemon.notice netifd: wan (1721): Lease of 192.168.1.194 obtained, lease time 60
Thu Oct 13 14:35:30 2016 daemon.notice netifd: wan (1721): Sending renew...
Thu Oct 13 14:35:30 2016 daemon.notice netifd: wan (1721): Lease of 192.168.1.194 obtained, lease time 60
Thu Oct 13 14:36:00 2016 daemon.notice netifd: wan (1721): Sending renew...
Thu Oct 13 14:36:00 2016 daemon.notice netifd: wan (1721): Lease of 192.168.1.194 obtained, lease time 60
Thu Oct 13 14:36:30 2016 daemon.notice netifd: wan (1721): Sending renew...
Thu Oct 13 14:36:30 2016 daemon.notice netifd: wan (1721): Lease of 192.168.1.194 obtained, lease time 60
Thu Oct 13 14:37:00 2016 daemon.notice netifd: wan (1721): Sending renew...
Thu Oct 13 14:37:00 2016 daemon.notice netifd: wan (1721): Lease of 192.168.1.194 obtained, lease time 60
Thu Oct 13 14:37:30 2016 daemon.notice netifd: wan (1721): Sending renew...
Thu Oct 13 14:37:30 2016 daemon.notice netifd: wan (1721): Lease of 192.168.1.194 obtained, lease time 60

exeq17 · 2016-10-13 13:53:12

exeq17
Użytkownik
Nieaktywny

Zarejestrowany: 2016-10-13
Posty: 20

Odp: wykorzystanie vlanow do stworzenia dwoch sieci

Czy ten mój eth0.3 w portach ma mieć połączenie z portem 0 czyli z cpu? jedyne co moge ustawić to tagowane bo nietagowane już jest przy jednym z vlanów.

Cezary · 2016-10-13 13:53:33

Cezary
...
Nieaktywny

Skąd: Warszawa
Zarejestrowany: 2006-02-25
Posty: 116,322

Odp: wykorzystanie vlanow do stworzenia dwoch sieci

Wg niego jest i działa.

PS - na wan nie możesz mieć tej samej adresacji co na lan, nie będzie to działać.

Masz niepotrzebny router, uszkodzony czy nie - chętnie przygarnę go.

exeq17 · 2016-10-13 13:59:36

exeq17
Użytkownik
Nieaktywny

Zarejestrowany: 2016-10-13
Posty: 20

Odp: wykorzystanie vlanow do stworzenia dwoch sieci

Zmienilem adresacje sieci lan na 192.168.3.1, pewnie przestanie się gryźć z wanem. Gdy wpinam się na port 4 do tego vlana to dostaje dns'a od razu na 192.168.3.1 ale ip po pewnym czasie prywatne czyli 169... i nie wiem co dalej.

Cezary · 2016-10-13 14:01:23

Cezary
...
Nieaktywny

Skąd: Warszawa
Zarejestrowany: 2006-02-25
Posty: 116,322

Odp: wykorzystanie vlanow do stworzenia dwoch sieci

To samo - wepnij kabel, pokaż logi, zobaczymy co i komu przydzielił.

Masz niepotrzebny router, uszkodzony czy nie - chętnie przygarnę go.

exeq17 · 2016-10-13 14:10:28

exeq17
Użytkownik
Nieaktywny

Zarejestrowany: 2016-10-13
Posty: 20

Odp: wykorzystanie vlanow do stworzenia dwoch sieci

około godziny 15:08 podłączyłem dwa kompy jeden w jednego lana drugi w vlana:

AR8316 ag71xx-mdio.0:00: Port 4 is up
Thu Oct 13 14:57:26 2016 kern.info kernel: [  613.440000] Atheros AR8216/AR8236/AR8316 ag71xx-mdio.0:00: Port 4 is down
Thu Oct 13 14:57:36 2016 kern.info kernel: [  623.490000] Atheros AR8216/AR8236/AR8316 ag71xx-mdio.0:00: Port 1 is up
Thu Oct 13 14:57:42 2016 daemon.notice netifd: wan (1712): Sending renew...
Thu Oct 13 14:57:42 2016 daemon.notice netifd: wan (1712): Lease of 192.168.1.194 obtained, lease time 60
Thu Oct 13 14:57:50 2016 kern.info kernel: [  637.560000] Atheros AR8216/AR8236/AR8316 ag71xx-mdio.0:00: Port 1 is down
Thu Oct 13 14:57:51 2016 daemon.info dnsmasq-dhcp[3551]: DHCPREQUEST(br-lan) 192.168.3.212 20:cf:30:bb:75:56
Thu Oct 13 14:57:51 2016 daemon.info dnsmasq-dhcp[3551]: DHCPACK(br-lan) 192.168.3.212 20:cf:30:bb:75:56 WDF6
Thu Oct 13 14:57:52 2016 kern.info kernel: [  639.570000] Atheros AR8216/AR8236/AR8316 ag71xx-mdio.0:00: Port 4 is up
Thu Oct 13 14:58:12 2016 daemon.notice netifd: wan (1712): Sending renew...
Thu Oct 13 14:58:12 2016 daemon.notice netifd: wan (1712): Lease of 192.168.1.194 obtained, lease time 60
Thu Oct 13 14:58:42 2016 daemon.notice netifd: wan (1712): Sending renew...
Thu Oct 13 14:58:42 2016 daemon.notice netifd: wan (1712): Lease of 192.168.1.194 obtained, lease time 60
Thu Oct 13 14:59:12 2016 daemon.notice netifd: wan (1712): Sending renew...
Thu Oct 13 14:59:12 2016 daemon.notice netifd: wan (1712): Lease of 192.168.1.194 obtained, lease time 60
Thu Oct 13 14:59:42 2016 daemon.notice netifd: wan (1712): Sending renew...
Thu Oct 13 14:59:42 2016 daemon.notice netifd: wan (1712): Lease of 192.168.1.194 obtained, lease time 60
Thu Oct 13 15:00:12 2016 daemon.notice netifd: wan (1712): Sending renew...
Thu Oct 13 15:00:12 2016 daemon.notice netifd: wan (1712): Lease of 192.168.1.194 obtained, lease time 60
Thu Oct 13 15:00:42 2016 daemon.notice netifd: wan (1712): Sending renew...
Thu Oct 13 15:00:42 2016 daemon.notice netifd: wan (1712): Lease of 192.168.1.194 obtained, lease time 60
Thu Oct 13 15:01:12 2016 daemon.notice netifd: wan (1712): Sending renew...
Thu Oct 13 15:01:12 2016 daemon.notice netifd: wan (1712): Lease of 192.168.1.194 obtained, lease time 60
Thu Oct 13 15:01:42 2016 daemon.notice netifd: wan (1712): Sending renew...
Thu Oct 13 15:01:42 2016 daemon.notice netifd: wan (1712): Lease of 192.168.1.194 obtained, lease time 60
Thu Oct 13 15:02:12 2016 daemon.notice netifd: wan (1712): Sending renew...
Thu Oct 13 15:02:12 2016 daemon.notice netifd: wan (1712): Lease of 192.168.1.194 obtained, lease time 60
Thu Oct 13 15:02:42 2016 daemon.notice netifd: wan (1712): Sending renew...
Thu Oct 13 15:02:42 2016 daemon.notice netifd: wan (1712): Lease of 192.168.1.194 obtained, lease time 60
Thu Oct 13 15:03:12 2016 daemon.notice netifd: wan (1712): Sending renew...
Thu Oct 13 15:03:12 2016 daemon.notice netifd: wan (1712): Lease of 192.168.1.194 obtained, lease time 60
Thu Oct 13 15:03:42 2016 daemon.notice netifd: wan (1712): Sending renew...
Thu Oct 13 15:03:42 2016 daemon.notice netifd: wan (1712): Lease of 192.168.1.194 obtained, lease time 60
Thu Oct 13 15:04:12 2016 daemon.notice netifd: wan (1712): Sending renew...
Thu Oct 13 15:04:12 2016 daemon.notice netifd: wan (1712): Lease of 192.168.1.194 obtained, lease time 60
Thu Oct 13 15:04:43 2016 daemon.notice netifd: wan (1712): Sending renew...
Thu Oct 13 15:04:43 2016 daemon.notice netifd: wan (1712): Lease of 192.168.1.194 obtained, lease time 60
Thu Oct 13 15:05:12 2016 daemon.notice netifd: wan (1712): Sending renew...
Thu Oct 13 15:05:12 2016 daemon.notice netifd: wan (1712): Lease of 192.168.1.194 obtained, lease time 60
Thu Oct 13 15:05:42 2016 daemon.notice netifd: wan (1712): Sending renew...
Thu Oct 13 15:05:42 2016 daemon.notice netifd: wan (1712): Lease of 192.168.1.194 obtained, lease time 60
Thu Oct 13 15:06:12 2016 daemon.notice netifd: wan (1712): Sending renew...
Thu Oct 13 15:06:12 2016 daemon.notice netifd: wan (1712): Lease of 192.168.1.194 obtained, lease time 60
Thu Oct 13 15:06:42 2016 daemon.notice netifd: wan (1712): Sending renew...
Thu Oct 13 15:06:42 2016 daemon.notice netifd: wan (1712): Lease of 192.168.1.194 obtained, lease time 60
Thu Oct 13 15:07:12 2016 daemon.notice netifd: wan (1712): Sending renew...
Thu Oct 13 15:07:12 2016 daemon.notice netifd: wan (1712): Lease of 192.168.1.194 obtained, lease time 60
Thu Oct 13 15:07:42 2016 daemon.notice netifd: wan (1712): Sending renew...
Thu Oct 13 15:07:42 2016 daemon.notice netifd: wan (1712): Lease of 192.168.1.194 obtained, lease time 60
Thu Oct 13 15:07:57 2016 kern.info kernel: [ 1244.580000] Atheros AR8216/AR8236/AR8316 ag71xx-mdio.0:00: Port 1 is up
Thu Oct 13 15:08:01 2016 kern.info kernel: [ 1248.610000] Atheros AR8216/AR8236/AR8316 ag71xx-mdio.0:00: Port 1 is down
Thu Oct 13 15:08:03 2016 kern.info kernel: [ 1250.620000] Atheros AR8216/AR8236/AR8316 ag71xx-mdio.0:00: Port 1 is up
Thu Oct 13 15:08:12 2016 daemon.notice netifd: wan (1712): Sending renew...
Thu Oct 13 15:08:12 2016 daemon.notice netifd: wan (1712): Lease of 192.168.1.194 obtained, lease time 60
Thu Oct 13 15:08:42 2016 daemon.notice netifd: wan (1712): Sending renew...
Thu Oct 13 15:08:42 2016 daemon.notice netifd: wan (1712): Lease of 192.168.1.194 obtained, lease time 60
Thu Oct 13 15:08:43 2016 authpriv.info dropbear[2268]: Exit (root): Keepalive timeout
Thu Oct 13 15:08:55 2016 kern.info kernel: [ 1302.870000] Atheros AR8216/AR8236/AR8316 ag71xx-mdio.0:00: Port 1 is down
Thu Oct 13 15:08:57 2016 kern.info kernel: [ 1304.880000] Atheros AR8216/AR8236/AR8316 ag71xx-mdio.0:00: Port 1 is up
Thu Oct 13 15:08:59 2016 kern.info kernel: [ 1306.890000] Atheros AR8216/AR8236/AR8316 ag71xx-mdio.0:00: Port 1 is down
Thu Oct 13 15:09:01 2016 kern.info kernel: [ 1308.900000] Atheros AR8216/AR8236/AR8316 ag71xx-mdio.0:00: Port 1 is up
Thu Oct 13 15:09:12 2016 daemon.notice netifd: wan (1712): Sending renew...
Thu Oct 13 15:09:12 2016 daemon.notice netifd: wan (1712): Lease of 192.168.1.194 obtained, lease time 60
Thu Oct 13 15:09:19 2016 kern.info kernel: [ 1326.990000] Atheros AR8216/AR8236/AR8316 ag71xx-mdio.0:00: Port 1 is down
Thu Oct 13 15:09:32 2016 authpriv.info dropbear[6092]: Child connection from 192.168.3.212:56808
Thu Oct 13 15:09:41 2016 authpriv.notice dropbear[6092]: Password auth succeeded for 'root' from 192.168.3.212:56808
Thu Oct 13 15:09:43 2016 daemon.notice netifd: wan (1712): Sending renew...
Thu Oct 13 15:09:43 2016 daemon.notice netifd: wan (1712): Lease of 192.168.1.194 obtained, lease time 60

Cezary · 2016-10-13 14:18:45

Cezary
...
Nieaktywny

Skąd: Warszawa
Zarejestrowany: 2006-02-25
Posty: 116,322

Odp: wykorzystanie vlanow do stworzenia dwoch sieci

Po za tym że masz port up/down to nic tu nie ma w logu. Jesteś pewien tego kabla co go podłączasz?

Masz niepotrzebny router, uszkodzony czy nie - chętnie przygarnę go.

exeq17 · 2016-10-13 14:27:57

exeq17
Użytkownik
Nieaktywny

Zarejestrowany: 2016-10-13
Posty: 20

Odp: wykorzystanie vlanow do stworzenia dwoch sieci

Jestem pewny tego kabla pozatym sprawdzałem jeszcze na dwóch innych. Bardzo dziwnie to sie zachowuje, teraz 3 razy restartowałem router i na każdym z portów dostawałem prywatne ip mimo restartowania sieciówki itd. Zaraz koniec pracy, wezmę router do domu i będę walczył dalej. Może gargoyle wrzuce.. Pierwszy raz mam taki duży problem.

Graffy · 2016-10-13 14:59:56

Graffy
Użytkownik
Nieaktywny

Zarejestrowany: 2013-04-23
Posty: 310

Odp: wykorzystanie vlanow do stworzenia dwoch sieci

U mnie tworzy "br-lan2" dla "lan2" u Ciebie nie widzę tego.
Pokaż /etc/config/network, firewall, dhcp

APU2 @ OpenWrt 18.06-SNAPSHOT, r7852-7ac6044632

exeq17 · 2016-10-13 15:46:20

exeq17
Użytkownik
Nieaktywny

Zarejestrowany: 2016-10-13
Posty: 20

Odp: wykorzystanie vlanow do stworzenia dwoch sieci

network:

config interface 'loopback'
        option ifname 'lo'
        option proto 'static'
        option ipaddr '127.0.0.1'
        option netmask '255.0.0.0'

config globals 'globals'
        option ula_prefix 'fd6a:127c:3e9d::/48'

config interface 'lan'
        option ifname 'eth1'
        option force_link '1'
        option type 'bridge'
        option proto 'static'
        option ipaddr '192.168.1.1'
        option netmask '255.255.255.0'
        option ip6assign '60'

config interface 'wan'
        option ifname 'eth0'
        option proto 'dhcp'

config interface 'wan6'
        option ifname 'eth0'
        option proto 'dhcpv6'

config switch
        option name 'switch0'
        option reset '1'
        option enable_vlan '1'
        option mirror_source_port '0'
        option mirror_monitor_port '0'

config switch_vlan
        option device 'switch0'
        option vlan '1'
        option vid '1'
        option ports '0 2 3 4'

config switch_vlan
        option device 'switch0'
        option vlan '2'
        option ports '5 6'
        option vid '2'

config switch_vlan
        option device 'switch0'
        option vlan '3'
        option vid '3'
        option ports '0t 1'

config interface 'vlan'
        option proto 'static'
        option ifname 'eth0.3'
        option ipaddr '192.168.2.1'
        option netmask '255.255.255.0'

dhcp

config dnsmasq
        option domainneeded '1'
        option boguspriv '1'
        option filterwin2k '0'
        option localise_queries '1'
        option rebind_protection '1'
        option rebind_localhost '1'
        option local '/lan/'
        option domain 'lan'
        option expandhosts '1'
        option nonegcache '0'
        option authoritative '1'
        option readethers '1'
        option leasefile '/tmp/dhcp.leases'
        option resolvfile '/tmp/resolv.conf.auto'
        option localservice '1'
        list rebind_domain 'free.aero2.net.pl'

config dhcp 'lan'
        option interface 'lan'
        option start '100'
        option limit '150'
        option leasetime '12h'
        option dhcpv6 'server'
        option ra 'server'

config dhcp 'wan'
        option interface 'wan'
        option ignore '1'

config odhcpd 'odhcpd'
        option maindhcp '0'
        option leasefile '/tmp/hosts/odhcpd'
        option leasetrigger '/usr/sbin/odhcpd-update'

config dhcp 'vlan'
        option start '100'
        option leasetime '12h'
        option limit '150'
        option interface 'vlan'

firewal:

config defaults
        option syn_flood '1'
        option input 'ACCEPT'
        option output 'ACCEPT'
        option forward 'REJECT'

config zone
        option name 'lan'
        option input 'ACCEPT'
        option output 'ACCEPT'
        option forward 'ACCEPT'
        option network 'lan'

config zone
        option name 'wan'
        option input 'REJECT'
        option output 'ACCEPT'
        option forward 'REJECT'
        option masq '1'
        option mtu_fix '1'
        option network 'wan wan6'

config forwarding
        option src 'lan'
        option dest 'wan'

config rule
        option name 'Allow-DHCP-Renew'
        option src 'wan'
        option proto 'udp'
        option dest_port '68'
        option target 'ACCEPT'
        option family 'ipv4'

config rule
        option name 'Allow-Ping'
        option src 'wan'
        option proto 'icmp'
        option icmp_type 'echo-request'
        option family 'ipv4'
        option target 'ACCEPT'

config rule
        option name 'Allow-IGMP'
        option src 'wan'
        option proto 'igmp'
        option family 'ipv4'
        option target 'ACCEPT'

config rule
        option name 'Allow-DHCPv6'
        option src 'wan'
        option proto 'udp'
        option src_ip 'fe80::/10'
        option src_port '547'
        option dest_ip 'fe80::/10'
        option dest_port '546'
        option family 'ipv6'
        option target 'ACCEPT'

config rule
        option name 'Allow-MLD'
        option src 'wan'
        option proto 'icmp'
        option src_ip 'fe80::/10'
        list icmp_type '130/0'
        list icmp_type '131/0'
        list icmp_type '132/0'
        list icmp_type '143/0'
        option family 'ipv6'
        option target 'ACCEPT'

config rule
        option name 'Allow-ICMPv6-Input'
        option src 'wan'
        option proto 'icmp'
        list icmp_type 'echo-request'
        list icmp_type 'echo-reply'
        list icmp_type 'destination-unreachable'
        list icmp_type 'packet-too-big'
        list icmp_type 'time-exceeded'
        list icmp_type 'bad-header'
        list icmp_type 'unknown-header-type'
        list icmp_type 'router-solicitation'
        list icmp_type 'neighbour-solicitation'
        list icmp_type 'router-advertisement'
        list icmp_type 'neighbour-advertisement'
        option limit '1000/sec'
        option family 'ipv6'
        option target 'ACCEPT'

config rule
        option name 'Allow-ICMPv6-Forward'
        option src 'wan'
        option dest '*'
        option proto 'icmp'
        list icmp_type 'echo-request'
        list icmp_type 'echo-reply'
        list icmp_type 'destination-unreachable'
        list icmp_type 'packet-too-big'
        list icmp_type 'time-exceeded'
        list icmp_type 'bad-header'
        list icmp_type 'unknown-header-type'
        option limit '1000/sec'
        option family 'ipv6'
        option target 'ACCEPT'
config include
        option path '/etc/firewall.user'

config rule
        option src 'wan'
        option dest 'lan'
        option proto 'esp'
        option target 'ACCEPT'

config rule
        option src 'wan'
        option dest 'lan'
        option dest_port '500'
        option proto 'udp'
        option target 'ACCEPT'

config zone
        option name 'vlan'
        option input 'ACCEPT'
        option forward 'REJECT'
        option output 'ACCEPT'
        option network 'vlan'

config forwarding
        option dest 'wan'
        option src 'vlan'

mar_w · 2016-10-13 16:12:06

mar_w
Użytkownik
Nieaktywny

Zarejestrowany: 2014-08-16
Posty: 2,127

Odp: wykorzystanie vlanow do stworzenia dwoch sieci

jakoś nie widać żebyś zmienił adresację na lanie tak jak pisałeś w poście #8

config interface 'lan'
        option ifname 'eth1'
        option force_link '1'
        option type 'bridge'
        option proto 'static'
        option ipaddr '192.168.1.1'

Xiaomi AX3000T @ Netgear R6220
* DVBT2 - T230C *

exeq17 · 2016-10-13 16:19:30

exeq17
Użytkownik
Nieaktywny

Zarejestrowany: 2016-10-13
Posty: 20

Odp: wykorzystanie vlanow do stworzenia dwoch sieci

Przywróciłem z backupu ustawienia. Aktualnie WANA mam odłączonego. Skupiam się na uzyskaniu adresu ip z 192.168.2.x i nie potrafie tego uzyskać.

mar_w · 2016-10-13 17:27:32

mar_w
Użytkownik
Nieaktywny

Zarejestrowany: 2014-08-16
Posty: 2,127

Odp: wykorzystanie vlanow do stworzenia dwoch sieci

skoro u Ciebie WAN to eth0 a LAN to eth1 to jakim cudem vlan3 wybrałeś eth0.3 zamiast eth1.3

Xiaomi AX3000T @ Netgear R6220
* DVBT2 - T230C *

Cezary · 2016-10-13 17:33:22

Cezary
...
Nieaktywny

Skąd: Warszawa
Zarejestrowany: 2006-02-25
Posty: 116,322

Odp: wykorzystanie vlanow do stworzenia dwoch sieci

Dobry strzał. Lan jest eth1 i to z niego się wydziela port.

Masz niepotrzebny router, uszkodzony czy nie - chętnie przygarnę go.

exeq17 · 2016-10-14 07:25:22

exeq17
Użytkownik
Nieaktywny

Zarejestrowany: 2016-10-13
Posty: 20

Odp: wykorzystanie vlanow do stworzenia dwoch sieci

Zmieniłem na tej konfiguracji z eth0.3 na eth1.3 i poprostu zaczeło działać. Dziwne bo wcześniej na troche innej konfiguracji zmieniałem to samo i nie poszło - zmieniałem numerek pod lan. W każdym razie dziękuje wszystkim i mar_w za pomoc.

Graffy · 2016-10-14 07:32:26

Graffy
Użytkownik
Nieaktywny

Zarejestrowany: 2013-04-23
Posty: 310

Odp: wykorzystanie vlanow do stworzenia dwoch sieci

Jak dobrze zauważył @mar_w

network

config interface 'vlan'
        option proto 'static'
        option type 'bridge'
        option ifname 'eth1.3'
        option ipaddr '192.168.2.1'
        option netmask '255.255.255.0'

firewall

config zone
        option name 'vlan'
        option network 'vlan'
        option input 'REJECT'
        option output 'ACCEPT'
        option forward 'REJECT'

config rule
        option name 'VLAN DNS'
        option src 'vlan'
        option dest_port '53'
        option proto 'tcpudp'
        option target 'ACCEPT'
        option family 'ipv4'

config rule
        option name 'VLAN DHCP'
        option src 'vlan'
        option src_port '67-68'
        option dest_port '67-68'
        option proto 'udp'
        option target 'ACCEPT'
        option family 'ipv4'

APU2 @ OpenWrt 18.06-SNAPSHOT, r7852-7ac6044632

FAQ o OpenWrt | Sprzedam różne routery | Oddam

wykorzystanie vlanow do stworzenia dwoch sieci

Posty: 20

1 Temat przez exeq17 2016-10-13 12:30:33

Temat: wykorzystanie vlanow do stworzenia dwoch sieci

2 Odpowiedź przez Cezary 2016-10-13 12:37:24

Odp: wykorzystanie vlanow do stworzenia dwoch sieci

3 Odpowiedź przez exeq17 2016-10-13 13:25:39

Odp: wykorzystanie vlanow do stworzenia dwoch sieci

4 Odpowiedź przez Cezary 2016-10-13 13:35:30

Odp: wykorzystanie vlanow do stworzenia dwoch sieci

5 Odpowiedź przez exeq17 2016-10-13 13:39:27

Odp: wykorzystanie vlanow do stworzenia dwoch sieci

6 Odpowiedź przez exeq17 2016-10-13 13:53:12

Odp: wykorzystanie vlanow do stworzenia dwoch sieci

7 Odpowiedź przez Cezary 2016-10-13 13:53:33

Odp: wykorzystanie vlanow do stworzenia dwoch sieci

8 Odpowiedź przez exeq17 2016-10-13 13:59:36

Odp: wykorzystanie vlanow do stworzenia dwoch sieci

9 Odpowiedź przez Cezary 2016-10-13 14:01:23

Odp: wykorzystanie vlanow do stworzenia dwoch sieci

10 Odpowiedź przez exeq17 2016-10-13 14:10:28

Odp: wykorzystanie vlanow do stworzenia dwoch sieci

11 Odpowiedź przez Cezary 2016-10-13 14:18:45

Odp: wykorzystanie vlanow do stworzenia dwoch sieci

12 Odpowiedź przez exeq17 2016-10-13 14:27:57

Odp: wykorzystanie vlanow do stworzenia dwoch sieci

13 Odpowiedź przez Graffy 2016-10-13 14:59:56

Odp: wykorzystanie vlanow do stworzenia dwoch sieci

14 Odpowiedź przez exeq17 2016-10-13 15:46:20

Odp: wykorzystanie vlanow do stworzenia dwoch sieci

15 Odpowiedź przez mar_w 2016-10-13 16:12:06

Odp: wykorzystanie vlanow do stworzenia dwoch sieci

16 Odpowiedź przez exeq17 2016-10-13 16:19:30

Odp: wykorzystanie vlanow do stworzenia dwoch sieci

17 Odpowiedź przez mar_w 2016-10-13 17:27:32

Odp: wykorzystanie vlanow do stworzenia dwoch sieci

18 Odpowiedź przez Cezary 2016-10-13 17:33:22

Odp: wykorzystanie vlanow do stworzenia dwoch sieci

19 Odpowiedź przez exeq17 2016-10-14 07:25:22

Odp: wykorzystanie vlanow do stworzenia dwoch sieci

20 Odpowiedź przez Graffy 2016-10-14 07:32:26 (edytowany przez Graffy 2016-10-14 07:33:01)

Odp: wykorzystanie vlanow do stworzenia dwoch sieci

Posty: 20