VPN LAN-Client bridging wont connect, can’t ping

Home Page Forums Network Management ZeroShell VPN LAN-Client bridging wont connect, can’t ping

This topic contains 0 replies, has 0 voices, and was last updated by  PeteCA 8 years, 3 months ago.

Viewing 2 posts - 1 through 2 (of 2 total)
  • Author
    Posts
  • #42947

    PeteCA
    Member

    Can anyone help me with this.

    If previous post isconfusing, i am sorry

    Love the way Zeroshell works, great product.

    i am currently trying to use Zeroshell Release 1.0.beta14

    Have the system up and running

    *****
    Need to have bridge mode working, to be able to access PLC’s and Equipment from remote location.

    the protocol used are non-routable, thus the reason for Bridging.
    *****

    Test Scenario

    Home LAN 192.168.1.0 , second network 192.168.0.0

    Zeroshell eth0 is at 192.168.1.99 192.168.1.99

    Eth1 192.168.1.25

    would line to browse with \XXXX from 192.168.0.x network to the 192.168.1.0 network

    second router is Wan port 192.167.1.25 and lan is on 192.168.0.0 network

    PC is connected to 192.168.0.0

    Using OPENVPN client

    P3 933 512mb 60gHd
    onboard Elink 100bt ETH00
    add in Elink 1000b ETH01

    How the test setup was executed

    Router/gateway/firewall

    Lan subnet 192.168.1.0/24

    After boot

    Changed ip on ETH00 to 192.168.1.99 from 192.168.0.75

    Connect to Zeroshell with PC1 on same subnet

    create VPN00 on port 1195 with remote Peer 192.168.1.202 no compression or encryption

    create BRIDGE00 and add ETH01,VPN00

    From console

    ifconfig ETH01 0.0.0.0 promisc up

    ifconfig VPN00 0.0.0.0 promisc up

    from WEB interface

    set BRIDGE00 to DHCP , ip is 192.168.1.25 permanent reserved from ADSL router

    From PC2 connected through another router in DMZ of other router with subnet 192.168.0.x/24

    using OpenVPN gui

    Config
    #============================================================================#
    remote 192.168.1.25
    port 1195
    proto udp

    #auth-user-pass
    #ca CA.pem
    ;cert client.pem
    ;key client.pem
    #secret PreKey.txt
    #============================================================================#
    # You should not need to change these settings. #
    #============================================================================#
    #comp-lzo
    verb 3
    mute 20
    resolv-retry infinite
    nobind
    #client
    dev tap
    #persist-key
    #persist-tap
    tun-mtu 1500
    ping 10
    ifconfig 192.168.1.202 192.168.1.201
    #ifconfig-nowarn

    Log file
    Mon Apr 11 17:53:50 2011 OpenVPN 2.1.4 i686-pc-mingw32 [SSL] [LZO2] [PKCS11] built on Nov 8 2010
    Mon Apr 11 17:53:50 2011 WARNING: –ping should normally be used with –ping-restart or –ping-exit
    Mon Apr 11 17:53:50 2011 NOTE: OpenVPN 2.1 requires ‘–script-security 2’ or higher to call user-defined

    scripts or executables
    Mon Apr 11 17:53:50 2011 ******* WARNING *******: all encryption and authentication features disabled —

    all data will be tunnelled as cleartext
    Mon Apr 11 17:53:50 2011 Socket Buffers: R=[8192->8192] S=[8192->8192]
    Mon Apr 11 17:53:50 2011 WARNING: Since you are using –dev tap, the second argument to –ifconfig must

    be a netmask, for example something like 255.255.255.0. (silence this warning with –ifconfig-nowarn)
    Mon Apr 11 17:53:50 2011 TAP-WIN32 device [Local Area Connection 2] opened: \.Global{18FB63C6-3D3F-

    4361-A106-74165561E6BB}.tap
    Mon Apr 11 17:53:50 2011 TAP-Win32 Driver Version 9.7
    Mon Apr 11 17:53:50 2011 TAP-Win32 MTU=1500
    Mon Apr 11 17:53:50 2011 Notified TAP-Win32 driver to set a DHCP IP/netmask of

    192.168.1.202/192.168.1.201 on interface {18FB63C6-3D3F-4361-A106-74165561E6BB} [DHCP-serv:

    192.168.1.200, lease-time: 31536000]
    Mon Apr 11 17:53:50 2011 Successful ARP Flush on interface [35] {18FB63C6-3D3F-4361-A106-74165561E6BB}
    Mon Apr 11 17:53:50 2011 Data Channel MTU parms [ L:1532 D:1450 EF:0 EB:4 ET:32 EL:0 ]
    Mon Apr 11 17:53:50 2011 Local Options hash (VER=V4): ‘4e19d666’
    Mon Apr 11 17:53:50 2011 Expected Remote Options hash (VER=V4): ‘4e19d666’
    Mon Apr 11 17:53:50 2011 UDPv4 link local: [undef]
    Mon Apr 11 17:53:50 2011 UDPv4 link remote: 192.168.1.25:1195

    Note: VPN99 Routing mode works great in Test scenario on port 1194

    Thanks in advance

    Pierre

    #51691

    PeteCA
    Member

    found a solution. Using another distribution.
    Built from scratch, configured and working.
    could not get Zeroshell to connect the bridge.
    And needed a solution
    Pierre

Viewing 2 posts - 1 through 2 (of 2 total)

You must be logged in to reply to this topic.