Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.


Messages - Paul Zanna

Pages: [1] 2 3 ... 21
1
Zodiac FX General / Re: Zodiak FX sends wrong packets
« on: April 22, 2019, 02:45:45 PM »
Hi Sebastian,

Do you have a particular test that I can run to help recreate this issue?

Regards,
Paul

2
Zodiac WX General / Firmware update v1.30
« on: March 19, 2019, 09:35:52 AM »
A new version (v1.30) of the Zodiac WX firmware is now available for download.

v1.30 Build 20190128_2

The following changes are included in this update:

- Update to OpenvSwitch v2.10 (includes support for meters)
- Update to Linux kernel 4.9.120

Please note as of firmware version 1.20 the Zodiac WX OpenFlow functions have now been replaced by Open vSwitch. The main reason for the change was to allow the maximum stability and compatibility with OpenFlow controllers.

The OpenFlow configuration settings are now in the rc.local start script which you can find in System->Startup menu. The only updates you should have to make are for your OpenFlow controller IP address and port. Remember to save & apply the settings and then restart. If you make a change that causes a configuration issue and can no longer connect to the device, press and hold the reset button underneath the device for 20 seconds and then release and it will restart.

NOTE: As the OVS config runs as the last part of the boot process any changes made to the running network config will not apply until a restart. So, for example, if you change the LAN IP address you will lose connectivity and need to restart. This happens because when OpenWRT reconfigures the interface and in doing so removes it from the OVS bridge which makes it unusable until the startup script runs and it is added back again. I'm currently looking into ways to make this more seamless, hopefully using NETIFD.

Also, please note that as this is a significant change to the settings you MUST reset them (uncheck keep settings) during the upgrade to ensure you have a default configuration.

Please post issues or questions related to this update within this thread.

Regards,
Paul

3
Zodiac FX General / Re: Zodiac FX closing TCP sesions to ODL
« on: December 21, 2018, 07:16:59 AM »
The Zodiac FX polls the controller at regular intervals to check it is still there, if it doesn't respond after a number of attempts it reconnects. Check the Wireshark log and see if the controller is responding to these messages.

Regards,
Paul

4
Zodiac FX General / Re: Zodiac FX with multiple subnets
« on: December 21, 2018, 07:12:35 AM »
Hi,

The Zodiac FX has to have an IP address on the same subnet as the controller to connect, the same as any 2 IP devices that need to talk to each other. The hosts can be on any subnet, their connectivity to each other is separate from the controller.

Regards,
Paul

5
Zodiac FX General / Re: No match on ICMPv6 packets
« on: December 21, 2018, 07:07:22 AM »
Hi Thomas,

The Zodiac FX doesn't support matching on IPv6 packets.

Regards,
Paul

6
Zodiac FX General / Re: Zodiac fx interfacing Issue
« on: December 09, 2018, 11:24:09 AM »
Hi Hamza,

There are a number of articles in our Knowledge Base on connecting to the Zodiac FX that may help - https://northboundnetworks.freshdesk.com/support/solutions/35000113092

Regards,
Paul

7
Zodiac GX General / Re: DHCP Server!
« on: October 18, 2018, 09:26:06 AM »
The only way would be to add the DHCP server package (dnsmasq) to the build config and recompile the firmware. It wasn't included because it is running as a switch as opposed to a router.

Regards,
Paul

8
Zodiac FX General / Re: Adding Meter Entries/QoS
« on: October 18, 2018, 09:11:45 AM »
Yes, meters are in the current firmware.

Regards,
Paul

9
Zodiac GX Firmware / Re: .bin file development
« on: September 24, 2018, 04:06:35 PM »
Hi Kursat,

The CPU in the Zodiac GX is a MT7621A. Unfortunately, it doesn't have a usable JTAG connector so you can't use a hardware debugger like the Zodiac FX but it does run Linux so all the standard Linux debugging tools are available.

Regards,
Paul

10
Hi,

Can you please turn on debugging via the serial console (trace command in the debug context) to see if that provides any additional information.

Regards,
Paul

11
Zodiac GX General / Firmware Update: v1.10
« on: September 11, 2018, 11:40:58 AM »
A new version (v1.10) of the Zodiac GX firmware is now available for download.

Zodiac_GX_v1_10_20180908_2.bin

Zodiac GX source code on GitHub

The following changes are included in this update:

Added: Updated OpenWRT build to v18.06.1 (Linux kernel 4.14.63).
Added: Updated Open vSwitch to v2.10.0.

Please post issues or questions related to this update within this thread.

Regards,
Paul

12
Zodiac GX General / Re: Meter Support for the GX
« on: September 08, 2018, 04:51:57 PM »
The current GX firmware (v1.01) is based on OVS 2.5 which doesn't support meters in the kernel module. The next firmware release (v1.10) which is using OVS 2.10.0 does support meters and should be available in the next couple of days if all goes well with testing.

Regards,
Paul   

13
Zodiac GX General / Firmware Update: v1.01
« on: August 26, 2018, 03:21:25 PM »
A new version (v1.01) of the Zodiac GX firmware is now available for download.

Zodiac_GX_v1_01_20180825_1.bin

Zodiac GX source code on GitHub

The following changes are included in this update:

Fixed: OVS was reporting the incorrect port speed to OpenFlow controllers.
Added: Support for SSL OpenFlow controller connections.

Please post issues or questions related to this update within this thread.

Regards,
Paul

14
Zodiac GX General / Latest versions of source code and firmware.
« on: August 26, 2018, 08:34:57 AM »
Firmware: Zodiac_GX_v1_10_20180908_2
MD5: 31f17dc16a8bb04c8df63d141b34324b
SHA256: d816448c211b45877e06182c7e02217618b7728b819ad363f57eb8df61aabc86

Release Notes: Firmware update v1.10

Source Code: Zodiac GX on Github

Knowledge Base: Zodiac GX Knowledge base

15
Zodiac FX General / Re: Default action in OpenFlow 1.3
« on: July 17, 2018, 06:35:25 AM »
The default action for non-matching packets is different based on the OpenFlow version. In the OpenFlow 1.0 specification it states "If no matching entry can be found for a packet, the packet is sent to the controller over the secure channel.", however in the OpenFlow 1.3 spec it is "If the table-miss flow entry does not exist, by default packets unmatched by flow entries are dropped". A table-miss entry is basically a match everything flow and a lot of OpenFlow applications will use this to sent unknown packets to the controller, similar to what 1.0 would do by default.

Regards,
Paul 

Pages: [1] 2 3 ... 21