Difference: AMC13DebugLog (162 vs. 163)

Revision 16301 Nov 2016 - DanielGastler

Line: 1 to 1
Please log AMC13 test activity below, blog style (new entries at top)

2016-11-01, Gastler

The MCH issues seem to be the netmask on the MCH.

Packets sent to them from outside the 192.168.1.* network are received, but can't be routed back since the netmask is 24.

Modified the netmask to 16 on the vadatech MCH and things are working again.

The modification was in /etc/rc.d/rc.conf.

The NAT MCH seems to have a bug in it that keeps it from correctly using the (16) netmask correctly.

Due to this, you can only talk to it via a 192.168.1.* addressed machine (cms2, cms3, cms4)


2016-10-31, hazen

Can't access any microTCA stuff. Pings to MCH go unanswered.

This site is powered by the TWiki collaboration platform Powered by PerlCopyright © 2008-2022 by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
Ideas, requests, problems regarding TWiki? Send feedback